Deploying Windows 10 with MDT/WDS - Fully Unattended

[Zoom7000]

So, following on from our flooding disaster, I've decided in the interim to migrate everyone on to our admin domain. The domain controller previously only served about 7 people (it's a legacy setup) and the server also doubles up as a SIMS server. I've created the users in AD and run some tests. However, the stumbling block I've come across is the PCs on CC4. No matter what I try, I can't get the PCs off the CC4 domain. I've logged in as the local built-in administrator on the PC, tried the cached profile for the (now defunct) domain administrator and I just keep getting a message saying the PC cannot be removed from the domain. The reason is: Access is Denied. Anyway, I've decided that the cleanest method (given the 85+ lingering RM CC4 agents and tools still on the PC probably causing havoc looking for a CC4 server) would probably be to rebuild all of the PCs as Windows 10 clients on the remaining server. I've installed WDS and MDT on to the server and the PCs are PXE booting and picking up images.

 

What I'd like to know, is there a way to make the installation fully unattended. I've followed the Technet guide on configuring the image with MDT. I've integrated Office 2016 in to the build too. Configured the CustomSettings.ini with the domain admin credentials to join the domain too. However, once I'm in the Lite Touch PE, I still get loads of prompts before hand. E.g. I've set the task sequences to install Office 2016, however, the build gives a window and asks for the application to be marked in the checkbox if I want to install it. Can it be pre-ticked?

 

I've also set the local administrator password in the answer file, but once it tries to log in to Windows to continue the build process, it fails saying incorrect password and then I have to type it in manually. It then also fails to join the domain.

 

I'm not sure what I could be doing wrong here, but is there a definitive guide on how it's done? Has anyone else successfully deployed Windows 10 with some base applications? How did you manage it?

[snagrat]

This shows the variables you can put into your cs.ini to skip a lot of the initial questions https://blogs.technet.microsoft.com/chuck_kiessling/2013/02/05/mdt-2012-customsettings-ini-switches/

 

You can add Office install to the task sequence using an Install Application step. This will then install regardless if the box is ticked or not.

 

On our setups everything is automated except for selecting the TS and entering a PC name

 

On our

[NB9457]

You sadly can't change the domain or rename CC4 machines, this is due to the way the RM Management console ties in with AD, it doesn't like changes inb AD that aren't done via the Console, hence why RM removed this functionality.

 

Regarding MDT, if you need to get online quickly, it may be easier to just create a fat image for now and fling it out. Or, you could just deploy a blank image and use the PDQ Deploy trial to fire out the apps after.

 

Best of luck!

[Decimas6]

We have started deploying W10, I install core software such as office/chrome/antivirus on the image before capturing, so there's no need to add them to the task sequence. You can add all software if you want, I just do one basic image that gets installed on everything then different task sequences to install the different software groups (Staff, IT, etc)

 

As mentioned above, you a can turn most options off with a line in your Deployment share rules/settings.ini.