From a04494ad0fd3d8937a32a3f4cdd93f9662a9063c Mon Sep 17 00:00:00 2001 From: Panu Saukko <25768171+PanuSaukko@users.noreply.github.com> Date: Fri, 2 Jun 2023 13:08:46 +0300 Subject: [PATCH 1/3] Update site-server-high-availability.md Need to add more info what to do with SMS Provider role after you have uninstalled the passive site server. --- .../deploy/configure/site-server-high-availability.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md index 0b4ba194d21..7543f830f87 100644 --- a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md +++ b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md @@ -285,6 +285,11 @@ The process to remove a site server in passive mode is the same as any site syst When you remove any other site system role, the site component manager (`sitecomp`) processes the request. When you remove a site server in passive mode, the failover manager processes the request. For status, monitor the **SMS_FAILOVER_MANAGER** component. +After you have removed passive site server role, **SMS Provider** role is not automatically removed and you cannot remove the server from Configuration Manager, because it still has a role. You need to start Configuration Manager Setup from the site server and select **Site Maintenance** to remove **SMS Provider** role. + +> [!NOTE] +> Tenant attach will use the first **SMS Provider** server in the site. If you don't remove **SMS Provider** role from the server, tenant attach will continue to use it even though the server doesn't have a site server role any more. --> + ## Next steps [Flowchart - Set up a site server in passive mode](passive-site-server-flowchart.md) From 5bd9f6a87b9aa67185e6c9b3efb0edc1713b1586 Mon Sep 17 00:00:00 2001 From: Panu Saukko <25768171+PanuSaukko@users.noreply.github.com> Date: Mon, 5 Jun 2023 15:01:40 +0300 Subject: [PATCH 2/3] Update memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../servers/deploy/configure/site-server-high-availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md index 7543f830f87..b8084eeeeac 100644 --- a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md +++ b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md @@ -288,7 +288,7 @@ When you remove any other site system role, the site component manager (`sitecom After you have removed passive site server role, **SMS Provider** role is not automatically removed and you cannot remove the server from Configuration Manager, because it still has a role. You need to start Configuration Manager Setup from the site server and select **Site Maintenance** to remove **SMS Provider** role. > [!NOTE] -> Tenant attach will use the first **SMS Provider** server in the site. If you don't remove **SMS Provider** role from the server, tenant attach will continue to use it even though the server doesn't have a site server role any more. --> +> Tenant attach will use the first **SMS Provider** server in the site. If you don't remove the **SMS Provider** role from the server, tenant attach will continue to use it even though the server no longer has a site server role. ## Next steps From 82b7ca7310b55ad7cec179c4c8bfca0276ac37a6 Mon Sep 17 00:00:00 2001 From: Panu Saukko <25768171+PanuSaukko@users.noreply.github.com> Date: Mon, 5 Jun 2023 15:02:20 +0300 Subject: [PATCH 3/3] Update memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../servers/deploy/configure/site-server-high-availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md index b8084eeeeac..ae1554affe7 100644 --- a/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md +++ b/memdocs/configmgr/core/servers/deploy/configure/site-server-high-availability.md @@ -285,7 +285,7 @@ The process to remove a site server in passive mode is the same as any site syst When you remove any other site system role, the site component manager (`sitecomp`) processes the request. When you remove a site server in passive mode, the failover manager processes the request. For status, monitor the **SMS_FAILOVER_MANAGER** component. -After you have removed passive site server role, **SMS Provider** role is not automatically removed and you cannot remove the server from Configuration Manager, because it still has a role. You need to start Configuration Manager Setup from the site server and select **Site Maintenance** to remove **SMS Provider** role. +After you have removed a passive site server role, the **SMS Provider** role is not automatically removed and you cannot remove the server from Configuration Manager because it still has a role. You need to start Configuration Manager Setup from the site server and select **Site Maintenance** to remove the **SMS Provider** role. > [!NOTE] > Tenant attach will use the first **SMS Provider** server in the site. If you don't remove the **SMS Provider** role from the server, tenant attach will continue to use it even though the server no longer has a site server role.