We have two sccm site servers (plus many DPs, 4 MPs, etc.), one of which is the active one and where the other is the passive one.
Additionally, the sccm database is hosted on external MS SQLServers.
There are two SQL Servers in high availability mode that connect to our sccm site servers.
As it happens, I needed to reboot our active sccm siteserver (Server-A). It is a virtual machine and restarting it lasts less than one minute. My understanding and feeling after many years of windows server administration is that such a restart of the active site server does not hurt the sccm software distribution system. And it won't hurt the databases for this SCCM system on the MS SQL servers either, even though the sql servers loose for a minute the connection to this active siteserver (Server-A).
However, some in the team feel that it would be necessary to promote the passive site server (Server-B) to become the active one before restarting Server-A.
My feeling is that a simple reboot of the active sccm siteserver is less invading into the whole SCCM system than first promoting the passive site server to become the active one.
I assume promoting and demoting will make changes under the hood with all the management point servers, Wsus-SCCM servers etc. and that this would stress the system more than quickly rebooting the active sccm site server without demoting it before.
Does a given rule by Microsoft exist how to proceed in the one and only correct way when rebooting the active sccm site server?
Thank you.
Additionally, the sccm database is hosted on external MS SQLServers.
There are two SQL Servers in high availability mode that connect to our sccm site servers.
As it happens, I needed to reboot our active sccm siteserver (Server-A). It is a virtual machine and restarting it lasts less than one minute. My understanding and feeling after many years of windows server administration is that such a restart of the active site server does not hurt the sccm software distribution system. And it won't hurt the databases for this SCCM system on the MS SQL servers either, even though the sql servers loose for a minute the connection to this active siteserver (Server-A).
However, some in the team feel that it would be necessary to promote the passive site server (Server-B) to become the active one before restarting Server-A.
My feeling is that a simple reboot of the active sccm siteserver is less invading into the whole SCCM system than first promoting the passive site server to become the active one.
I assume promoting and demoting will make changes under the hood with all the management point servers, Wsus-SCCM servers etc. and that this would stress the system more than quickly rebooting the active sccm site server without demoting it before.
Does a given rule by Microsoft exist how to proceed in the one and only correct way when rebooting the active sccm site server?
Thank you.
Last edited:
