gpduck / WDSiPXE

Current Status:

WDSiPXE is a web application that generates customized answer files for OS builds over HTTP (in particular Linux and ESXi over iPXE). This is accomplished by merging templates with information from a device repository. The currently supported device repositories are WDS Standalone and MDT Database (Active Directory support is planned).

Quick Start

1. Install the ASP.Net Core 2.1 Runtime Hosting Bundle from https://dotnet.microsoft.com/download/dotnet-core/2.1
2. Download the latest Zip file from the releases page and extract to a web application in IIS.

Urls

http://example.com/{TemplateFolder}/{DeviceID}?Template={TemplateName}

TemplateFolder

The folder under Views to locate the template in.

DeviceID

The value used to locate the device in the repository. Generally the device's MAC address, but check the documentation for the provider you plan on using to see what key values are suppored.

Template

The name of the template file to merge for the device. This file should be located at /Views/{TemplateFolder}/{Template}.cshtml

http://example.com/kickstart/001122334455?Template=rh8

TemplateFolder

The folder under Views to locate the template in.

DeviceID

The value used to locate the device in the repository. Generally the device's MAC address, but check the documentation for the provider you plan on using to see what key values are suppored.

TemplateProperty

The name of a property in the device repository that will have the value of the template name. The device will be located by the DeviceID, then the template will be located by the device's TemplateProperty value. The template file should be located at /Views/{TemplateFolder}/{Device.TemplateProperty}.cshtml

http://example.com/kickstart/001122334455?TemplateProperty=OperatingSystemVersion

DeviceID

The value used to locate the device in the repository. Generally the device's MAC address, but check the documentation for the provider you plan on using to see what key values are suppored.

Device Repositories

Active Directory

Active Directory support is planned for a future release.

MDT Database

AppSettings

Name	Mandatory	Default	Value
DeviceRepository	True		"MDT"

ConnectionStrings

Name	Mandatory	Default	Value
MDT	True		The SQL connection string to your MDT database. You can provide a username/password for SQL authentication or use the AppPool account with Windows authentication.

Device Lookup

Device lookup is currently hard coded to use the MacAddress field in the MDT database. Use ${net0/mac} in your iPXE script or DHCP option 67 to pass the device's MAC address to you WDSiPXE site.

WDS (Standalone)

AppSettings

Name	Mandatory	Default	Value
DeviceRepository	True		"WDS"
WDS.RemoteInstallPath	False	(registry)	The path to the RemoteInst folder of WDS. If this is a network path the AppPool user will be used to access the remote share. Ex: c:\RemoteInstall