Deploying Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update (KB2919355) Using System Center Configuration Manager

Deploying Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update (KB2919355) Using System Center Configuration Manager

  • Comments 2
  • Likes

Author:  Michael Cureton Development Manager, Configuration Manager Sustaining Engineering

Applies to: System Center Configuration Manger 2007, System Center 2012 Configuration Manager

Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update is a cumulative update that includes all previous released security updates and non-security updates that were released before March, 2014. This cumulative update is available for deployment using the software updates management (SUM) feature built into Configuration Manager.

NOTE: All future security and non-security updates for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 require this update to be installed. It is recommend that you install this update on your Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2-based computer in order to receive continued future updates. Please see Windows 8.1 Update: The IT Pro Perspective for more details.

While this update can be deployed using SUM in the same fashion as other updates, there are a few things to consider to achieve the best deployment experience. For starters, there is a servicing stack update (KB2919442) that is a prerequisite for installing this cumulative update. If this servicing stack update is not installed the cumulative update will be evaluated as not required. Therefore, it is recommended that this servicing stack update be deployed well in advance of the cumulative update and compliance closely monitored.

The size of the payload for the cumulative update is much larger than typical updates. The time that it can take clients to download the content will vary depending on the environment. It is recommended that your deployment be configured to leverage the advanced downloading functionality so that the content is downloaded into the client’s local cache once the deployment is received and before the Software available time setting is reached. This will allow the cumulative update installation to begin as soon as the software available time is reached.

To accomplish this, configure the deployment with the following:

  • Software available time: A required deployment should be leveraged with a specific time defined for the software available time that is far enough in the future to allow the complete download of the content soon after the deployment is received.
  • Installation deadline: The Installation deadline setting should be defined for a sufficient offset after the software available time.
  • Maximum run time: Given the size of the cumulative update and client machine configurations, the installation time for the update could take anywhere from 30 minutes to an hour or more. There is a Maximum run time setting for each update with a default value. It is recommended before deployment that the properties of the cumulative update be modified and Maximum run time setting on the Maximum Run Time tab be changed to a value suitable for your environment. The total installation times observed during your pilot testing should be leveraged as a guideline.

   --Michael Cureton

 

Configuration Manager Resources

Documentation Library for System Center 2012 Configuration Manager

Configuration Manager 2012 Forums

System Center 2012 Configuration Manager Survival Guide

System Center Configuration Manager Support

This posting is provided "AS IS" with no warranties and confers no rights.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • thank you

  • i was surprised to see why kb showed as not required in SCCM. this is helpful