How to Upgrade SCCM ConfigMgr Current Branch to Next Version 1511 to 1602


Upgrade process of SCCM Current Branch (CB) is entirely different from the service pack (SP) or feature pack (R2/3) upgrades of previous versions of SCCM (2007, 2012 etc..). You don’t need to download the setup from Microsoft and install it manually. SCCM/ConfigMgr CB site servicing is automated process which will ease loads of headaches of SCCM admins. SCCM CB upgrade using site servicing option is more reliable and I had not seen the need of site recovery/rebuild if in case something goes wrong in between upgrade process. In my opinion, the experience of SCCM CB site servicing is similar to Windows 10 upgrade experience. Can we upgrade SCCM 2012/2007 hierarchies directly to SCCM CB 1602? The answer is NO. We need to first upgrade SCCM 2012/2007 to SCCM CB 1511 and then upgrade SCCM 1511 to 1602 using automatic site servicing.

Upgrade Path ==> SCCM 2007/2012 –> SCCM CB 1511 –> SCCM CB 1602

If you are not able to see the 1602 update in SCCM CB 1511 console, then you can run the PowerShell script in the blog post here. Following is the PS command you need to run to get the updates available in SCCM 1511 console ASAP. Don’t forget to restart SMS Executive service after running the PS command.

.\EnableUpdateRing.ps1 siteservername

C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7 is the folder where the source file of SCCM CB 1602 updates will get automatically downloaded. You can refer to 3 log files to verify the download and other related processes – dmpdownloader.log, ConfigMgrSetup.log and ConfigMgrPrereq.log. If the download is stuck for long time and you can see some errors in DMPDOWNLOADER log then it’s always try your luck by restarting SMS Executive services. Don’t try to run the setup directly from EasySetupPayload folder because that is not at all supported.SCCM_1602_6

Some of the snippets of  dmpdownloader.log file, this will help to understand the Verification phase, start of the download and completion of download stages of “SMS_DMP_DOWNLOADER” thread.

Connecting to MessageDownloader.  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.291-330><thread=2856 (0xB28)>
Checking for preview version~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.485-330><thread=2856 (0xB28)>
Site is preview? no~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.491-330><thread=2856 (0xB28)>
Check whether the site has intune subscription~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.493-330><thread=2856 (0xB28)>
EasySetupDownload thread is starting...  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.513-330><thread=4084 (0xFF4)>

Download Easy setup payloads~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.521-330><thread=4084 (0xFF4)>
Get url~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:04.523-330><thread=4084 (0xFF4)>
Get new Easy Setup Package IDs~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:13.635-330><thread=4084 (0xFF4)>
Found a new available update~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:13.638-330><thread=4084 (0xFF4)>
Go through each package and process~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:13.639-330><thread=4084 (0xFF4)>
The payload to be processed is at C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:13.639-330><thread=4084 (0xFF4)>
Download content for payload 037cd17e-4d7b-40e1-802b-14bb682364c7~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:13.639-330><thread=4084 (0xFF4)>
Download large file with BITs~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:13.642-330><thread=4084 (0xFF4)>
Redirected to URL  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:03:14.146-330><thread=4084 (0xFF4)>

Successfully download redist for 037cd17e-4d7b-40e1-802b-14bb682364c7.~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:24:16.042-330><thread=4084 (0xFF4)>
Write the package meta data to connector's outbox~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:24:16.090-330><thread=4084 (0xFF4)>
The CMU file name is C:\Program Files\Microsoft Configuration Manager\inboxes\\ForwardingMsg\___CMU037cd17e-4d7b-40e1-802b-14bb682364c7.MCM~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:24:16.125-330><thread=4084 (0xFF4)>
outerxml is <ConfigurationManagerUpdateContent Guid="037cd17e-4d7b-40e1-802b-14bb682364c7" State="262146" ReportTime="2016-03-15T04:54:16" />~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:24:16.139-330><thread=4084 (0xFF4)>
Successfully write the update meta into outbox for package 037cd17e-4d7b-40e1-802b-14bb682364c7~~  $$<SMS_DMP_DOWNLOADER><03-15-2016 10:24:16.153-330><thread=4084 (0xFF4)>

