First published on CloudBlogs on Aug, 23 2013
One request we often receive is for information on reinstalling cumulative updates with System Center 2012 Configuration Manager. This comes up specifically in the case of a disaster recovery scenario, where hotfixes may need to be reinstalled to the same server following a
restore from backup
.
The challenge is that our cumulative updates do not support the uninstall operation via Add/Remove Programs, and a proper reinstall will be blocked due to the presence of Windows Installer data for the cumulative updates in the registry.
For example, the file system on the site server may have binaries from RTM, but the database was backed up after cumulative update 2 (CU2) was applied. CU2 binaries will need to be re-applied after completing a restore. In this scenario, the CU2 installer would return the following message:
“This update is already installed on the computer. Only options to create deployments for this update are available.”
To unblock this scenario, you need to remove the Windows Installer data for CU2 with the MSIEXEC command line. This requires the CU2 .MSI file, or its associated Windows Installer Product Code property.
Using CU2 for System Center 2012 Configuration Manager Service Pack 1 as an example, either of the following commands could be run from an elevated command prompt on the site server:
MSIEXEC /X C:CU2cm12-sp1cu2-kb2854009-x64-enu.msi
or
MSIEXEC /X {6600CD0C-1503-490D-9351-9556F689837D}
The Product Code property can be obtained through various scripts, or by using the
Orca.exe
tool – the value to look for is ProductCode in the Property table.
Depending on the recovery scenario, the .MSI file may still be available under <smsroot>hotfixesKB<KBiID>server.
Alternately, it can be manually extracted from the cumulative update package by running the .EXE installer with a /X switch. For example:
CM12-SP1CU2-KB2854009-X64-ENU.EXE /X
will display a “Choose Directory For Extracted Files” window. The resulting MSI will be available in the specified location.
Note that while this is utilizing the MSIEXEC uninstall parameter (which can also be listed as /Uninstall instead of /X), this process is not supported for normal site operation. Even though Windows Installer data is removed, and some files may be rolled back, updates to the site database are not. This means the only time you should utilize this process is immediately preceding the reinstallation of the cumulative update.
System Center 2012 Configuration Manager Cumulative Update Product Codes
CU1 for Configuration Manager SP1
{4D526D52-29EE-47CE-AAF8-0591ED7E3FF8}
CU2 for Configuration Manager SP1
{6600CD0C-1503-490D-9351-9556F689837D}
CU3 for Configuration Manager SP1
{2C9004EA-6D8C-4C57-B03F-B872293133B8}
CU4 Configuration Manager SP1
{0C48AB64-7ECD-4EBD-A8B4-9490285ADF6C}
CU5 for Configuration Manager SP1
{B55DE6D7-A406-4E51-81AB-0C99D7C166B5}
CU1 for R2 Configuration Manager
{DF7BE5C8-C0C1-42E1-B99C-C2675D11FEEE}
CU2 for R2 Configuration Manager
{14B6FD8E-10DC-475D-A79B-CB28971C7B0D}
CU3 for R2 Configuration Manager
{D9E97CFF-7E7A-4B38-ACCC-99920E49D7AF}
CU4 for R2 Configuration Manager
{ACC439EB-0945-4162-9775-067753F8874D}
CU5 for R2 Configuration Manager
{070EB545-5A08-46FC-9C1B-2DDA5B619A6A}
CU1 for R2 Configuration Manager SP1 and Configuration Manager SP2
{A687702D-36B1-4278-98AA-BA511AD644D4}
CU2 for R2 Configuration Manager SP1 and Configuration Manager SP2
{994B0F53-53C3-4B52-9C39-35773837DBF6}
(original - Administrator Console version 5.0.8239.1301)
{A02ACDD2-77FE-477A-A7F6-B60EFF096CCE}
(refreshed - Administrator Console version 5.0.8239.1302)
--
Brian Huneycutt
and
QianDong Ni
This posting is provided "AS IS" with no warranties and confers no rights.
