According to Technet documentation, Windows 10 will receive two to three new feature upgrades per year. The update from Windows 10 1507 to 1511 is one of those feature upgrades. When using System Center Configuration Manager (SCCM) for a Windows 10 upgrade, you can either work with SCCM’s Windows 10 Servicing feature or use a Task Sequence.

Both methods have their advantages and disadvantages, and you might run into a few issues. When doing an in-place upgrade, some settings and customizations that we normally make, such as deploying a customized Start menu, a new background, and so on might be lost after the upgrade.

Windows 10 Servicing in Configuration Manager CB ^

Working with the Windows 10 Servicing of Configuration Manager Current Branch (CB) is comparable to using WSUS for upgrading Windows 10. Windows 10 Servicing in Configuration Manager CB is a new feature that allows you to automate Windows 10 upgrades using the Software Updates component in Configuration Manager.

Windows 10 Servicing in SCCM

Windows 10 Servicing in SCCM

Configuration Manager also gives you a nice view of the Windows 10 versions used in your network.

Overview of Windows 10 versions

Overview of Windows 10 versions

There is also a little chart that shows the Windows 10 versions currently available with their support end dates.

Available Windows 10 versions

Available Windows 10 versions

An Automated Deployment Rule (ADR) in SCCM can be used to assign a branch to a computer collection, and you can configure how long to wait on installation after a Windows 10 version has been released.

Note that if you are on 1511, you should block the updates you don’t want to deploy in the WSUS Administration Console; otherwise, WSUS will download all the available updates for Windows 10. This is fixed in 1602.

Creating a Service Plan

Creating a Service Plan

A downside of this method is that you lose many of tweaks that you performed after the first Windows 10 installation, such as changing the background, replacing default pictures, and uninstalling built-in-apps (many of them provide no business value). Here is a screenshot from a Windows 10 1507 installation before it was upgraded to 1511.

Windows 10 1507 installation

Windows 10 1507 installation

In the next screenshot, you see the same Windows 10 installation after the upgrade to 1511 using a standalone installer, either WSUS or SCCM. All default apps have been reinstalled.

Windows 10 installation after the upgrade to 1511

Windows 10 installation after the upgrade to 1511

Other examples of lost tweaks are:

  • Uninstalled default apps are installed again
  • Modifications of the default background and branding are lost
  • Language packs are not installed; only the base language is upgraded

Another example is shown in the screenshot below. The “Hide notification while presenting” setting will be reset to its default configuration.

Hide notification while presenting

Hide notification while presenting

Task Sequence in SCCM CB 1511/1602 ^

A Task Sequence in SCCM is mainly designed for deploying operating systems, but it can also be used for software deployments that require the execution of multiple steps in a controlled order.

Creating Task Sequence

Creating Task Sequence

In Configuration Manager CB, there is a built-in Task Sequence template to do an in-place upgrade of Windows 7/8.1 to Windows 10. However, you can also use it to upgrade Windows 10 1507 to 1511. When you start the wizard to create a new Task Sequence, you will see a new option:

Upgrade an operating system from upgrade package

Upgrade an operating system from upgrade package

The advantage of using a Task Sequence is that you can reapply branding and uninstall any unwanted apps once again.

Branding Windows 10

Branding Windows 10

However, after upgrading computers this way, you’ll run into the following issues.

Issue 1:
After the upgrade is complete, the Configuration Manager client might no longer be working. An additional step that runs Repair SCCM client and then reboots the computer solves this problem.

Repair SCCM client

Repair SCCM client

Issue 2:
When logging on the first time after the upgrade, you might receive the error message The Group Policy Client service failed the sign-in.

The Group Policy Client service failed the sign-in

The Group Policy Client service failed the sign-in

This problem has existed since Windows 8.1, and the same solution can be applied:

Subscribe to 4sysops newsletter!

Fixing the Group Policy Client

Fixing the Group Policy Client

Conclusion ^

Microsoft has to fix a couple of issues to guarantee a smooth Windows 10 upgrade process. In particular, it would be helpful if Windows configurations did not revert to the default settings. Currently, admins have to start from scratch again after every upgrade or users have to be trained for the new work environment.

