Sccm windows 10 upgrade

Вопрос

Коллеги, добрый день!

Хочу обновить все Windows 10 до 1709 с помощью SCCM. Ранее (месяца 4 назад), использовал этот механизм для обновления до 1703 на тестовой группе машин — всё прошло успешно.

Сейчас, другая тестовая группа (пять машин с 1511): отчёт о развертывании докладывает, что всё обновилось; по факту — нет.

Развернул ВМ с windows 1603 (на своей Windows 10 1709) и пытаюсь её обновить — итог тот же.

После «применения образа ОС» система перегружается и всё. smsts заканчивается RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram; GetTsRegValue() is unsuccessful. 0x80070002.

Подключил диск с образом непосредственно в ВМ, запускаю D:\SETUP.EXE /ImageIndex 3 /auto Upgrade /noreboot /DynamicUpdate Disable /compat IgnoreWarning /compat ScanOnly. После стадии «проверки свободного места на диске» окно установщика гаснет и всё.

setupact.log заканчивается MOUPG SetupHost: Reporting error event -> [0xC1900210, 0x5001A] Но 0xC1900210 — это no issues found.

Перепробовал 4 образа: 1703, 1709 vlsc ноябрьский,1709 vlsc текущий и 1709 от media creation tool. В то же время, установка в ручном режиме с этих образов проходит нормально.

The Blog

Benoit Lecours September 20, 2016 SCCM, WINDOWS 10 49 Comments

With the introduction of new Windows 10 service branches, you will need to upgrade your Windows 10 devices at a much faster pace. Hopefully, SCCM Current Branch (1511 and higher) has built-in features to help you fulfill this task. You can choose between Upgrade Task Sequence or the new Windows Servicing feature. This post will describe how to use SCCM Windows 10 servicing plans to upgrade Windows 10 devices.

If you are running SCCM 1511 we recommend using the Upgrade Task Sequence over servicing plans. SCCM 1511 has an issue that makes all Windows 10 languages and editions to be downloaded to the device when the ADR runs. This is fixed in SCCM 1602, using a new filter you can exclude unwanted languages and editions.

If you are running SCCM 1602 or later, it’s really a matter of preference of which process to use. Each one has their own advantages, the new servicing features is using the ADR/Software Update engine, the Task Sequence one is using Task Sequence engine. The Task Sequence method allows to run additional tasks after the upgrade or install new applications. Read both our post before making your decision or use both if needed.

In this post, we will be upgrading a Windows 10 1511 to Windows 10 1607 using SCCM 1606 serving plans. You can use this method to upgrade any upcoming Windows 10 release. You can’t use servicing plans to upgrade Windows 7 or Windows 8 computers.

SCCM Windows 10 Servicing Plans Requirements

Before using Windows 10 servicing plans you need:

• An Active Software Update Point
• Enable Heartbeat Discovery – Data displayed in the Windows 10 servicing dashboard is found by using discovery
• Install WSUS hotfixes and follow the required manual installation steps that are outlined in the KB3159706 article
• Install WSUS hotfix to enable WSUS support for Windows 10 feature upgrades
• Enable Windows 10 product and Upgrade classification in your software update point

Once the first 4 steps are completed, let’s bring Windows 10 upgrade packages to your software update point :

• Open the SCCM Console
• Go to Administration \ Site Configuration \ Sites
• On the top ribbon, select Configure Site component and Software Update Point

• In the Products tab, select Windows 10

• In the Classifications tab, select Upgrades

• Accept the prerequisite warning. Go back and install these hotfixes if you haven’t done it before

• Close the Software Update Point Component properties window
• Go to Software Library \ Windows 10 Servicing
• Right-click Windows 10 Servicing, select Synchronize Software Updates

• As for any Software Update synchronization process, follow the action in Wsyncmgr.log in your SCCM installation directory
• Once completed, go to Software Library \ Windows 10 Servicing \ All Windows 10 Updates
• You should have Windows 10 Upgrade packages listed

Feature Updates vs Upgrades

After your synchronization, you’ll notice 2 types of packages. This is a bit confusing. As you can see in the screenshot, for Windows 1607 Enterprise, we only has Feature Update to Windows 10 Enterprise we don’t have an Upgrade to Windows 10 Enterprise package for 1607… yet.

The short story : At the time of this writing, the 1607 build is in the Current Branch readiness state. (listed as Feature Update). When this build falls into Current Branch for Business (Approximately 4 months), a new release will be available in Windows Update and then in SCCM (listed as Upgrade).

• Feature Upgrade : New build at the time of the release
• Upgrade : Feature Update + Servicing Update (Patches) since media first published

In this post, we’ll be using Feature Updates. During our tests, we also tried the Upgrade package on a 1507 computer (1507 -> 1511) without issues. If you have both available at the time of creating your servicing plan, use the Upgrade package since it includes Servicing Updates.

Long Story : If you want the Microsoft version, refer to the complete Technet documentation.

The 2 key phrases from this documentation are:

• Feature upgrades that install the latest new features, experiences, and capabilities on devices that are already running Windows 10. Because feature upgrades contain an entire copy of Windows, they are also what customers use to install Windows 10 on existing devices running Windows 7 or Windows 8.1, and on new devices where no operating system is installed
• Approximately four months after publishing the feature upgrade, Microsoft uses Servicing Branch #1 again to republish/updated installation media for Windows 10 Pro, Education, and Enterprise editions. The updated media contains the exact same feature upgrade as contained in the original media except Microsoft also includes all the servicing updates that were published since the feature upgrade was first made available. This enables the feature upgrade to be installed on a device more quickly, and in a way that is potentially less obtrusive to users.

Create Servicing Plans

Now that we have Windows 10 upgrade packages in SCCM, we can create a servicing plan for our Windows 10 devices. Servicing Plan and Automatic Deployment Rules shares the same engine so you won’t be disoriented by servicing plans.