Once the download is completed then you would be able to see Configuration Manager 1602 updates in the console as AVAILABLE.


Once SCCM CB 1602 update is in available state, you can right click on it and select on “Install Update Pack” to start the SCCM 1602 upgrade process.


Follow the SCCM 1602 upgrade wizard, it’s very straight forward. Once you finish this wizard it will automatically start the actual upgrade process in the background.


Now you can either monitor SCCM 1511 console “\Monitoring\Overview\Site Servicing Status” or refer to the log files CMUpdate.log, hman.log and SMSProv.log to know the status/progress of the SCCM CB 1602 upgrade process.


The SCCM CB 1602 upgrade process starts with CONFIGURATION_MANAGER_UPDATE thread. This thread is notified about the upgrade process by placing a notification file (.CMI) in “C:\Program Files\Microsoft Configuration Manager\inboxes\” folder.


Detected a change to the "\\\SMS_AC1\inboxes\" directory.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:23.999-330><thread=1176 (0x498)>
INFO: setup type: 1, top level: 1.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:24.146-330><thread=1176 (0x498)>
Checking if the CMU Staging folder already has the content extracted.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:24.157-330><thread=1176 (0x498)>
Creating hash for algorithm 32780  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:24.228-330><thread=1176 (0x498)>
Staging folder has hash = 34798AB3EBE62CBE4B7A6B005746315C8DB4B4EA52D81CAF4AC23420E6FCB5E5  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:24.480-330><thread=1176 (0x498)>
Staging folder (C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\) has hash 2E96AE3C4E89CA0156D9D7586A11A3922B73E1BE562CD09D962E6F13E8E63A8E which does not match hash from content library 34798AB3EBE62CBE4B7A6B005746315C8DB4B4EA52D81CAF4AC23420E6FCB5E5  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:24.481-330><thread=1176 (0x498)>
Delete folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\ returned 0  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:13:24.494-330><thread=1176 (0x498)>
update package content 037CD17E-4D7B-40E1-802B-14BB682364C7 has been expanded to foler C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:20.549-330><thread=1176 (0x498)>
File 'C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\' is signed and trusted.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:20.637-330><thread=1176 (0x498)>
File 'C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\' is signed with MS root cert.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:20.637-330><thread=1176 (0x498)>
Extracting file C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\ to C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:20.638-330><thread=1176 (0x498)>
Extracted C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:22.042-330><thread=1176 (0x498)>
Successfully read file C:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:22.442-330><thread=1176 (0x498)>

During this stage of SCCM CB 1602 upgrade, CONFIGURATION_MANAGER_UPDATE service will get stopped and started again. All the other SCCM CB services will be in stopped state until CM update thread hand over the process to HMAN thread. At this stage, CM Update thread will also check whether the Site Servicing is allowed now or not. If the service windows is set then the upgrade will happen only during the maintenance window schedule.


Waiting for changes to the "\\\SMS_AC1\inboxes\" directories, updates will be polled in 105 seconds...  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:33.991-330><thread=1176 (0x498)>
CONFIGURATION_MANAGER_UPDATE service is stopping...  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:39.060-330><thread=2392 (0x958)>
 RETURN CODE -2  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:39.074-330><thread=1176 (0x498)>
