Deploying Windows 10 Part 12017. 8. 27. · Deploying Windows 10 – Part 1 System Center 2012 R2 Configuration Manager SP1 CU2 and MDT 2013 Update 2 ·

www.configmgr-tutelage.com

Deploying Windows 10 – Part 1

System Center 2012 R2 Configuration Manager SP1 CU2 and MDT 2013 Update 2


Creating Windows 10 reference image

In my previous post, I have installed and integrated MDT 2013 Update 2 with ConfigMgr 2012 R2 SP1

See post: Installing and Integrating MDT 2013 (Update 2) with ConfigMgr 2012 R2 SP1

In this post we will be working on Windows 10 Deployment and the followings will be covered to Create Windows 10 reference image:

Creating MDT New Deployment share

Adding Windows 10 Enterprise x64 Full Source

Adding Applications

Adding Drivers

Creating and Modifying Task Sequence for Reference Image

Editing the Bootstrap.ini file

Configuring the MDT deployment share rules

Updating Custom Background Image

Update the deployment share

Build the Windows 10 reference image

Setting up MDT Lab Deployment Share Create the MDT Lab deployment share Open the Deployment Workbench

http://www.configmgr-tutelage.com/mdt-2013/installing-and-integrating-mdt-2013-update-2-with-configmgr-2012-r2-sp1/


From the Deployment Workbench, right-click Deployment Shares and select New Deployment Share

On Path screen, specify the Deployment share path: In my case E:\MyMDTLab and click Next

On Share page, provide the UNC share name: In my case MyMDTLab$ and click Next


Specify the Deployment share description: My MDT Lab and click Next


Customize the deployment wizard behavior, select desired option. These settings can be changed later on using the Rules from deployment share and click Next


Review the summary page and click Next


Progress…


Click on Finish once done


PowerShell script can be used to create the deployment share

[New-SmbShare -Name "MyMDTLab$" -Path "E:\MyMDTLab" -FullAccess Administrators Import-Module "E:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1" new-PSDrive -Name "DS001" -PSProvider "MDTProvider" -Root "E:\MyMDTLab" -Description "My MDT Lab" -NetworkPath "\\SC12-CAS-01\MyMDTLab$" -Verbose | add-MDTPersistentDrive -Verbose]


My MDT Lab share has been created, now it is ready to add Operating Systems, Applications, Drivers and Task Sequences to capture and deploy images from MDT Workbench

Folder structure of MDT share

Verify that you can access the \\SC12-CAS-01\MyMDTLab$ share

Configure permissions for the deployment share In order to write the reference image back to the deployment share, grant/modify permissions to the MDT Admin Account (MDT.Admin) for the Captures subfolder in the E:\MyMDTLab folder


Modify the NTFS permissions for the E:\MyMDTLab\Captures folder by running the following command in an elevated Windows PowerShell prompt: icacls E:\MyMDTLab\Captures /grant '"MDT.Admin":(OI)(CI)(M)'

Or right click on Capture folder, open properties and manually grant required permissions


Adding Windows 10 Source

Add Windows 10 Enterprise x64 (full source) installation files I have copied the content of a Windows 10 Enterprise x64 ISO to the E:\SourceCode\Windows 10 Ent x64 folder. From Deployment Workbench, expand the Deployment Shares node Right-click the Operating Systems node and create a New folder

Specify the folder name, in my case Windows 10 and type folder comment if any in comment box


On Summary page click Next


Click Finish You can view the PowerShell script by clicking on view script tab. This script can be used to perform same steps later on using PS.


Expend the Operating Systems node, right-click on Windows 10 folder, and select Import Operating System

On OS type page choose Full set of source files and click Next


On Source page, specify the Source directory where Windows 10 full source files are copied. In my case E:\SourceCode\Windows 10 Ent x64 and click Next


Specify the Destination directory name Windows10Entx64 and click Next


Review the summary page and click Next to start importing the Windows 10


Files are being copied….

Click Finish once completed


