Sccm deploy windows 10

Sccm deploy windows 10 DEFAULT

How to push windows 10 upgrade with SCCM step by step

Upgrade windows 10 using sccm step by step

God news, yesterday in state 21 may , today for us Europeans windows 10 was released  http://www.sccm.ie/news/what-s-new-in-windows So let's start the engine and upgrade our windows 10 fleet to windows 10 :)

1. First check if SCCM synchronize the WSUS VB with Microsft and the new version is available in SCCM console. Go to Software Library --> Overview --> Windows 10 Servicing -->All Windows 10 Updates. I highlighted the version I need in my environment 

Windows_10__is_avaible_in_sccm

2. Right Click and select deploy 

Windows_10__deploy2

3. General, chose a deployment name and a test collection

Windows_10__deploy_general

4. Deployment settings, Required

Windows_10__deployment_settings

5. Scheduling, in my case is just a pilot test so I chose imediatly

Windows 10 deployment scheduling

6.  User experience, in my case I have chose to force install and restart at deadline

Windows 10 deployment user experience

6. Alerts

Windows 10 deployment alerts

7. Deployment Package, chose an existing one or create a new

Windows 10 deployment package

8. Download Location

Windows 10 deployment download

9. Language

Windows 10 deployment language

Download settings

Windows 10 deployment download settings

Summary, review the information

Completion

 Now on computer client in software center 

error_0x_fixed

Windows_10__deployment_install

  If you have this error0xC – () see this link how to fixFix sccm error 0xc deploying windows 10

Sours: https://www.sccm.ie/operating-system/upgrade-windowsusing-sccm-step-by-step

Deploy Windows 10 in a test lab using Microsoft Endpoint Configuration Manager

Applies to

Important: This guide leverages the proof of concept (PoC) environment, and some settings that are configured in the following guides:

Please complete all steps in these guides before attempting the procedures in this guide. If you wish to skip the Windows 10 deployment procedures in the MDT guide and move directly to this guide, you must at least install MDT and the Windows ADK before performing procedures in this guide. All steps in the first guide are required before attempting the procedures in this guide.

The PoC environment is a virtual network running on Hyper-V with three virtual machines (VMs):

  • DC1: A contoso.com domain controller, DNS server, and DHCP server.
  • SRV1: A dual-homed contoso.com domain member server, DNS server, and default gateway providing NAT service for the PoC network.
  • PC1: A contoso.com member computer running Windows 7, Windows 8, or Windows that has been cloned from a physical computer on your corporate network for testing purposes.

This guide leverages the Hyper-V server role to perform procedures. If you do not complete all steps in a single session, consider using checkpoints and saved states to pause, resume, or restart your work.

Multiple features and services are installed on SRV1 in this guide. This is not a typical installation, and is only done to set up a lab environment with a bare minimum of resources. However, if less than 4 GB of RAM is allocated to SRV1 in the Hyper-V console, some procedures will be extremely slow to complete. If resources are limited on the Hyper-V host, consider reducing RAM allocation on DC1 and PC1, and then increasing the RAM allocation on SRV1. You can adjust RAM allocation for a VM by right-clicking the VM in the Hyper-V Manager console, clicking Settings, clicking Memory, and modifying the value next to Maximum RAM.

In this guide

This guide provides end-to-end instructions to install and configure Microsoft Endpoint Configuration Manager, and use it to deploy a Windows 10 image. Depending on the speed of your Hyper-V host, the procedures in this guide will require hours to complete.

Topics and procedures in this guide are summarized in the following table. An estimate of the time required to complete each procedure is also provided. Time required to complete procedures will vary depending on the resources available to the Hyper-V host and assigned to VMs, such as processor speed, memory allocation, disk speed, and network speed.

TopicDescriptionTime
Install prerequisitesInstall prerequisite Windows Server roles and features, download, install and configure SQL Server, configure firewall rules, and install the Windows ADK.60 minutes
Install Microsoft Endpoint Configuration ManagerDownload Microsoft Endpoint Configuration Manager, configure prerequisites, and install the package.45 minutes
Download MDOP and install DaRTDownload the Microsoft Desktop Optimization Pack and install DaRT 15 minutes
Prepare for Zero Touch installationPrerequisite procedures to support Zero Touch installation.60 minutes
Create a boot image for Configuration ManagerUse the MDT wizard to create the boot image in Configuration Manager.20 minutes
Create a Windows 10 reference imageThis procedure can be skipped if it was done previously, otherwise instructions are provided to create a reference image. minutes
Add a Windows 10 operating system imageAdd a Windows 10 operating system image and distribute it.10 minutes
Create a task sequenceCreate a Configuration Manager task sequence with MDT integration using the MDT wizard15 minutes
Finalize the operating system configurationEnable monitoring, configure rules, and distribute content.30 minutes
Deploy Windows 10 using PXE and Configuration ManagerDeploy Windows 10 using Configuration Manager deployment packages and task sequences.60 minutes
Replace a client with Windows 10 using Configuration ManagerReplace a client computer with Windows 10 using Configuration Manager.90 minutes
Refresh a client with Windows 10 using Configuration ManagerUse a task sequence to refresh a client with Windows 10 using Configuration Manager and MDT90 minutes

Install prerequisites

  1. Before installing Microsoft Endpoint Configuration Manager, we must install prerequisite services and features. Type the following command at an elevated Windows PowerShell prompt on SRV1:

    If the request to add features fails, retry the installation by typing the command again.

  2. Download SQL Server SP2 from the Microsoft Evaluation Center as an .ISO file on the Hyper-V host computer. Save the file to the C:\VHD directory.

  3. When you have downloaded the file SQLServerSP2-FullSlipstream-xENU.iso and placed it in the C:\VHD directory, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:

    This command mounts the .ISO file to drive D on SRV1.

  4. Type the following command at an elevated Windows PowerShell prompt on SRV1 to install SQL Server:

    Installation will take several minutes. When installation is complete, the following output will be displayed:

  5. Type the following commands at an elevated Windows PowerShell prompt on SRV1:

  6. Download and install the latest Windows Assessment and Deployment Kit (ADK) on SRV1 using the default installation settings. The current version is the ADK for Windows 10, version Installation might require several minutes to acquire all components.

Install Microsoft Endpoint Configuration Manager

  1. On SRV1, temporarily disable IE Enhanced Security Configuration for Administrators by typing the following commands at an elevated Windows PowerShell prompt:

  2. Download Microsoft Endpoint Manager and Endpoint Protection on SRV1 (download the executable file anywhere on SRV1), double-click the file, enter C:\configmgr for Unzip to folder, and click Unzip. The C:\configmgr directory will be automatically created. Click OK and then close the WinZip Self-Extractor dialog box when finished.

  3. Before starting the installation, verify that WMI is working on SRV1. See the following examples. Verify that Running is displayed under Status and True is displayed next to TcpTestSucceeded:

    You can also verify WMI using the WMI console by typing wmimgmt.msc, right-clicking WMI Control (Local) in the console tree, and then clicking Properties.

    If the WMI service is not started, attempt to start it or reboot the computer. If WMI is running but errors are present, see WMIDiag for troubleshooting information.

  4. To extend the Active Directory schema, type the following command at an elevated Windows PowerShell prompt:

  5. Temporarily switch to the DC1 VM, and type the following command at an elevated command prompt on DC1:

  6. Right-click ADSI Edit, click Connect to, select Default (Domain or server that you logged in to) under Computer and then click OK.

  7. Expand Default naming context>DC=contoso,DC=com, and then in the console tree right-click CN=System, point to New, and then click Object.

  8. Click container and then click Next.

  9. Next to Value, type System Management, click Next, and then click Finish.

  10. Right-click CN=system Management and then click Properties.

  11. On the Security tab, click Add, click Object Types, select Computers, and click OK.

  12. Under Enter the object names to select, type SRV1 and click OK.

  13. The SRV1 computer account will be highlighted, select Allow next to Full control.

  14. Click Advanced, click SRV1 (CONTOSO\SRV1$) and click Edit.

  15. Next to Applies to, choose This object and all descendant objects, and then click OK three times.

  16. Close the ADSI Edit console and switch back to SRV1.

  17. To start Configuration Manager installation, type the following command at an elevated Windows PowerShell prompt on SRV1:

  18. Provide the following in the Microsoft Endpoint Manager Setup Wizard:

    • Before You Begin: Read the text and click Next.
    • Getting Started: Choose Install a Configuration Manager primary site and select the Use typical installation options for a stand-alone primary site checkbox.
      • Click Yes in response to the popup window.
    • Product Key: Choose Install the evaluation edition of this Product.
    • Microsoft Software License Terms: Read the terms and then select the I accept these license terms checkbox.
    • Prerequisite Licenses: Review license terms and select all three checkboxes on the page.
    • Prerequisite Downloads: Choose Download required files and enter c:\windows\temp next to Path.
    • Site and Installation Settings: Site code: PS1, Site name: Contoso.
      • use default settings for all other options
    • Usage Data: Read the text and click Next.
    • Service Connection Point Setup: Accept the default settings (SRV1.contoso.com is automatically added under Select a server to use).
    • Settings Summary: Review settings and click Next.
    • Prerequisite Check: No failures should be listed. Ignore any warnings and click Begin Install.

    There should be at most three warnings present: WSUS on site server, configuration for SQL Server memory usage, and SQL Server process memory allocation. These warnings can safely be ignored in this test environment.

    Depending on the speed of the Hyper-V host and resources allocated to SRV1, installation can require approximately one hour. Click Close when installation is complete.

  19. If desired, re-enable IE Enhanced Security Configuration at this time on SRV1:

Download MDOP and install DaRT

  1. Download the Microsoft Desktop Optimization Pack to the Hyper-V host using an MSDN subscription. Download the .ISO file (mu_microsoft_desktop_optimization_pack__x86_x64_dvd_iso, GB) to the C:\VHD directory on the Hyper-V host.

  2. Type the following command at an elevated Windows PowerShell prompt on the Hyper-V host to mount the MDOP file on SRV1:

  3. Type the following command at an elevated Windows PowerShell prompt on SRV1:

  4. Install DaRT 10 using default settings.

  5. Type the following commands at an elevated Windows PowerShell prompt on SRV1:

Prepare for Zero Touch installation

This section contains several procedures to support Zero Touch installation with Microsoft Endpoint Configuration Manager.

Create a folder structure

  1. Type the following commands at a Windows PowerShell prompt on SRV1:

Enable MDT ConfigMgr integration

  1. On SRV1, click Start, type configmgr, and then click Configure ConfigMgr Integration.
  2. Type PS1 next to Site code, and then click Next.
  3. Verify The process completed successfully is displayed, and then click Finish.

Configure client settings

  1. On SRV1, click Start, type configuration manager, right-click Configuration Manager Console, and then click Pin to Taskbar.
  2. Click Desktop, and then launch the Configuration Manager console from the taskbar.
  3. If the console notifies you that an update is available, click OK. It is not necessary to install updates to complete this lab.
  4. In the console tree, open the Administration workspace (in the lower left corner) and click Client Settings.
  5. In the display pane, double-click Default Client Settings.
  6. Click Computer Agent, next to Organization name displayed in Software Center type Contoso, and then click OK.

Configure the network access account

  1. In the Administration workspace, expand Site Configuration and click Sites.
  2. On the Home ribbon at the top of the console window, click Configure Site Components and then click Software Distribution.
  3. On the Network Access Account tab, choose Specify the account that accesses network locations.
  4. Click the yellow starburst and then click New Account.
  5. Click Browse and then under Enter the object name to select, type CM_NAA and click OK.
  6. Next to Password and Confirm Password, type [email protected], and then click OK twice.

Configure a boundary group

  1. In the Administration workspace, expand Hierarchy Configuration, right-click Boundaries and then click Create Boundary.
  2. Next to Description, type PS1, next to Type choose Active Directory Site, and then click Browse.
  3. Choose Default-First-Site-Name and then click OK twice.
  4. In the Administration workspace, right-click Boundary Groups and then click Create Boundary Group.
  5. Next to Name, type PS1 Site Assignment and Content Location, click Add, select the Default-First-Site-Name boundary and then click OK.
  6. On the References tab in the Create Boundary Group window select the Use this boundary group for site assignment checkbox.
  7. Click Add, select the \\SRV1.contoso.com checkbox, and then click OK twice.

Add the state migration point role

  1. In the Administration workspace, expand Site Configuration, click Sites, and then in on the Home ribbon at the top of the console click Add Site System Roles.
  2. In the Add site System Roles Wizard, click Next twice and then on the Specify roles for this server page, select the State migration point checkbox.
  3. Click Next, click the yellow starburst, type C:\MigData for the Storage folder, and click OK.
  4. Click Next, and then verify under Boundary groups that PS1 Site Assignment and Content Location is displayed.
  5. Click Next twice and then click Close.

Enable PXE on the distribution point

Important

Before enabling PXE in Configuration Manager, ensure that any previous installation of WDS does not cause conflicts. Configuration Manager will automatically configure the WDS service to manage PXE requests. To disable a previous installation, if it exists, type the following commands at an elevated Windows PowerShell prompt on SRV1:

  1. Determine the MAC address of the internal network adapter on SRV1. To determine this, type the following command at an elevated Windows PowerShell prompt on SRV1:

    If the internal network adapter, assigned an IP address of , is not named "Ethernet" then replace the name "Ethernet" in the previous command with the name of this network adapter. You can review the names of network adapters and the IP addresses assigned to them by typing ipconfig.

  2. In the Microsoft Endpoint Manager console, in the Administration workspace, click Distribution Points.

  3. In the display pane, right-click SRV1.CONTOSO.COM and then click Properties.

  4. On the PXE tab, select the following settings:

    • Enable PXE support for clients. Click Yes in the popup that appears.

    • Allow this distribution point to respond to incoming PXE requests

    • Enable unknown computer support. Click OK in the popup that appears.

    • Require a password when computers use PXE

    • Password and Confirm password: [email protected]

    • Respond to PXE requests on specific network interfaces: Click the yellow starburst and then enter the MAC address determined in the first step of this procedure.

      See the following example: Config Mgr PXE.

  5. Click OK.

  6. Wait for a minute, then type the following command at an elevated Windows PowerShell prompt on SRV1, and verify that the files displayed are present:

    If these files are not present in the C:\RemoteInstall directory, verify that the REMINST share is configured as C:\RemoteInstall. You can view the properties of this share by typing "net share REMINST" at a command prompt. If the share path is set to a different value, then replace C:\RemoteInstall with your REMINST share path. You can also type the following command at an elevated Windows PowerShell prompt to open the Configuration Manager Trace Log Tool. In the tool, click File, click Open, and then open the distmgr.log file. If errors are present, they will be highlighted in red:

    The log file will updated continuously while Configuration Manager is running. Wait for Configuration Manager to repair any issues that are present, and periodically re-check that the files are present in the REMINST share location. Close the Configuration Manager Trace Log Tool when done. You will see the following line in distmgr.log that indicates the REMINST share is being populated with necessary files:

    Once the files are present in the REMINST share location, you can close the cmtrace tool.

