-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Microsoft System Center Configuration Manager Cookbook
By :

CM synchronizes with the Microsoft cloud service to get updates. You can then install from within the CM console. Only updates that apply to your infrastructure and version are downloaded and made available. This synchronization can be automatic, or manual depending on how you configure the service connection point for your hierarchy.You can choose either of the following methods for upgrading your CM Infrastructure.
You can choose either of the following methods for upgrading your CM Infrastructure:
By default, CM checks for new updates every 24 hours. Beginning with version 1602 or later, you can also check for updates immediately by:
To view updates in the console, a user must be assigned a security role that includes the Read permission in the permission group Site, and the security scope All.
To configure the service connection point role:
The service connection point site system role may only be installed on a central administration site or standalone primary site. The service connection point must have Internet access.
Before applying a CM update, there are three recommended actions you can execute in order to safely update CM:
Refer to the checklist available at https://technet.microsoft.com/en-us/library/mt691556.aspx for updating from System Center Configuration Manager version 1511 to 1602.
CD.Latest
folder of a site that runs the version you plan to update to from the lab environment. For example, if your site runs version 1501 and you want to update to 1602, you must get a CD.Latest
folder from a site that has already updated to version 1602.CD.Latest
, for example, SMSSETUP\BIN\X64\Setup.exe /TESTDBUPGRADE DBtest\CM_ABC
.ConfigMgrSetup.log
in the root of the system drive.ConfigMgrPrereq.log
.Before installing a new CM update, be sure to have done the prerequisite checks described in the Getting ready section.
Child primary sites start the update automatically after the central administration site completes installation of the update. You can use Service Windows for site servers to control when a site installs updates.
When it comes to updating CM to a new version, you will have to consider updating the CM hierarchy in the following order:
You have to manually update secondary sites from the CM console after the primary parent site update is completed. Automatic update of secondary site servers is not supported. When you open the CM console after the site update, you are prompted to update the console.
As part of the update installation, CM re-installs any affected components such as site system roles or the console, manages updates to clients based on the selections you made for client piloting, and basically there is no need to reboot site system servers as part of the update.
When updates are installed, Configuration Manager also updates the CD.Latest
folder which is used during a site recovery.
From the CM console, it is also possible to verify any update installation status as well as monitor the update in progress.
To verify the status of updated packages, navigate to Administration | Cloud Services | Updates and Servicing. This node shows the installation status for all updated packages.
To monitor the CM update while it's applied, follow these steps:
CMUpdate.log
file in <ConfigMgr_Installation_Directory>\Logs\
.After a CAS or primary site updates, each CM console that connects to that site must also update.
To start updating CM consoles:
Change the font size
Change margin width
Change background colour