After updating to System Center Configuration Manager Technical Preview 1604, the site server component SMS_BUSINESS_APP_PROCESS_MANAGER on the site server is not reinstalled by Site Component Manager.  This prevents onboarded applications from the Windows Store for Business from appearing in the Administrator console.

To work around this, please run the following PowerShell script as an administrator on your site server:

https://gallery.technet.microsoft.com/Technical-Preview-1604-b2213345/

This script will reinstall the SMS_BUSINESS_APP_PROCESS_MANAGER component and restore the Windows Store for Business functionality.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Please be aware that the value that is defined for the SMSTSRebootDelay task sequence variable is not honored for restarts after the first restart when multiple applications are installed by using a dynamic variable list in Microsoft Configuration Manager. The default restart time-out value is used instead.

A supported hotfix is now available to address this issue. After this hotfix is applied to target clients, the value that is defined for the SMSTSRebootDelay variable will be honored for the whole task sequence. This update applies to Microsoft System Center 2012 R2 Configuration Manager Service Pack 1 and Microsoft System Center 2012 Configuration Manager Service Pack 2 (ConfigMgr 2012 and ConfigMgr 2012 R2).

For all the details including download and installation instructions, please see the following:

3151994 – The SMSTSRebootDelay variable does not work for multiple restarts in System Center 2012 Configuration Manager (https://support.microsoft.com/en-us/kb/3151994)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Today we’re happy to announce a preview of Microsoft’s new documentation service: https://docs.microsoft.com. The preview is launching with a showcase of content for Enterprise Mobility, which consists of Advanced Threat Analytics, Azure Active Directory, Azure Remote App, Multi-factor Authentication, Azure Rights Management, Intune and Microsoft Identity Manager. In the future, as our platform matures with the help of your feedback, we will migrate more of our documentation to this new experience.

Why docs.microsoft.com?

In short, content matters. We interviewed and surveyed hundreds of developers and IT pros and sifted through years of website feedback, and it soon became clear that we needed to make a change and create a modern web experience for content. The first thing we did was evaluate our existing content infrastructure: TechNet and MSDN. Both sites are built on a 10-15 year-old codebase with an archaic publishing and deployment system that was never designed to run on the cloud. For our new documentation service, our focus was not only on the experience, but also on the content we create and how each of you consume it. For years you have told us to go beyond walls of text with feature-level content and helps you implement solutions to your business problems. We knew that the content we delivered and the platform we built must make it easy for you to learn and deploy solutions. We realized that to get the overall experience right we needed to start from scratch, and from this effort comes https://docs.microsoft.com.

If you’d like to see a detailed walkthrough of how docs.microsoft.com works then head over here for an in-depth look at all the new features, including the cool new social integration as well as the new feedback options available for each article. We hope you enjoy the preview version of docs.microsoft.com, and please send us your feedback to http://aka.ms/sitefeedback.

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:

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:

– or –

Program Files\Microsoft Configuration Manager\EasySetupPayload:

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.

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)

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:

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)

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:

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.

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-BE45-4D65-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

Hi everyone, Buz Brodin here. Recently I worked on a problem where a customer reported that sometimes App-V applications (shortcuts on desktops) that were deployed to users logged in to a Citrix server never appeared for some of the users, or they did appear but showed up rather slowly (within two hours or so). For other users everything seemed to work perfectly fine.

When this happens, it’s usually because one of the required applications is failing, which can cause a delay of up to 90 minutes before the other applications are deployed. If you see a scenario such as this one, here is a method you can use to find what is targeted to a user SID and what application is having the problem.

1. First, have one of the users who is experiencing the problem log in to the system. Once you confirm that the user did not receive the required applications, collect the CIAGENT and the DCMAGENT logs and use CMTrace to combine them into one file.

2. Using the SID of the user (in this example we’ll use S-1-5-21-2414399092-292161696-3476272628-181234), search for InitiateCIAgentJob in the combined log and find the first instance that mentions this SID. Here you will find the CIAGENT and DCMAGENT Job ID:

DCMAgentJob({2CAFAAAF-E4DE-46BD-8D8B-6488E21C6F61}): CDCMAgent::InitiateCIAgentJob – Starting CI Agent Job {B4B0C5E5-C9B0-4D87-9058-F8B03C820A78} for target: S-1-5-21-2414399092-292161696-3476272628-181234. Refer to this CI agent job ID in ciagent.log for more details DCMAgent 3/25/2016 4:21:47 PM 5244 (0x147C)

DCMAgentJob  ({2CAFAAAF-E4DE-46BD-8D8B-6488E21C6F61})

