ConfigMgr CB Update & High Availability Groups Failover Pre-requisite

If you have HA setup to use SQL Server Always on availability group, then this blog may just help you. Recently, I needed to perform a Current Branch update in ConfigMgr to 2010 and as part of the preparation, I ran the pre-requisite checker. Almost immediately it threw an error pointing to Failover Availability group not being in correct state.


This is a customer's environment so I was only getting to know the specifics of the configuration. That is the beauty of the pre-requisite checker in ConfigMgr, it flags up such issues and allows you to address and correct them before installing the actual update.

In order to fix the issue, one needs to switch the Failover from Automatic to Manual against the Availability Group. According to Microsoft, this is needed when installing ConfigMgr updates. Also, as far as I know, this is also needed when performing any kind of site maintenance.


After the change was made in SQL, I ran the pre-requisite checker again and everything passed with no errors or warnings. Installed the update and everything was good in the World again.

Just make sure to switch the Failover from Manual to Automatic after the update has installed as this will not automatically change.

Until next time..

Comments

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

Intune: Configure Printers for Non-Administrative Users

Prevent users from running certain programs or applications on Windows endpoints using Intune