Upgrading Windows 10 with SCCM – Windows 10 Servicing or Task Sequence?

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?

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 ?

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" 
    } 

}

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.