CIAGENTLOG – {B4B0C5E5-C9B0-4D87-9058-F8B03C820A78}

3. Filter for the CIAGENT JOB ID first: This shows all of the Application IDs targeted for that user as well as the status at the job. Here’s an example showing some of the required applications:

CIAgentJob({B4B0C5E5-C9B0-4D87-9058-F8B03C820A78}): AddCI called for ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_5f588354-71d3-4dce-b366-5fd7db6331cf:6 CIAgent 3/25/2016 4:21:47 PM 5244 (0x147C)
CIAgentJob({B4B0C5E5-C9B0-4D87-9058-F8B03C820A78}): AddCI called for ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_0ef22753-ceab-4941-bafe-8fe937addbf6:10 CIAgent 3/25/2016 4:21:47 PM 5244 (0x147C)
CIAgentJob({B4B0C5E5-C9B0-4D87-9058-F8B03C820A78}): AddCI called for ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_2166f012-1d6e-4b5a-84a9-20b0379b2fed:9 CIAgent 3/25/2016 4:21:47 PM 5244 (0x147C)

4. This is the important part: Notice the status of the job noting a failure:

CIAgentJob({B4B0C5E5-C9B0-4D87-9058-F8B03C820A78}): QueueDebug – Executing Event. CIAgent 3/25/2016 4:21:47 PM 9576 (0x2568)

5. Now look at the time between this line and the previous line – it’s exactly 90 minutes, which is the default timeout for DCMAGENT.

CIAgentJob({B4B0C5E5-C9B0-4D87-9058-F8B03C820A78}): CAgentJob::VersionInfoTimedOut for ModelName ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_4ff04363-a52b-4fb1-a2f0-3328d9b346e3, version 8 not available. CIAgent 3/25/2016 5:51:47 PM 9448 (0x24E8)

Now we know something about what failed; it was this required application: RequiredApplication_4ff04363-a52b-4fb1-a2f0-3328d9b346e3, and it failed with this message version 8 not available.

6. Next, filter your log for that RequiredApplicationID: 4ff04363-a52b-4fb1-a2f0-3328d9b346e3. You’ll probably see entries similar to the following:

CIAgentJob({5E261F3F-8BB7-4E9F-9FE9-57DC253D6AD2}): CAgentJob::VersionInfoTimedOut for ModelName ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_4ff04363-a52b-4fb1-a2f0-3328d9b346e3, version 8 not available. CIAgent 3/25/2016 5:32:05 PM 12312 (0x3018)

VersionInfo ModelName=ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_4ff04363-a52b-4fb1-a2f0-3328d9b346e3, Version=8, IsVersionSpecific=TRUE timed out CIAgent 3/25/2016 5:32:05 PM 5172 (0x1434)

5. For the final step, unfilter your log and search for this required application string (4ff04363-a52b-4fb1-a2f0-3328d9b346e3:8). You are looking for an entry that starts with PopulateCIsFromAssignment:

DCMAgentJob({6D2C8935-2B30-468E-8901-739238DE3D32}): CDCMAgentJob::PopulateCIsFromAssignment – [SKIPPING] CI policy Id :ScopeId_AA0BA009-8B99-4F9F-A54D-4E5F3F43F0FA/RequiredApplication_4ff04363-a52b-4fb1-a2f0-3328d9b346e3 version:8 – Assignment:{4B634692-9479-4904-8BAA-42B3BCD9C7C0}. DCMAgent 3/25/2016 4:08:22 PM 8416 (0x20E0)

From there, go up a few lines to the first instance of CDCMAgentJob that comes before PopulateCIsFromAssignment. This gives you the friendly name of the deployment that failed:

DCMAgentJob({6D2C8935-2B30-468E-8901-739238DE3D32}): CDCMAgentJob::SetupJob – Add assignment Contoso_Application_73003101084_r1_APPL-D-ContosoApplication-7300-3-10-1084_Install({4B634692-9479-4904-8BAA-42B3BCD9C7C0}) DCMAgent 3/25/2016 4:08:22 PM 8416 (0x20E0)

Contoso_Application_73003101084_r1_APPL-D-ContosoApplication-7300-3-10-1084_Install

Now that you know which deployment is failing, simply remove this deployment and the problem with the 90 minute delay should be resolved.

Hopefully this method will make troubleshooting these issues a bit easier moving forward. Keep in mind that other things also need to happen in this scenario, such as CIAGENT download and policy requests, but at its core DCMAGENT is doing the work here.

Buz Brodin, Senior Support Escalation Engineer
Microsoft Enterprise Cloud Group

Hi everyone, Luke Ramsdale here with a tip for you on using mandatory user profiles in an integrated App-V/ConfigMgr environment.

