Let’s find out the method SCCM Secondary Server Hotfix Installation details. The SCCM hotfixes won’t get automatically installed on ConfigMgr secondary servers.
From this post, You shall learn how to install hotfixes on Configuration manager secondary servers. You must Install a secondary site hotfix from within the SCCM console. The Secondary sites don’t support a scripted command-line installation process.
Introduction
Before getting there let’s check whether the hotfix or patch is installed on the secondary server using the following method. Change the HS0 to your secondary server site code.
select dbo.fnGetSecondarySiteCMUpdateStatus ('HS0')
As you can see the result of the query is zero (0) and if this query result shows 0 means the hotfix is not installed on SCCM secondary server. You need to go through the steps explained in the next section of this post to get more details about the installation of the secondary server.
Install Hotfix on ConfigMgr Secondary Server
Follow the steps to complete the hotfix installation on the secondary server:
- Launch SCCM console
- Navigate to \Administration\Overview\Site Configuration\Sites
- Click secondary server and click on Recover Secondary Site from the ribbon menu
NOTE! – You are about to recover a secondary site, HSO – Secondary site FQDN. The recovery process installs the secondary site by using the same configuration as the previous site HS0. To monitor the recovery process and identify additional actions you might need to take, use the action Show Install Status.
- Click OK to continue SCCM Secondary Server Hotfix Installation.
Monitor Hotfix Installation
- Right-click on the secondary site and click on Show Install Status to know more about installation status.
After the successful prerequisite check, the secondary server state changed from pending to recovering.
- The hotfix installation files are getting copied to the secondary server as part of the recovery process.
- SMS_Bootstrap.pkg
Logs
The following are the log files that might help you to understand and troubleshoot the issues with the secondary server hotfix installation. All these files are located on the secondary site server.
- SMS_BOOTSTRAP.log
- smstsvc.log
- ConfigMgrSetup.log
NOTE! – You can read about troubleshooting details of the SCCM secondary site from the previous blog post. SCCM Secondary Server Installation Failed Error | ConfigMgr | Fix.
The following entries from smstsvc.log are important to understand how the upgrade or hotfix installation of the secondary server is progressing.
try to open file \\MEMCMSecondary.memcm.com\admin$\smstsvc_test_2.ini
Enforced using sql native client to talk to SQL server.
INFO: Retrieved collation <SQL_Latin1_General_CP1_CI_AS>
Successfully write the result file \\MEMCMSecondary.memcm.com\admin$\smstsvc_test_6.rst (1)
Results – SCCM Secondary Server Hotfix Installation is Completed Successfully
Let’s check whether you got the following status message: [Passed]: ConfigMgr Setup – Recovered ConfigMgr secondary site successfully. to confirm the successful hotfix installation on the secondary server.
[Passed]:Secondary site server bootstrap installation service succeeded
[Passed]:ConfigMgr Setup - Upgrading ConfigMgr secondary site successfully.
[Passed]:Installation of secondary site server component manager service succeeded
- [Passed]: Secondary site server bootstrap installation service succeeded
Run the following SQL query to confirm whether the secondary site hotfix installation is completed or not. More details – Check SCCM Secondary Server Hotfix Installation Status.
select dbo.fnGetSecondarySiteCMUpdateStatus ('HS0')
Resources
- SCCM Secondary Server Installation Failed Error | ConfigMgr | Fix
- List of prerequisite checks for Configuration Manager
- Install a secondary site
- Add SCCM Server Computer Account to SQL Login Sys Admin Access
Author
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…