Deploying Windows 10: Part 2
This is part two of a series about deploying Windows 10. For part one, see the WME blog.
In this part, we will capture and deploy our base Windows 10 image for ConfigMgr 1511. As I stated in Part 1, I recommend doing this entire process in a VM. With a VM, we can take a snapshot just before capture that can revert too if there are any issues, as well as in the future when we need to patch or change our base image.
Image Cleanup
Before cleanup, take your pre-sysprep snapshot. We cleanup the image after the snapshot has been taken.
Before capture, you should clean up your base image. First, if you running VMware, or another virtualization product that installs any tools to help with integration, uninstall these first.
If you are using VMware, ensure that this registry key gets set back to this before capturing, and after you have uninstall VMware tools:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3]
“REGDBVersion”=hex:01,00,00
If you do not reset this key, you will not be able to execute any VB scripts after the image has been installed.
Next, go ahead and empty the Recycle Bin and run Disk Cleanup. If I am capturing a base, I always like to run all of the options in Disk Cleanup, as well as going to the “More Options” tab and cleaning up system restore points and shadow copies.
You can also utilize tools like CCleaner to remove stale files and registry keys. The point is to get the image as clean as possible.
Capture The Image
After you have cleaned up your base, you can use the ConfigMgr capture media to run sysprep and capture the base. You can build a capture media ISO from the “Create Task Sequence Media” option under the Task Sequences node of your ConfigMgr Console. Just feed the capture wizard the required information. Note that you will have to specify the destination as a UNC share, so you must have network connectivity.
Building a Task Sequence
Importing the WIM into ConfigMgr is exactly the same as it has been for previous versions of Windows. Be sure to check the data access box if you access content over the network for task sequences instead of download and install.
There’s no real difference between a Windows 10 task sequence and a Windows 7 task sequence. If you installed from the ISO, be sure to reference the correct image index on the “Apply Operating System” step. It should be index 2-2.
Also, be sure to add a step to re-enable Windows Store updates. This can be anywhere after “Setup Windows and Configuration Manager”.
After that, you can deploy the task sequence to your machines.
Disclaimer
All content provided on this blog is for information purposes only. Windows Management Experts, Inc makes no representation as to accuracy or completeness of any information on this site. Windows Management Experts, Inc will not be liable for any errors or omission in this information nor for the availability of this information. It is highly recommended that you consult one of our technical consultants, should you need any further assistance.