There are a number of scenarios where an organization may require that the user profiles on their workstations not be stored locally. For example, maybe mandatory profiles are configured or the profiles are deleted after the user logs off, or VDI machines are in use and are not persistent. When an organization uses Microsoft Application Virtualization (App-V) integrated with Configuration Manager, this scenario can lead to problems when deploying virtual applications to collections of users. This is because when the user profile is returned to its mandatory state, or it is deleted after logging off, the App-V files stored in the user profile are also deleted. This proves problematic when the users eventually log back on to the machines because the shortcuts and part of the virtual applications are not available until the application deployment evaluation cycle runs, which is by default every 7 days.

There are a couple of ways to work around this issue which will allow a user to access these applications automatically when logging on for a second time or any subsequent attempts:

The first option is to run the application deployment evaluation cycle programmatically via a script every time a user logs in to a machine. Note that this needs to be evaluated carefully because there are network and client performance implications of performing this action at scale.

An example of the command line you would need to run would be:

WMIC.exe /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000121}” /NOINTERACTIVE

The second option is to run this PowerShell script via a traditional package and program using the following method:

1. Create a new package and configure the PowerShell script as the source.

2. Create a standard program with the following command line:

%WinDir%\Sysnative\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File .\Republish_App-V_5_package_script.ps1

3. Configure the program to run “hidden”.

4. Configure it to run with administrative rights and to “only run when a user is logged on”:

5. When the package has been configured and deployed to the distribution point, deploy the package program as required with a date-time and a “Log on” assignment schedule, and ensure the rerun behavior is configured to “Always rerun program”:

All other deployment settings can be left at the default values.

That’s it! Once this is deployed, App-V shortcuts and the associated files should be available every time the user logs on.

Note that this applies to Microsoft System Center 2012 R2 Configuration Manager (ConfigMgr 2012 R2) but should also apply newer versions as well (current branch).

Luke Ramsdale, Support Escalation Engineer
Microsoft Enterprise Cloud Group

We’ve spent a lot of time over the past year talking about Windows 10 (including new roadmap details), but we also know that organizations are still working with Windows 7, regularly updating their Windows 7 SP1 images to include the latest updates, app versions and more. Because of this, we’re happy to announce that we’re making available a new convenience rollup for Windows 7 SP1 that will help. This new rollup contains all of the security and non-security fixes released since the release of Windows 7 Service Pack 1 that are suitable for general distribution, through April 2016.  Install this one update and then you only need new updates released after April 2016.

We’re also announcing that non-security updates for the following Windows versions will be available as a monthly rollup:

• Windows 7 SP1
• Windows 8.1
• Windows Server 2008 R2 SP1
• Windows Server 2012
• Windows Server 2012 R2

This means that each month we will release a single update containing all of the non-security fixes for that month. For all the details regarding these new rollup packages please see the following:

Simplifying updates for Windows 7 and 8.1

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Hi everyone, just a quick note to let you know we have a new guide available that helps you understand the Install Application task sequence process in Configuration Manager and troubleshoot common problems that can occur. The guide begins where the Install Application task sequence process kicks off and examines each of the major steps. Suggestions for troubleshooting failures are provided as you progress through the guide.

The information in this guide applies to System Center 2012 Configuration Manager (ConfigMgr 2012), System Center 2012 R2 Configuration Manager (ConfigMgr 2012 R2) and all versions of Configuration Manager current branch (e.g. Configuration Manager 1511 and Configuration Manager 1602).

You can find more information and get started with the guide here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

A new Update Rollup package is now available for ConfigMgr 1602. 

Issues that are fixed

Remote Control: The SccmRdpsystem.exe process stops running on Windows Embedded clients after you try to start Remote Control.

Site Systems: The DBSchemaChangeHistory table in the site database grows excessively because of incorrectly reported changes.

Microsoft Intune and mobile device management:

• The Service Connection Point may take 30 minutes to recognize a newly added Intune subscription.
• Some mobile device management actions, such as a remote wipe, can be initiated by using the incorrect certificate data. This causes those actions to fail.
• The Service Connection Point may try to renew the wrong certificate that’s used to communicate with Microsoft Intune if multiple certificates are installed that have the same expiration date.
• An “Invalid parameter to CIM setting” message is displayed when you try to check the baseline deployment status of a custom IOS or Mac profile.
• The SMS_DMP_Connector registry key remains after you remove a Microsoft Intune subscription. Successive attempts to add a new Microsoft Intune subscription trigger authentication errors.

For complete details including download and installation instructions, please see the following:

3155482 – Update rollup for System Center Configuration Manager current branch, version 1602

