Walking through an upgrade from Microsoft ConfigMgr 1511 to ConfigMgr 1602

Hi everyone, Pramod Kashyap here. I’m a support engineer here at Microsoft and today I’d like to share some things I learned about upgrading to ConfigMgr 1602. There’s some documentation out there already that talks about the upgrade process from Microsoft System Center Configuration Manager v1511 to Configuration Manager v1602, however I wanted to take the opportunity to go through the process and include some logs and screen shots that may help you better understand the process and troubleshoot it in the off chance that something goes wrong.

Getting Ready

Before we start with the actual upgrade process, let’s first go over a few things that you should know in order to ensure that things so smoothly.

  1. Review the Checklist for updating from System Center Configuration Manager version 1511 to 1602. This link has many things you’ll need to be aware of before upgrading.
  2. Be aware that you must be running Configuration Manager build 1511 before you can upgrade to build 1602. If you’re running a previous version of ConfigMgr then you must upgrade to 1511, then upgrade to 1602.

Starting the Download

Now that we’re ready to perform the actual upgrade to 1602, we can kick that off from the Updates and Servicing node of the UI:

clip_image002

The download will start automatically and the progress can be tracked in the SMS downloader log as shown in dmpdownloader.log here:

SMS_DMP_DOWNLOADER is starting…

SMS_DMP_DOWNLOADER 4/18/2016 2:02:08 AM 4616 (0x1208)
Connecting to MessageDownloader. SMS_DMP_DOWNLOADER 4/18/2016 2:02:08 AM 4616 (0x1208)
Checking for preview version SMS_DMP_DOWNLOADER 4/18/2016 2:02:51 AM 4616 (0x1208)
Site is preview? no SMS_DMP_DOWNLOADER 4/18/2016 2:02:51 AM 4616 (0x1208)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:02:51 AM 4616 (0x1208)
EasySetupDownload thread is starting… SMS_DMP_DOWNLOADER 4/18/2016 2:02:51 AM 5324 (0x14CC)
AdminUI Content Download thread is starting… SMS_DMP_DOWNLOADER 4/18/2016 2:02:51 AM 5756 (0x167C)
Download Admin UI content payload SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5756 (0x167C)
Download Easy setup payloads SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5324 (0x14CC)
Get AdminUI content cab url SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5756 (0x167C)
Get manifest.cab url SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5324 (0x14CC)
The payload will be downloaded to C:\Program Files\Microsoft Configuration Manager\AdminUIContentPayload\ConfigMgr.AdminUIContent.AUC SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5756 (0x167C)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5324 (0x14CC)
Download manifest.cab SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5756 (0x167C)
The site is non-hybrid with no intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5324 (0x14CC)
Download manifest.cab SMS_DMP_DOWNLOADER 4/18/2016 2:02:54 AM 5324 (0x14CC)
Redirected to URL https://download.microsoft.com/download/5/2/C/52C5F0D5-2095-4227-BBA4-D3205D9B9714/ConfigMgr.Update.Manifest.cab SMS_DMP_DOWNLOADER 4/18/2016 2:02:58 AM 5324 (0x14CC)
Redirected to URL https://download.microsoft.com/download/8/6/5/8652FD86-65AB-4D77-B1E3-F595F7A40EB7/ConfigMgr.AdminUIContent-8331.cab SMS_DMP_DOWNLOADER 4/18/2016 2:02:58 AM 5756 (0x167C)
Got fwdlink and recreating the httprequest/response SMS_DMP_DOWNLOADER 4/18/2016 2:02:58 AM 5324 (0x14CC)
Got fwdlink and recreating the httprequest/response SMS_DMP_DOWNLOADER 4/18/2016 2:02:58 AM 5756 (0x167C)
File ‘C:\Program Files\Microsoft Configuration Manager\AdminUIContentPayload\ConfigMgr.AdminUIContent.AUC’ is signed and trusted. SMS_DMP_DOWNLOADER 4/18/2016 2:03:01 AM 5756 (0x167C)
File ‘C:\Program Files\Microsoft Configuration Manager\AdminUIContentPayload\ConfigMgr.AdminUIContent.AUC’ is signed with MS root cert. SMS_DMP_DOWNLOADER 4/18/2016 2:03:01 AM 5756 (0x167C)
AdminUI Content Download interval is: every 1440 minutes SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5756 (0x167C)
File ‘C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\ConfigMgr.Update.Manifest.cab’ is signed and trusted. SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
File ‘C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\ConfigMgr.Update.Manifest.cab’ is signed with MS root cert. SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Finished calling verify manifest SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Manifest.cab was successfully moved to the connector outbox SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Get new Easy Setup Package IDs SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Found a new avilable update SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Go through each package and process SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)