Create a branding image file

  1. If you have a bitmap (.BMP) image for suitable use as a branding image, copy it to the C:\Sources\OSD\Branding folder on SRV1. Otherwise, use the following step to copy a simple branding image.

  2. Type the following command at an elevated Windows PowerShell prompt:

    You can open C:\Sources\OSD\Branding\contoso.bmp in MSPaint.exe if desired to customize this image.

Create a boot image for Configuration Manager

  1. In the Configuration Manager console, in the Software Library workspace, expand Operating Systems, right-click Boot Images, and then click Create Boot Image using MDT.

  2. On the Package Source page, under Package source folder to be created (UNC Path):, type \\SRV1\Sources$\OSD\Boot\Zero Touch WinPE x64, and then click Next.

    • The Zero Touch WinPE x64 folder does not yet exist. The folder will be created later.
  3. On the General Settings page, type Zero Touch WinPE x64 next to Name, and click Next.

  4. On the Options page, under Platform choose x64, and click Next.

  5. On the Components page, in addition to the default selection of Microsoft Data Access Components (MDAC/ADO) support, select the Microsoft Diagnostics and Recovery Toolkit (DaRT) checkbox, and click Next.

  6. On the Customization page, select the Use a custom background bitmap file checkbox, and under UNC path, type or browse to \\SRV1\Sources$\OSD\Branding\contoso.bmp, and then click Next twice. It will take a few minutes to generate the boot image.

  7. Click Finish.

  8. In the console display pane, right-click the Zero Touch WinPE x64 boot image, and then click Distribute Content.

  9. In the Distribute Content Wizard, click Next, click Add and select Distribution Point, select the SRV1.CONTOSO.COM checkbox, click OK, click Next twice, and then click Close.

  10. Use the CMTrace application to view the distmgr.log file again and verify that the boot image has been distributed. To open CMTrace, type the following command at an elevated Windows PowerShell prompt on SRV1:

    In the trace tool, click Tools on the menu and choose Find. Search for "STATMSG: ID=". For example:

  11. You can also review status by clicking the Zero Touch WinPE x64 image, and then clicking Content Status under Related Objects in the bottom right-hand corner of the console, or by entering \Monitoring\Overview\Distribution Status\Content Status on the location bar in the console. Double-click Zero Touch WinPE x64 under Content Status in the console tree and verify that a status of Successfully distributed content is displayed on the Success tab.

  12. Next, in the Software Library workspace, double-click Zero Touch WinPE x64 and then click the Data Source tab.

  13. Select the Deploy this boot image from the PXE-enabled distribution point checkbox, and click OK.

  14. Review the distmgr.log file again for "STATMSG: ID=" and verify that there are three folders under C:\RemoteInstall\SMSImages with boot images. See the following example:

    The first two images (*.wim files) are default boot images. The third is the new boot image with DaRT.

Create a Windows 10 reference image

If you have already completed steps in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit then you have already created a Windows 10 reference image. In this case, skip to the next procedure in this guide: Add a Windows 10 operating system image. If you have not yet created a Windows 10 reference image, complete the steps in this section.

  1. In Step by step guide: Deploy Windows 10 in a test lab the Windows 10 Enterprise .iso file was saved to the c:\VHD directory as c:\VHD\wenterprise.iso. The first step in creating a deployment share is to mount this file on SRV1. To mount the Windows 10 Enterprise DVD on SRV1, open an elevated Windows PowerShell prompt on the Hyper-V host computer and type the following command:

  2. Verify that the Windows Enterprise installation DVD is mounted on SRV1 as drive letter D.

  3. The Windows 10 Enterprise installation files will be used to create a deployment share on SRV1 using the MDT deployment workbench. To open the deployment workbench, click Start, type deployment, and then click Deployment Workbench.

  4. In the Deployment Workbench console, right-click Deployment Shares and select New Deployment Share.

  5. Use the following settings for the New Deployment Share Wizard:

    • Deployment share path: C:\MDTBuildLab
    • Share name: MDTBuildLab$
    • Deployment share description: MDT build lab
    • Options: click Next to accept the default
    • Summary: click Next
    • Progress: settings will be applied
    • Confirmation: click Finish
  6. Expand the Deployment Shares node, and then expand MDT build lab.

  7. Right-click the Operating Systems node, and then click New Folder. Name the new folder Windows 10. Complete the wizard using default values and click Finish.

  8. Right-click the Windows 10 folder created in the previous step, and then click Import Operating System.

  9. Use the following settings for the Import Operating System Wizard:

    • OS Type: Full set of source files
    • Source: D:\
    • Destination: W10Ent_x64
    • Summary: click Next
    • Confirmation: click Finish
  10. For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the Add applications section of the Create a Windows 10 reference image topic in the TechNet library.

  11. The next step is to create a task sequence to reference the operating system that was imported. To create a task sequence, right-click the Task Sequences node under MDT Build Lab and then click New Task Sequence. Use the following settings for the New Task Sequence Wizard:

    • Task sequence ID: REFW10X
    • Task sequence name: Windows 10 Enterprise x64 Default Image
    • Task sequence comments: Reference Build
    • Template: Standard Client Task Sequence
    • Select OS: click Windows 10 Enterprise Evaluation in W10Ent_x64 install.wim
    • Specify Product Key: Do not specify a product key at this time
    • Full Name: Contoso
    • Organization: Contoso
    • Internet Explorer home page: http://www.contoso.com
    • Admin Password: Do not specify an Administrator password at this time
    • Summary: click Next
    • Confirmation: click Finish
  12. Edit the task sequence to add the Microsoft NET Framework , which is required by many applications. To edit the task sequence, double-click Windows 10 Enterprise x64 Default Image that was created in the previous step.

  13. Click the Task Sequence tab. Under State Restore click Tattoo to highlight it, then click Add and choose New Group. A new group will be added under Tattoo.

  14. On the Properties tab of the group that was created in the previous step, change the Name from New Group to Custom Tasks (Pre-Windows Update) and then click Apply. To see the name change, click Tattoo, then click the new group again.

  15. Click the Custom Tasks (Pre-Windows Update) group again, click Add, point to Roles, and then click Install Roles and Features.

  16. Under Select the roles and features that should be installed, select .NET Framework (includes .NET and ) and then click Apply.

  17. Enable Windows Update in the task sequence by clicking the Windows Update (Post-Application Installation) step, clicking the Options tab, and clearing the Disable this step checkbox.

    Note: Since we are not installing applications in this test lab, there is no need to enable the Windows Update Pre-Application Installation step. However, you should enable this step if you are also installing applications.

  18. Click OK to complete editing the task sequence.

  19. The next step is to configure the MDT deployment share rules. To configure rules in the Deployment Workbench, right-click MDT build lab (C:\MDTBuildLab) and click Properties, and then click the Rules tab.

  20. Replace the default rules with the following text:

  21. Click Apply and then click Edit Bootstrap.ini. Replace the contents of the Bootstrap.ini file with the following text, and save the file:

  22. Click OK to complete the configuration of the deployment share.

  23. Right-click MDT build lab (C:\MDTBuildLab) and then click Update Deployment Share.

  24. Accept all default values in the Update Deployment Share Wizard by clicking Next. The update process will take 5 to 10 minutes. When it has completed, click Finish.

  25. Copy c:\MDTBuildLab\Boot\LiteTouchPE_xiso on SRV1 to the c:\VHD directory on the Hyper-V host computer. Note that in MDT, the x86 boot image can deploy both x86 and x64 operating systems, except on computers based on Unified Extensible Firmware Interface (UEFI).

    Hint: Top copy the file, right-click the LiteTouchPE_xiso file and click Copy on SRV1, then open the c:\VHD folder on the Hyper-V host, right-click inside the folder and click Paste.

  26. Open a Windows PowerShell prompt on the Hyper-V host computer and type the following commands:

  27. In the Windows Deployment Wizard, select Windows 10 Enterprise x64 Default Image, and then click Next.

  28. Accept the default values on the Capture Image page, and click Next. Operating system installation will complete after 5 to 10 minutes and then the VM will reboot automatically. Allow the system to boot normally (do not press a key). The process is fully automated.

    Additional system restarts will occur to complete updating and preparing the operating system. Setup will complete the following procedures:

    • Install the Windows 10 Enterprise operating system.
    • Install added applications, roles, and features.
    • Update the operating system using Windows Update (or WSUS if optionally specified).
    • Stage Windows PE on the local disk.
    • Run System Preparation (Sysprep) and reboot into Windows PE.
    • Capture the installation to a Windows Imaging (WIM) file.
    • Turn off the virtual machine.

    This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host and your network's download speed. After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. The image is located in the C:\MDTBuildLab\Captures folder on SRV1. The file name is REFW10Xwim.

Add a Windows 10 operating system image

  1. Type the following commands at an elevated Windows PowerShell prompt on SRV1:

  2. In the Configuration Manager console, in the Software Library workspace, expand Operating Systems, right-click Operating System Images, and then click Add Operating System Image.

  3. On the Data Source page, under Path:, type or browse to \\SRV1\Sources$\OSD\OS\Windows 10 Enterprise x64\REFW10Xwim, and click Next.

  4. On the General page, next to Name:, type Windows 10 Enterprise x64, click Next twice, and then click Close.

  5. Distribute the operating system image to the SRV1 distribution point by right-clicking the Windows 10 Enterprise x64 operating system image and then clicking Distribute Content.

  6. In the Distribute Content Wizard, click Next, click Add, click Distribution Point, add the SRV1.CONTOSO.COM distribution point, click OK, click Next twice and then click Close.

  7. Enter \Monitoring\Overview\Distribution Status\Content Status on the location bar (be sure there is no space at the end of the location or you will get an error), click Windows 10 Enterprise x64, and monitor the status of content distribution until it is successful and no longer in progress. Refresh the view with the F5 key or by right-clicking Windows 10 Enterprise x64 and clicking Refresh. Processing of the image on the site server can take several minutes.

    If content distribution is not successful, verify that sufficient disk space is available.

Create a task sequence

Complete this section slowly. There are a large number of similar settings from which to choose.

  1. In the Configuration Manager console, in the Software Library workspace expand Operating Systems, right-click Task Sequences, and then click Create MDT Task Sequence.

  2. On the Choose Template page, select the Client Task Sequence template and click Next.

  3. On the General page, type Windows 10 Enterprise x64 under Task sequence name: and then click Next.

  4. On the Details page, enter the following settings:

    • Join a domain: contoso.com
    • Account: click Set
    • Windows Settings
      • User name: Contoso
      • Organization name: Contoso
      • Product key: <blank>
    • Administrator Account: Enable the account and specify the local administrator password
    • Click Next
  5. On the Capture Settings page, accept the default settings and click Next.

  6. On the Boot Image page, browse and select the Zero Touch WinPE x64 boot image package, click OK, and then click Next.

  7. On the MDT Package page, select Create a new Microsoft Deployment Toolkit Files package, under Package source folder to be created (UNC Path):, type \\SRV1\Sources$\OSD\MDT\MDT (MDT is repeated here, not a typo), and then click Next.

  8. On the MDT Details page, next to Name: type MDT and then click Next.

  9. On the OS Image page, browse and select the Windows 10 Enterprise x64 package, click OK, and then click Next.

  10. On the Deployment Method page, accept the default settings for Zero Touch Installation and click Next.

  11. On the Client Package page, browse and select the Microsoft Corporation Configuration Manager Client package, click OK, and then click Next.

  12. On the USMT Package page, browse and select the Microsoft Corporation User State Migration Tool for Windows package, click OK, and then click Next.

  13. On the Settings Package page, select Create a new settings package, and under Package source folder to be created (UNC Path):, type \\SRV1\Sources$\OSD\Settings\Windows 10 x64 Settings, and then click Next.

  14. On the Settings Details page, next to Name:, type Windows 10 x64 Settings, and click Next.

  15. On the Sysprep Package page, click Next twice.

  16. On the Confirmation page, click Finish.

Edit the task sequence

  1. In the Configuration Manager console, in the Software Library workspace, click Task Sequences, right-click Windows 10 Enterprise x64, and then click Edit.

  2. Scroll down to the Install group and click the Set Variable for Drive Letter action.

  3. Change the Value under OSDPreserveDriveLetter from False to True, and then click Apply.

  4. In the State Restore group, click the Set Status 5 action, click Add in the upper left corner, point to User State, and click Request State Store. This adds a new action immediately after Set Status 5.

  5. Configure the Request State Store action that was just added with the following settings:

    • Request state storage location to: Restore state from another computer
    • Select the If computer account fails to connect to state store, use the Network Access account checkbox.
    • Options tab: Select the Continue on error checkbox.
    • Add Condition: Task Sequence Variable:
      • Variable: USMTLOCAL
      • Condition: not equals
      • Value: True
      • Click OK
    • Click Apply
  6. In the State Restore group, click Restore User State, click Add, point to User State, and click Release State Store.

  7. Configure the Release State Store action that was just added with the following settings:

    • Options tab: Select the Continue on error checkbox.
    • Add Condition: Task Sequence Variable:
      • Variable: USMTLOCAL
      • Condition: not equals
      • Value: True
      • Click OK
    • Click OK

Finalize the operating system configuration

