Consulting ServicesNeed help with your SCCM infrastructure ? Consult our fixed price consulting plans to see our rates or contact us for a custom quote.
The first Update Rollupfor SCCM Current Branch (1702) is now available. This post is a complete SCCM 1702 Update Rollup 1 (KB4010155) installation guide. If you’re looking for a complete SCCM 1511 installation guide, see our blog series which covers it all. You can’t install this upgrade if you are running SCCM 2012. You need to be running SCCM 1702 to apply this update.
Installing SCCM upgrades is important for your infrastructure. It fixes a lot of issues from SCCM 1702, which some of them are important.
New Update and Servicing Model
If you’re not familiar with the new SCCM servicing model, read our New Update and Servicing section of the 1602 upgrade post which explain it all.
You may wonder what’s the difference between a Cumulative Update (CU) and an Update Rollup (UR) :
A CU is a new servicing baseline. A post-CU1 hotfix requires CU1 first, whereas a post-UR1 hotfix doesn’t require UR1. Like CU, UR are cumulative which means that UR2 will include previous hotfixes.
*If you are running SCCM 1511, 1602, 1606 or 1610, you first need to upgrade to 1702 prior to applying this Update Rollup, see our blog which covers the upgrade process. Once completed, the Update Rollup 3 will be available under Update and Servicing node.
SCCM 1702 Update Rollup 1 Fixes
Consult this support page for a full list of issues fixed.
Before you begin
Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear in your console once synchronized.
When you install an in-console update: (New Versions,CU,UR,KB)
- It automatically runs a prerequisite check. You can also run this check prior to starting the installation
- It installs at the central administration site (if you have one), and at primary sites automatically. You can control when each primary site server is allowed to update its infrastructure by using Service Windows for site servers
- After a site server updates, all affected site system roles (including instances of the SMS Provider) automatically update. Configuration Manager consoles also prompt the console user to update the console, after the site installs the update
- If an update includes the Configuration Manager client, you are offered the option to test the update in pre-production, or to apply the update to all clients immediately
- After a primary site is updated, secondary sites do not automatically update. Instead, you must initiate the secondary site update
In this post, we’ll be updating a standalone Primary Site Server, console and clients.
It’s a best practice to have some exclusions for your antivirus/anti-malware software on the SCCM server. Here a list for exclusions from SCCM 2012, which is still valid for CB as far as we know.You could also consider disabling the AV prior to installing the update and re-enable it once completed.
Before installing, check if your site is ready for the update :
- Open the SCCM console
- Go to Administration \ Cloud Services \ Updates and Servicing
- In the State column, ensure that the update is Available
- If not already downloaded, hit Download
- If it’s not available, right-click Updates and Servicing and select Check for Updates
- The update state will change to Downloading
- You can follow the download in Dmpdownloader.log
- The update files are stored in the EasyPayload folder in your SCCM Installation directory
SCCM 1702 Update Rollup 1 Installation Guide
Step 1 | SCCM 1702 Update Rollup 1 Prerequisite Check
Before launching the update, we recommend to launch the prerequisite check:
- Open the SCCM console
- Go to Administration \ Cloud Services \ Updates and Servicing
- Right-click the Configuration Manager 1702 Hotfix (KB4019926) update and select Run prerequisite check
- Nothing will happen, the prerequisite check runs in the background. All menu options will be grayed out during the check
- You can monitor prerequisite check by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status
- When completed the State column will show Prerequisite check passed
Step 2 | Launching the SCCM 1702 Update Rollup 1
We are now ready to launch the SCCM 1702 Update Rollup 1. At this point, plan about 30 minutes for the update installation.
- Right click the Configuration Manager 1702 update and select Install Update Pack
- On the General tab, click Next
- In the Client Update Options, select the desired option for your client update
- This new feature allows updating only clients member of a specific collection. Refer to our post here
- On the License Terms tab, accept the licence terms and click Next
- On the Summary tab, review your choices and click Next
- On the Completion tab, close the wizard. The whole process took a minute but the installation is not over, it has been initiated
- During installation, the State column changes to Installing
- You can monitor installation by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status
- … or you can follow detailed installation progress in SCCM Installation Directory\Logs\CMUpdate.log
- When completed, you’ll notice the message There are no pending update package to be processed in the log file
- Refresh the Updates and Servicing node, the State column will be Installed
Updating the consoles
Since 1602, the console has an auto-update feature. At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.
- Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console
- Click OK, console update will start automatically
- Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version
After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 5.0.8498.1711. Note that the Site Version is not changed to the Update Rollup version. This is normal.
The client version will be updated to 5.00.8498.1711 (after updating, see section below)
SCCM 1702 Update Rollup 1 Client Package distribution
You’ll see that the 2 client packages are updated:
- Navigate to Software Library \ Application Management \ Packages
- Check if both packages were updated, if not, select both packages and initiate a Distribute Content to your distribution points
Updating the Clients
Our preferred way to update our clients is by using the Client Upgrade feature:
- Open the SCCM Console
- Go to Administration / Site Configuration / Sites
- Click the Hierarchy Settings in the top ribbon
- Select Client Upgrade tab
- The Upgrade client automatically when the new client update are available checkbox has been enabled
- Review your time frame and adjust it to your needs
Monitor SCCM Client Version Number
You can see our SCCM Client version reports to give detailed information about every client’s versions in your environment. It’s the easiest way to track your client updates.Collections
You can also create a collection that targets clients without the latest client version. I use it to monitor which client haven’t been updated yet.
Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)
Happy updating! 🙂
I was having the same issue and C:\ConfigMgrPrereq.log on showed the issue as not enough disk space. IT was that simple.
I have started the Update for 1702 Hotfix Rollout KB4019926 today.
Prerequisted checks are fine.
Installation works until point – Upgrade site control settings – [In progress]:Upgrading site control settings. Check cmupdate.log for details.
in cmupdate.log the last entry is:
[In progress]:Upgrading site control settings. Check cmupdate.log for details.
It hangs here since 5 hours now.
Nothing happens now.
Does someone have an idea what is going on?
This is the last entry in cmupdate.log:
calling UpgradeProxySetting for role AI Update Service Point
I am unable to find 1702 update rollup on the console. There was an error:-
ERROR: Failed to download Admin UI content payload with exception: Unable to connect to the remote server SMS_DMP_DOWNLOADER 8/9/2017 9:41:16 AM 12800 (0x3200)
Failed to call AdminUIContentDownload. error = Error -2146233079 SMS_DMP_DOWNLOADER 8/9/2017 9:41:16 AM 12800 (0x3200)
AdminUI Content Download thread is exiting… SMS_DMP_DOWNLOADER 8/9/2017 9:41:16 AM 12800 (0x3200)
Checking if dmpdownloader has synced recently… SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
User hasn’t synced in more than 600 seconds. User requested dmpdownloader sync. Will sync. SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Last time user Requested to sync: Wed Aug 09 09:41:14 2017 SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Last time dmpdownloader Synced:Wed Aug 09 02:01:37 2017 SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Last poll time: Wed Aug 09 09:41:24 2017 SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Registering registry key change … SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Calling EasySetupDownload … SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Hasn’t synced recently. SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Generating state message: 0 for package 00000000-0000-0000-0000-000000000000 SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Write the state message in G:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\high\___CMUdonoizcp.SMX SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
Successfully Dropped the state message 0 SMS_DMP_DOWNLOADER 8/9/2017 9:41:24 AM 12436 (0x3094)
What needs to be done when installation is stuck at “Prerequisite check passed”?
I, too, get ‘prerequisite check failed’ for the current state, however, no log files (even the ones in the C:\root) show what the problem is or have the word ‘failure’ in them. Any ideas? I’m totally stumped.
i am having the same issue too. my Problem was an aktive Migration gathering Job. i stop that Task and now the check passed.
I ran the prerequisite checks and everything passed so I started the install. It looks like all but one package has processed. The log continues to show Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…
All services are started and seem to be working. There is nothing in cmupdate.box an done package is left in EasySetupPayload dbef803d-d936-46b3-88fe-a5bdd7a03168
Any idea how ot get this to finish would be greatly appreciated.
Disregard. The install status finally changed to installed and the hotfix became available. Running that completed the process.
Does this update the version of the primary site as well, its still showing my primary as 5.00.8498.1000 and its not giving the option to upgrade the secondary site… I was under the impression the primary site would be 5.00.8498.1711 and give the option to upgrade the secondary sites to the same version…
if I run select dbo.fnGetSecondarySiteCMUpdateStatus (‘secondary site code’) it returns a 0 indicating it needs to be updated but I don’t have the option to. Only thing I can do is recovery secondary site…
Just updated my Primary. Having the same issue, only option is to recover my secondary sites – not upgrade.
This is what I could find, it looks like you do have to recover:
Hi, Do we still need to update this roll up pacth, if we are planning to upgrade SCCM 1702 after the this patch released (Release date of this patch is Jun 9, 2017),
I believe, this patch (KB4019926) should be injected to the existing SCCM 1702 that is available in SCCM console via updates and servicing.
Any idea, how to proceed?
Update rollup are not injected in the major release. After you install 1702, the KB will show up and will be required.
It will only be injected on the next major release like 1709(should be that version number)
Pingback: ConfigMgr 1702 Rollup Update Deployment Gotchas | DollarUnderscore
This popped up in my new SCCM that is soon to go live and when I run it it fails with “prerequisite checks failed”. I for the life of me cannot figure out why as all the logs I have looked have no errors. Any idea where I can check??
I am having the exact same issue. tells me to look in CMUpdate.log but it just has
Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 281 seconds… CONFIGURATION_MANAGER_UPDATE 6/14/2017 11:44:41 AM 1628 (0x065C)
nevermind, i checked the C:\ConfigMgrPrereq.log on my primary site and found what i was missing.