Can I safely remove the SCCM client from our domain controllers?

November 19, 2026 5 answers
Asked by 7p~gasketcaddy_416

We inherited two domain controllers and migrated them to a new virtualization platform. Logins now pause for a few minutes while a Configuration Manager extension applies. The old management server was not migrated.

Removing the client from an unused server cleared the delay there. What should I check before doing the same on the domain controllers?

Answers

_x74~velmori.6

If these servers only have the Configuration Manager client agent, ccmsetup.exe /uninstall is the documented way to remove it. It removes the client, not Active Directory Domain Services, DNS, SYSVOL, or replication.

I'd do one controller at a time. Check its health and replication before the change, then run dcdiag and repadmin /replsummary afterward and verify logins before moving to the second one. The test server result is encouraging, but it doesn't prove the controllers have exactly the same cause for the delay.

Mivnelo.3q:

Also check for a group policy or scheduled task that might reinstall the client. That could make the fix look temporary.

Reply to this answer
_m47+bravino.6

First make sure you are dealing with just the agent. A server can also host Configuration Manager site roles, such as a management point or distribution point. Check the site configuration and logs if available, and find out whether any clients still reference those roles before removing or retiring anything.

The client uninstall is not a procedure for removing site roles. Those are separate questions, and an old server being gone doesn't necessarily tell you what was left on the domain controllers.

Reply to this answer
6b+canvasratchet_392

Before removing the agent, figure out what replaced its management functions. If it was handling updates or other deployments, the controllers need another way to receive them. An unreachable site may already mean those functions aren't working, but that's worth verifying rather than assuming.

Reply to this answer
Nuvdexa.7p

The extension named on the login screen is a useful clue, not a complete diagnosis. Check group policy for User State Management settings and look at the Configuration Manager logs. The client may be waiting on the missing management server, but the pause could have another cause.

Reply to this answer
4g!canvascaddy_617

Longer term, clean new domain controllers are another option if these machines have a lot of undocumented baggage. Build and promote replacements, check that they are healthy and replicating, then demote the old controllers. That's a separate project from fixing the login delay, though.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions