Set up the server OS and install the WDS role.
Go through the initial set up process. You need to take the d:sourcesboot.wim file from a Windows installation disc to create the boot image.
There are some other steps that I can’t remember.
Once that’s done, you have to right click the server name in the WDS console, Properties, Advanced, and register the DHCP server in Active Directory.
To slipstream network drivers, download and extract the driver file so you get the .inf.
Right click Drivers in the left pane, Add Driver Package…, then find the inf file. You can add to a driver group, doesn’t really matter.
Then, go to the Boot Images, right click your boot image, click Add Driver Packages to Image, then click the Search for Packages button. Find the driver in the lower pane, click next and stuff. Then that’s done.
That’s the setup image done. To create a capture image, right click the boot image, click Create Capture Image, then in the path box, type a new path. It should be in the c:remoteinstallimages etc…folder, same as the existing boot.wim that has been created, but give it a new name (capture.wim).
If the capture file fails to boot, error 0xc000000f in winload.exe, then mount the WIM on the server and commit the changes as detailed below.
Mount the WIM file with the command
dism /mount-wim /wimfile:<path to capture WIM> /mountdir:<create a temporary directory first> /index:1
Unmount the WIM file, committing changes (even though you didn’t make any) with the command
dism /unmount-wim /mountdir:<temp path> /commit
60% of the time, it works every time. Actually, it has worked 2 out of 2 times for me. Why they have this stupid problem, I don’t know, but they do.
Once you’ve created the capture image, create an Install Image group. Boot to the capture image, connect to the server and choose image group, then specify a local drive where the image can be saved. I used an external hard drive.