Capturing the Reference Windows 10 Image using MDT 2013 Update 2

This is the second of a three-part series on Windows 10 OSD using MDT and SCCM.

Recap: In the first post we populated our MDT deployment share and then created and ran a task sequence to install Windows 10 on a virtual machine along with our applications and the .NET Framework 3.5 enabled. We left the post at the point of having a Windows 10 installation which we can brand as our own and customize the default user profile.

Here, we’re going to pick up from where we left off – I’m going to assume you’ve done all the customization to your liking and thus effectively turning the Windows 10 virtual machine into a reference machine. We’ll create a task sequence to sysprep and capture an image of our virtual machine which will give us our “Reference Windows 10 Image”. We’ll also create the unattend.xml file in this post which we’ll need in the next post. Ok, let’s get started.

Step 1) Create Task Sequence to Capture the Windows 10 Reference Image

1.1) Open Deployment Workbench, expand Task Sequences under your deployment share. Right-click on the Windows 10 folder which you created in the first part and select New Task Sequence. Enter/choose the following options:

  • Task sequence id: captw10-1511
  • Task sequence name: Capture Reference Image – Windows 10 ENT x64 (1511)
  • Task sequence template: Sysprep and Capture
  • Select OS: choose the Windows 10 OS you imported in the first part of this series
  • Specify Product Key: Do not specify a product key at this time
  • Full Name: Enter the name of your organisation
  • Organization: Enter the name of your organisation
  • Internet Explorer home page: choose a desired home page
  • Specify an Administrator password

Step 2) Create/Edit the Unattend.xml Answer File

The primary goal of this answer file is to set the CopyProfile setting to make sure our Administrator user profile (which we customised in the first post) will be copied over to the Default user profile at the time of deployment. While we’re at it we’ll also set the keyboard and system langauge, customise Internet Explorer (home page, popup blocker, etc) and set the date and time settings.

2.1) Right-click on the task sequence you just created and select Properties

2.2) On the OS Info tab, click on the “Edit Unattend.xml” button. This will launch the Windows System Image Manager (Windows SIM) tool, which looks like this:

clip_image002

2.3) Expand the “1 windowsPE” node under Components in the Answer File pane (in the middle). Enter/choose the following in the Properties pane (right side)

  • InputLocale: en-GB
  • SystemLocale: en-GB
  • UILanguage: en-GB
  • UILanguageFallback: en-GB
  • UserLocale: en-GB

2.4) Expand the “4 specialise” node. Make the following changes under this node

a) Select the “amd64_Microsoft-Windows-IE-InternetExplorer_neutral” component and enter/choose the following in the Properties pane:

  • BlockPopups: yes
  • DisableFirstRunWizard: yes
  • DisableWelcomePage: true
  • Home_page: Type in a home page for IE
  • IntranetCompatibilityMode: if your organisation’s local Intranet requires compatibility view in IE change this to true
  • LocalIntranetSites: Enter the url to your local Intranet if you’re setting IntranetCompatibility mode to true

b) Select the “amd64_Microsoft-Windows-Internation-Core_neutral” component and enter/choose the following in the Properties pane:

  • InputLocale: en-GB
  • SystemLocale: en-GB
  • UILanguage: en-GB
  • UILanguageFallback: en-GB
  • UserLocale: en-GB

c) Select the “amd64_Microsoft-Windows-Shell-Setup_neutral” component and enter/choose the following in the Properties pane:

  • CopyProfile: true

2.5) Expand the “7 oobeSystem” node. Make the following changes under this node.

a) Select the “amd64_Microsoft-Windows-Internation-Core_neutral” component and enter/choose the following in the Properties pane:

  • InputLocale: en-GB
  • SystemLocale: en-GB
  • UILanguage: en-GB
  • UILanguageFallback: en-GB
  • UserLocale: en-GB

b) Select the “amd64_Microsoft-Windows-Shell-Setup_neutral” component and enter/choose the following in the Properties pane:

  • DisableAutoDaylightTimeSet: false
  • RegisteredOrganisation: enter your organization name
  • RegisteredOwner: enter your organization name
  • TimeZone: GMT Standard Time

2.6) Click on the Save button to save the answer file. Do not close out of Windows SIM

Step 3) Create a Backup Copy of the Unattend.xml Answer File

While still inside Windows SIM click on File > Save Answer File As…and save a backup copy to a USB or a network share. Give it a descriptive name to identify which version of Windows 10 this answer file refers to. I’ve called mine Unattend-win10ent64-1511.xml. You’ll need this answer fil in the next post in the series when it comes to deploying our Windows 10 reference image using SCCM.

Step 4) Capture the Windows 10 Reference Image

1) Fire up your virtual machine which you’ve used in the last post to customize your Windows 10 installation

2) Open a Run window within Windows and type in the full path to your MDT deployment share. In my example this is \\MNI-SCCM01\MDTLab$\

3) Open the Scripts folder and double-click on LiteTouch.vbs – this will launch the MDT deployment wizard

4) Select the capture task sequence you created in Step 1 and click on Next

5) When you come to the Capture Image pane in the wizard choose/enter the following options

  • Select “Capture an image of this reference computer”
  • Verify the location where the captured image is to be stored. This should default to the “Captures” folder in your deployment share
  • Change the image file name to something meaningful. It’s a good idea to give your reference images build numbers along with the date/time. I’m going to call my image “Ref-W10ENT-x64-1511-310116”

6) MDT should start sysprep’ing your Windows 10 reference machine and capture the image

clip_image004

clip_image006

Once the task sequence finishes you’ll find your captured reference image in the “Captures” folder in your deployment share. You’ll need this image in the next post where we’ll first import it into SCCM along with the answer file we created in Step 2 and then deploy it to a target computer.

Stay tuned.

Advertisements

7 thoughts on “Capturing the Reference Windows 10 Image using MDT 2013 Update 2

  1. I never even get the CAPTURE IMAGE screen appear – it just immediately says it has completed successfully after I choose the task sequence…

    I’ve followed this guide to the LETTER so far…please can you help?

    Jon

    • Hi Jon, just to make sure are you starting the task sequence from within Windows (and not the boot image)?

      Does it start to Sysprep your computer? If Sysprep does start but doesn’t proceed to capture the image then take a look at your customsettings.ini rules. Make sure you don’t have DoCapture set to No. In fact, it’s best to take out DoCapture entirely if you plan on capturing images.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s