In case you would like to use PowerShell script. Click on view script and save it as .ps1 file for later use [Import-Module "E:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1" New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\MyMDTLab" import-mdtoperatingsystem -path "DS001:\Operating Systems\Windows 10" -SourcePath "E:\SourceCode\Windows 10 ENT X64" -DestinationFolder "Windows10Entx64" -Verbose]

By default when you import the OS source the Name will be too lengthy….Just rename it to short one. From Deployment Workbench, Operating Systems Node, Windows 10 folder, double-click the newly added operating system name


Change the name to the following: Windows 10 Enterprise Eval x64 Default Image. Click OK

Adding Applications to MDT Build Lab share Before creating the MDT task sequence, add all of the applications and other sample scripts to the MDT Build Lab share.

We will add the following applications to MDT Build Share

Install - Microsoft Office 2013 Pro Plus - x86

Install - Microsoft Silverlight 5.0 - x64

Install - Microsoft Visual C++ 2005 SP1 - x86






Install - Microsoft Visual C++ 2012 Update 4 - x86



I have downloaded the software source files to the E:\SourceCode\Apps folder. We will add an application using the UI; we will use Windows PowerShell to add remaining application as MDT supports PowerShell.

All the Microsoft Visual C++ downloads can be downloaded from Microsoft Support page: http://support.microsoft.com/kb/2019667. Add the Microsoft Office Professional Plus 2013 x86 installation files

From Deployment Workbench, right click on Applications, Click on New Folder

Type folder name as Microsoft and click Next All MS related applications will be created under this folder.

http://support.microsoft.com/kb/2019667


Click Next on summary page


Click Finish


Create the Install: Microsoft Office Professional Plus 2013 x86 From Deployment Workbench, Expend the Applications node, right click on Microsoft Folder and click New Application

On Application Type Page, choose Application with Source Files and click Next


On Details page, provide the Name of Application, Publisher, and Version Click Next


Click on Browse and specify the source directory and click Next


Specify the destination directory name to be created and click Next


Type the Installation command line to be executed while application installation during task sequence Click Next


Review the summary and click Next


Application is being created…


Click Finish


Review the newly created MS Office 2013 Application In Deployment Workbench

Customize the Office installation using a Config.xml file To Create another Application, follow the same steps as performed above. Adding - Install - Microsoft Visual C++ 2005 SP1 - x86 From Deployment Workbench, Expend the Applications node, right click on Microsoft Folder and click New Application On Application Type Page, choose Application with Source Files and click Next


On Details page, provide the Name of Application, Publisher, and Version Click Next

Click on Browse and specify the source directory and click Next


Specify the Destination directory name to be created and click Next


Type the Installation command line to be executed while application installation during task sequence Click Next


Click Next


Click Finish Click on View Script to save the PS file for other applications.


Import Remaining Applications using PowerShell Script Import the MDT Module and Map the MDT share PSDrive using following PS command

Open PowerShell window and type the PS command. This will create Install - Microsoft Visual C++ 2008 SP1 - x86 Application


Follow the same PS script for remaining applications. Just modify the application source location, name of application and command line. Install - Microsoft Visual C++ 2005 SP1 - x86 [import-MDTApplication -path "DS001:\Applications\Microsoft" -enable "True" -Name "Install - Microsoft Visual C++ 2005 - x86" -ShortName "Install - Microsoft Visual C++ 2005 - x86" -Version "" -Publisher "" -Language "" -CommandLine "vcredist_x86.exe /Q" -WorkingDirectory ".\Applications\Install - Microsoft Visual C++ 2005 - x86" -ApplicationSourcePath "E:\SourceCode\Apps\VisualC++ Source\VC2005\x86" -DestinationFolder "Install - Microsoft Visual C++ 2005 - x86" –Verbose]

Install - Microsoft Visual C++ 2005 - x64 [import-MDTApplication -path "DS001:\Applications\Microsoft" -enable "True" -Name "Install - Microsoft Visual C++ 2005 - x64" -ShortName "Install - Microsoft Visual C++ 2005 - x64" -Version "" -Publisher "" -Language "" -CommandLine "vcredist_x64.exe /Q" -WorkingDirectory ".\Applications\Install - Microsoft Visual C++ 2005 - x64" -ApplicationSourcePath "E:\SourceCode\Apps\VisualC++ Source\VC2005\x64" -DestinationFolder "Install - Microsoft Visual C++ 2005 - x64" –Verbose]






Install - Microsoft Visual C++ 2012 - x86 [import-MDTApplication -path "DS001:\Applications\Microsoft" -enable "True" -Name "Install - Microsoft Visual C++ 2012 - x86" -ShortName "Install - Microsoft Visual C++ 2012 - x86" -Version "" -Publisher "" -Language "" -CommandLine "vcredist_x86.exe /quiet /norestart" -WorkingDirectory ".\Applications\Install - Microsoft Visual C++ 2012 - x86" -ApplicationSourcePath "E:\SourceCode\Apps\VisualC++ Source\VC2012\x86" -DestinationFolder "Install - Microsoft Visual C++ 2012 - x86" –Verbose]




Now we have all required applications which will be used during our Window 10 image build


Adding Drivers We will add required Drivers. If you are using Hyper-V for your test environment than you don’t have to add drivers when creating reference images for Windows 10. Windows Preinstallation Environment (Windows PE) already has all the needed drivers built-in for Hyper-V.

From Deployment Workbench, right click on Out-of-Box Drivers and click Import Drivers

Specify the source directory where drivers are copied, in my lab, driver source are copied to E:\Packages\Drivers folder. Click Next


Review summary and click Next


Click Finish


All required drivers have been added now


Create Task Sequence for Reference Image Creating the Task Sequence for Windows 10 Enterprise

From Deployment Workbench in the My MDT Lab deployment share, right-click Task Sequences, and create a New Folder named Windows 10. Right-click the New Windows 10 folder and select New Task Sequence

On General Settings Page

Specify the Task sequence ID: REFWIN10X64-01

Task sequence name: Windows 10 Enterprise x64 Default Image

Task sequence comments: Default reference Build Click Next


On Select Template page, select Standard Client Task Sequence template Click Next


On Select OS page, select the default Windows 10 Enterprise Eval x64 Default Image Click Next


Select Do not specify a product key at this time and click Next


Type the information Full Name, Organization, and Internet Explorer home page Click Next


Select Do not specify an Administrator Password at this time and Click Next


Review the summary page and click Next if all looks good


Click Finish


Our Task Sequence is ready now.

Edit the Windows 10 task sequence From Deployment Workbench

Right-click the Windows 10 Enterprise x64 Default Image task sequence, and select Properties


Task Sequence properties will open

On the Task Sequence tab, configure the Windows 10 Enterprise x64 Default Image task sequence a. State Restore. Enable the Windows Update (Pre-Application Installation) action by going to the Options tab

and clearing the Disable this step check box.

b. State Restore. Enable the Windows Update (Post-Application Installation) action by going to the Options tab and clearing the Disable this step check box.


c. State Restore. After the Tattoo action, add a new Group action:


Group Name: Custom Tasks (Pre-Windows Update)

d. State Restore. After Windows Update (Post-Application Installation) action, rename Custom Tasks to Custom

Tasks (Post-Windows Update)


e. State Restore / Custom Tasks (Pre-Windows Update). Add a new Install Roles and Features action Click on Add, go to Roles and select Install Roles and Features

Type the Name: Install - Microsoft NET Framework 3.5.1 Select the operating system for which roles are to be installed: Windows 10 Select the roles and features that should be installed: .NET Framework 3.5 (includes .NET 2.0 and 3.0)


f. State Restore - Custom Tasks (Pre-Windows Update). After the Install - Microsoft NET Framework 3.5.1

action, add a new Install Application action with the following settings: Click on Add, go to General and select Install Application

Type the Name: Install - Microsoft Visual C++ 2005 SP1 - x86 Select Install a Single Application and click on Browse and choose Install - Microsoft Visual C++ 2005 SP1 - x86


Click OK

g. Repeat the previous step (Click on Add, go to General and select Install Application) to add the following

applications:


Install - Microsoft Silverlight 5.0 - x64









Install - Microsoft Office 2013 Pro Plus - x86


Click OK h. Add a new Restart Computer action after the Install - Microsoft Office 2013 Pro Plus - x86 action Click on Add, go to General and select Restart Computer


Add a Suspend action. This is an optional configuration Click on Add, go to General and select Run Command Line

Type the Name: Suspend Specify the Command line: cscript.exe “%SCRIPTROOT%\LTISuspend.wsf”

Click OK


The LTISuspend.wsf file can be found in Script folder in MyMDTLab share

Note: If you need to do some manual configuration, you can add a little-known feature called Lite Touch Installation (LTI) Suspend. If you add the LTISuspend.wsf script as a custom action in the task sequence, it will suspend the task sequence until you click the Resume Task Sequence shortcut icon on the desktop. In addition to using the LTI Suspend feature for manual configuration or installation, you can also use it simply for verifying a reference image before you allow the task sequence to continue and use Sysprep and capture the virtual machine.


Edit the Unattend.xml file for Windows 10 Enterprise From Deployment Workbench

Right-click the Windows 10 Enterprise x64 Default Image task sequence, and select Properties


In the OS Info tab, click Edit Unattend.xml. MDT now generates a catalog file

This will take a few minutes, and then Windows System Image Manager (Windows SIM) will start



In Windows SIM, expand the 4 Specialize node in the Answer File pane and select the amd64_Microsoft-Windows-IE-InternetExplorer_neutral entry In the right-hand window, set the required values and make the changes: DisableDevTools, Allowed Sites, Company Name and Home Page Save the Unattend.xml file, and close Windows SIM


On the Windows 10 Enterprise x64 Default Image Properties, click OK

Configure the MDT deployment share rules From Deployment Workbench, right-click the My MDT Lab deployment share and select Properties


Select the Rules tab and click Edit Bootstrap.ini


Change the existing values as per below

[Settings] Priority=Default [Default] DeployRoot=\\SC12-CAS-01\MyMDTLab$ UserDomain=XPOSURE UserID=MDT.Admin


UserPassword=Pas5w0rd SkipBDDWelcome=YES Save the changes in Bootstrap.ini file

On the Rules tab Replace Rules with following entries


[Settings] Priority=Default [Default] Properties=MyCustomProperty _SMSTSORGNAME=XPOSURE UserDataLocation=NONE DoCapture=YES OSInstall=Y AdminPassword=P@ssw0rd TimeZoneName=Pacific Standard Time JoinWorkgroup=WORKGROUP HideShell=YES FinishAction=SHUTDOWN DoNotCreateExtraPartition=YES WSUSServer=http://SC12-PR01.xposure.com:80 ApplyGPOPack=NO SLSHARE=\\SC12-CAS-01\OSDLogs$ SkipAdminPassword=YES SkipProductKey=YES


SkipComputerName=YES SkipDomainMembership=YES SkipUserData=YES SkipLocaleSelection=YES SkipTaskSequence=NO SkipTimeZone=YES SkipApplications=No SkipBitLocker=YES SkipSummary=YES SkipRoles=No SkipCapture=NO SkipFinalSummary=YES Now select Windows PE Tab In the Windows PE tab, in the Platform drop-down list, select x86 in General Tab In the Lite Touch Boot Image Settings area, Change the following configurations

Image description: MDT Lite Touch Windows PE (x86)

ISO file name: MDT LiteTouchPE_x86.iso


In the Windows PE tab, in the Platform drop-down list, select x64 in General Tab In the Lite Touch Boot Image Settings area, Change the following configurations

Image description: MDT Lite Touch Windows PE (x64)

ISO file name: MDT LiteTouchPE_x64.iso Click OK

Updating Custom Background Image In the Windows PE tab, from Windows PE Customization Replace the Custom Background bitmap file with the one you want to display during image install and capture state Location for custom background file: .\Program Files\Microsoft Deployment Toolkit\Samples


Update the deployment share It’s time to Update the Deployment Share. This will create the Windows PE boot images. From the Deployment Workbench, right-click the My MDT Lab deployment share and click Update Deployment Share

Select the default option and click Next


On Summary page, click Next


The update process will take 10 to 15 minutes



Click Finish


PowerShell script: to perform same action [Import-Module "E:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1" New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\MyMDTLab" update-MDTDeploymentShare -path "DS001:" –Verbose]

Now we have our My MDT Lab fully functional and Windows PE boot ISO images ready to boot the machines to install and capture images.

Build the Windows 10 reference image

Let’s begin to build our test machines and boot from ISO. Copy the E:\MyMDTLab\Boot\MDT LiteTouchPE_x86.iso to your host machines Note: Remember, in MDT you can use the x86 boot image to deploy both x86 and x64 operating system images. That's why you can use the x86 boot image instead of the x64 boot image.


Create a virtual machine with the following settings:

Name: Windows 10 Reference Build

Location: D:\Virtual Machines\...

Memory: 4096 MB

Network: Host Only(The network that is connected to the same infrastructure as SCCM/MDT is)

Hard disk: 60 GB (dynamic disk)

Image file: .\My MDT ISO\MDT LiteTouchPE_x86.iso


Locate the Lite Touch ISO and mount it

Power on the Windows 10 Reference Build Virtual Machine. This will boot into Windows PE


Window PE loads the Custom Background Image


Processes Bootstrap Settings


Processes custom settings


Select a Task Sequence to execute on this computer Window appears Select the Windows 10 Enterprise x64 Default Image from the list and click Next


On Capture Image page, Select Capture an image of this reference computer and specify the Location and File Name Location: \\SC12-CAS-01\MyMDTLab$\Captures File name: REFW10X64-01.wim Click Next


The setup now starts and does the following:

Installs the Windows 10 operating system

Installs the added applications, roles, and features

Updates the operating system via local Windows Server Update Services (WSUS) server

Stages Windows PE on the local disk

Runs System Preparation (Sysprep) and reboots into Windows PE

Captures the installation to a Windows Imaging (WIM) file

Turns off the virtual machine Running Lite Touch Installation….



Computer restarts here and configures settings, this will take 10 to 15 minutes

Computer will restart once again to configure Windows and prepare the windows for 1st time this will take 10 - 20 minutes


Installing Added Applications…


Computer restarts one more time after installing the applications..

Updates the operating system via local Windows Server Update Services (WSUS) server


Finally, Image Installation process has been completed… We will get Suspend message as we have added Task Sequence Action to Suspend the Operating System Capture as soon as Installation completes so required changes/customizations can be made into new operating system Click OK

Now we have Windows 10 Desktop loaded.. ..make the required customizations/changes you like and click on Resume Task Sequence icon to start Image creation



Computer restarts here After computer restart Image Capture task starts


Path where reference image will be created

Image Capture may take an hour or so…

Once Image is captured, machine will automatically shut down. We have successfully captured the Windows 10 Image and Part 1 is completes here.


In my next post we will cover the followings:

Deploying Windows 10 – Part 2 Deploy Windows 10 with System Center 2012 R2 Configuration Manager

Prepare for Zero Touch Installation of Windows 10 with SCCM

Create the custom Windows PE boot image

Add the Captured Windows 10 image using SCCM

Create an application to deploy with Windows 10

Add drivers to a Windows 10 deployment with Windows PE

Create a task sequence with Configuration Manager and MDT

Deploy Windows 10 using PXE and SCCM

Refresh a Windows 7 SP1 client machine with Windows 10 Thank You for reading..!!

Documents

Deploying Windows 10 Part 12017. 8. 27. · Deploying Windows 10 – Part 1 System Center 2012 R2 Configuration Manager SP1 CU2 and MDT 2013 Update 2 ·