Easy way to upgrade machines

%3CLINGO-SUB%20id%3D%22lingo-sub-1962511%22%20slang%3D%22en-US%22%3EEasy%20way%20to%20upgrade%20machines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1962511%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%20-%20we%20have%20thousands%20of%20systems%20which%20is%20in%20the%20process%20of%20upgrade%20and%20our%20SCCM%20Admins%20are%20using%20software%20center%20to%20push%20these%20updates.%20SCCM%20DP%20is%20hosted%20on%20corporate%20network%20but%20since%20users%20are%20working%20from%20home%20the%20updates%20are%20going%20via%20WAN%20and%20failing%20apart%20and%20update%20process%20is%20not%20successful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20there%20is%20any%20more%20easier%20way%20to%20update%20windows%20from%201809%20to%201909%20like%20usb%2C%20iso%2C%20copy%20the%20task%20sequence%20file%20etc%20%3F%20any%20sort%20of%20easier%20way%20to%20upgrade%20these%20machines%20for%20remote%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1962511%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESCCM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1963259%22%20slang%3D%22en-US%22%3ERe%3A%20Easy%20way%20to%20upgrade%20machines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1963259%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F594117%22%20target%3D%22_blank%22%3E%40alitaqvi%3C%2FA%3E%26nbsp%3BYou%20could%20deploy%20a%20CMG%20and%20host%20the%20content%20there%2C%20or%20use%20Windows%20servicing%20(essentially%2C%20deploying%20the%20feature%20update%20just%20like%20any%20other%20software%20update)%20and%20allow%20your%20clients%20to%20download%20the%20content%20from%20the%20Microsoft%20Update%20cloud%20service.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1985312%22%20slang%3D%22en-US%22%3ERe%3A%20Easy%20way%20to%20upgrade%20machines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1985312%22%20slang%3D%22en-US%22%3EThe%20Windows%20feature%20upgrade%20is%20an%20approach%20I%20had%20attempted%20to%20complete%20and%20had%20been%20fairly%20successful%20for%20remote%20computers.%20However%2C%20the%20challenge%20is%20after%20selecting%20to%20download%20the%20upgrade%20content%20for%20the%20deployment%20in%20the%20CM%20infrastructure%2C%20we%20cannot%20select%20Microsoft%20Update%20as%20the%20source%20for%20a%20remote%20computer%20use%20case%20simultaneously.%3CBR%20%2F%3EEssentially%2C%20I%20was%20trying%20to%20complete%20two%20use%20cases%3A%3CBR%20%2F%3E1%20-%20VPN%20-%20a%20remote%20computer%20would%20go%20to%20Microsoft%20Update%20to%20download%20the%20specified%20OS%20Upgrade.%3CBR%20%2F%3E2%20-%20non-VPN%20-%20a%20non-remote%20computer%20would%20go%20to%20a%20DP%20to%20download%20the%20same%20OS%20Upgrade.%3CBR%20%2F%3E%3CBR%20%2F%3EOne%20option%20is%20to%20complete%20remote%20upgrades%20first%20and%20follow-up%20with%20non-remote%20upgrades%20in%20sequence.%20Not%20the%20most%20sophisticated%20approach.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20recommend%20the%20product%20group%20consider%20allowing%20having%20either%20selections%20to%20occur%20simultaneously%20within%20the%20deployment%20wizard.%20Unless%20I%E2%80%99m%20missing%20something%20because%20when%20I%20run%20through%20it%2C%20there%E2%80%99s%20no%20other%20choice%20after%20the%20OS%20feature%20upgrade%20is%20a%20downloaded%20deployment.%3C%2FLINGO-BODY%3E
Contributor

Hi all - we have thousands of systems which is in the process of upgrade and our SCCM Admins are using software center to push these updates. SCCM DP is hosted on corporate network but since users are working from home the updates are going via WAN and failing apart and update process is not successful.

 

If there is any more easier way to update windows from 1809 to 1909 like usb, iso, copy the task sequence file etc ? any sort of easier way to upgrade these machines for remote users.

3 Replies

@alitaqvi You could deploy a CMG and host the content there, or use Windows servicing (essentially, deploying the feature update just like any other software update) and allow your clients to download the content from the Microsoft Update cloud service.

The Windows feature upgrade is an approach I had attempted to complete and had been fairly successful for remote computers. However, the challenge is after selecting to download the upgrade content for the deployment in the CM infrastructure, we cannot select Microsoft Update as the source for a remote computer use case simultaneously.
Essentially, I was trying to complete two use cases:
1 - VPN - a remote computer would go to Microsoft Update to download the specified OS Upgrade.
2 - non-VPN - a non-remote computer would go to a DP to download the same OS Upgrade.

One option is to complete remote upgrades first and follow-up with non-remote upgrades in sequence. Not the most sophisticated approach.

I would recommend the product group consider allowing having either selections to occur simultaneously within the deployment wizard. Unless I’m missing something because when I run through it, there’s no other choice after the OS feature upgrade is a downloaded deployment.

@pghealey You should be able to achieve this by creating a VPN boundary group and configure that to prefer cloud-based sources over on-premise sources. This would cause VPN clients to prefer Microsoft Update over an on-premise distribution point. The fact that you're downloading update content and distributing that to your distribution points doesn't mean all clients have to get it from there. See Boundary groups: Prefer cloud based sources over on-premise sources and Managing Patch Tuesday with Configuration Manager in a remote work world for details.