WDS unattend file(s) for LTSC 2019

[mrstrong]

Hi,

 

experimenting with WDS: would anyone be able to post a working unattend file for deploying LTSC 2019 ?

 

Also a bit confused as to if I need two unattend files? e.g. you can specify an unattend in the server properties (client tab)

but also you can specify an unattend file for each image (right click on image, select properties)?!

[BKGarry]

@mrstrong I would highly recommend that you download the Microsoft Deployment Toolkit. (MDT)

 

You will need some aspects of the ADK installed but it will make your life a hell of a lot easier, you used WDS to boot and then MDT does all the installations and the Unattended files for you. It is free and can run on your WDS server, as it uses a network share and a MMC for it's part and makes boot ISOs for booting from WDS

[mavhc]

MDT seems more useful if you want different machines imaged in different ways. I used https://www.windowsafg.com/ but if you're just using WDS watch out the UEFI booting = computer AD account has deny permissions weirdness.

[mrstrong]

thanks for replies,

 

I do know a bit about MDT but would also like to able to setup WDS working as well as it is a lot easier to set up quickly.

 

I had found https://www.windowsafg.com/ also, @mavhc are you saying there's issues using their windows 10 UEFI ?

So use windows 10 MBR (with CSM in bios on)?

 

Also what about my orig question, i.e. are two unattend files necessary for WDS ?

I'm tempted to just try one unattend file associated with the image.

Maybe the other unattend file is for any global WDS settings you want for all images ?

[mavhc]

You may want one for the server itself, under server>properties>client, that automates the setup program, picks an image if you wish, formats the disk. Then each image has an unattend file.

 

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc730695(v=ws.10)

 

https://serverfault.com/a/798591 for the UEFI issue, not sure if they ever fixed it. More abandoned MS tech. If only we could pay for people to work on the features we want instead of a generic bucket of money....

[Duke5A]

I've got WDS working with UEFI and BIOS booting. If you have any trouble, let me know and I can post my DHCP configuration and answer files. As stated though, MDT might be a better solution if you're starting from scratch.

[mrstrong]

I've got WDS working with UEFI and BIOS booting. If you have any trouble, let me know and I can post my DHCP configuration and answer files. As stated though, MDT might be a better solution if you're starting from scratch.

 

thanks, I'm moving back to MDT now, did manage to get WDS working partly the way I had it was with 3 unattend files, one for the image with the oobe stuff etc and

then two in the server properties (one for UEFI and one for BIOS) these two do the wipe disk and partition.

 

In WDS managing the drivers seemed a bit limited and domain join / naming PC also tricky so like I said going back to MDT for now.