Keep These In Mind While Remotely Deploying Windows 10

Remote deployment of Windows 10 is a great example of proper SCCM implementation, but you need to keep the following in mind.

• Standardisation: Don't create too many different configurations. It will save a lot of effort during the roll-out. It will also reduce the burden of support in the future. You should have a few sets of applications and configurations.

• Group Policy: If something can be configured using group policy, you should certainly use that. It is easily managed and it can be easily changed in the future.

• Hardware: All the systems should be modern and should have at least 2GB of RAM. You should have standard hardware and not too many different models to handle. Hardware from major vendors is the key here as they have better support.

• Base Image: The base image should be created using the most basic computer. This image should have the pure OS. Some patches and some customisations can be done on the OS. VMWare can also be used to create a virtual PC for this purpose. ]

• User State Migration: USMT (User State Migration Tool) is a great choice for transferring user data and setting into the new OS but it has a bug as well. This bug can be nasty because it requires on fix from the server side and another fix from the user side. Moreover, USMT is configured using XML files which needs certain level of expertise. If you can avoid using USMT, do that.