CONFIGURATION_MANAGER_UPDATE service is signalled to stop...  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:39.074-330><thread=1176 (0x498)>
*******************************************************************************  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.255-330><thread=4356 (0x1104)>
CONFIGURATION_MANAGER_UPDATE service is starting...  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.255-330><thread=4356 (0x1104)>
Microsoft System Center Configuration Manager v5.00 (Build 8355)  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.255-330><thread=4356 (0x1104)>
Process ID: 3292  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.255-330><thread=4356 (0x1104)>
Worker thread ID: 4356  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.256-330><thread=4356 (0x1104)>
Set inbox to C:\Program Files\Microsoft Configuration Manager\inboxes\  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.290-330><thread=4356 (0x1104)>
Getting SYSCENTERID & iLicenseType  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.508-330><thread=4356 (0x1104)>
This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.509-330><thread=4356 (0x1104)>
INFO: setup type: 1, top level: 1.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.509-330><thread=4356 (0x1104)>
There is no service window defined for the site server to apply the CM server updates.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.534-330><thread=4356 (0x1104)>
~FQDN for server ACNCM001 is  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:49.539-330><thread=4356 (0x1104)>
INFO: Target computer is a 64 bit operating system.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.810-330><thread=4356 (0x1104)>
INFO: Checking for existing setup information.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.811-330><thread=4356 (0x1104)>
INFO: Setting setup type to  1.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.811-330><thread=4356 (0x1104)>
INFO: Checking for existing SQL information.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.811-330><thread=4356 (0x1104)>
INFO: '' is a valid FQDN.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.811-330><thread=4356 (0x1104)>
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8325~  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.811-330><thread=4356 (0x1104)>
INFO: Phase is 1C7~  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:15:51.811-330><thread=4356 (0x1104)>
INFO: Successfully dropped update pack installed notification to HMan CFD box.  $$<CONFIGURATION_MANAGER_UPDATE><03-15-2016 11:44:41.280-330><thread=4356 (0x1104)>

Once CMUpdate thread dropped update pack install notification to HMan CFD box then SMS_HIERARCHY_MANAGER thread (HMAN.log) will take over the upgrade process. Following are some of the snippets from hman.log.

SMS_EXECUTIVE started SMS_HIERARCHY_MANAGER as thread ID 2652 (0xA5C).  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.207-330><thread=3456 (0xD80)>
~Hierarchy Manager (build 8355) is starting...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.434-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting Hierachy Monitoring Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.434-330><thread=2652 (0xA5C)>
~   Hierachy Monitoring Thread is starting, thread ID = 0x2B0 (688)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.434-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting Hierachy Message Forwarding Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.434-330><thread=2652 (0xA5C)>
~   Hierachy Message Forwarding Thread is starting, thread ID = 0xCFC (3324)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.435-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting Hierachy Site Reassign Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.435-330><thread=2652 (0xA5C)>
~   Hierachy Site Reassign Thread is starting, thread ID = 0xFBC (4028)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.435-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting SQL Monitoring Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.435-330><thread=2652 (0xA5C)>
~   SQL Monitoring Thread is starting, thread ID = 0x135C (4956)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.435-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting CFD Handler Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.443-330><thread=2652 (0xA5C)>
~   CFD Hander Thread is starting, thread ID = 0x7f4 (2036)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.443-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting Configuration Manager Update Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.443-330><thread=2652 (0xA5C)>
Configuration Manager Update Thread is starting, thread ID = 0x1228 (4648)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.444-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting Client Upgrade Handling Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.444-330><thread=2652 (0xA5C)>
Client Upgrade Handling Thread is starting, thread ID = 0x9A8 (2472)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.444-330><thread=2652 (0xA5C)>
~   Hierarchy Manager is starting ISM Handler Thread...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.444-330><thread=2652 (0xA5C)>
~   ISM Hander Thread is starting, thread ID = 0xE2C (3628)  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.444-330><thread=2652 (0xA5C)>
CPublicKeyLookup::Initialize("C:\Program Files\Microsoft Configuration Manager\inboxes\\pubkey")  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.464-330><thread=2652 (0xA5C)>
CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to C:\Program Files\Microsoft Configuration Manager\inboxes\\pubkey~  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.464-330><thread=2652 (0xA5C)>
   CHierarchyManager::THREAD_SQLMonitoring - SQL Monitoring Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.496-330><thread=4956 (0x135C)>
   CHierarchyManager::THREAD_HSSiteReassign - Hierachy Site Reassign Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.496-330><thread=4028 (0xFBC)>
   CHierarchyManager::THREAD_HSMsgForwarding - Hierachy Message Forwarding Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.496-330><thread=3324 (0xCFC)>
   CHierarchyManager::THREAD_HSMonitoring - Hierachy Monitoring Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.497-330><thread=688 (0x2B0)>
   CHierarchyManager::THREAD_ISMHandler - ISM Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.497-330><thread=3628 (0xE2C)>
   CHierarchyManager::THREAD_ClientUpgradeHandler - Client upgrade Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.498-330><thread=2472 (0x9A8)>
   CHierarchyManager::THREAD_CMUHandler - CMU Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.498-330><thread=4648 (0x1228)>
   CHierarchyManager::THREAD_CFDHandler - CFD Thread has started.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.498-330><thread=2036 (0x7F4)>