The payload to be processed is at C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)Download content for payload 609f1263-04e0-49a8-940b-09e0e34de2d2 SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Download large file with BITs SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Redirected to URL http://download.microsoft.com/download/E/3/A/E3A89E8D-F1F4-4AAA-BF2F-1C157142894B/609F1263-04E0-49A8-940B-09E0E34DE2D2.cab SMS_DMP_DOWNLOADER 4/18/2016 2:03:02 AM 5324 (0x14CC)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:08:22 AM 4616 (0x1208)
Verify the payload signature, hash value and extract the payload SMS_DMP_DOWNLOADER 4/18/2016 2:10:04 AM 5324 (0x14CC)

File ‘C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab’ is signed and trusted. SMS_DMP_DOWNLOADER 4/18/2016 2:10:09 AM 5324 (0x14CC)
File C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 4/18/2016 2:20:55 AM 5324 (0x14CC)
File SMSSETUP\OSD\Tools\WTG\BitLocker\I386\OsdBitLocker_wtg.exe is being extracted SMS_DMP_DOWNLOADER 4/18/2016 2:20:55 AM 5324 (0x14CC)
File C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 4/18/2016 2:20:55 AM 5324 (0x14CC)
File SMSSETUP\OSD\Tools\WTG\BitLocker\x64\OsdBitLocker_wtg.exe is being extracted SMS_DMP_DOWNLOADER 4/18/2016 2:20:55 AM 5324 (0x14CC)
File C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2.cab has been extracted with 0 SMS_DMP_DOWNLOADER 4/18/2016 2:20:56 AM 5324 (0x14CC)
Check if there is redist to download for update, 609f1263-04e0-49a8-940b-09e0e34de2d2 SMS_DMP_DOWNLOADER 4/18/2016 2:20:56 AM 5324 (0x14CC)
Download redist for update 609f1263-04e0-49a8-940b-09e0e34de2d2 SMS_DMP_DOWNLOADER 4/18/2016 2:20:58 AM 5324 (0x14CC)
Start to download redist for 609f1263-04e0-49a8-940b-09e0e34de2d2 with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=724436 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=724434 /RedistVersion 112015 /NoUI “\\VNCAS.CONTOSO.COM\EasySetupPayload\609f1263-04e0-49a8-940b-09e0e34de2d2\redist” . SMS_DMP_DOWNLOADER 4/18/2016 2:20:59 AM 5324 (0x14CC)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:23:22 AM 4616 (0x1208)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:28:23 AM 4616 (0x1208)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:33:23 AM 4616 (0x1208)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:38:23 AM 4616 (0x1208)
Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:43:23 AM 4616 (0x1208)

Successfully download redist for 609f1263-04e0-49a8-940b-09e0e34de2d2. SMS_DMP_DOWNLOADER 4/18/2016 2:45:36 AM 5324 (0x14CC)

Write the package meta data to connector’s outbox SMS_DMP_DOWNLOADER 4/18/2016 2:45:36 AM 5324 (0x14CC)
The CMU file name is C:\Program Files\Microsoft Configuration Manager\inboxes\hman.box\ForwardingMsg\___CMU609f1263-04e0-49a8-940b-09e0e34de2d2.MCM SMS_DMP_DOWNLOADER 4/18/2016 2:45:36 AM 5324 (0x14CC)

Check whether the site has intune subscription SMS_DMP_DOWNLOADER 4/18/2016 2:45:36 AM 5324 (0x14CC)
outerxml is< ConfigurationManagerUpdateContent Guid=”609f1263-04e0-49a8-940b-09e0e34de2d2″ State=”262146″ ReportTime=”2016-04-18T09:45:36″ /> SMS_DMP_DOWNLOADER 4/18/2016 2:45:36 AM 5324 (0x14CC)
Successfully write the update meta into outbox for package 609f1263-04e0-49a8-940b-09e0e34de2d2 SMS_DMP_DOWNLOADER 4/18/2016 2:45:37 AM 5324 (0x14CC)
Download QFE payloads SMS_DMP_DOWNLOADER 4/18/2016 2:45:37 AM 5324 (0x14CC)
searching for QFE packages in C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline SMS_DMP_DOWNLOADER 4/18/2016 2:45:37 AM 5324 (0x14CC)

