Last week Microsoft announced 1602 for SCCM Current Branch Production Environments:

Receiving updates to your System Center Configuration Manager Server(s) is today more important than ever in order to have your SCCM environment keep track with Windows 10 and the ever fast paste with Cloud development where new features are added constantly. To make the updates experience of your SCCM solution as smooth as possible Microsoft has introduced dynamic updates for SCCM. This basically means that you will get a notice in your SCCM Administration console that a new update is available for installation. But there is a but, Microsoft requires you to send data to them in order to actually receive the updates. Now, if your Service Connection Point is set to Online, then you will come to the office one morning with a fresh update waiting to be installed. However, if your Service Connection Point is set to Offline for some reason, then there are some manual steps that need to be done in order to actually retrieve a new update.  Before your read any further I suggest you read the following blogs and articles.

  1. My colleague’s blog, Kent Agerlund about: SCCM Current Branch Dynamic updates and telemtry data
  2. My colleague’s blog, Tim De Keukelaere: Configuration Manager 1511 Updates and Servicing : a closer look at the updating experience
  3. Technet : About the Service Connection Point


If you for some reason do not have a internet connection and/or your service connection point is set to offline then there are 3 main steps that needs to be taken in order to get the new updates.

  1. Prepare Usage data that will be sent to Microsoft
  2. Connect to Microsoft, send usage data and retrive update
  3. Import the update

All this is done with the ServiceConnectionTool.exe which can be found under cd.latest folder.

So how is this done? Go to your SCCM CB server and open an elevated PowerShell prompt and change directory to “Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\ServiceConnectionTool”

Then create this folder and subfolders on a drive:

  1. \ConfigMgrServiceConnection
    1. \ConfigMgrUsageData
    2. \ConfigMgrUpdatePacks

Then from your PowerShell prompt run this command to create which will be sent to Microsoft.

.\ServiceConnectionTool.exe -prepare -usagedatadest D:\ConfigMgrServiceConnection\ConfigMgrUsageData\

Verify result by looking at ServiceConnectionTool.log which is in the same folder as ServiceConnectionTool.exe and that you actually have created in ConfigMgrUsageData folder.



Now, if your ConfigMgr Server is not connected to Internet, then you have to copy both the and the ServiceConnection to a computer or server that is connected since the Telemetry Data will be sent out in exchange for the update package (EasySetup Payload).

Next Run the following command to send data and retrieve update.

.\ServiceConnectionTool.exe -connect -usagedatasrc D:\ConfigMgrServiceConnection\ConfigMgrUsageData\ -updatepackdest D:\ConfigMgrUpdatePacks


Verify result by looking at ServiceConnectionTool.log where you will see that the bits is actually downloading.


When all is done, you should have these files in  .\ConfigMgrUpdatePacks


Next step is now to import the newly downloaded data into your ConfigMgr environment for processing. Return to your ConfigMgr Server and bring .\ConfigMgrUpdatePacks folder with you in case you downloaded them on an other computer or server. On the ConfigMgr server open a Elevated PowerShell prompt and run the following command


.\ServiceConnectionTool.exe -import -updatepacksrc D:\ConfigMgrServiceConnection\ConfigMgrUpdatePacks


This will import the content of  .\ConfigMgrUpdatePacks to D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline

  • ConfigMgr.AdminUIContent.auc will be copied to D:\Program Files\Microsoft Configuration Manager\AdminUIContentPayload
  • will be copied to D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline

Now if you return to these two foldes later and you do not see the files, do not worry. ConfigMgr has moved them to the Inbox folder for further processing. To further monitor what is going on behind the scene you can monitor the following log file; dmpdownloader.log which is located here: D:\Program Files\Microsoft Configuration Manager\Logs


After you have imported the Payload, wait 10 – 20 minutes and you should be able to see the 1602 update being available in the ConfigMgr Console. However, Microsoft has announced that they are slowly rolling out the update globally which means that it could take a while until you see anything. But there is a solution for those who can’t wait. A PowerShell script to the rescue. If your dmpdownloader.log files do not indicate anything happening and your console has no updates available, then go to this link and download the script at the end of the page.

(Right click and Save As to download. Rename the .txt extension to .ps1 after downloading)

When downloaded, open a elevated PowerShell prompt and run the following command

.\EnableUpdateRing.ps1 SCCMServerName


Your update is ready to be installed:


Take a look at this blog post for further instructions on how to actually install the update: Configuration Manager 1511 Updates and Servicing : a closer look at the updating experience


Last but not least, to view your telemetry data before you send them to Microsoft run the following command

.\ServiceConnectionTool.exe -export -dest D:\ConfigMgrServiceConnection\ConfigMgrUsageData\UsageData.csv


Do not forget to leave a comment if you have any questions – Have a great Easter! Smilefjes