This post will show you how to build and capture Windows 10 using MDT.
Earlier when Windows 10 was still in preview I posted a quick guide on how to do this using SCCM 2012, but since then a lot has happened. I can no longer say that using SCCM with MDT integration is the best option. Instead, as many other, I now recommend capturing the image with MDT.
In this demo I will use a Server Technical Preview 2 to install MDT and WSUS on. You can run this on any system and have the WSUS on another server, but I prefer to have everything on the same machine.
To start with, we need to download a few files. Some of these are optional, but I personally think that the core image should contain these files and applications. (Links open in new window)
- Windows 10 Enterprise
- MDT 2013 Update 1 (Still in preview so you need to register)
- ADK 10 (Direct Link)
Optional applications:
- Visual C++ Redistributional 2008 x86
- Visual C++ Redistributional 2008 x64
- Visual C++ Redistributional 2010 x86
- Visual C++ Redistributional 2010 x64
- Visual C++ Redistributional 2012 x86 and x64
- Visual C++ Redistributional 2013 x86 and x64
ADK 10
Now that we have all of our files it is time to start installing!
We will start with ADK 10, so run the downloaded adksetup.exe file and run through the wizard with the below settings. (No image means default values)
ICD that is marked in red is an optional feature. The installation time will depend on your internet connection speed, so sit back and relax while the installation finishes.
MDT 2013 Update 1
Since update one for MDT 2013 still is in preview, there are a few kinks, some files needs to be replaced and certain things might not work as expected. As far as I have seen everything seems to be fine, but it’s still a preview.
Run the MicrosoftDeploymentToolkit2013_x64.exe file downloaded and follow the wizard, accepting the EULA and the default installation path.
Before we can use MDT 2013 Update 1, we need to download and replace a few files. This will hopefully be fixed with the next preview version, or the final version when released.
Follow the instructions at the following link under “MDT Updated Content” before continuing.
Install WSUS (Optional)
To install the latest updates with the captured core image, we need to install WSUS as well. Follow these instructions to install WSUS and to download the latest updates for Windows 10.
If not already running, start the “Server Manager” and click on “Add roles and features”.
Then select “Role-based or feature-based installation”.
From the “Server pool”, select your server and click on “Next”
Then, under “Server Roles”, select “Windows Server Update Services” and accept to install the required roles and features.
Then click “Next” until you get to “Role Services” under “WSUS”.
Here, make sure that the top two boxes are ticked according to the screenshot.
Under “Content”, select the path were downloaded updates should be stored and complete the wizard.
When completed, launch the configuration wizard by clicking in the top right corner of “Server Manager”.
When the configuration is complete, start the WSUS-console from “Tools” to configure the settings for WSUS.
Follow the wizard that pops up and apply settings as shown in the screenshot below. (If there is no image, the setting is left to default)
This step could take up to 20 minutes to complete, so give it time before wondering if anything is wrong.
When completed, deselect everything under “Choose Products” and mark only the following products. (If you are building images for different OSes, select these as well, but for this guide we will only use Windows 10)
At the end of the wizard, choose to begin and initial synchronization.
The final step is to approve the found updates. When the wizard completes, the console will open. From here, select all updates and on the right hand side click on “Approve”.
When prompted, choose to approve the updates for all computers. (If multiple OSes are being used, you should create different groups)
Preparing the Deployment Share
Okay, now we are ready to start up the deployment workbench and create the deployment share that we will be using.
The first step in this process is to create a new “Deployment Share”.
Follow the guide and enter the details to match your environment.
If you are to change the “Share Name”, make sure that you do not remove the $-sign at the end!!
Under “Option”, deselect everything before continuing, these setting will be set later on in this guide.
Importing OS and adding applications
Now that we have our Deployment Share ready, we will import the OS and add the applications we downloaded earlier.
To get the OS we need to mount the ISO of Windows 10 and copy the “install.wim” file from the following directory: X:\Sources (Where X: is the drive letter of the mounted ISO)
Next, in the Deployment Workbench, right click on “Operating Systems”, selecting “Import Operating System”.
In the wizard that opens up, select “Custom image file” and click on “Next”.
Then follow the wizard through, with the following settings. (Default selections are left out in the screenshots)
Deselect marked box if checked
When completed, it is time to add the applications that should be installed. In this case I’m only adding the Visual C++ redistributional packages. The same principal applies to most applications, so I will only show how to add one of the packages.
Right click on the folder where the application should be created. (I’ve created several sub-folders to better separate the different versions)
Deselect marked box if checked
Follow the above steps to create a application package for the other applications downloaded. If you are adding other applications, the command line may differ. Check this with the publisher of the application!
Creating the Task Sequence
On of the last steps is to create the task sequence that we will be using to build our own Windows 10 core image.
Right click on “Task Sequences” and select “New Task Sequence”
In the wizard that appears, add the information required according to the screenshots below. (Same here, no screenshot, default values)
When you have completed the wizard to create the task sequence, we need to add the applications we created. To do this, right click on the newly created task sequence and click on “Properties”.
Under the tab “Task Sequence” you will see a step called “Install Applications”
Rename this step to Visual C++ 2008 x86 and select to install a single application, selecting the corresponding application we created earlier.
Then copy the step and paste it directly under, and repeat the process to add the other applications. (Or click on “Add” – > General -> Install Application)
Also, enable the two steps to install updates located before and after the applications. The complete task sequence should look something like this.
When finished, save the task sequence by clicking on “OK”.
Adding rules for installation
The last step we need to do is to add some rules for the installation.
The first place we need to do this is directly on the Deployment Share.
Right click on the Deployment Share we created and select “Properties”
Under the tab called “Rules”, replace everything with the following:
[Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y DeploymentType=NEWCOMPUTER UserID=MDT_User UserDomain=guidestomicrosoft.com UserPassword=P@ssw0rd SkipBDDWelcome=YES SkipDeploymentType=YES SkipDomainMembership=YES SkipApplications=YES SkipSummary=YES SkipUserData=YES SkipComputerName=YES SkipTaskSequence=YES SkipLocaleSelection=YES SkipTimeZone=YES SkipAppsOnUpgrade=YES SkipAdminPassword=YES SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=YES SkipCapture=YES SkipFinalSummary=YES ComputerName=WIN10 UILanguage=en-US UserLocale=en-US KeyboardLocale=0409:00000409 TimeZoneName=W. Europe Standard Time TaskSequenceID=Win10 WSUSServer=http://MDT.guidestomicrosoft.com:8530 DoCapture=YES ComputerBackupLocation=NETWORK BackupShare=\\MDT.guidestomicrosoft.com\OSD BackupDir=CustomImage BackupFile=Win10EntCustomImage.wim FinishAction=SHUTDOWN
In the text above, you need to edit the following settings to match your environment:
- UserID
- UserDomain
- UserPassword
- WSUSServer
- BackupShare
The final thing we need to edit is the bootstrap.ini. Click on “Edit Bootstrap.ini” and add the following to the end:
SkipBDDWelcome=Yes UserID=MDT_User UserDomain=guidestomicrosoft.com UserPassword=P@ssw0rd
Then save the file and click on “OK” to save all changes.
Start the build and capture
Now that everything is done, the last step is to update the Deployment Share and boot a virtual client from the ISO “LiteTouchPE_x86.iso” that is located in “C:\DeploymentShare\Boot”
Pingback: Build and Capture Windows 10 - A guide to Microsoft ProductsA guide to Microsoft Products