Windows Deployment Services filter provider sample
Demonstrates how to create a custom PXE provider DLL that can replace or run in conjunction with the standard WDSDCPXE PXE provider on a Windows Deployment Services (WDS) server.
Windows Deployment Services (WDS) enables the deployment of Windows operating systems. You can use WDS to set up new clients with a network-based installation without requiring that administrators visit each computer or install directly from CD or DVD media. The PXE Server contains the core networking capability of the server solution. The PXE Server supports a plug-in interface. Plug-ins are also known as "PXE Providers". This provider model allows for custom PXE solutions to be developed while leveraging the same core PXE Server networking code base.
- Plug-ins known as "PXE Providers" enable you to develop custom solutions that use the core networking code base of the WDS PXE Server implementation. This sample consists of a filter provider that illustrates how to create an additional PXE Provider that sits before BINL, or any other PXE Provider, in the ordered provider list.
- A filter provider acts as a gate before the WDSDCPXE or another PXE provider and controls whether or not a client will be serviced by the next provider in the provider list. If you would like your provider to always have the first opportunity to answer an incoming PXE request, you should place it first in the list.
- This filter provider sample stores data in a text file rather than in Active Directory.
A simple walkthrough for using the sample filter provider consists of the following. First, compile the sample code into a DLL. Second, create an .ini file. Third, register the sample provider as first in the ordered provider list. Fourth, boot a sample client using PXE. Any requests not filtered by the sample provider will then be passed to the next registered provider in the ordered list.
When you download this sample you will also receive a README.txt file.
Related topics
Using the Windows Deployment Services Server API
Windows Deployment Services image enumeration sample
Windows Deployment Services provider sample
Windows Deployment Services transport manager sample
Operating system requirements
Client
None supported
Server
Windows Server 2012 R2
Build the sample
- Start Visual Studio and select File > Open > Project/Solution.
- Go to the directory named for the sample, and double-click the Microsoft Visual Studio Solution (.sln) file titled FilterProv.sln.
- Press F7 (or F6 for Visual Studio 2013) or use Build > Build Solution to build the sample.
Run the sample
To debug the app and then run it, press F5 or use Debug > Start Debugging. To run the app without debugging, press Ctrl+F5 or use Debug > Start Without Debugging.
For detailed information on how to run the Windows Deployment Services PXE filter provider sample see the Readme.txt file provided with this sample.
Windows Deployment Services (WDS) enables the deployment of Windows operating systems using a network-based installation. You also need the following to complete this sample.
- Install the Windows Deployment Services server role on Windows Server 2012 R2.
- Initialize the Windows Deployment Services server.
- Add a boot image (Boot.wim) to the server. This is a Windows PE image that a client computer can boot into to install the operating system. The boot image (Boot.wim) can be found on the Windows product DVD.