~Initializing Hierarchy SiteReassign (8355) ...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.499-330><thread=4028 (0xFBC)>
~Initializing Hierarchy Message Forwarding (8355) ...  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:17.500-330><thread=3324 (0xCFC)>
CheckPinResetCertificate() - start the pin reset certificate check task  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:43.776-330><thread=2652 (0xA5C)>
Pin reset cert scan threshold is not met yet.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:43.776-330><thread=2652 (0xA5C)>
HandleRBACPermissions : Check if there is request.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:43.776-330><thread=2652 (0xA5C)>
End sync rbac permissions.  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:43.780-330><thread=2652 (0xA5C)>
Update site server active directory informtion into DB  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:43.782-330><thread=2652 (0xA5C)>
Site AC1 in Sites table: Site status = 1, Detailed status = 110  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:44.948-330><thread=2652 (0xA5C)>
~Processing site control file: Site AC1  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:44.948-330><thread=2652 (0xA5C)>
Update the Sites table: Site=AC1 Parent=~  $$<SMS_HIERARCHY_MANAGER><03-15-2016 11:45:45.374-330><thread=2652 (0xA5C)>

By this time you would be able to see the state of Configuration manager 1602 update is changed from Installing to Installed.


Once SCCM CB 1602 update is installed, under the features node “\Administration\Overview\Cloud Services\Updates and Servicing\Features” you would be able to see the features. The feature “Pre-release – Conditional access for managed PCs” is Turn Off and right click on that feature and click on Turn ON. Feature updates details will be logged in to log file called HMAN.log.


To get SCCM 1511 console upgraded on the primary server site, you need to close the console and open it again. Also, if you go and see the about details of SCCM console, it will give you the following message. “A New version of the console is available (5.00.8355.1000). Click OK to close the console and install the new version now. Click Cancel to continue working with the old console (5.0.8325.1000). Working in the old console might corrupt data



  1. Very nice guide, thank you!
    We’re having issues with updating a 1511 site to 1602 in an offline environment, with serviceconnectiontool.exe. the import goes fine, but the update does not show up in the console. Any ideas?

    • Thank you 🙂
      ServiceConnectionTool.log and HMAN.log are two log files which will come handy in this situation. ServiceConnectionTool.log will ensure the import process went well or not. After the import, if you have not restarted the SMS EXEC service then I would do that first then try to monitor HMAN.log.

      Hope this helps!

  2. Hi,
    I have a problem with sccm 1602. It show me that the upgraded to 1602 5.00.8355.1000 but on the state is still “Installing”. If I go to the CMupdate.log I see there following message:
    Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\” directories, updates will be polled in 600 seconds… $$
    What should I do?

  3. @Ola Holtberget, You can also use the splash.hta in the EasySetupPayLoad directory after you imported the package with ServiceConnectionTool.exe You will get the normal installation procedure, but after that you have an upgraded environment to 1602. So, you have 2 different ways, first way is via the console and is the quickiest and the second is via the traditional way, the splash.hta. If you run the upgrade with splash.hta, don’t forget to download the prerequisites first. You have to download them separately.

  4. Hi, a very nice and handful guide; thank you!

    [I am new to SCCM 2007] My Question is: I am using SCCM 2007 and i would like to know is it possible to upgrade straight to SCCM 2016? or should I upgrade to SCCM 2012 first? I asked here at work why aren’t we upgrading to 2012 and they said “we going to move straight to 2016” and now we have Windows 10 machines which are not patched, i even applied some hotfix (3044077) for Windows 10 Compatibility Pack, but nothing still; now i get an error “WU Agent version too low (7.0.6001.18000), needs to be at least: 7.1.6001.65” So i got this advice “So the only Option for you is to migrate to SCCM Current Branch v1511/v1602.” While searching on the internet i found your page so i would love some guidance! Thank you!


Please enter your comment!
Please enter your name here