[su_box title=”Warning” style=”glass” box_color=”#dac6c6″ title_color=”#F0F0F0″]Servicing plans are designed to upgrade Windows 10 from one build to another build only. You can’t use that to upgrade Windows 7 to Windows 10. If you need to upgrade your Windows 7 to Windows 10 use the Upgrade Task Sequence instead.[/su_box]

Looking at the Windows 10 Servicing dashboard, our 3 Windows 10 1511 are near expiration (Expire Soon).

• Go to Software Library \ Windows 10 Servicing \ Servicing Plan
• Right-click Servicing Plan and select Create Servicing Plan

• In the General Pane, give a Name and Description, click Next

• On the Servicing Plan tab, click Browse and select your Target Collection

• In the Deployment Ring tab :
  • Specify the Windows readiness state to which your servicing plan should apply
  • Specify how many days you want to wait before deploying

• In the Upgrade tab, specify the Language, Required and Title of the upgrade packages you want to deploy. This is a nice addition to the SCCM 1602 release, in 1511 all languages were downloaded

• Use the Preview button to ensure that you are targeting the right version (We are targeting Windows 10 1607 Enterprise en-us devices that are Required)

• In the Deployment Schedule tab, select the desired behavior

• In the User Experience tab, select the desired options

• In the Deployment Package tab, select Createa new deployment package and enter your Package Source path

• In the Distribution Points tab, select your distribution point

• In the Download Location tab, select Download software updates from the Internet

• In the Language Selection tab, select your language

• In the Summary tab, review your settings and close the Create Servicing Plan wizard

• Right-click your newly created Servicing Plan and select Run Now

• You can see that the deployment gets created in the Monitoring / Deployments section

Servicing Plan Deployment

Now that the deployment are triggered for clients, we will launch the installation manually using software center.

• Log on your Windows 10 computer
• We verify that we are running Windows 10 Enterprise version 1511 (Build 10586.218)

• Open the Software Center, under Updates,Feature Update to Windows 10 Enterprise 1607 is listed

• Select it and select Install

• Accept the warning by clicking Install Operating System. (Your data won’t be lost)

• Installation is running

• The computer will restart after about 5 minutes
• The whole upgrade process takes about 30 to 45 minutes and your device will be rebooted several time

• Once completed, log on the computer using your account. Windows is happy to tell you that it’s updated

• We are now running Windows 10 Enterprise version 1607 (Build 14393)

• Back in the Software Library \ Windows 10 Servicing \ Servicing Plan node
• Our machine is now listed as version 1607 and is no longer listed as Expire Soon
• The Service Plan Monitoring section can be used to monitor compliance and you can use the Deploy Now button to deploy the same service plan to a new collection

Use the comment section to tell which upgrade method you are preferring.

How useful was this post?

Click on a star to rate it!

Average rating 5 / 5. Vote count: 2

No votes so far! Be the first to rate this post.

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

49 Comments on “Upgrade Windows 10 using SCCM Servicing Plans”

How do you monitor the Feature Upgrade on the client to see what is happening. My clients just get stuck at installing, but never reboot. Windows 10 1803 x64 endpoint, SCCM 1806, trying to deploy Feature Upgrade 1809 or even 1903.

The Service Plan is created, sees the upgrade, created the deployment package, client sees it, select install, downloads, starts installing, and just sits on this part.

I need a little clarification on Windows 10 servicing via SCCM 1710.

I have three tier hierarchy, CAS , Primary 1 and Primary 2 all running on Windows server 2012 R2 . Must I install all the prerequisite patches and IIS MIME types on all the three. Ref : https://systemcenterdudes.com/sccm-windows-10-servicing-plans. Or do i need to install these patches on the Central site only.

All my secondaries are running Windows server 2016.

Any help is really appriciated. i am up against a deadline and my dear customer is deeply in love with Windows 10 servicing.

I need a little clarification on Windows 10 servicing via SCCM 1710.

I have three tier hierarchy, CAS , Primary 1 and Primary 2 all running on Windows server 2012 R2 . Must I install all the prerequisite patches and IIS MIME types on all the three. Ref : https://systemcenterdudes.com/sccm-windows-10-servicing-plans. Or do i need to install these patches on the Central site only.

All my secondaries are running Windows server 2016.

Any help is really appriciated. i am up against a deadline and my dear customer is deeply in love with Windows 10 servicing.

Question : How can i exclude the Creator Update from getting applied on the Windows 10 machines? Is there a Registry key that we can set to control that kind of update from getting installed ?

Kindly suggest the best possible way.

Regards,
Binu Kumar

Hi, I have set up a servicing plan to upgrade from 1607 to 1709, SCCM is current Branch (1710) running on Server 2016. I am not getting any errors, the device collection has been targeted but upgrade is not going through. I have targeted Semi Annual Channel (targeted) with a 0 day deferral period. Any help would be greatly appreciated.

Found my issue. Had to synch from the update point first. Once that completed all the updates showed in the list. THANKS AGAIN for a great guide. For people having issues with the collection here is a great article. https://blog.hosebei.ch/2016/03/26/configmgr-create-device-collections-based-on-windows-10-build/

Great guide love the screen shots, however I can’t get the updates to show under the Windows 10 updates. I have triple checked that I have the required settings selected an patches. I went as far to check SUS to make sure all the selections were tagged. Ran 3 syncs and still no updates. Any assistance would be great.

Can anyone please answer the following question: I need to get the feature packs to a NON connected CM environment in order to upgrade Windows 10 on my classified workstations. Is there a way to take the feature packs from an internet environment and import them into my non-internet connected CM environment? Thanks

Hi.
I have Expired Windows 10 Client and I see on Windows 10 Servicing dashboard.
but, I haven’t done upgrade current version of windows 10 which 1703.

also, I have another version of windows 10 that 1607. I can doing upgrade ones.

can I upgrade expired client with sccm servicing plan or should I use task sequence

Hi,
Is it possible to push Cumulative and Security updates of windows 10 using Windows 10 servicing ( Servicing plans ) please ?

Servicing is not made for Cumulative and Security updates. it’s only made for major releases.
Our guide about patch management cover it all.
https://systemcenterdudes.com/sccm-software-update-management-guide/

On the upgrades i have English and Required >0, title 1607.
But preview shows nothing,
what have i missed?
Thank you

Be sure that you don’t have a GPO that enable this setting.

Under : Computer\Administrative Templates\Windows Components\Store

Turn off the offer to update to the latest version of Windows.

After I changed this setting to Disabled or Not Configured, the update is now discovered as Required.

I read this tips on a forum. Can’t remember where.

How to Use serving plan when we have multiple Geographical locations, different languages being used. As far as I can see it is mentioned or ideal to use one Language. Can you please explain more on scenario of upgrading win10 builds having 5 to 6 Different Languages. Cheers Murthy

Murthy – did you get an answer to your question yet? We, too, have multiple geographical locations, with a dozen languages worldwide. The approach we’re developing now is to create a servicing plan for almost every one of the dozen languages. Here’s how we are proceeding: 1) If the underlying OS is Traditional Chinese, for example, we will create a servicing plan using the Traditional Chinese language update. 2) If the underlying OS is English but with a French language pack, for example, the English language update delivered by the servicing plan will wipe out the French language pack, requiring a new language pack to be installed post-upgrade. We plan to either create a required deployment of the French language pack post-upgrade, or create a task sequence for scenario 2 systems that does an in-place upgrade to the new Windows build and applies the language pack.