Next, the files that are downloaded are saved and extracted to a shared folder (EasysetupPayload) on the Service Connection Point server:

\\Site Server Share\EasySetupPayload:

clip_image009

– or –

Program Files\Microsoft Configuration Manager\EasySetupPayload:

clip_image007

Replication

At this point the package is created as shown below. Note that this is just like the Client Upgrade Package and only visible in the Content Status tab.

clip_image003

Now we start processing the package:

Found package properties updated notification for package ‘VCS00010’        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:30 AM        6268 (0x187C)
Adding package ‘VCS00010’ to package processing queue.        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:40 AM        6268 (0x187C)
Started package processing thread for package ‘VCS00010’, thread ID = 0x948 (2376)        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:41 AM        6268 (0x187C)
Info: package ‘VCS00010’ is set to replicate to site servers only.        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:41 AM        2376 (0x0948)
STATMSG: ID=2300 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_DISTRIBUTION_MANAGER” SYS=VNCAS.contoso.com SITE=VCS PID=6584 TID=2376 GMTDATE=Mon Apr 18 10:57:41.376 2016 ISTR0=”Configuration Manager Easy Setup Package” ISTR1=”VCS00010″ ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=1 AID0=400 AVAL0=”VCS00010″        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:41 AM        2376 (0x0948)
Start adding package VCS00010…        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:41 AM        2376 (0x0948)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=VCS00010, Version=1, Status=2300        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:41 AM        2376 (0x0948)
Taking package snapshot for package VCS00010 from source \\VNCAS.CONTOSO.COM\EasySetupPayLoad\609F1263-04E0-49A8-940B-09E0E34DE2D2        SMS_DISTRIBUTION_MANAGER        4/18/2016 3:57:41 AM        2376 (0x0948)
The hash for algorithm 32780 is F15F6756075AC6BC64B9A9F7B6F09DB35BBA8FE95D8CDB216719336B2A06BC6A        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:30:59 AM        2376 (0x0948)
The RDC signature hash for algorithm 32780 is 20D3B2515A5D894CEB5E05ABE325CABC496E5F4328CDBC63E75CC6EA471A90F1        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:30:59 AM        2376 (0x0948)
Adding these contents to the package VCS00010 version 1.        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:01 AM        2376 (0x0948)
STATMSG: ID=2376 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_DISTRIBUTION_MANAGER” SYS=VNCAS.contoso.com SITE=VCS PID=6584 TID=2376 GMTDATE=Mon Apr 18 11:31:01.221 2016 ISTR0=”VCS00010″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=1 AID0=400 AVAL0=”VCS00010″        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:01 AM        2376 (0x0948)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=VCS00010, Version=1, Status=2376        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:01 AM        2376 (0x0948)
Adding these contents to the package VCS00010 version 1.        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:03 AM        2376 (0x0948)
Successfully created/updated the package VCS00010        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:04 AM        2376 (0x0948)
STATMSG: ID=2311 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_DISTRIBUTION_MANAGER” SYS=VNCAS.contoso.com SITE=VCS PID=6584 TID=2376 GMTDATE=Mon Apr 18 11:31:04.767 2016 ISTR0=”VCS00010″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=1 AID0=400 AVAL0=”VCS00010″        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:04 AM        2376 (0x0948)
ProcessSiteReplicatePkg skip current site VCS.        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:04 AM        2376 (0x0948)
Package VCS00010 does not have a preferred sender.        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:05 AM        2376 (0x0948)
STATMSG: ID=2333 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_DISTRIBUTION_MANAGER” SYS=VNCAS.contoso.com SITE=VCS PID=6584 TID=2376 GMTDATE=Mon Apr 18 11:31:05.677 2016 ISTR0=”VCS00010″ ISTR1=”VNP” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=1 AID0=400 AVAL0=”VCS00010″        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:05 AM        2376 (0x0948)
Needs to send the compressed package for package VCS00010 to site VNP        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:05 AM        2376 (0x0948)
Sending a copy of package VCS00010 to site VNP        SMS_DISTRIBUTION_MANAGER        4/18/2016 4:31:05 AM        2376 (0x0948)

clip_image005

NOTE When troubleshooting replication related issues, check hman.log,  distmgr.log, sender.log on the CAS or stand alone primary and despool.log on the primaries.

The package will get replicated to all the sites and then the prereq check starts. During file replication, you won’t see any status in the Monitoring node.