(https://support.microsoft.com/en-us/kb/3155482)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Version 1602 of System Center Configuration Manager current branch contains many changes intended to both prevent issues and improve features. A list of these changes is included in the Knowledge Base article below. This list doesn’t include all of the changes, but instead captures the work that our product development team believes is most relevant to our broad customer base. Many of these changes are the result of direct customer feedback on product issues as well as ideas for product improvement. Update 1602 is available as an in-console update to be installed at the top-most site in a hierarchy. For more information regarding installation, see Checklist for updating from System Center Configuration Manager version 1511 to 1602.

For the complete and most current list of fixes included in build 1602 please see the following:

3168240 – Summary of changes in System Center Configuration Manager current branch, version 1602 (https://support.microsoft.com/en-us/kb/3168240)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Just a quick note to let know that we have refreshed the 1604 release of the Microsoft System Center Configuration Manager Cmdlet Library previously announced here. This release replaces the previous 1604 release (build 1182) and applies to the following System Center Configuration Manager releases:

• System Center 2012 Configuration Manager R2 SP1
• System Center 2012 Configuration Manager SP2
• System Center Configuration Manager Current Branch

Fixes in this release

• Add/Set-CMGooglePlayDeploymentType and Add/SetCMIosDeploymentType not adding MAM details on Configuration Manager current branch v1511 and above
• Add/Set-CMMsiDeploymentType not having option to configure InstallationBehaviorType
• Add-CMCollectionToAdministrativeUser UserId parameter not recognized
• Get/New/Remove/Set-CMDeviceVariable not working with pipelined objects
• Move-CMObject and New/Set-CMSoftwareUpdateAutoDeploymentRule fixes
• New-CMWindowsServicingPlan unable to set AvailableTime or SuccessPercentage
• Remove-CMAutoDeploymentRuleDeployment missing Force parameter
• Remove-CMIntuneSubscription not working
• Set-CMConditionalAccessPolicy not recognizing Add/RemoveExcludedCollectionName/Id
• Set-CMIntuneSubscriptionAppleMdmProperty and Set-CMIntuneSubscriptionWindowsPhoneProperty NullReferenceException failures

For more information including the release notes and a download link, please see the following:

System Center Configuration Manager Cmdlet Library

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Just a quick note to let you know that Update 1606 for Configuration Manager Technical Preview 5 is now available. Update 1606 for TP5 is available directly in the Configuration Manager console, and if you’d like to install the Configuration Manager Technical Preview for the very first time you can find the installation bits in the TechNet Evaluation Center.

For complete details regarding what’s new, see the following post from the Configuration Manager product team:

Update 1606 for Configuration Manager Technical Preview – Available Now!

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 2016 TP

When a Microsoft System Center Configuration Manager (ConfigMgr 1511 or ConfigMgr 1602) site is installed to a directory that has a path that is longer than 68 characters, software that’s available from the Updates and Servicing node in the administrator console may not be downloaded. This problem affects software such as individual hotfixes and new product versions such as the update to ConfigMgr current branch, version 1602. Additionally, errors that resemble the following are recorded in the Dmpdownloader.log file on the service connection point that’s used by the site server:

Error: Failed to calculate hash for file ‘E:\Program Files\Microsoft System Center 2012 R2\Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\Licenses\SYSTEM_CLR_TYPES_FOR_MICROSOFT_SQL_SERVER_2014\System_CLR_Types_for_Microsoft_SQL_Server_2014-Chinese_Traditional.pdf’ with error 0x80070002
Failed to validate hash for file E:\Program Files\…
Failed to install update files. CONFIGURATION_MANAGER_UPDATE

A new update is available to address this issue. Note that for sites that have an installation path that’s longer than 68 characters, ConfigMgr 1602 is listed as Not Applicable in the administrator console regardless of whether this update is installed. After it becomes available, ConfigMgr version 1606 will be listed as Not Applicable if this hotfix is not yet installed. After the hotfix is installed, ConfigMgr 1606 will be listed as Available.

For complete details please see the following:

3163344 – Product updates are not downloaded in System Center Configuration Manager (https://support.microsoft.com/en-us/kb/3163344)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

The Microsoft Configuration Manager team has announced a live Ask Me Anything (AMA) event that will be hosted on reddit.com/r/sccm on June 29th from 1:00 to 5:00 PM PST. This will be a live Q&A forum where the entire Configuration Manager engineering team will be available to answer your questions about features new and old. For more details you can check out there post here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

In December 2015, Microsoft made some major changes to System Center Configuration Manager when the current branch model was introduced. This new model transformed how ConfigMgr was delivered, moving from longer release cycles to regular updates that are designed to support the faster pace of updates for Windows 10 and Microsoft Intune. With this change comes questions, and the Configuration Manager team has posted a FAQ that addresses some of the more common questions customer have. To get more details and check out the FAQ, see the following:

FAQ: System Center Configuration Manager (Current Branch)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Recently, Microsoft IT installed the latest update to System Center Configuration Manager. To upgrade to System Center Configuration Manager version 1602, they used a new in-console service that automates many tasks and helps ensure that they are running the latest version of the product. The new in-console service provides updates as they become available, making it much easier for IT administrators to manage the update process. This also means that there are no more service packs or cumulative update versions to be downloaded and deployed separately. As an added bonus, they were able to use existing infrastructure and complete the update 50 percent faster than previous updates. For all the details regarding how they completed the upgrade, please see the following:

Installing System Center Configuration Manager 1602 using in-console updates

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

ConfigMgr 1602

During an Operating System deployment (OSD) of Windows 10 via System Center Configuration Manager, the Install Software Updates task sequence may freeze when large numbers of updates are applied (e.g. 50 or more). When this problem occurs, the CCMExec and TSInstallSWupdate processes appear to hang. If the thread count is monitored with Task Manager or other tools, the TSInstallSWupdate process shows that approximately 774 threads are in use.

This problem occurs in ConfigMgr 2012 SP2, ConfigMgr 2012 R2 SP1 and ConfigMgr 1602. If you encounter this problem, a supported hotfix is now available from Microsoft. See the Knowledge Base article below for details.

3174008 – Software update installation freezes on System Center Configuration Manager clients (https://support.microsoft.com/en-us/kb/3174008)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

If you’re trying to enroll a device but running into problems, a good place to start troubleshooting is with the new System Center Configuration Manager Hybrid Diagnostic tool. The Hybrid Diagnostic tool runs a series of automated checks that will help reduce the amount of time it takes to find and fix problems, plus it provides insight into some of the more common configuration issues.

To use the tool, simply run it on the computer that hosts the service connection point and specify the device type and UPN. The Hybrid Diagnostic Tool will then run the following automated checks:

• Checks that the SMS Executive service is running.
• Checks for the service connection point certificate.
• Checks for potential conflicts between service connection point certificates.
• Checks for DNS CName entry for the specified UPN.
• Checks for device type enablement in Configuration Manager.
• Checks for known errors in Status Messages.
• Checks for UPN synchronization in AAD.
• Checks that the specified user is a member of the cloud user collection.
• Checks that the AAD ID and cloud user ID match.
• Checks for user exceeding device cap.
• Checks for multiple valid certificates present on Service Connection
  Point.

If one of these checks fails, the More Info link will show you additional details regarding how to resolve the issue.

You can download the tool here, and you can get more details regarding what it does and how to use it here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Just a quick note to let you know that version 1606 of Microsoft Configuration Manager is now available. This update is available in-console for previously installed sites that run ConfigMgr 1511 or ConfigMgr1602. For all the details regarding what’s new, please see the following:

Now Available: Update 1606 for System Center Configuration Manager

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

In System Center 2012 Configuration Manager (ConfigMgr 2012 and ConfigMgr 2012 R2) you may experience the following symptoms related to content distribution:

– Content distribution fails when many distribution points (typically more than 75) are updated at the same time. When this occurs, the HTTPUrl value for Package Status will be blank and the locationservices.log file on target clients will contain entries that resemble the following:

Calling back with empty distribution points list.

– The Distribution Manager component stalls when it attempts to update multiple distribution points. This occurs when there’s a problem with IIS communication on a single remote distribution point. When that problem occurs, communication with other distribution points stalls. Additionally, messages that resemble the following will be recorded approximately every two minutes in the distmgr.log file on the site server:

There are still 1 DP threads active for package CAS00101, waiting for them to complete.
There are still 1 DP threads active for package CAS00102, waiting for them to complete.
There are still 1 DP threads active for package CAS00103, waiting for them to complete.
There are still 2 DP threads active for package CAS00104, waiting for them to complete.

– The StoredPkgVersion value is not restored when a secondary site is recovered from the console. This triggers later failures in content validation and the distmgr.log file on the secondary site contains entries that resemble the following, which also indicate that the StoredPkgVersion value in the database has been reset to 0:

StoredPkgVersion (0) of package Package_ID. StoredPkgVersion in database is 0.

If you experience these symptoms, a supported hotfix is available from Microsoft Support to address this issue. For complete details please see the following:

3174047 – Package content is not distributed in System Center 2012 Configuration Manager (https://support.microsoft.com/en-us/kb/3174047)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group