Wow. thanks for this guide im so glad i found it!! Im about to take over a project from Win 7 to Win 10 for 3300 users and i believe they are using SCCM. I will definitely be providing this guide to our SCCM admin to see if this can be used. If I have any questions I’ll definitely reach out here on the forum. Thanks again for providing.

First of all – thanks for the guide.
I’m running into a strange behavior and I’m not sure what to do or where I could check for more information related to the following.
I followed the guide until the point of deploying the update package.
Now the problem, I have a couple of testclients in the targeted collection but all of them are just staying under “unknown” -> “Client check passed/active” I really don’t know where or what I could possibly check/test.

Maybe I should mention that our Clients are receiving updates usually from a different WSUS which has nothing to do with the SCCM. Could this may cause the problem?
Sorry for the spam.

Did you ever get this resolved? I’m getting the same thing (although it’s from 1607 to 1703) – Unknown -> “Client check passed/active”. It won’t move past that (currently just testing with one client machine, which happens to be my own).

As far as I know I’ve followed these steps to a T. I’m running Configuration manager 1610 and as soon as I get to the step to select the filters in the Create servicing plan, I don’t get the Feature update to Windows 10 Enterprise, version 1607, en-us isn’t listed, I’m also finding that when doing a search in All Windows 10 Updates it is listed but not deployable. I’m Wondering if it is because of the placement of the ” ” line of the manual KB3159706 article. Would someone be able to let me know where they placed that line?

I think you are experiencing the same thing what is described down below in some other comments. Since they move 1607 to CBB out of CB you won’t find any Upgrades there. I think a lot of people are struggling because that is not what you would expect, right? So if you setting the plan to CBB you should find all the 1607 feature updates (upgrades).

I have followed this to the letter, and my servicing plan to upgrade from 1511 to 1607 fails. I am getting a ToastNotification error in the logs, I have no clue what I am missing?! Upgrade TS works flawlessly

Just a note that Microsoft did not rename their 1607 CBB upgrade, it was still called Feature Update (at least for us). I think it makes more sense to have an obvious distinction between CB and CBB…hopefully that change happens.

Thank you for this article, I’m still trying to iron out all of the necessary settings to get the Win10 servicing and general monthly patching to work as expected. I have a somewhat-related question: Does anyone know exactly what happens to a client machine once its OS version, such as Win10 1507, reaches the status of ‘expired’? I can’t imagine Microsoft would stop providing updates. Is there any consequence at all?
Thanks much,
Bill

Now that Windows 10 1607 has been flagged as CBB, how does the SCCM Console / Servicing Node see this as CBB and no longer just CB? When I click the ‘Preview’ button, after selecting the CB radio button, I’m only presented with Windows 10 Build 1511. Any ideas?

Same thing here. I’ve been testing the deployment of 1607 over the last 2 weeks and noticed that my deployment was gone this morning. I went into my Software Update Groups and the 1607 updates were expired. I figured I would create another deployment and I only see 1511 when clicking the ‘Preview’ button as well.

And if you go back into your Servicing Plans and change it from CB to CBB, the 1607 updates will show up once again.

