Interoperability update for System Center Configuration Manager version 1610

Issues that are fixed

• The /SkipPrereq client installation command-line parameter is not recognized. No errors are returned when you use this parameter, but any specified prerequisite programs will still install.
  
  After this update is applied, any prerequisites that are incorrectly installed on clients can be uninstalled.
  
  Note Existing clients can take advantage of this fix by updating to the latest version of CCMSetup.exe. This does not require reinstallation of the client. Instead, this file is updated automatically if the automatic client upgrade feature is enabled.
  
  More information
  
  For more information, see the following resources:
  

• • About the automatic client upgrade feature, see How to upgrade clients for Windows computers in System Center Configuration Manager.

  • About CCMSetup.exe, see About client installation properties in System Center Configuration Manager. CCMSetup.exe may also be distributed via software distribution or other means.
    

• After clients upgrade to Configuration Manager, version 1610, the contents of the CCM Cache folder (%windir%\ccmcache by default) are orphaned. Although the files are still present on disk, they are not available for application installations and will not be managed or deleted by the client.
  
  Installing this update prevents the cache issue on future client upgrades. Previously upgraded clients will redownload applicable content, and any expired content can be manually deleted as needed.
  
  

• After you upgrade a central administration site (CAS) to Configuration Manager, version 1610, new or updated package contents are not processed at lower-version child sites. This may include boot image updates, software distribution or software update packages, and other content.
  
  When you try to process package instructions from the version 1610 parent site, the SMS_Despooler component on the earlier-version child site logs entries that resemble the following in the despool.log file:
  
  

  ~Received package package_id version 570448640. Compressed file - PCA as SMS_INSTALL_DIR\Inboxes\despoolr.box\receive\PKGxxxx1.TRY
  ~Old package stored UNC path is .
  ~This package[package_id]'s information hasn't arrived yet for this version [570448640]. Retry later ...
  ~Created retry instruction for job job_id
  ~Despooler failed to execute the instruction, error code = 12

  
  Notes
  
  

  • The package version number recorded in the log file does not match any expected version.

  • SMS_Despooler on the child sites will retry the instructions up to 100 times.

  • On version 1511 or 1602 sites, this equates to approximately 36 hours for package updates and 8 hours for new packages. The retry duration on version 1606 and later versions is approximately 50 hours for both new and updated packages.

  • Sites that are upgraded or installed within the retry time frames will automatically resolve the issue and process the package instructions.

  • If all retries are exhausted before the child site is upgraded, the following message is logged in the despool.log file:
    

    We've retried enough times on job <job_id>, give it up.

  • For the sites that upgrade after all retries are exhausted, the package contents must be refreshed at the CAS post-upgrade to resolve this issue.

Update information for System Center Configuration Manager, version 1610

This update is available for installation in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using builds of version 1610 that were downloaded before December 20, 2016.

To verify which build is used, look for one of the following Package GUIDs in the console:

• C43A89E4-B642-4FC8-ABF0-255BF5D88D82

• 171DD417-F82A-451D-92B2-35FA0CD073C6

• 91406B1D-7C14-42D8-A68B-484BE5C5E9B8

This can be seen by adding the Package GUID column to the details pane of the Updates and Servicing node.

After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.

Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
If the returned value is 1, the site is up-to-date by having all the hotfixes applied on its parent primary site.

If the returned value is 0, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.