Prerequisites Check and Install

Now that the package is downloaded and replicated, we start the installation by doing a prerequisites check. The progress can be monitored via the UI as shown here:

clip_image011

clip_image013

clip_image015

clip_image017

You can also follow along in the cmupdate.log as shown here:

Detected a change to the “\\VNCAS.contoso.com\SMS_VCS\inboxes\cmupdate.box” directory.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:43 AM        1824 (0x0720)
INFO: setup type: 8, top level: 1.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:50 AM        1824 (0x0720)
Checking if the CMU Staging folder already has the content extracted.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:50 AM        1824 (0x0720)
Creating hash for algorithm 32780        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:50 AM        1824 (0x0720)
Staging folder has hash = 34798AB3EBE62CBE4B7A6B005746315C8DB4B4EA52D81CAF4AC23420E6FCB5E5        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:53 AM        1824 (0x0720)
Staging folder (C:\Program Files\Microsoft Configuration Manager\CMUStaging\609F1263-04E0-49A8-940B-09E0E34DE2D2\) has hash F15F6756075AC6BC64B9A9F7B6F09DB35BBA8FE95D8CDB216719336B2A06BC6A which does not match hash from content library 34798AB3EBE62CBE4B7A6B005746315C8DB4B4EA52D81CAF4AC23420E6FCB5E5        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:53 AM        1824 (0x0720)
Delete folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\609F1263-04E0-49A8-940B-09E0E34DE2D2\ returned 0        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:46:54 AM        1824 (0x0720)
update package content 609F1263-04E0-49A8-940B-09E0E34DE2D2 has been expanded to foler C:\Program Files\Microsoft Configuration Manager\CMUStaging\609F1263-04E0-49A8-940B-09E0E34DE2D2\        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:39 AM        1824 (0x0720)
INFO: Language: Mobile Device (INTL), LangPack: 0.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:44 AM        1824 (0x0720)
INFO: Configuration Manager Build Number = 8355        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:44 AM        1824 (0x0720)
INFO: Configuration Manager Version = 5.0        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:44 AM        1824 (0x0720)
INFO: Configuration Manager Minimum Build Number = 800        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:44 AM        1824 (0x0720)
Preparing prereq check for site server [VNCAS.contoso.com]…        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:44 AM        1824 (0x0720)
prereqcore has hash value SHA256:182DB394330E89831B43D85BE9C4A0324F955E3DB9FD753FE3F85BD3E1A410D4        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:44 AM        1824 (0x0720)
Running prereq checking against Server [VNCAS.contoso.com] …        CONFIGURATION_MANAGER_UPDATE        4/18/2016 4:56:45 AM        1824 (0x0720)

clip_image019

Then during the install we see entries similar to these:

PackageGuid        DateReleased        FullVersion        DateCreated        MinCMVersion        MaxCMVersion        MoreInfoLink        State        Flag        UpdateMapHash        UpdateMapHashAlgorithm        LastUpdateTime        Error        Reserved        ClientVersion        UpdateType        Impact        RedistVersion
609F1263-04E0-49A8-940B-09E0E34DE2D2        2016-03-09 00:00:00.000        5.00.8355.1000        2016-04-14 09:01:18.093        5.00.8325.0000        5.00.8325.9999       
http://go.microsoft.com/fwlink/?LinkID=626569        196609        2        8521ECC05999517833ED9610A9B4EA77086AF89D039FC3E8185036688338DBDA        SHA256        2016-04-18 12:56:32.383        NULL                5.00.8355.1000        0        31        112015

State – 196609
Flag – 2

CONFIGURATION_MANAGER_UPDATE service is starting…        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:29 AM        6604 (0x19CC)
Microsoft System Center Configuration Manager v5.00 (Build 8355)        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:29 AM        6604 (0x19CC)
Process ID: 3456        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:29 AM        6604 (0x19CC)
Worker thread ID: 6604        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:29 AM        6604 (0x19CC)
Set inbox to C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:29 AM        6604 (0x19CC)
Getting SYSCENTERID & iLicenseType        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:31 AM        6604 (0x19CC)
This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:31 AM        6604 (0x19CC)
INFO: setup type: 8, top level: 1.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:31 AM        6604 (0x19CC)
There is no service window defined for the site server to apply the CM server updates.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
FQDN for server VNCAS is VNCAS.contoso.com        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Target computer is a 64 bit operating system.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Checking for existing setup information.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Setting setup type to  8.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Checking for existing SQL information.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: ‘VNCAS.contoso.com’ is a valid FQDN.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Verifying the registry entry for Asset Intelligence installation        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8325        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Phase is 1C7        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: SDK Provider is on VNCAS.contoso.com.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
Set working directory to the staging folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\609F1263-04E0-49A8-940B-09E0E34DE2D2\SMSSetup        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Setting the default CSV folder path        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Language: Mobile Device (INTL), LangPack: 0.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Configuration Manager Build Number = 8355        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Configuration Manager Version = 5.0        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
INFO: Configuration Manager Minimum Build Number = 800        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
Checking if the CMU Staging folder already has the content extracted.        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)
Creating hash for algorithm 32780        CONFIGURATION_MANAGER_UPDATE        4/18/2016 5:56:32 AM        6604 (0x19CC)

