We have been running Windows 7. With our new CAD workstation configuration, it will require us to deploy Windows 10.

Team Members

Tagged MSPs

Categories

I have been using WDS/MDT running on a Windows 2008 R2 server to deploy Windows 7. To deploy Windows 10, it would require me updating to the latest version of MDT. Rather than potentially break my current working setup, I decided to spin up a new server. So the first thing I had to do was purchase a new server license. The new server is running Windows Server 2016 with the latest version of MDT.

The setup was not much different than my previous setup. I performed the following tasks.

- Imported Windows 10 Enterprise from my VL media
- Added out-of-box drivers for my systems
- Created profile groups for each model of system
- Created Task Sequences for each model. Each task sequence had to be updated so that it injected just the drivers for that model.

One of the first issues I had to overcome was a .NET Framework issue. By default, when installing Windows 10, it include .NET Framwork 4.7. We need to also have 3.5 installed. When trying to install after the fact, the download was failing. I was able to modify the task sequence to install .NET Framewok 3.5 during the deployment.

I also tried to have include the Hyper-V role as part of the deployment. But when installing one application on the physical side, that application thought I was installing into a virtual machine and would not permit it. Once I removed the Hyper-V role, the installation of the application went fine.

As part of this deployment I added the updated/new admx files for Windows 10. In order to use them though, I had to manage group policy on the new server running Windows Server 2016. When I tried to manage group policy on the old server running Windows Server 2008 R2, I would get errors when I tried to edit a gpo.

I also have an agent that needed to be installed on the workstation. This agent is pushed to the workstation and requires the Remote Registry service to be running. I discovered that by default this service is disabled by default. I created a Windows 10 gpo and set the Remote Registry server startup to automatic.

I also configured the deployment process to install my choice of Office Professional Plus 2016, Project Standard 2016, and Visio Professional 2016. Previously when I was deploying Windows 7, I installed Office 2013 after the fact and not as part of the OS deployment process.

Update:
We have completed deployment for the new workstations as part of our refresh cycle. We are now looking at deploying Windows 10 to the rest of the staff.