7 Comments
  1. Ben 6 years ago

    Great article, I have a very reliable Win7 to Win10 1607 task sequence now.

    I am wondering if the separate step to repair the SCCM client is still necessary?  I was looking at the smsts.log file of a machine I just upgraded, and noticed that OSDUpgradeOS.exe is already doing a client remediation of sorts:

     

    Command line: “OSDUpgradeOS.exe” OSDUpgradeWindows 12/7/2016 9:49:58 AM 3096 (0x0C18)

    Remediating CCM client in the upgraded operating system OSDUpgradeWindows 12/7/2016 9:49:58 AM 3096 (0x0C18)

    Executing C:\WINDOWS\ccmsetup\ccmsetup.exe /remediate:client /OSUpgradeRepair OSDUpgradeWindows 12/7/2016 9:49:58 AM 3096 (0x0C18)

    Command line for extension .exe is “%1” %* OSDUpgradeWindows 12/7/2016 9:49:58 AM 3096 (0x0C18)

    Set command line: “C:\WINDOWS\ccmsetup\ccmsetup.exe” /remediate:client /OSUpgradeRepair OSDUpgradeWindows 12/7/2016 9:49:58 AM 3096 (0x0C18)

    Executing command line: “C:\WINDOWS\ccmsetup\ccmsetup.exe” /remediate:client /OSUpgradeRepair OSDUpgradeWindows 12/7/2016 9:49:58 AM 3096 (0x0C18)

    Process completed with exit code 0 OSDUpgradeWindows 12/7/2016 9:57:29 AM 3096 (0x0C18)

    Or is it still wise to have another separate repair step anyway?

     

  2. Author

    Hi,
    No it is not necessary anymore only for Configuration Manager 1602 where the client failed the repair of the client that is done in the scripts that was why we had to do it twice.

    Regards,
    Jörgen

  3. existenz 5 years ago

    Hello – I just upgraded from 1607 to 1703 with a servicing plan , and lost the programs pinned manually to start menu , have you ever had this issue before ?

  4. Dennis.Wong 4 years ago

    Kia Ora

    I meet a problem in a new sccm 1802.

    I setting a task for install windows10

    But when the task runing format drive and install windows10 was failed

    I saw the sccm server log was ” Command line for extension .exe is “%1″%* (install windwos)

    I have no idea about it

    So any ideas for me?

    Cheers mate

    Which you have a nice day.

  5. aravind 4 years ago

    Hello Jason,

    I have a powershell script to uninstall apps. When I run manually it uninstall apps. When I include that in TS, it runs but it wont uninstall apps. I tired with every option I know, created package, ran it as part of TS . it successfully runs but wont uninstall apps. it works good when I add the script to deploy on bare metal it works. but not in upgrade TS. Also I created custom TS and deployed on one of the test machine it ran but no success.
    Am I missing anything?

    $AppsList = "Microsoft.BingFinance","Microsoft.BingNews","Microsoft.BingWeather","Microsoft.XboxApp","Microsoft.SkypeApp","Microsoft.MicrosoftSolitaireCollection","Microsoft.BingSports","Microsoft.ZuneMusic","Microsoft.ZuneVideo","Microsoft.Windows.Photos","Microsoft.People","Microsoft.MicrosoftOfficeHub","Microsoft.WindowsMaps","microsoft.windowscommunicationsapps","Microsoft.Getstarted","Microsoft.3DBuilder"
    
    ForEach ($App in $AppsList) 
    { 
        $PackageFullName = (Get-AppxPackage $App).PackageFullName
        $ProPackageFullName = (Get-AppxProvisionedPackage -online | where {$_.Displayname -eq $App}).PackageName
            write-host $PackageFullName
            Write-Host $ProPackageFullName 
        if ($PackageFullName) 
        { 
            Write-Host "Removing Package: $App"
            remove-AppxPackage -package $PackageFullName 
        } 
        else 
        { 
            Write-Host "Unable to find package: $App" 
        } 
            if ($ProPackageFullName) 
        { 
            Write-Host "Removing Provisioned Package: $ProPackageFullName"
            Remove-AppxProvisionedPackage -online -packagename $ProPackageFullName 
        } 
        else 
        { 
            Write-Host "Unable to find provisioned package: $App" 
        } 
    
    }

  6. Author

    Hi,

    at what phase in the Upgrade TS do you run the script? I always do the same and it works just fine..

    Regards,
    Jörgen

  7. Jonn 3 years ago

    We have been using TS to upgrade from windows 10 version 1803, and 1809 to 1903.  Approximately 50% of the upgrades work flawlessly.  The other 50% perform the upgrade, but after the upgrade has finished, the sms agent service is left as disabled.  After enabling the service, I usually have to run a PS cmd to reset the WMI, and the TS for the upgrade shows up in software center, and the notifications as if it's running again (appears to be stuck in a loop).  When this happens i run ccm setup.exe /Uninstall, and reinstall via cmd line.  

Leave a reply to Jonn Click here to cancel the reply

Please enclose code in pre tags

Your email address will not be published.

*

© 4sysops 2006 - 2022

CONTACT US

Please ask IT administration questions in the forums. Any other messages are welcome.

Sending

Log in with your credentials

or    

Forgot your details?

Create Account