If you completed all procedures in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit then the MDT deployment share is already present on SRV1. In this case, skip the first four steps below and begin with step 5 to edit CustomSettings.ini.

  1. In the MDT deployment workbench on SRV1, right-click Deployment Shares and then click New Deployment Share.

  2. Use the following settings for the New Deployment Share Wizard:

    • Deployment share path: C:\MDTProduction
    • Share name: MDTProduction$
    • Deployment share description: MDT Production
    • Options: click Next to accept the default
    • Summary: click Next
    • Progress: settings will be applied
    • Confirmation: click Finish
  3. Right-click the MDT Production deployment share, and click Properties.

  4. Click the Monitoring tab, select the Enable monitoring for this deployment share checkbox, and then click OK.

  5. Type the following command at an elevated Windows PowerShell prompt on SRV1:

  6. Replace the contents of the file with the following text, and then save the file:

    As noted previously, if you wish to migrate accounts other than those in the Contoso domain, then change the OSDMigrateAdditionalCaptureOptions option. For example, the following option will capture settings from all user accounts:

  7. Return to the Configuration Manager console, and in the Software Library workspace, expand Application Management, click Packages, right-click Windows 10 x64 Settings, and then click Update Distribution Points. Click OK in the popup that appears.

  8. In the Software Library workspace, expand Operating Systems, click Task Sequences, right-click Windows 10 Enterprise x64, and then click Distribute Content.

  9. In the Distribute Content Wizard, click Next twice, click Add, click Distribution Point, select the SRV1.CONTOSO.COM distribution point, click OK, click Next twice and then click Close.

  10. Enter \Monitoring\Overview\Distribution Status\Content Status\Windows 10 Enterprise x64 on the location bar, double-click Windows 10 Enterprise x64, and monitor the status of content distribution until it is successful and no longer in progress. Refresh the view with the F5 key or by right-clicking Windows 10 Enterprise x64 and clicking Refresh.

Create a deployment for the task sequence

  1. In the Software Library workspace, expand Operating Systems, click Task Sequences, right-click Windows 10 Enterprise x64, and then click Deploy.

  2. On the General page, next to Collection, click Browse, select the All Unknown Computers collection, click OK, and then click Next.

  3. On the Deployment Settings page, use the following settings:

    • Purpose: Available
    • Make available to the following: Only media and PXE
    • Click Next.
  4. Click Next five times to accept defaults on the Scheduling, User Experience, Alerts, and Distribution Points pages.

  5. Click Close.

Deploy Windows 10 using PXE and Configuration Manager

In this first deployment scenario, we will deploy Windows 10 using PXE. This scenario creates a new computer that does not have any migrated users or settings.

  1. Type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

  2. Press ENTER when prompted to start the network boot service.

  3. In the Task Sequence Wizard, provide the password: [email protected], and then click Next.

  4. Before you click Next in the Task Sequence Wizard, press the F8 key. A command prompt will open.

  5. At the command prompt, type explorer.exe and review the Windows PE file structure.

  6. The smsts.log file is critical for troubleshooting any installation problems that might be encountered. Depending on the deployment phase, the smsts.log file is created in different locations:

    • X:\Windows\temp\SMSTSLog\smsts.log before disks are formatted.

    • X:\smstslog\smsts.log after disks are formatted.

    • C:\_SMSTaskSequence\Logs\Smstslog\smsts.log before the Microsoft Endpoint Manager client is installed.

    • C:\Windows\ccm\logs\Smstslog\smsts.log after the Microsoft Endpoint Manager client is installed.

    • C:\Windows\ccm\logs\smsts.log when the task sequence is complete.

      Note: If a reboot is pending on the client, the reboot will be blocked as long as the command window is open.

  7. In the explorer window, click Tools and then click Map Network Drive.

  8. Do not map a network drive at this time. If you need to save the smsts.log file, you can use this method to save the file to a location on SRV1.

  9. Close the Map Network Drive window, the Explorer window, and the command prompt.

  10. The Windows 10 Enterprise x64 task sequence is selected in the Task Sequence Wizard. Click Next to continue with the deployment.

  11. The task sequence will require several minutes to complete. You can monitor progress of the task sequence using the MDT Deployment Workbench under Deployment Shares > MDTProduction > Monitoring. The task sequence will:

    • Install Windows 10
    • Install the Configuration Manager client and hotfix
    • Join the computer to the contoso.com domain
    • Install any applications that were specified in the reference image
  12. When Windows 10 installation has completed, sign in to PC4 using the contoso\administrator account.

  13. Right-click Start, click Run, type control appwiz.cpl, press ENTER, click Turn Windows features on or off, and verify that .NET Framework (includes .NET and ) is installed. This is a feature included in the reference image.

  14. Shut down the PC4 VM.

Note

The following two procedures 1) Replace a client with Windows 10 and 2) Refresh a client with Windows 10 have been exchanged in their order in this guide compared to the previous version. This is to avoid having to restore Hyper-V checkpoints to have access to PC1 before the OS is upgraded. If this is your first time going through this guide, you won't notice any change, but if you have tried the guide previously then this change should make it simpler to complete.

Replace a client with Windows 10 using Configuration Manager

Before starting this section, you can delete computer objects from Active Directory that were created as part of previous deployment procedures. Use the Active Directory Users and Computers console on DC1 to remove stale entries under contoso.com\Computers, but do not delete the computer account (hostname) for PC1. There should be at least two computer accounts present in the contoso.com\Computers container: one for SRV1, and one for the hostname of PC1. It is not required to delete the stale entries, this is only done to remove clutter.

contoso.com\Computers.

In the replace procedure, PC1 will not be migrated to a new operating system. It is simplest to perform this procedure before performing the refresh procedure. After refreshing PC1, the operating system will be new. The next (replace) procedure does not install a new operating system on PC1 but rather performs a side-by-side migration of PC1 and another computer (PC4), to copy users and settings from PC1 to the new computer.

Create a replace task sequence

  1. On SRV1, in the Configuration Manager console, in the Software Library workspace, expand Operating Systems, right-click Task Sequences, and then click Create MDT Task Sequence.

  2. On the Choose Template page, select Client Replace Task Sequence and click Next.

  3. On the General page, type the following:

    • Task sequence name: Replace Task Sequence
    • Task sequence comments: USMT backup only
  4. Click Next, and on the Boot Image page, browse and select the Zero Touch WinPE x64 boot image package. Click OK and then click Next to continue.

  5. On the MDT Package page, browse and select the MDT package. Click OK and then click Next to continue.

  6. On the USMT Package page, browse and select the Microsoft Corporation User State Migration Tool for Windows package. Click OK and then click Next to continue.

  7. On the Settings Package page, browse and select the Windows 10 x64 Settings package. Click OK and then click Next to continue.

  8. On the Summary page, review the details and then click Next.

  9. On the Confirmation page, click Finish.

If an error is displayed at this stage it can be caused by a corrupt MDT integration. To repair it, close the Configuration Manager console, remove MDT integration, and then restore MDT integration.

Deploy PC4

Create a VM named PC4 to receive the applications and settings from PC1. This VM represents a new computer that will replace PC1. To create this VM, type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

Hyper-V enables us to define a static MAC address on PC4. In a real-world scenario you must determine the MAC address of the new computer.

Install the Configuration Manager client on PC1

  1. Verify that the PC1 VM is running and in its original state, which was saved as a checkpoint and then restored in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit.

  2. If a PC1 checkpoint has not already been saved, then save a checkpoint by typing the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

  3. On SRV1, in the Configuration Manager console, in the Administration workspace, expand Hierarchy Configuration and click on Discovery Methods.

  4. Double-click Active Directory System Discovery and on the General tab select the Enable Active Directory System Discovery checkbox.

  5. Click the yellow starburst, click Browse, select contoso\Computers, and then click OK three times.

  6. When a popup dialog box asks if you want to run full discovery, click Yes.

  7. In the Assets and Compliance workspace, click Devices and verify that the computer account names for SRV1 and PC1 are displayed. See the following example (GREGLIN-PC1 is the computer account name of PC1 in this example):

If you do not see the computer account for PC1, try clicking the Refresh button in the upper right corner of the console.

The Client column indicates that the Configuration Manager client is not currently installed. This procedure will be carried out next.

  1. Sign in to PC1 using the contoso\administrator account and type the following at an elevated command prompt to remove any pre-existing client configuration, if it exists. Note: this command requires an elevated command prompt not an elevated Windows PowerShell prompt:

    If PC1 still has Configuration Manager registry settings that were applied by Group Policy, startup scripts, or other policies in its previous domain, these might not all be removed by CCMSetup /Uninstall and can cause problems with installation or registration of the client in its new environment. It might be necessary to manually remove these settings if they are present. For more information, see Manual removal of the Configuration Manager client.

  2. On PC1, temporarily stop Windows Update from queuing items for download and clear all BITS jobs from the queue. From an elevated command prompt, type:

    Verify that both services were stopped successfully, then type the following at an elevated command prompt:

    Verify that BITSAdmin displays 0 jobs.

  3. To install the Configuration Manager client as a standalone process, type the following at an elevated command prompt:

  4. On PC1, using file explorer, open the C:\Windows\ccmsetup directory. During client installation, files will be downloaded here.

  5. Installation progress will be captured in the file: c:\windows\ccmsetup\logs\ccmsetup.log. You can periodically open this file in notepad, or you can type the following command at an elevated Windows PowerShell prompt to monitor installation progress:

    Installation might require several minutes, and display of the log file will appear to hang while some applications are installed. This is normal. When setup is complete, verify that CcmSetup is existing with return code 0 is displayed on the last line of the ccmsetup.log file and then press CTRL-C to break out of the Get-Content operation (if you are viewing the log in Windows PowerShell the last line will be wrapped). A return code of 0 indicates that installation was successful and you should now see a directory created at C:\Windows\CCM that contains files used in registration of the client with its site.

  6. On PC1, open the Configuration Manager control panel applet by typing the following command from a command prompt:

  7. Click the Site tab, click Configure Settings, and click Find Site. The client will report that it has found the PS1 site. See the following example:

    site.

    If the client is not able to find the PS1 site, review any error messages that are displayed in C:\Windows\CCM\Logs\ClientIDManagerStartup.log and LocationServices.log. A common reason the site code is not located is because a previous configuration exists. For example, if a previous site code is configured at HKLM\SOFTWARE\Microsoft\SMS\Mobile Client\GPRequestedSiteAssignmentCode this must be deleted or updated.

  8. On SRV1, in the Assets and Compliance workspace, click Device Collections and then double-click All Desktop and Server Clients. This node will be added under Devices.

  9. Click All Desktop and Server Clients and verify that the computer account for PC1 is displayed here with Yes and Active in the Client and Client Activity columns, respectively. You might have to refresh the view and wait few minutes for the client to appear here. See the following example:

    client.

    It might take several minutes for the client to fully register with the site and complete a client check. When it is complete you will see a green check mark over the client icon as shown above. To refresh the client, click it and then press F5 or right-click the client and click Refresh.

Create a device collection and deployment

  1. On SRV1, in the Configuration Manager console, in the Asset and Compliance workspace, right-click Device Collections and then click Create Device Collection.

  2. Use the following settings in the Create Device Collection Wizard:

    • General > Name: Install Windows 10 Enterprise x64
    • General > Limiting collection: All Systems
    • Membership Rules > Add Rule: Direct Rule
    • The Create Direct Membership Rule Wizard opens, click Next
    • Search for Resources > Resource class: System Resource
    • Search for Resources > Attribute name: Name
    • Search for Resources > Value: %
    • Select Resources > Value: Select the computername associated with the PC1 VM
    • Click Next twice and then click Close in both windows (Next, Next, Close, then Next, Next, Close)
  3. Double-click the Install Windows 10 Enterprise x64 device collection and verify that the PC1 computer account is displayed.

  4. In the Software Library workspace, expand Operating Systems, click Task Sequences, right-click Windows 10 Enterprise x64 and then click Deploy.

  5. Use the following settings in the Deploy Software wizard:

    • General > Collection: Click Browse and select Install Windows 10 Enterprise x64
    • Deployment Settings > Purpose: Available
    • Deployment Settings > Make available to the following: Configuration Manager clients, media and PXE
    • Scheduling > Click Next
    • User Experience > Click Next
    • Alerts > Click Next
    • Distribution Points > Click Next
    • Summary > Click Next
    • Verify that the wizard completed successfully and then click Close

Associate PC4 with PC1

  1. On SRV1 in the Configuration Manager console, in the Assets and Compliance workspace, right-click Devices and then click Import Computer Information.

  2. On the Select Source page, choose Import single computer and click Next.

  3. On the Single Computer page, use the following settings:

    • Computer Name: PC4
    • MAC Address: DFF
    • Source Computer: <type the hostname of PC1, or click Search twice, click the hostname, and click OK>
  4. Click Next, and on the User Accounts page choose Capture and restore specified user accounts, then click the yellow starburst next to User accounts to migrate.

  5. Click Browse and then under Enter the object name to select type user1 and click OK twice.

  6. Click the yellow starburst again and repeat the previous step to add the contoso\administrator account.

  7. Click Next twice, and on the Choose Target Collection page, choose Add computers to the following collection, click Browse, choose Install Windows 10 Enterprise x64, click OK, click Next twice, and then click Close.

  8. In the Assets and Compliance workspace, click User State Migration and review the computer association in the display pane. The source computer will be the computername of PC1 (GREGLIN-PC1 in this example), the destination computer will be PC4, and the migration type will be side-by-side.

  9. Right-click the association in the display pane and then click Specify User Accounts. You can add or remove user account here. Click OK.

  10. Right-click the association in the display pane and then click View Recovery Information. Note that a recovery key has been assigned, but a user state store location has not. Click Close.

  11. Click Device Collections and then double-click Install Windows 10 Enterprise x64. Verify that PC4 is displayed in the collection. You might have to update and refresh the collection, or wait a few minutes, but do not proceed until PC4 is available. See the following example:

    collection.