Prereq check passed, site installation will continue.        Configuration Manager Setup        4/18/2016 5:55:59 AM        5716 (0x1654)
INFO: VNCAS.contoso.com is a 64 bit operating system.        Configuration Manager Setup        4/18/2016 5:56:00 AM        5716 (0x1654)

INFO: Successfully dropped update pack installed notification to HMan CFD box.        CONFIGURATION_MANAGER_UPDATE        4/19/2016 3:19:19 AM        3488 (0x0DA0)
Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…        CONFIGURATION_MANAGER_UPDATE        4/19/2016 3:19:19 AM        3488 (0x0DA0)

Installed:
State – 196612

After CAS is upgraded and Primary in progress state will be – 196611

After the upgrade succeeds, you will be asked to close the console if its open, then you will be asked to upgrade the console as well. You’ll want to do this because using an older version of the console can corrupt data. Assuming you click OK at this point, the console is closed and the new console MSI file is downloaded and run. This will remove the older version and install the new version which you can then use to verify your new version of Configuration Manager:

clip_image020

Common Issues

Here are a couple notes covering a couple issues you may face during the upgrade process:

1. Downloading the files: If you experience problems initially downloading the upgrade files, restart SMSEXEC. This will reinitiate the DMP Downloader component which has a default download interval of 1440 minutes (1 day). Note that you can change this interval via the registry value below but only in build 1602. This registry value is not exposed in build 1511 and prior versions.

clip_image022

2. Both during and after the upgrade, keep an eye on the State value in “CM_UpdatePackages” for the package “609F1263-04E0-49A8-940B-09E0E34DE2D2” (Package GUID). This GUID is same in all cases. There have been some instances where the upgrade is successful but the value is not updated and thus it stills shows as being in the Installing state. This will help you track the upgrade process and at what stage it is currently in.

3. Please make sure that you have at least 15GB of free space on the drive. This is one of the prerequisites, and this as well as other checks can be tracked in the ConfigMgrPrereq log. Installation or upgrade process is logged in CMUpdate.log.

4. You may see entries similar to those below continuously in hman.log:

C:\Program Files\Microsoft Configuration Manager\CMUStaging\ApplicabilityChecks\CM1511-KB3122637_AppCheck.sql has hash value SHA256:5D9478C20EEDC47BD884AB8720125A31204E17E52B3B97BCD4C92094A8637970            SMS_HIERARCHY_MANAGER       4/18/2016 4:01:21 AM    5004 (0x138C)
Configuration Manager Update (PackageGuid=10BE05BB-BE45-4D65-8C3D-D12BAC995233) is not applicable and should be filtered.          SMS_HIERARCHY_MANAGER       4/18/2016 4:01:21 AM    5004 (0x138C)
Successfully checking Site server readiness for update.     SMS_HIERARCHY_MANAGER       4/18/2016 4:01:21 AM    5004 (0x138C)

These messages can be ignored, because if you check the version of this package in the CM_UpdatePackages table you’ll see that it is 5.00.8325.1102, which is lower than that of 1602 (which is 5.00.8355.1000) and hence is identified as Not Applicable. Please note that this can also happen even if you have not upgraded to 1602. 10BE05BB-BE454D65-8C3D-D12BAC995233 is Exchange connector QFE and won’t be applicable to your site if you didn’t have the on-premise Exchange connector installed.

Hopefully this will be helpful as you plan and execute your own upgrade to Configuration Manager 1602. And don’t forget, if you have any feedback please let the Configuration Manager team know at https://connect.microsoft.com/ConfigurationManagervnext/Feedback.

Pramod Kashyap, Support Engineer
Microsoft