Primary Site Fault Tolerance makes it in TP1706

Not sure if the ConfigMgr team ever sleeps, month after month new features are released in ConfigMgr Technical Preview. June is no exception, and I must confess this is truly the month I have been waiting for. Among many of the new features we now have support for active/passive site servers.


A passive primary site server adds fault tolerance to your site by creating a copy of your primary site server and keeping it in sync. If a disaster occurs, you can manually make the passive site server active.

There are a couple of things you need to consider before using the feature:

  • The passive server will use the same SQL server, but not write anything to the database while being passive.
  • The Active and Passive site servers must be in the same domain.
  • SQL configuration can be default instance, named instance, SQL Server cluster, or an Always On Availability Group. Especially SQL always on is a perfect fit for this configuration.
  • SQL database cannot be hosted on the primary site server.
  • The provider can’t be installed on the passive server (or any other site system roles).
  • Promoting a passive site server to Active is a manual process.

Design impact

As you read this post, you might realize that using this new feature will impact your site design. Most MVP’s that I know, highly recommend having SQL installed on the primary site server. With this feature hopefully making it into Current Branch, we must re-visit that recommendation. My advice, start looking into SQL Always on along with active/passive site servers. Another important change is the location of the provider. I would say that the majority have a single provider and it’s installed on the primary site server.

What is the benefit of this, is it worth the hassle? Absolutely, besides the obvious fault tolerance benefit, you know also have the opportunity the rename the primary site server. I know this has been a feature request for many, especially as we know have begun the move to Azure (where new naming standards often are part of the move). With this, install your passive site server in Azure, promote it from passive to Active and goal as achieved.

Have fun and being passive is the new Green – for more information check out

By |2017-08-22T09:33:56+00:00June 25th, 2017|Configuration Manager (SCCM)|2 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.


  1. Cristopher June 26, 2017 at 14:10 - Reply

    I read on Twitter that the requirement “SQL database cannot be hosted on the primary site server” is only temporary for this Technical Preview and may go away.

    • Johan July 26, 2017 at 11:11 - Reply

      Hi Christopher where have you read that on twitter , I am not able to find this
      Thanks in advance

Leave A Comment