Create a device collection for PC1

  1. On SRV1, in the Configuration Manager console, in the Assets and Compliance workspace, right-click Device Collections and then click Create Device Collection.

  2. Use the following settings in the Create Device Collection Wizard:

    • General > Name: USMT Backup (Replace)
    • General > Limiting collection: All Systems
    • Membership Rules > Add Rule: Direct Rule
    • The Create Direct Membership Rule Wizard opens, click Next
    • Search for Resources > Resource class: System Resource
    • Search for Resources > Attribute name: Name
    • Search for Resources > Value: %
    • Select Resources > Value: Select the computername associated with the PC1 VM (GREGLIN-PC1 in this example).
    • Click Next twice and then click Close in both windows.
  3. Click Device Collections and then double-click USMT Backup (Replace). Verify that the computer name/hostname associated with PC1 is displayed in the collection. Do not proceed until this name is displayed.

Create a new deployment

In the Configuration Manager console, in the Software Library workspace under Operating Systems, click Task Sequences, right-click Replace Task Sequence, click Deploy, and use the following settings:

  • General > Collection: USMT Backup (Replace)
  • Deployment Settings > Purpose: Available
  • Deployment Settings > Make available to the following: Only Configuration Manager Clients
  • Scheduling: Click Next
  • User Experience: Click Next
  • Alerts: Click Next
  • Distribution Points: Click Next
  • Click Next and then click Close.

Verify the backup

  1. On PC1, open the Configuration Manager control panel applet by typing the following command in a command prompt:

  2. On the Actions tab, click Machine Policy Retrieval & Evaluation Cycle, click Run Now, click OK, and then click OK again. This is one method that can be used to run a task sequence in addition to the Client Notification method that will be demonstrated in the computer refresh procedure.

  3. Type the following at an elevated command prompt to open the Software Center:

  4. In the Software Center , click Available Software and then select the Replace Task Sequence checkbox. See the following example:

    software.

    If you do not see any available software, try running step #2 again to start the Machine Policy Retrieval & Evaluation Cycle. You should see an alert that new software is available.

  5. Click INSTALL SELECTED and then click INSTALL OPERATING SYSTEM.

  6. Allow the Replace Task Sequence to complete, then verify that the C:\MigData folder on SRV1 contains the USMT backup.

Deploy the new computer

  1. Start PC4 and press ENTER for a network boot when prompted. To start PC4, type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

  2. In the Welcome to the Task Sequence Wizard, enter [email protected] and click Next.

  3. Choose the Windows 10 Enterprise X64 image.

  4. Setup will install the operating system using the Windows 10 Enterprise x64 reference image, install the configuration manager client, join PC4 to the domain, and restore users and settings from PC1.

  5. Save checkpoints for all VMs if you wish to review their status at a later date. This is not required (checkpoints do take up space on the Hyper-V host). Note: the next procedure will install a new OS on PC1 update its status in Configuration Manager and in Active Directory as a Windows 10 device, so you cannot return to a previous checkpoint only on the PC1 VM without a conflict. Therefore, if you do create a checkpoint, you should do this for all VMs.

    To save a checkpoint for all VMs, type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

Refresh a client with Windows 10 using Configuration Manager

Initiate the computer refresh

  1. On SRV1, in the Assets and Compliance workspace, click Device Collections and then double-click Install Windows 10 Enterprise x64.

  2. Right-click the computer account for PC1, point to Client Notification, click Download Computer Policy, and click OK in the popup dialog box.

  3. On PC1, in the notification area, click New software is available and then click Open Software Center.

  4. In the Software Center, click Operating Systems, click Windows 10 Enterprise x64, click Install and then click INSTALL OPERATING SYSTEM. See the following example:

    installOS.

    The computer will restart several times during the installation process. Installation includes downloading updates, reinstalling the Configuration Manager Client Agent, and restoring the user state. You can view status of the installation in the Configuration Manager console by accessing the Monitoring workspace, clicking Deployments, and then double-clicking the deployment associated with the Install Windows 10 Enterprise x64 collection. Under Asset Details, right-click the device and then click More Details. Click the Status tab to see a list of tasks that have been performed. See the following example:

    asset.

    You can also monitor progress of the installation by using the MDT deployment workbench and viewing the Monitoring node under Deployment Shares\MDT Production.

    When installation has completed, sign in using the contoso\administrator account or the contoso\user1 account and verify that applications and settings have been successfully backed up and restored to your new Windows 10 Enterprise operating system.

    post-refresh.

Related Topics

System Center Configuration Manager Survival Guide

Feedback

View all page feedback

Sours: https://docs.microsoft.com/en-us/windows/deployment/windowspoc-sc-config-mgr
  1. Open tabs on my phone
  2. 48forty solutions nashville tn
  3. Kirkland sliced almonds
  4. Writing equations of exponential functions

The Blog

This blog post is a complete SCCM Windows 10 Deployment Guide. It contains all you need to know for a successful Windows 10 Deployment. The race to update Windows 7 computers from your environment is entering its home stretch. Microsoft has ended Windows 7 support on January 14th, If you still have Windows 7 computers in your company, it&#;s time to seriously plan your migration. If you&#;ve been reading our blog for a while, you may have seen a couple of posts regarding Windows 10 migration. We thought that regrouping all posts in a single one would save you time finding all needed SCCM Windows 10 deployments resources to start.

SCCM Windows 10 Deployment Guide

If you are still running SCCM and have plans to deploy Windows 10, we recommend starting with part 2 of this guide. (Hint: Deploy SCCM Current Branch).

If you&#;re already running SCCM Current Branch, start by creating a Windows 7 Upgrade Task Sequence. Upgrading Windows 7 to Windows 10 is not a complicated task, but it needs proper planning. You can use Desktop Analytics to help you with the applications and driver&#;s compatibility.

We will update this post as we add more parts to our SCCM Windows 10 deployments guide on our blog.

Download and own this SCCM Windows 10 Deployment Guide in a single PDF file.

The PDF file is a pages document that contains all you need to know for a successful Windows 10 Deployment.. Use our products page or use the button below to download it .

Download the FREE guide

SCCM Windows 10 Deployment Guide

Part 1 | Windows 10 Resources

Before starting a Windows 10 migration project, it’s always a good idea to be informed. There was so much information about Windows 10 in the past year: the OS itself has a couple of new features that you need to first understand. Your infrastructure needs various updates before you can start managing Windows 10 devices. The Windows 10 servicing options are also a huge chunk to understand. This can be overwhelming at first so we decided to compile a list of documentation that we found helpful during our multiple deployment projects.

Come back often as this list will continue to grow with time as Microsoft releases interesting documentation on a weekly basis.

GENERAL DOCUMENTATION

Huge compiled list of documentation provided by Microsoft about various topics :

Introduction to the new Windows 10 device management strategies:

Windows 10 release are frequent, it may be hard to follow. This page keep track of all update history :

An overview of requirements, editions, and languages available for Windows 10 :

WINDOWS 10 NEW FEATURES

Find out what’s new in Windows 10 and get an overview of key features for IT professionals :

WINDOWS 10 IMPROVEMENTS

Learn about the improvements in Windows 10 :

EDUCATION

Take advantage of free, online training courses from Microsoft Virtual Academy and walk through the latest features and functionality.

UPDATE YOUR DEPLOYMENT SKILLS

Familiarize with the latest deployment strategies, and download free tools to ease the deployment process.

DEVICE MANAGEMENT

Learn new policies for devices that are running Windows This post include new GPO and MDM policies

WINDOWS 10 SERVICING

This post is the post to go if you need to understand CBB and LTSB editions. It’s also an absolute must to understand the different Windows 10 servicing options :

DOWNLOAD WINDOWS 10

Links for downloading a Windows 10 media to get started :

PREPARE FOR DEPLOYMENT

There are specific infrastructure requirements to deploy and manage Windows 10 that should be in place prior to significant Windows 10 deployments within your organization. Information about Deployment tools (MDT, SCCM), Management Tools (AD, GPO, WSUS) and Activation tools (KMS) :

Begin the process of evaluating the impact of application compatibility in your deployment project :

Understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task :

UPGRADE TO WINDOWS 10 WITH SYSTEM CENTER CONFIGURATION MANAGER

Learn how to upgrade to Windows 10 using MDT and Configuration Manager :

WINDOWS 10 CUSTOMIZATION

Read about Windows 10 customizing options by reading our blog posts :

WINDOWS 10 SERVICING USING SYSTEM CENTER CONFIGURATION MANAGER

Everything you need to know to manage Windows 10 as a service :

WINDOWS 10 REPORTS

Use our report to has better visibility of Windows 10 devices in your organisation :

In the first part of this blog series on how to deploy Windows 10 with SCCM, we will prepare our environment for Windows If you’re already deploying other operating systems with SCCM , adding Windows 10 is just a matter of adding a new WIM (which our post covers in part 4). If you’re new to deploying operating system with SCCM, follow this post which will covers all steps needed before you can deploy your first systems.

Part 2 | OVERVIEW SCCM WINDOWS 10 DEPLOYMENT

  1. Upgrade to SCCM
  2. Enable PXE Support
  3. Prepare your boot image
  4. Prepare your Operating Systems
  5. Create your SUG
  6. USMT Packages

UPGRADE TO SCCM

It’s possible to manage Windows 10 with SCCM  but when it comes to deploying Windows 10, if you want to use the full features, you need SCCM and further. Follow our guide to upgrade your SCCM server and make sure that you are upgrading your Windows ADK version which is included in the upgrade process.

ENABLE PXE SUPPORT

Follow these steps if you want to deploy your images using PXE boot (recommended)

  • Open the SCCM Console
  • Go to Administration / Site Configuration / Servers and Site System Roles
  • Select your distribution point and right-click on the Distribution point role on the bottom, select Properties
SCCM Windows 10 deployment
  • Select the PXE tab
  • Enable the Enable PXE support for Clients check-boxandanswer Yes when prompted about firewall ports (UDP ports 67, 68, 69 and )
SCCM Windows 10 deployment
  • Check the Allow this distribution point to respond to incoming PXE requests check box
  • Check the Enable unknown computer support check box
  • Ensure that the Respond to PXE request on all network interfaces is selected
  • Click Ok
SCCM Windows 10 deployment

Your distribution point will now install Windows Deployment Services (if not already installed) and will copy the necessary files on the distribution point.

You can monitor this process in the SCCM Console :

  • Go to Monitoring / Distribution Status / Distribution Point Configuration Status
  • Click your distribution point on the top and select the Details tab on the bottom
  • You will see that the distribution point PXE settings has changed
SCCM Windows 10 deployment

PREPARE YOUR BOOT IMAGE

[su_box title=”Important note” style=”glass” title_color=”#F0F0F0″]If you have created any custom boot images in previous version, you won’t be able to manage it (customize, add drivers, ect…) through the SCCM console. The only manageable version would be PE10 images. Other version could still be used but you’ll have to manage them outside the console using DISM.[/su_box]

DRIVERS

Before launching your first boot image you must include your Windows 10 drivers into the boot image. Our rule of thumb about drivers is to try to boot a certain model and if it fails, add the drivers. Do not add all your NIC drivers to your boot image, it’s overkill and unnecessary increase the size of the boot image.

To add drivers to the boot image :

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Boot Images
  • Right-click your Boot Image, select Properties
  • Select the Drivers tab
SCCM Windows 10 deployment
  • Click the Star icon
  • Select the desired drivers and click OK
SCCM Windows 10 deployment
  • The selected drivers are added to the boot image, once you click OK, SCCM will inject the driver in your boot image
SCCM Windows 10 deployment

Windows 10 CUSTOMIZATION

We will now make a couple customization to the boot image to enable command support (F8) and add a custom background image to the deployment

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Boot Images
  • Right-click your Boot Image
  • Select the Customization tab
  • Check the Enable command support checkbox. This allows to have the F8 command line support during deployment
  • Specify a custom background if needed by checking Specify the custom background image file checkbox
SCCM Windows 10 deployment
  • If you’re using a PXE-enable distribution point, select the Data Source tab and check the Deploy this boot image from the PXE-Enabled distributon point checkbox
  • Click Apply and Yes to the warning, close the window
SCCM Windows 10 deployment

DISTRIBUTE YOUR BOOT IMAGE

Since you’ve upgraded your ADK to version 10 and made modifications to your boot image, you need to redistribute it to your distribution points.

  • Right click your boot image and select Update Distribution Points
SCCM Windows 10 deployment

PREPARE YOUR OPERATING SYSTEMS

We will now import the Windows 10 WIM file for Windows 10 deployment.

[su_box title=”Important” style=”glass” title_color=”#F0F0F0″]You’ll see bothOperating System ImagesandOperating System Upgrade Packages.One is to import .WIM files and the other one is for Full Media. We will need both for different scenarios. In the case of a vanilla deployment or after a build and capture, you useOperating System Imagesto import the WIM files. In an Upgrade task Sequence, you will need to have the Full media imported inOperating System Upgrade Packages.[/su_box]

We will start by importing the default Install.Wim from the Windows 10 media for a “vanilla” Windows 10 deployment. You could also import a WIM file that you’ve created through a build and capture process.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Images
  • Right click Operating System Images and select Add Operating System Image
SCCM Windows 10 deployment
  • On the Data Source tab, browse to your WIM file. The path must be in UNC format
SCCM Windows 10 deployment
  • In the General tab, enter the Name, Version and Comment, click Next
SCCM Windows 10 deployment
  • On the Summary tab, review your information and click Next
SCCM Windows 10 deployment
  • Complete the wizard and close this window
SCCM Windows 10 deployment

DISTRIBUTE YOUR OPERATING SYSTEM IMAGE

We now need to send the Operating System Image (WIM file) to our distribution points.

  • Right click your Operating System Image, select Distribute Content and complete the Distribute Content wizard
SCCM Windows 10 deployment

We will now import the complete Windows 10 media in Operating System Upgrade Packages. This package will be used to upgrade a Windows 7 (or ) device to Windows 10 using an Upgrade Task Sequence.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Upgrade Packages
  • Right click Operating System Upgrade Packages and select Add Operating System Upgrade Packages
SCCM Windows 10 deployment
  • In the Data Source tab, browse to the path of your full Windows 10 media. The path must point on an extracted source of a ISO file. You need to point at the top folder where Setup.exe reside
SCCM Windows 10 deployment
SCCM Windows 10 deployment
  • In the General tab, enter the Name, Version and Comment, click Next
SCCM Windows 10 deployment
  • On the Summary tab, review your information and click Next
SCCM Windows 10 deployment
  • Complete the wizard and close this window
SCCM Windows 10 deployment

DISTRIBUTE YOUR OPERATING SYSTEM UPGRADE PACKAGES

We now need to send the Operating System Upgrade Package to your distribution points.

  • Right click your Operating System Upgrade Package, select Distribute Content and complete the Distribute Content wizard
SCCM Windows 10 deployment

CREATE SOFTWARE UPDATE GROUP

One important thing in any OSD project, is to make sure that every machines deployments are up to date. Before deploying Windows 10, make sure that your Software Update Point is configured to include Windows 10 patches.

Once Windows 10 is added to your Software Update Point, we will create a Software Update Group that will be deployed to our Windows 10 deployment collection. This way, all patches released after the Windows 10 media creation (or your Capture date) will be deployed during the deployment process.

To create a Windows 10 Software Update Group :

  • Open the SCCM Console
  • Go to Software Library / Software Updates / All Software Updates
  • On the right side, click Add Criteria, select Product, Expired and Superseded
    • Product : Windows 10
    • Expired  : No
    • Superseded : No
SCCM Windows 10 deployment
  • Select all patches and select Create Software Update Group
SCCM Windows 10 deployment
  • Once created, go to Software Library / Software Updates / Software Update Groups
  • Right-click your Windows 10 SUG and deploy it to your OSD deployment collection

USMT PACKAGE

If you are planning to use USMT to capture and restore user settings and files, you need to make sure that the USMT package is created and distributed.

  • Open the SCCM Console
  • Go to Software Library / Application Management / Packages
  • Right-click the User State Migration Tool for Windows 10 package and select Properties
  • On the Data Source tab, ensure that the package is using the ADK 10 – Which is per default C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool
  • Right-click the User State Migration Tool for Windows 10 package and select Distribute Content
SCCM Windows 10 deployment

That’s it ! You have everything that’s needed to create your first Windows 10 deployment. Read the next parts of this blog series to successfully deploy Windows

Part 3 | CREATE SCCM WINDOWS 10 TASK SEQUENCE

In the second post of this blog series about Windows 10 Deployment using SCCM, we will show you how to create a SCCM Windows 10 Task Sequence and deploy it. Complete the preparation of your environment before reading this post.

This task sequence will help you deploy what we call a “vanilla” Windows 10 using the default Install.wim from the Windows 10 media. This means that you’ll end up with a basic Windows 10 with the SCCM client and nothing else.

You will be able to edit this task sequence later to customize it to your environment.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Create Task Sequence
SCCM Windows 10 Task Sequence
  • On the Task Sequence wizard, select Install an existing image package
SCCM Windows 10 Task Sequence
  • On the Task Sequence Information pane, enter the desired Name, Description and Boot Image
SCCM Windows 10 Task Sequence
  • On the Install Windows pane, select the Image package and Image index you imported in part 1
  • Leave the check box beside Partition and Format the target computer before installing the operating system
  • For this example we will remove the Configure task sequence for use with Bitlocker
  • Leave the Product key blank, if you are using MAK keys, read this post on how to handle that in your Task Sequence. (TL;DR: Even with MAK key, you need to leave the Product key blank)
  • Enter an Administrator password
SCCM Windows 10 Task Sequence
  • In the Configure Network pane, you can select to Join a workgroup or domain. If you select Join a domain, enter your domain information, OU and credentials
SCCM Windows 10 Task Sequence
  • On the Install Configuration Manager Client pane, select your Configuration Manager Client Package and enter your installation properties
SCCM Windows 10 Task Sequence
  • On the State Migration pane, we will remove all checkbox as we don’t want to use User State Migration at this time
SCCM Windows 10 Task Sequence
  • On the Include Updates pane, select the desired Software Update task
    • All Software Updates will install the updates regardless of whether there is a deadline set on the deployment (on your OSD collection)
    • Mandatory Software Updates will only install updates from deployments that have a scheduled deadline (on your OSD collection)
    • Do not install any software updates will not install any software update during the Task Sequence
SCCM Windows 10 Task Sequence
  • On the Install Applications tab, click on the Star Icon to add any application that you want to be installed during your deployment. Only applications will be listed. If you need to add packages, you can add it by editing the task sequence later. Theses applications will be deployed each time the task sequence is executed.
SCCM Windows 10 Task Sequence
  • On the Summary tab, review your settings and click Next
SCCM Windows 10 Task Sequence
  • On the Completion tab, click Close
SCCM Windows 10 Task Sequence

DEPLOY WINDOWS 10 TASK SEQUENCE

Now that your Task Sequence is created, we will deploy it to a collection and start a Windows 10 deployment.[su_box title=”Warning” style=”glass” title_color=”#F0F0F0″]Be careful when targeting the deployment. This task sequence will format and install a new OS to targeted devices.[/su_box]

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click your Windows 10 Task Sequence and select Deploy
SCCM Windows 10 Task Sequence
  • On the General pane, select your collection. This is the collection that will receive the Windows 10 installation. For testing purposes, we recommend putting only 1 computer to start
SCCM Windows 10 Task Sequence
  • Select the Purpose of the deployment
    • Available will prompt the user to install at the desired time
    • Required will force the deployment at the deadline (see Scheduling)
  • In the Make available to the following drop down, select the Only media and PXE. This will ensure that you do not send the deployment on clients. This is also useful to avoid errors, using this options you *could* send the deployment to All Systems and no clients would be able to run the deployment from Windows
SCCM Windows 10 Task Sequence
  • On the Scheduling tab, enter the desired available date and time. On the screenshot, we can’t create an Assignment schedule because we select Available in the previous screen
SCCM Windows 10 Task Sequence
  • In the User Experience pane, select the desired options
SCCM Windows 10 Task Sequence
  • In the Alerts tab, check Create a deployment alert when the threshold is higher than the following checkbox if you want to create an alert on the failures
SCCM Windows 10 Task Sequence
  • On the Distribution Point pane, select the desired Deployment options. We will leave the default options
SCCM Windows 10 Task Sequence
  • Review the selected options and complete the wizard
SCCM Windows 10 Task Sequence
SCCM Windows 10 Task Sequence

PXE BOOT

Now that we’ve created our task sequence and that it’s deployed. We can start the deployment on the machine. Make sure that your system is a member of your deployment collection and start the device. For this example, we will be using a virtual machine running on Hyper-V.

  • The machine is booting and waiting for the PXE to respond
SCCM Windows 10 Task Sequence
  • Our SCCM Distribution point is sending the boot image to our VM
SCCM Windows 10 Task Sequence
  • The Welcome to the Task Sequence Wizard pops-up. This is because of the Available purpose in the Deployment Settings. If we had a Required deployment, the task sequence would start right away. Click Next
SCCM Windows 10 Task Sequence
  • All the available task sequence are listed. In our example we have only 1 deployment on our collection so only 1 task sequence is available. Select the task sequence and click Next
SCCM Windows 10 Task Sequence
SCCM Windows 10 Task Sequence

MONITORING

See our blog post on this topic which covers the various ways to monitor your Task Sequence progress.

Part 4 | CREATE SCCM WINDOWS 10 BUILD AND CAPTURE TASK SEQUENCE

In the third post of this blog series about Windows 10 Deployment using SCCM, we will show you how to create a SCCM Windows 10 Build and Capture Task Sequence and deploy it. Complete the preparation of your environment before reading this post. You will be able to edit this task sequence later to customize it to your environment.

The goal of a build and capture task sequence is to capture a reference machine OS in order to redeploy its configuration multiple time. As a best practice, we recommend not to add too much software and customization to your reference image. Rather, use the task sequence steps to customize your deployment which decrease management operation tasks in the long run.

For example, if you want to include Adobe Reader to your reference image because all your users need it, do not install it on your reference machine and do your capture. Instead, use the Installed Software step in the capture task sequence. When a new version of Adobe Reader will be released, it will be a matter of a couple of clicks to replace the old version with the new one.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Build and capture a reference operating system image
SCCM Windows 10 Build and Capture Task Sequence
  • On the Task Sequence Information tab enter a task sequence Name and Description
  • Select the desired boot image
SCCM Windows 10 Build and Capture Task Sequence
  • On the Install Windows pane, select the Image package and Image index you imported in part 1
  • Leave the Product key blank, if you are using MAK keys, read this post on how to handle that in your Task Sequence. (Hint : Even with MAK key, you need to leave the Product key blank)
  • Enter a password for the local Administrator account
SCCM Windows 10 Build and Capture Task Sequence
  • In the Configure Network pane, select to Join a workgroup. There’s no reason to join a domain when creating a build and capture task sequence. You’ll still be able to join a domain when creating a task sequence to deploy this image
SCCM Windows 10 Build and Capture Task Sequence
  • On the Install Configuration Manager Client pane, select your Configuration Manager Client Package and enter your installation properties
SCCM Windows 10 Build and Capture Task Sequence
  • On the Include Updates pane, select the desired Software Update task
    • All Software Updates will install the updates regardless of whether there is a deadline set on the deployment (on your OSD collection)
    • Mandatory Software Updates will only install updates from deployments that have a scheduled deadline (on your OSD collection)
    • Do not install any software updates will not install any software update during the Task Sequence
SCCM Windows 10 Build and Capture Task Sequence
  • On the Install Applications tab, click on the Star Icon to add any application that you want to be installed during your build and capture deployment. These applications will be part of the reference image, we recommended adding only software that need to be included in every deployment… and even there, I prefer add it to a deployment task sequence rather to include it in my image. The reason is pretty simple, if you need to make an application change, you only have 1 step to change to your task sequence rather than redo the whole build and capture process and then modify your task sequence with the new image. Some likes to add Office or other big applications that every users needs to reduce deployment time.
SCCM Windows 10 Build and Capture Task Sequence
  • On the System Preparation tab, click Next
SCCM Windows 10 Build and Capture Task Sequence
  • On the Image Properties tab, enter the desired information
SCCM Windows 10 Build and Capture Task Sequence
  • On the Capture Image tab, select the path where you want to save the .WIM file
  • Enter the account to access the folder. This account needs write permission
SCCM Windows 10 Build and Capture Task Sequence
  • On the Summary tab, review your choices and complete the wizard
SCCM Windows 10 Build and Capture Task Sequence
SCCM Windows 10 Build and Capture Task Sequence

DEPLOY WINDOWS 10 BUILD AND CAPTURE TASK SEQUENCE

Now that our Task Sequence is created, we will deploy it to a collection and start a Windows 10 Build and capture. It’s strongly recommended to deploy a build and capture on a virtual machine.

Be careful when targeting the deployment. This task sequence will format and install a new OS to targeted devices.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click your Windows 10 Build and Capture Task Sequence and select Deploy
SCCM Windows 10 Build and Capture Task Sequence
  • On the General pane, select your build and capture collection. This is the collection that will receive the Windows 10 installation and be captured to create the new WIM file
SCCM Windows 10 Build and Capture Task Sequence
  • Select the Purpose of the deployment
    • Available will prompt the user to install at the desired time
    • Required will force the deployment at the deadline (see Scheduling)
  • In the Make available to the following drop down, select the Only media and PXE. This will ensure that you do not send the deployment on clients. This is also useful to avoid errors, using this options you *could* send the deployment to All Systems and no clients would be able to run the deployment from Windows
SCCM Windows 10 Build and Capture Task Sequence
  • On the Scheduling tab, enter the desired available date and time. On the screenshot, we can’t create an Assignment schedule because we select Available in the previous screen
SCCM Windows 10 Build and Capture Task Sequence
  • In the User Experience pane, select the desired options
SCCM Windows 10 Build and Capture Task Sequence
  • In the Alerts tab, check Create a deployment alert when the threshold is higher than the following checkbox if you want to create an alert on the failures
SCCM Windows 10 Build and Capture Task Sequence
  • On the Distribution Point pane, select the desired Deployment options. We will leave the default options
SCCM Windows 10 Build and Capture Task Sequence
  • Review the selected options and complete the wizard
SCCM Windows 10 Build and Capture Task Sequence
SCCM Windows 10 Build and Capture Task Sequence

PXE BOOT

Now that we’ve created our task sequence and that it’s deployed. We can start the deployment on the machine. Make sure that the system you want to capture is a member of your deployment collection and start the device. (See this Technet article to know how to import a computer).

For this example, we will be using a virtual machine running on Hyper-V.

  • The machine is booting and waiting for the PXE to respond
SCCM Windows 10 Task Sequence
  • Our SCCM Distribution point is sending the boot image to our VM
SCCM Windows 10 Task Sequence
  • The Welcome to the Task Sequence Wizard pops-up. This is because of the Available purpose in the Deployment Settings. If we had a Required deployment, the task sequence would start right away. Click Next
SCCM Windows 10 Build and Capture Task Sequence
  • All the available task sequence are listed. In our example we have our deployment and our build and capture task sequence. Select the Build and Capture task sequence and click Next
SCCM Windows 10 Build and Capture Task Sequence
SCCM Windows 10 Build and Capture Task Sequence

MONITORING

See our blog post on this topic which covers the various ways to monitor your task sequence progress.

Part 5 | MONITOR SCCM TASK SEQUENCE USING THE CONSOLE

When deploying Windows 10 operating system using SCCM, you will need to monitor SCCM task sequence progress. This allows us to track task sequence start, end time and most importantly errors (if any). Our post will show 4 different ways to monitor SCCM task sequences. Each of them has its own benefits and drawbacks.

You can view the progress of a task sequence using the SCCM console. This method is simple and easy but permit to see the status of only one machine at the time. If your deployment staff don’t have access to the console or view deployment status, this option is not for you.

  • Open the SCCM Console
  • Go to Monitoring / Deployments
  • Search and right-click the deployment linked to your Windows 10 task sequence
  • On the menu, select View Status
Monitor SCCM Task Sequence
  • In the Deployment Status screen, select the In Progress tab for a running task sequence or the Success tab to review a completed task sequence
  • At the bottom, click the Asset Details pane, right-click your device and select More Details
Monitor SCCM Task Sequence
  • On the Asset Message screen, click the Status tab
  • You can view all task sequence Action Name with their Last Message Name
Monitor SCCM Task Sequence

CONSOLE STATUS MESSAGE QUERIES

You can use Status Message Queries in the SCCM console to filter only task sequence messages. This method is useful to have messages from multiple devices instead of targeting a specific computer like in the previous methods. This method is a bit trickier to implement.

  • The first step is to get the DeploymentID of your task sequence deployment
  • Go to Monitoring / Deployments
  • Add the DeploymentID column by right-clicking the top row. Note your DeploymentID, in our example B
Monitor SCCM Task Sequence
  • Go to Monitoring / System Status / Status Message Queries
  • Right-click Status Message Queries and select Create Status Message Query
Monitor SCCM Task Sequence
  • On the General tab, enter a desired Name and click on Edit Query Statement
Monitor SCCM Task Sequence
  • On the Query Statement Properties window, click on Show Query Language
Monitor SCCM Task Sequence
  • Enter the following query in the Query Statement window
[su_box title=”Query” style=”glass” title_color=”#F0F0F0″]select SMS_StatusMessage.*,SMS_StatMsgInsStrings.*,SMS_StatMsgAttributes.*,SMS_StatMsgAttributes.AttributeTimefrom SMS_StatusMessageleft join SMS_StatMsgInsStrings on SMS_StatMsgInsStrings.RecordID = SMS_StatusMessage.RecordIDleft join SMS_StatMsgAttributes on SMS_StatMsgAttributes.RecordID = SMS_StatusMessage.RecordIDwhere SMS_StatMsgAttributes.AttributeID = and SMS_StatMsgAttributes.AttributeValue = “B” and SMS_StatMsgAttributes.AttributeTime >= ##PRM:SMS_StatMsgAttributes.AttributeTime##order by SMS_StatMsgAttributes.AttributeTime DESC[/su_box]
  • Change the SMS_StatMsgAttributes.AttributeValue to reflect your DeploymentID
Monitor SCCM Task Sequence
  • Click OK
  • In the Status Message Queries node, find your newly created Query, right-click on it and select Show Messages
Monitor SCCM Task Sequence
  • Select the desired Date and Time and click OK
Monitor SCCM Task Sequence
  • All messages from your selected deployment will be displayed for all devices that run it
Monitor SCCM Task Sequence

SCCM BUILT-IN REPORTS

There’s 28 built-in reports concerning task sequence in SCCM. The majority of the reports focus on statistics about overall deployments. To monitor progress, we refer to the 2 following reports :

  • Task Sequence – Deployment Status / Status of a specific task sequence deployment for a specific computer
    • This report shows the status summary of a specific task sequence deployment on a specific computer.
Monitor SCCM Task Sequence
  • Task Sequence – Deployment Status / History of a task sequence deployment on a computer
    • This report displays the status of each step of the specified task sequence deployment on the specified destination computer. If no record is returned, the task sequence has not started on the computer.
Monitor SCCM Task Sequence

As you can see, readability is easier using the console but keep in mind that reports can be accessible without having console access.

 OUR SCCM OSD REPORT

We offer a report for you to buy to keep track of your Windows 10 deployment. The report gives you all the information needed to keep track of a deployment.

You can find the report on our product page or directly on the SCCM Windows 10 Report product page

SMSTS.LOG

Last method we want to cover to monitor Windows 10 task sequence deployment is using the SMSTS.log file. This is the method you’ll want to use when you have a failing task sequence. The SMSTS.log file contains every details about every steps in your task sequence. It’s the first place to look to troubleshoot a problem with a specific deployment.

The downside of this file is that it’s stored locally on the computer (by default). Another downside is that this file location change depending on the stage you are at :

In Windows PE – Before the hard disk is formatted X:\Windows\Temp\Smstslog\Smsts.log
In Windows PE – After the hard disk is formattedX:\Smstslog\Smsts.log and C:\_SMSTaskSequence\Logs\Smstslog\Smsts.log
In Windows – Before the SCCM client is installedC:\_SMSTaskSequence\Logs\Smstslog\Smsts.log
In Windows – After the SCCM client is installedC:\Windows\Ccm\Logs\Smstslog\Smsts.log
In Windows – When the Task Sequence is completeC:\Windows\Ccm\Logs\Smsts.log
  • Connect on the computer you want to troubleshoot
  • Press the F8 key. A command prompt will open. If you have no command prompt by pressing F8, consult our Preparation post to enable Command Line support in your Boot image
  • In the command windows, enter CMTrace to open the log viewer (it’s included by default in the latest WinPE version)
Monitor SCCM Task Sequence
  • Browse to the location when the file reside (see above table)
Monitor SCCM Task Sequence
  • The SMSTS.log opens and you can search for errors
Monitor SCCM Task Sequence

There’s also methods to redirect your SMSTS.log automatically to a network share which could help :

We hope this post will ease your Windows 10 deployments. Leave your comments and questions in the comment section.

Part 6 | SCCM WINDOWS 7 TASK SEQUENCE UPGRADE

In the fourth post of this blog series about Windows 10 Deployment using SCCM, we will show you how to upgrade Windows 7 to Windows computer 10 using SCCM task sequence upgrade.

The goal of an upgrade task sequence is to upgrade an existing operating system to Windows 10 without loosing any data and installed software. This post assumes that you are running SCCM  or SCCM  and that you completed the preparation of your environment for Windows

If you are running SCCM R2 SP1, the product team has release important information about SCCM task sequence upgrade that you can find in this blog post.

In the past, an in-place upgrade scenario was not a reliable and popular option to deploy the latest version of Windows. With Windows 10, it’s now reliable and features an automatic rollback in case something goes wrong. This scenario can also be considered faster than the wipe and reload deployment scenarios, since applications and drivers don’t need to be reinstalled.

WHEN TO USE WINDOWS 7 IN-PLACE UPGRADE SCENARIO ?

Consider using SCCM upgrade task sequence if :

  • You need to keep all existing applications and settings on a device
  • You need to migrate Windows 10 to a later Windows 10 release (ex: to )
  • You don’t need to change the system architecture (32 bits to 64 bits)
  • You don’t need to change the operating system base language
  • You don’t need to downgrade a SKU (Enterprise to Pro). The only supported path is Pro to Enterprise or Enterprise to Enterprise)
  • You don’t need to change the BIOS architecture from legacy to UEFI
  • You don’t have multi-boot configuration

Windows 10 is now managed as a service, this upgrade process can also be used to migrate Windows 10 to a later Windows 10 release or you can use the new Windows 10 servicing feature in SCCM and later.

POSSIBLE UPGRADE PATH WHEN USING SCCM WINDOWS 7 TASK SEQUENCE UPGRADE

  • Windows 7, Windows 8 and Windows can use this method to upgrade to Windows 10
  • You can’t upgrade a Windows XP or Windows Vista computer to Windows 10
  • Windows 10 is the only final destination OS (You can’t upgrade a Windows 7 to Windows using this method)

REQUIREMENTS

  • As stated in the start of this blog post, you need at least SCCM R2 SP1 (or SCCM SP2) to support the upgrade task sequence
  • You cannot use a custom image for this scenario, you must start from the original WIM from the Windows 10 media
[su_box title=”Device using disk encryption” style=”glass” title_color=”#F0F0F0″]Devices using Bitlocker can be upgraded to Windows 10 using this method. If you are using third-party disk encryption product, it can be done but you need far more effort.[/su_box]

Three major vendors have supported workarounds documented on their support sites :

UNDERSTANDING THE IN-PLACE UPGRADE PROCESS

If you want to understand all the phases in the upgrade process, we strongly recommend watching the Upgrading to Windows In Depth video from the last Microsoft Ignite event.

CREATE SCCM TASK SEQUENCE UPGRADE WINDOWS 7 TO WINDOWS 10

Enough writing, let’s create a SCCM task sequence upgrade for a Windows 7 deployment.

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Upgrade an operating system from upgrade package
SCCM Task Sequence Upgrade
  • In the Task Sequence Information tab, enter a Task Sequence Name and Description
SCCM Task Sequence Upgrade
  • On the Upgrade the Windows Operating System tab, select your upgrade package by using the Browse button. If you don’t have imported an upgrade package yet, use the step provided in our preparation blog post
SCCM Task Sequence Upgrade
  • On the Include Updates tab, select the desired Software Update task
    • All Software Updates will install the updates regardless of whether there is a deadline set on the deployment (on your OSD collection)
    • Mandatory Software Updates will only install updates from deployments that have a scheduled deadline (on your OSD collection)
    • Do not install any software updates will not install any software update during the Task Sequence
SCCM Task Sequence Upgrade
  • On the Install Applications tab, select any application you want to add to your upgrade process
SCCM Task Sequence Upgrade
  • On the Summary tab, review your choices and click Next
SCCM Task Sequence Upgrade
  • On the Competition tab, click Close
SCCM Task Sequence Upgrade

EDIT THE SCCM TASK SEQUENCE UPGRADE

Now that we have created the task sequence, let’s see what it looks like under the hood:

  • Open the SCCM Console
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click your upgrade task sequences and select Edit

As you can see, it’s fairly simple. SCCM will take care of everything in a couple of steps :

SCCM Task Sequence Upgrade
  • The Upgrade Operating System step contains the important step of applying Windows 10
SCCM Task Sequence Upgrade

DEPLOY THE SCCM WINDOWS 7 UPGRADE TASK SEQUENCE

We are now ready to deploy our task sequence to the computer we want to upgrade. In our case, we are targeting a Windows 7 computer.

  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click Task Sequences and select Deploy
SCCM Task Sequence Upgrade
  • On the General pane, select your collection. This is the collection that will receive the Windows 10 upgrade. For testing purposes, we recommend putting only 1 computer to start
SCCM Task Sequence Upgrade
  • On the Deployment Settings tab, select the Purpose of the deployment
    • Available will prompt the user to install at the desired time
    • Required will force the deployment at the deadline (see Scheduling)
  • You cannot change the Make available to the following drop-down since upgrade packages are available to client only
SCCM Task Sequence Upgrade
  • On the Scheduling tab, enter the desired available date and time. On the screenshot, we can’t create an Assignment schedule because we select Available in the previous screen
SCCM Task Sequence Upgrade
  • In the User Experience pane, select the desired options
SCCM Task Sequence Upgrade
  • In the Alerts tab, check Create a deployment alert when the threshold is higher than the following check-box if you want to create an alert on the failures
SCCM Task Sequence Upgrade
  • On the Distribution Point pane, select the desired Deployment options. We will leave the default options
SCCM Task Sequence Upgrade
  • Review the selected options and complete the wizard
SCCM Task Sequence Upgrade

LAUNCH THE UPGRADE PROCESS

Now that our upgrade task sequence is deployed to our clients, we will log on our Windows 7 computer and launch a Machine Policy Retrieval & Evaluation Cycle from Control Panel / Configration Manager Icon

SCCM Task Sequence Upgrade
  • Open the new Software Center from the Windows 7 Start Menu
  • You’ll see the SCCM upgrade task sequence as available. We could have selected the Required option in our deployment schedule, to launch automatically without user interaction at a specific time
SCCM Task Sequence Upgrade
  • When ready, click on Install
SCCM Task Sequence Upgrade
  • The following warning appears
SCCM Task Sequence Upgrade
[su_box title=”Warning” style=”glass” title_color=”#F0F0F0″]TheWhen you install a new operating system, all the existing data on your computer will be removedwarning is not true. This issue will be resolved in future release.[/su_box]
  • Click on Install Operating System
  • The update is starting, the task sequence Installation Progress screen shows the different steps
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
  • The WIM is downloading on the computer and saved in C:\_SMSTaskSequence
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
  • You can follow task sequence progress in C:\Windows\CCM\Logs\SMSTSLog\SMSTS.log
SCCM Task Sequence Upgrade
  • After downloading, the system will reboot
SCCM Task Sequence Upgrade
  • The computer restart and is loading the files in preparation of the Windows 10 upgrade
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
  • The upgrade process starts. This step should take about 15 to 30 minutes depending of the device hardware
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
SCCM Task Sequence Upgrade
  • Windows 10 is getting ready, more minutes and the upgrade will be completed
SCCM Task Sequence Upgrade
  • Once completed the SetupComplete.cmd script runs. This step is important to set the task sequence service to the correct state
SCCM Task Sequence Upgrade
  • Windows is now ready, all software and settings are preserved
SCCM Task Sequence Upgrade

Part 7 | SCCM WINDOWS 10 CUSTOMIZATION

In this post we will describe how to customize your windows 10 image to personalize it to your company. There’s an infinite amount of customization that can be made but i’ll try to cover the more frequent one, those that are asked 95% of every Windows 10 projects I was involved in. You could also do all those modifications through group policies if you want to enforce those settings.

Before we begin any customization, we will create a Windows 10 Customization package that we will use in our task sequence. It will be empty to start but we will create the folders and scripts during this blog post.

  • Open the SCCM Console
  • Go to Software Library / Application Management / Packages
  • Create a new package
  • On the Package tab, enter a Name, Description, Manufacturer and Source folder (this is where all scripts will be stored)
SCCM Windows 10 customization
  • On the Program Type tab, select Do not create a program
SCCM Windows 10 customization
  • On the Summary tab, review your choices and complete the wizard
SCCM Windows 10 customization

FILE ASSOCIATION

The first item we will be covering is file association. By default, Windows 10 uses Microsoft Edge to open every PDF files and HTTP links. For this post, we will redirect PDF files to Adobe Reader and HTTP/HTTPS to Internet Explorer. You can redirect any extension to any software. You just need to make sure that the application that you associate is installed during your Windows 10 deployment (or in your image).

The first step is to make the association manually, we will then export the configuration to a XML file and we will use DISM in our task sequence to import the configuration.

  • Log on a Windows 10 machine
  • Open Control Panel / Programs / Default Programs / Set Associations
SCCM Windows 10 customization
  • Navigate to .PDF and click on Change Program
SCCM Windows 10 customization
  • Select Adobe Reader and click OK
SCCM Windows 10 customization
  • Your .PDF files are now associated to Adobe Reader
  • For Internet Explorer association, select HTTP Protocol, .HTM and .HTML files, change program to Internet Explorer

Now that our associations has been done, we need to export the associations to a XML file using DISM :

  • Open an elevated command prompt
  • Run the following command : Dism /Online /Export-DefaultAppAssociations:C:\Temp\SCDAppAssoc.xml
    • (Change the XML file name and path if desired but make sure that the directory exists or you’ll get an error code 3)
SCCM Windows 10 customization

The XML file can be opened using any text editor. You can see our modifications has been made. It’s possible to change manually in this file but it’s a bit tricky to find ProdId and ApplicationName.

SCCM Windows 10 customization
  • Copy the XML file to your Windows 10 customization package in the FileAssociations Folder
SCCM Windows 10 customization
  • Open the SCCM Console and browse to Packages
  • Right-click your Windows 10 Customization package and select Update Distribution Point
SCCM Windows 10 customization
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click and Edit your Windows 10 task sequence
  • Select Add / General / Run Command Line
    • Name : Set File Association
    • Command line : Dism.exe /online /Import-DefaultAppAssociations:FileAssociations\SCDAppAssoc.xml
    • Check the Package box and specify your Windows 10 customization package
  • Position this step after the Windows image has been deployed
SCCM Windows 10 customization

SETTING THE DEFAULT WINDOWS 10 WALLPAPER

We will now change the default Windows 10 wallpaper to a corporate one.

  • The default Windows 10 wallpapers are stored in the C:\Windows\Web\Wallpaper\Windows\ folder
  • Windows 10 also support 4K wallpapers which are stored in C:\Windows\Web\4K\Wallpaper\Windows
SCCM Windows 10 customization
SCCM Windows 10 customization

For our post, we will delete the 4K wallpapers and overwrite the default img0.jpg file. If you need to support 4K wallpaper, just place them in the 4K folder before updating your distribution points and the script will copy it to the right location.

By default, you can’t modify those files, we will use a PowerShell script to change the security of the folder and overwrite the wallpaper file. We will grant access to the SYSTEM account since it’s the account used during the SCCM task sequence.

  • Create a new WallPaper\DefaultRes and WallPaper\4K folder in your Windows 10 customization directory
  • Rename your wallpaper to img0.jpg copy it in the WallPaper\DefaultRes directory
  • If 4K support is needed, copy your files in the WallPaper\4K Directory

Create a new Powershell script in the root of the Wallpaper directory and copy this code into it :

Powershell Script

takeown /f c:\windows\WEB\wallpaper\Windows\img0.jpg
takeown /f C:\Windows\Web\4K\Wallpaper\Windows\*.*
icacls c:\windows\WEB\wallpaper\Windows\img0.jpg /Grant ‘System:(F)’
icacls C:\Windows\Web\4K\Wallpaper\Windows\*.* /Grant ‘System:(F)’
Remove-Item c:\windows\WEB\wallpaper\Windows\img0.jpg
Remove-Item C:\Windows\Web\4K\Wallpaper\Windows\*.*
Copy-Item $PSScriptRoot\img0.jpg c:\windows\WEB\wallpaper\Windows\img0.jpg
Copy-Item $PSScriptRoot\4k\*.* C:\Windows\Web\4K\Wallpaper\Windows

You’ll end up with the following structure :

SCCM Windows 10 customization
  • Open the SCCM Console and browse to Packages
  • Right-click your Windows 10 Customization package and select Update Distribution Point
SCCM Windows 10 customization
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click and Edit your Windows 10 task sequence
  • Select Add / General / Run PowerShell Script
    • Name : Set Wallpaper
    • Script Name : Wallpaper\ChangeWallpaper.ps1
    • PowerShell execution policy : Bypass
  • Position this step after the Windows image has been deployed
SCCM Windows 10 customization

CHANGE LOCK SCREEN IMAGE

The lock screen image is the image you see when the computer is locked. To change it, we must copy our image locally on the computer and then modify a registry key to read it.

  • Create a new LockScreen folder in your Windows 10 customization directory
  • Create a new LockScreen.cmd file and copy the following code

LockScreen.cmd

xcopy LockScreen\LockScreen.jpg C:\SCD\LockScreen\ /Y /S
reg import LockScreen\LockScreen.reg
reg import LockScreen\LockScreen.reg /reg

  • Create a new LockScreen.reg file and copy the following code (watch out of the “” when copy/pasting)

LockScreen.reg

Windows Registry Editor Version [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization] &#;LockScreenImage&#;=&#;C:\\SCD\\LockScreen\\LockScreen.jpg&#;

  • Copy the image you want to set as the lock screen. For this blog post we will call it LockScreen.jpg. If you rename this file, make sure to change the script to fit this name.

You’ll end up with the following structure :

SCCM Windows 10 customization
  • Open the SCCM Console and browse to Packages
  • Right-click your Windows 10 Customization package and select Update Distribution Point
SCCM Windows 10 customization
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click and Edit your Windows 10 task sequence
  • Select Add / General / Run Command Line
    • Name : Set File Association
    • Command line : cmd.exe /c LockScreen\LockScreen.cmd
    • Check the Package box and specify your Windows 10 customization package
  • Position this step after the Windows image has been deployed
SCCM Windows 10 customization

DISABLE MICROSOFT CONSUMER EXPERIENCES

The latest Windows 10 feature upgrade includes a new feature that automatically installs a few apps from the Windows Store. Some apps like Candy Crush and Minecraft gets installed, we don’t think that belong to a work environment so we’ll delete it.

SCCM Windows 10 customization

The good news is that it’s quite simple to disable. You need to disable a function called Microsoft Consumer Experiences. We will do this using a registry modification :

  • Create a new ConsumerExperience folder in your Windows 10 customization directory
  • Create a new DisableConsumerExperience.reg file and copy the following code :

DisableConsumerExperience.reg

Windows Registry Editor Version [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent] “DisableWindowsConsumerFeatures”=dword

You’ll end up with the following structure :

SCCM Windows 10 customization
  • Open the SCCM Console and browse to Packages
  • Right-click your Windows 10 Customization package and select Update Distribution Point
SCCM Windows 10 customization
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click and Edit your Windows 10 task sequence
  • Select Add / General / Run Command Line
    • Name : Disable Consumer Experience
    • Command line : Regedit.exe /s ConsumerExperience\DisableConsumerExperience.reg
    • Check the Package box and specify your Windows 10 customization package
  • Position this step after the Windows image has been deployed
SCCM Windows 10 customization

CREATE CUSTOM START MENU

We will now create a default Windows 10 start menu that will be used on every Windows 10 machine by default. If you add shortcuts to applications, make sure that you’ve include them in your task sequence or you’ll end up with a start menu looking like swiss cheese. (empty spots)

SCCM Windows 10 customization
  • Log on a Windows 10 machine
  • Manually configure the Start Menu
  • Create a new StartMenu folder in your Windows 10 customization package
  • Start an elevated PowerShell and run the following command : Export-StartLayout -Path “C:\Temp\StartMenu.bin”
  • Copy the StartMenu.bin file to your Windows 10 customization package in the StartMenu folder
SCCM Windows 10 customization
  • Open the SCCM Console and browse to Packages
  • Right-click your Windows 10 Customization package and select Update Distribution Point
SCCM Windows 10 customization
  • Go to Software Library \ Operating Systems \ Task Sequences
  • Right-click and Edit your Windows 10 task sequence
  • Select Add / General / Run Command Line
    • Name : Set Start Menu Layout
    • Command line : Powershell.exe Import-StartLayout -LayoutPath StartMenu\StartMenu.bin -MountPath C:\
    • Check the Package box and specify your Windows 10 customization package
  • Position this step after the Windows image has been deployed
Sours: https://systemcenterdudes.com/sccm-windowsdeployment-guide/
Creating and deployment images using SCCM (Step by Step)

Windows 10 is out and if you are looking to deploy it using SCCM , this post is for you. Windows 10, version includes performance improvements, enterprise features and quality enhancements.

If you are running Windows 10 version , then updating to the new version will have a much faster update experience because the update will install like a monthly update. I will cover about all these cool features in a separate post. Click here to know all the new features baked in Windows 10

If you want to deploy Windows 10 using SCCM, I would suggest use SCCM to deploy it. That&#;s because as per the below chart, you can use Windows 10 as a client with Configuration Manager

The following table lists the versions of Windows 10 that you can use as a client with different versions of Configuration Manager.

Step 1 &#; Add Windows 10 Operating System Image

Before you start, ensure you download the Windows 10 ISO (either from VLSC or MSDN) and extract all the files to a folder.

Launch the Configuration Manager console. Go to Software Library > Overview > Operating Systems. Right click Operating System Images and click Add Operating System Image.

Add operating system image

On the Data Source page, click Browse and specify the path to Windows 10 install.wim. I love this option where you can extract a specific image index from the specified WIM.

Select the Image Index which is Windows 10 Enterprise in my case. Next, select the Architecture and Language. Click Next.

specify database source

On the General page, specify the information about operating system image.

OS information

Review the settings on summary page and click Next.

OS Summary

On the Completion page, click Close.

Completion

Step 2 &#; Distribute the Windows 10 Content

The next step after you add Windows 10 image is distribute the content to all the distribution points. Right click Windows 10 Enterprise and click Distribute Content.

Distribute Windows 10

Click Next.

Distribute Windows 10

Click Add to specify distribution points or distribution point groups. Click Next.

Select distribution point

Finally on the competition page, click Close.

Distribute the operating system

You must wait until the content is distributed to distribution points. You can know that when you check the content status. Green color indicates the content has been distributed to the DP.

operating system content distributed

Step 3 &#; Create SCCM Task Sequence to Deploy Windows 10

  • In the SCCM console, go to Software Library > Operating Systems > Task Sequences.
  • Right click Task Sequences and click Create Task Sequence.

Create SCCM Task Sequence

Under Select a new task sequence to be created, click Install an existing image package. Click Next.

Create SCCM Task Sequence

Specify the task sequence name. Click Browse and select the boot image. Click Next.

Specify OS info

Click Browse and select Windows 10 Enterprise Image Package. The Image Index should be populated automatically. To activate your copy of Windows 10, specify the product key.

You can also choose to randomly generate local admin password or you can specify an administrator password. Click Next.

Install windows step

Select Join a domain, specify the domain and domain OU. Specify the account that has permissions to join the machine to the domain. Click Next.

Domain join information

If you need to specify additional installation properties while installing SCCM client, you can specify it here.

Configuration Manager Client package

Do not select any thing under State Migration. Click Next.

state migration

If you wish to install software updates along with Windows 10, you got some options here.

Include Updates

You can install applications along with Windows 10

Install applications

Review the settings on Summary page and click Next.

Summary

Click Close on the Completion page.

Completion

Step 4 &#; Deploy Windows 10 using SCCM

It&#;s time to deploy the task sequence that we created in Step 3. Right click Install Windows 10 task sequence and click Deploy.

Deploy Windows 10 Using SCCM

Select the collection to which you want to deploy the Task Sequence. Click Next.

Deploy Windows 10 Using SCCM

Under Deployment Settings, select the purpose as Available. Under Make available to the following, select Only media and PXE.

Deploy Windows 10 Using SCCM

If you want to schedule the TS deployment, you can do it under Scheduling.

Task sequence deployment settings

On User Experience page, click Next.

Task sequence deployment settings

Under Deployment options, select Download content locally when needed by the running task sequence.

Task sequence deployment settings

Verify the settings on Summary page and click Next.

Task sequence deployment settings

On the completion page click Close.

Task sequence deployment settings

Step 5 &#; Windows 10 Deployment

I assume you have enabled PXE under distribution point server properties. In addition to that ensure the boot images are distributed to distribution points. If you want to know how to do that, refer this guide &#; https://www.prajwaldesai.com/boot-images-distribution-point-configuration-osd-sccmr2/

PXE boot the client computer or VM and allow it to boot from network. Wait until the boot image loads. If you have set a TS password, enter it or just click Next.

Deploy Windows 10 Using SCCM

Select the Windows 10 task sequence and click Next.

Deploy Windows 10 Using SCCM

The below screenshot is taken at the step where TS applies the OS image.

Deploy Windows 10 Using SCCM

The task sequence execution is complete. Login to the Windows 10 computer and check the Windows 10 version. Go to Run and type Winver command.

We have successfully installed Windows 10 OS build

Windows 10 If you have any questions, post it under Comments or to get help post your questions in community forums.

Did this post help? Buy me a coffee!

Sours: https://www.prajwaldesai.com/deploy-windowsusing-sccm/

10 sccm deploy windows

3 methods to deploy Windows 10 Feature Updates using MECM (SCCM)

With the advent of the Windows 10 Software as a Service (Saas) model it has become necessary to manage deployment of feature updates almost annually. Many federal and corporate organizations use the “semi-annual” servicing channel for Windows 10 which gets updates in March and September. It is the responsibility of the desktop engineering team to keep management informed and stay well ahead of End of Service (EOS) dates.

I will outline 3 methods for performing Windows 10 feature updates using MECM (SCCM). Thorough testing is required for each method on test devices to confirm that everything works, and user data is retained as expected.

Method 1: Software Update

This method is the easiest to deploy and monitor but will require additional steps to remediate any failed or stuck updates.

  1. Ensure “upgrades” classifications is selected under Software Updates properties.
  2. Synchronize Software Updates catalog.
  3. Right click and download the desired feature update.
  4. Deploy feature update to device collections.
    If your organization is working mostly remote it is best practice to deploy to smaller collections over a longer period so as not to cause VPN over utilization issues.
  5. Monitor deployment and remediate errors (more details below).

Method 2: Upgrade Task Sequence
If you require additional steps such as upgrading drivers, removing incompatible applications, or suspending BitLocker, using an upgrade Task Sequence provides much more control. This method is more flexible and error remediation steps can be performed before upgrades occur.

  1. Download the full ISO file from the Microsoft MSDN site for the Windows 10 version you wish to upgrade to.
  2. Mount the ISO or extract the files with a tool such as 7-Zip.
  3. Copy the files from the ISO to a MECM network share location.
  4. In MECM browse to Software Library\Operating Systems\Task Sequences. Right click and choose “Create Task Sequence.” Select “Upgrade an operating system from and upgrade package”. On the select an operating system upgrade package page of the wizard select the network share path that contains the setup.exe file. Set the remaining options that are relevant to your environment and complete the wizard.
  5. You can deploy the upgrade task sequence as is or edit to customize to your needs.

Method 3: Create an application

A third method is to create an application with the extracted ISO files or the ESD files that are downloaded to C:\Windows\SoftwareDistribution\download during an upgrade. This method works but should only be used if other upgrade methods are failing. One drawback of this method is controlling the reboot after the upgrade but that could be done with the application exit code actions or a task sequence step.

ISO Files:

  1. Create an application using the extracted ISO files outlines in Method 2 to a MECM network share location
  2. Use a command line to install the application:
    Sample command line (reference link below): setup.exe /Auto Upgrade /Compat IgnoreWarning /NoReboot /Priority Low /ShowOOBE None
  3. Set the detection method to Registry:
    • Key: Software\Microsoft\Windows NT\CurrentVersion
    • Value: CurrentBuild
      Data Type: String, Operator “Equals”, Value “XXXXX” (eg. for Windows 10 )

ESD Files:

  1. Upgrade a computer to the desired Windows 10 build using any method (even Windows Update from Microsoft) to the desired build. The upgrade files will be stored in: C:\Windows\SoftwareDistribution\download\XXXXXXXX and can be copied to a MECM network share location. There will be 2 files: updatebox.exe, and the .esd file.
  2. Create a batch file with the following command lines:
    start /w WindowsUpdateBox /Update /PreDownload /quiet /noreboot
    start /w WindowsUpdateBox /Update /Install /quiet /noreboot
    start /w WindowsUpdateBox /Update /Finalize /quiet /noreboot
  3. Create an application in MECM and use the created .bat file in the command line.
  4. Set the detection method to Registry:
    • Key: Software\Microsoft\Windows NT\CurrentVersion
    • Value: CurrentBuild
      Data Type: String, Operator “Equals”, Value “XXXXX” (eg. for Windows 10 )
  5. Set exit code 0 to cause a system reboot or create a task sequence with the application and add a reboot step.

Upgrade error remediation

Clear the cache
If installation errors occur create a script to delete the upgrade caches C:\$Windows.~BT, C:\Windows\SoftwareDistribution and rename the c:\Windows.old folder to c:\Windows.old_old. Clearing the cache and rebooting resolves most upgrade issues. It is also a good idea to add some windows repair commands to this script such as “sfc /scannow” (restores missing system files) and the Windows Update component repair command DISM.exe /Online /Cleanup-image /Restorehealth

Check the logs
If issues persist check the C:\$Windows.~BT\Sources\panther directory logs. You can also run the PowerShell command Get-WindowsUpdateLog to consolidate the logs into one log.

Reimage the computer
This is a last resort measure and should only be done after all other remediate methods have been exhausted. You can build an in-place upgrade task sequence to refresh Windows with a clean install while retaining user data and settings to make this process easier.

 

References:
Sours: https://insights.gocloudforce.com/3-methods-to-deploy-windowsfeature-updates-using-mecm-sccm
How to Create, Manage, and Deploy Applications in Microsoft SCCM - Application Deployment SCCM 2012

Create Windows 10 Task Sequence through SCCM

In this post I will be showing how to create Windows 10 task sequence through SCCM. I will be deploying Windows 10 x64 version. There are few pr-requisites before deploying Windows 10 image to a system.

Boot Image:

Winpe PE Boot image (x64) distributed successfully on Distribution Point.

Navigate to \Software Library\Overview\Operating Systems\Boot Images, and make sure Content Status shows as Success.


Create Windows 10 Task Sequence through SCCM 1

Operating System Images:

Import Windows 10 image ie. Install.wim.

You can download the iso file from Volume Licensing Service Center. Once downloaded extract / mount the iso file. Navigate to folder sources and copy install.wim to a source location (in my case: \\sccm01\d$\Source\OS\OS Images).

Create Windows 10 Task Sequence through SCCM 2

Rename install.wim to Win10_wim (this is optional, just for the sake of better naming convention).

Add Operating System Image

Navigate to \Software Library\Overview\Operating Systems\Operating System Images, right click and select Add Operating System Image.

Create Windows 10 Task Sequence through SCCM 3

This will open up Add Operating System Image Wizard with Data Source page, specify the path of the wim file and click Next.

Create Windows 10 Task Sequence through SCCM 4

Under General page, provide the name as “Windows 10 Enterprise” and click Next.

Create Windows 10 Task Sequence through SCCM 5

Verify the information under Summary page and click Next.

Under Completion page, you will be seeing the process has been completed, click on Close to exit the wizard.

Once you see image under \Software Library\Overview\Operating Systems\Operating System Images, right click and select Distribute Content to proceed with distributing it on Distribution point.

Create Windows 10 Task Sequence through SCCM 6

Verify the image Content Status, it should show as Success.

Create Windows 10 Task Sequence through SCCM 7

PXE setup should be configured:

Follow SCCM PXE Boot configuration if not done yet. Incase of pxe boot issues follow PXE Troubleshoot guide.

Navigate to \Software Library\Overview\Operating Systems\Task Sequences, right click Task Sequences and select Create Task Sequence.

Create Windows 10 Task Sequence through SCCM 8

This will launch Create Task Sequence Wizard with Create New Task Sequence page, select Install an existing image package and select Next.

Create Windows 10 Task Sequence through SCCM 9

Under Task Sequence Information page, provide Task Sequence name as “Windows 10 ” and specify Boot Image by clicking on Browse and selecting Boot image (x64) click on OK to close boot image selection window and click Next.

Create Windows 10 Task Sequence through SCCM 10

Under Install Windows page, select Image Package we created previously ie. “Windows 10 Enterprise”. Select Image index as “3 – Windows 10 Enterprise”. Uncheck the box “configure task sequence for use with BitLocker” as we are not using Bitlocker configuration. Select Enable the account and specify the local administrator password and specify password of your choice.

Create Windows 10 Task Sequence through SCCM 11

Under Configure Network page, select Join a domain.
Under Domain click on Browse and select your existing Domain.

Under Domain OU, select the OU where you want the system to be moved, make sure to select OU not container.
Under Account, click on Set and specify User name and password with the account which has permission for Domain joining and moving system to OU, you can verify this by connecting to existing LDAP and click on Test connection to verify the same. Click on Next.

Create Windows 10 Task Sequence through SCCM 12

Under Install Configuration Manager client, default client package will be selected, we can change if we like, click on Next.

Create Windows 10 Task Sequence through SCCM 13

Under Configure state migration page, we will not select any option as we are not going to use USMT for capture and restore of data, hence uncheck:
Capture user settings and files
Capture network settings
Capture Microsoft Windows settings

Create Windows 10 Task Sequence through SCCM 14

Under Include Updates, we will go with option Do not install any software updates as we are not planning to install updates during this process.

Create Windows 10 Task Sequence through SCCM 15

Under Install Applications page, we can select any application which is optional, I have gone with selection of 7-zip application, click Next.

Create Windows 10 Task Sequence through SCCM 16

Under Confirm the settings page, verify all the details we have specified and click on Next to proceed with creation of Task Sequence.

If we right click the task sequence and select Edit, this how the task sequence will look.

Create Windows 10 Task Sequence through SCCM 17

Add a Restart Computer step right after Setup Windows and Configuration Manager step as there is a known issue of screen getting stuck at “Just a moment” right after Configmgr client install, and will not show any progress related to steps there after. Once step is added, this should be your final task sequence.

Create Windows 10 Task Sequence through SCCM 18

Above mentioned task sequence will generate a generic ComputerName, you can follow Prompt for ComputerName during TS to manually provide the name during

Navigate to \Software Library\Overview\Operating Systems\Task Sequences, select the task sequence we recently created ie. “Windows 10 ”, right click and click on Deploy.

Create Windows 10 Task Sequence through SCCM 19

This will launch Deploy Software Wizard with General page, select the Collection as “All Unknown Computers” and select Next.

Create Windows 10 Task Sequence through SCCM 20

Under Deployment Settings page, select Make available to the following drop down menu which has following values:

Only Configuration Manager Clients
Configuration Manager clients, media and PXE
Only media and PXE
Only media and PXE (hidden)

We will be proceeding with Only media and PXE as we are just interested deploying to new systems only.

Create Windows 10 Task Sequence through SCCM 21

Under Scheduling page, check the box Schedule when this deployment will become available and provide the date and time which will be used as when to make this policy available, click on Next.

Create Windows 10 Task Sequence through SCCM 22

Under User Experience page, we will be going with default options, click on Next.

Create Windows 10 Task Sequence through SCCM 23

Under Alerts page, once again we will be going with default settings, hence no changes here, click on Next.

Create Windows 10 Task Sequence through SCCM 24

Under Distribution Points page, make sure Download content locally when needed by the running task sequence is selected under Deployment options.

Create Windows 10 Task Sequence through SCCM 25

Under Summary, verify the details and click on next to proceed with deploying the task sequence.

Create Windows 10 Task Sequence through SCCM 26

As we are ready with the deployment, we will now PXE boot the system.

Create Windows 10 Task Sequence through SCCM 27

System will contact DHCP and WDS server and WinPE boot image will load.

Create Windows 10 Task Sequence through SCCM 28
Create Windows 10 Task Sequence through SCCM 29

Under Task Sequence Wizard, select Next.

Create Windows 10 Task Sequence through SCCM 30

Select the Task Sequence “Windows 10 ” and click on Next to initiate the Operating System deployment process.

Create Windows 10 Task Sequence through SCCM 31

Task sequence will be initiated now and will go through all the steps as mentioned in the Task sequence including Apply operating System step.

Create Windows 10 Task Sequence through SCCM 32

Wait for the process to get completed. Once completed login to the system, you may verify the OS Build with version by running command winver, along with 7-Zip installed:

Create Windows 10 Task Sequence through SCCM 33

Like this:

SCCM, OSDConfigMgr, OSD, SCCM, Task Sequence, Windows 10

Sours: https://www.manishbangia.com/create-windowstask-sequence-through-sccm/

You will also be interested:

This guide provides step by step instructions to install PXE role, Creation of boot image, Creation of OS image, Creation of OSD task sequence and deploying Windows 10 OS via PXE boot on SCCM lab environment.

Enable SCCM PXE Role

First we need to prepare environment for configuration manager OSD. we have to create Network Access account in Active Directory and this account is used by the client to access the Configuration Manager Distribution point when booted under WinPE so make sure the account has the necessary permission for this action. Then we have to Enable PXE role on our SCCM server.

Follow the Below Steps to Enable PXE support,

Open the SCCM Console
Go to Administration / Site Configuration / Servers and Site System Roles
Select your distribution point and right-click on the Distribution point role on the bottom, select Properties

Select the PXE tab
Enable the Enable PXE support for Clients check-boxandanswer Yes when prompted about firewall ports (UDP ports 67, 68, 69 and )

Check the Allow this distribution point to respond to incoming PXE requests check box
Check the Enable unknown computer support check box
Ensure that the Respond to PXE request on all network interfaces is selected Click OK

Go to Monitoring / Distribution Status / Distribution Point Configuration Status
Click your distribution point on the top and select the Details tab on the bottom
We will see that the distribution point PXE settings has changed

BOOT Image Distribution

Here we are going to use the default SCCM boot image,
Open the SCCM Console, Go to Software Library / Operating Systems / Boot Images, Right-click Boot Image (X64) and distribute to DPs.

Add Operating System Image

Launch the Configuration Manager console, click on Software Library, click Operating Systems, right click on Operating systems images and click on Add Operating System Image.

Specify the path where the install.wim is present. Click Next.

Provide details for the operating system image. Click Next.

Click Next and click close.

Distribute the image into DPs

Select the Distribution Point

Click Next and Close

Configure Network Access account and this account is used by the client to access the Configuration Manager Distribution point when booted under WinPE

Specify Network Access account

Task Sequence Creation

Launch the Configuration Manager console, click on Software Library, expand Overview, expand Operating Systems, right click Task Sequences and click Create Task Sequence.

Type Task sequence Name

Select Boot Image

Select Operating System Image

Select Image Index ,type the Product Key ,type Local Administrator password and Next

Configure Domain Join Account

Select Join a Domain and browse the Domain OU and Click Next

Select Configuration Manager Client Package

Click Next since we are not using State Migration here

Select the Appropriate Software Update option, here i have selected Do not install any software updates

Select the Application Which we want to install during the task sequence

Click Next and Close

Task sequence has been created successfully, below is our basic win 10 task sequence view

Deploy task sequence into Unknown Computer Collection

Select task sequence right click and Click Deploy

Select All unknown Computers collection

And Select Pupose & Make available to PXE and Click Next

Select the Deployment schedule and click Next

Select User experience Option as per below and Click Next

Select deployment options as download locally and click Next

Verify the Summary and click Next

The Deploy task sequence wizard completed Successfully

Deploying Windows 10 via PXE boot

Here I have prepared another hyper V host and deploying windows 10 via configured PXE boot

Press F12 to boot from the network and the machine will get IP from DHCP, Contacting PXE server,Downloading and initiating the Boot Image

Task sequence wizard will appear and type task sequence password

Click Next

Task sequence variable will appear and Type the OSDComputerName

Click Next

Partition Disk stage Running

Applying Operating system stage Running

Setup Windows and Configuration Manger Stage Running

Setup Windows completed and Auto reboot initiated

Post Reboot, System Initiating

Imaging Completed and type the Administrator password to login,

Verify the same from smsts.log

Windows 10 deployment completed Successfully.

Thank You:-)

Like this:

LikeLoading

Related

Published by Tamilkovan

My name is Tamil Kovan and I work as a Technical Lead at PCCW Solutions. This is my blog where I will share tips and stuff for my own on System Center related topics. View more posts

Sours: https://tamilkovan.com//09/29/windowsdeployment-using-sccmosd-step-by-step-guide/


1574 1575 1576 1577 1578