It’s funny as the day I posted my question, the very next day a new release came out (19th January 2017) and this Feature update now appears as CBB. This matched the timing for global notification of the 1607 CBB release (even though we were advised back on the 29th November 2016) So I guess the newer Feature Update coming down via the Synchronise Software Updates works automatically with the Windows 10 Servicing Wizard’s logic / criteria selection.

Thanks for saving my life, I almost went crazy. 2 months ago I updated the 450PC company (1511 to 1607) through Sevicing plane and now two days I deal with why the same process does not work on the second server.

Hello, great guide
What if our clients is placed all over europe, running different language versions of 1511? Our base image is English, with 8 different language packs on.
Under “Upgrades” you choose only “English”. Does this means, that all computers will end up being english?
And/or, should we then set the correct settings under “Language selection”?
Thanks in advance 🙂
Best regards

Can you do this if your site server is 2008 R2 but on SCCM Build 1610 and your WSUS server is 2012 R2?
I have installed the hotfixes and did the configuration settings on the WSUS server.

good guide. what do we do if we want to roll back to 1511? I’m seeing a handful of issues on some test machines, like links/shortcuts will open to a blank IE page instead of opening the webpage. the lock screen is blank instead of the image we specified and worked in 1511. Cortana now pops up fun facts, which I won’t want in my environment.

All goes well until I try to deploy this to my clients. Keep getting error 0x80091007 “hash value is not correct” and happens for all Win10 1511 clients. I’ve applied all the correct WSUS hotfixes and have re-synced my SUP and DP several times. All hash values match on ESD files from server and clients. Anyone else have ideas on things to check?

Did you ever find a solution for this? We’re pushing Win10 1607 Upgrade to our Current Branch for Business workstations and are seeing the same error on about a dozen machines so far, while

20 machines successfully install the upgrade.

Vad är tilltalande med att vara ett offer och varför är sällan de största offrena offer? Inte jag heller Daniel, jag skulle åtminstone skratta för mig själv om någon öppet började driva att homosexuella män exkluderar kvinnor.

Hi, and thanks for the amazing guide.
I’m ready to go with the win 10 upgrades, just wondering about the “expired” status of the win 10 clients.
If no upgrades are deployed, at some point will they update trough regular windows update, or are they going to remain “expired” for ever?
Thanks,
Ariel

It depend of your Windows Update settings but if your machines are not connecting to Microsoft to update, it will be expired forever.

Do you mean through group policy? To prevent the automated deployment of Windows updates. What GP setting should be configured? This was is a problem I have been dealing deploying the CB version of 1607.

If Software Updates are managed by SCCM, then by default a Windows 10(as any other OS) will not look online for updates/upgrades.

The risk here is, if you remove the SCCM Client or change the Client settings for unmanaged Software Update, then the Windows 10 client can look online for update/upgrade.

I generally use the GPO Computer/Aministrative Templates/Windows Components/Windows Update/ Configure Automatic Updates, set to Disabled.
This prevent mistakes and client will never look online for updates/upgrades. This will not affect the Software Update for the SCCM client

Hope this help.
Jonathan

Hi SCD,
great guides like allways.

I was wondeding that if it’s possible while preparing for downloading Windows 10 Updates just do download Enterprise Versions of the Updates? Any known way to filter?

Great, thks and keep up the great Job.

In the Select the property filters and search criteria, you could add a requirement in the Title for Enterprise.
That should do it!

If you are talking about what is seen in the console, you can achieve this by using Saved Searches (in the Ribbon)
Jonathan

Hello, Thank you for the guide.
We are excited to get this going on our network but we have run into a sync issue.
We installed the hotfixes required and made the changes required by KB3159706
When we kick off the sync we get errors with the Upgrade to Windows 10 **, version 1511, in all it’s flavors and the sync stops. The error it kicks out is

Failed to sync update ***. Error: The Microsoft Software License Terms have not been completely downloaded and

cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.LicenseAgreement.GetById

Do you have any suggestions what could be causing this issue?
Thank you

thank you for the article. I have tried deploying to some laptops, but when attempting the install it fails with error code 0xc1800118 (-1048575720). Will investigate further