Merge pull request #3114 from lamosley/patch-3

Update to reflect passive site server install limit

Author: aczechowski

memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md

@@ -101,7 +101,7 @@ The site content library must be on a remote network share. Both site servers ne
 
 Both site servers must use the same site database.
 
-- The database can be remote from each site server. The Configuration Manager setup process doesn't block installation of the site server role on a computer with the Windows role for Failover Clustering. SQL Server Always On availability groups require this role, so previously you couldn't colocate the site database on the site server. With this change, you can create a highly available site with fewer servers by using an availability group and a site server in passive mode.<!-- SCCMDocs issue 1074 -->
+- The database can be remote from each site server. The Configuration Manager setup process doesn't block installation of the site server role on a computer with the Windows role for Failover Clustering. SQL Server Always On availability groups require this role, so previously you couldn't colocate the site database on the site server. With this change, you can create a highly available site with fewer servers by using an availability group and a site server in passive mode. Only an active server can be installed to a node in an Always On availability group. Passive servers must be installed to standalone servers that do not have any existing site roles on them.<!-- SCCMDocs issue 1074 -->
 
 - The SQL Server that hosts the site database can use a default instance, named instance, [failover cluster instance](use-a-sql-server-cluster-for-the-site-database.md), or an [availability group](sql-server-alwayson-for-a-highly-available-site-database.md).
 
@@ -131,6 +131,8 @@ Both site servers must use the same site database.
 
 - Only a single site server in passive mode is supported at each site.
 
+- Passive site servers cannot be installed to nodes in the Always On availability group hosting the Configuration Manager database and must be installed on standalone servers. Moving a passive site server into the Always On availability group after installation is not currently supported. 
+
 - A site server in passive mode isn't supported at a secondary site.<!--SCCMDocs issue 680-->
 
     > [!NOTE]