Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
In the current branch of Microsoft Configuration Manager, remove a distribution point (DP) by opening Administration → Site Configuration → Servers and Site System Roles, selecting the site-system server, selecting Distribution point, choosing the Site Role tab, and clicking Remove Role. Confirm only after verifying that clients, content, boundaries, PXE, and task sequences have another suitable content source.
What removing the DP role actually does
A distribution point is a site-system role that makes a server a Configuration Manager content location. Removing the role removes that designation from Configuration Manager. It does not automatically uninstall Windows Server, remove the server from Active Directory, remove other site-system roles, delete the Configuration Manager site, or complete your organization’s secure-erasure process.
| Action | Result |
|---|---|
| Remove DP role | Stops the server from functioning as a Configuration Manager distribution point. |
| Remove a DP from a DP group | Removes group membership; Microsoft says content remains on the DP. |
| Remove selected content | Deletes chosen content from that DP while leaving the DP role installed. |
| Remove another site-system role | Uses a separate role-removal operation; other roles on the server remain. |
| Uninstall a site | Removes a primary or secondary site and is a different, larger operation. |
See Microsoft’s role-removal procedure at Uninstall roles, sites, and hierarchies.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check these dependencies before removal
Provide another content location
Identify every client population that currently uses the DP and confirm an alternative: another DP in the same or a related boundary group, a DP group, a pull-distribution point, a cloud-based distribution point where supported, or a deliberately configured peer or alternate-content mechanism. Client behavior is environment-dependent; do not assume automatic failover.
#1 Best Overall
Review boundaries and boundary groups
- Check whether the DP is the preferred or only content location for a branch, VPN range, or isolated network.
- Review fallback relationships and the order in which clients can search other groups.
- Confirm that replacement DPs are associated with the intended boundaries before removing the old one.
Microsoft’s distribution-point guidance covers boundary groups and content locations: Manage distribution points.
Inventory content and operating-system deployment use
Check applications, packages and programs, software-update packages, boot images, operating-system images, driver packages, task-sequence packages, and any client-installation content. PXE and task-sequence deployments are especially easy to break when a DP is the only server holding boot or deployment files.
Check other roles and the change window
Open the server’s complete Site System Roles list. A management point, state migration point, reporting point, or another role may need to stay. Record current boundaries, content assignments, PXE settings, and replacement-server details, and schedule the change when failed deployments can be investigated.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteUse maintenance mode correctly
Maintenance mode can stop new content distribution and prevent management points from offering the DP to clients during temporary hardware work. Microsoft also states that you should not use Remove Role while the DP is in maintenance mode. If you used maintenance mode during a transition, return the DP to the required normal state before removing the role, following your change procedure.
Remove the Distribution Point role from the console
- Open the Configuration Manager console.
- Go to Administration and expand Site Configuration.
- Select Servers and Site System Roles.
- Select the server that hosts the DP.
- In the details pane, select Distribution point.
- On the ribbon, open the Site Role tab and select Remove Role.
- Confirm the operation.
After processing completes, Distribution point should no longer be listed for that server. The server can remain in the console if it still hosts other roles. This operation is documented by Microsoft at Uninstall roles, sites, and hierarchies.
Remove a DP with PowerShell
Use the Configuration Manager PowerShell module from the Configuration Manager site drive. The DP-specific cmdlet is clearer than a generic site-role command.
Remove by server name
PS XYZ:> Remove-CMDistributionPoint `
-SiteSystemServerName "dp01.contoso.com" `
-SiteCode "CM1"-SiteCode identifies the Configuration Manager site associated with the site-system server. Without -Force, the cmdlet asks for confirmation.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Suppress confirmation in a controlled script
PS XYZ:> Remove-CMDistributionPoint `
-SiteSystemServerName "dp01.contoso.com" `
-SiteCode "CM1" `
-ForceUse -Force only when the server name, site code, and change approval have already been checked.
Rank #3
- Mastering Active Directory: Design, deploy, and protect Active Directory Domain Services for Windows Server 2022, 3rd Edition
- ABIS BOOK
- Packt Publishing
Remove by object
PS XYZ:> $dp = Get-CMDistributionPoint `
-SiteSystemServerName "dp01.contoso.com"
PS XYZ:> Remove-CMDistributionPoint `
-InputObject $dp `
-ForceSyntax and examples are in Microsoft’s Remove-CMDistributionPoint documentation.
Generic site-role removal
Remove-CMSiteRole `
-SiteSystemServerName "dp01.contoso.com" `
-RoleName "SMS Distribution Point" `
-SiteCode "CM1"Remove-CMSiteRole is a generic alternative. Microsoft’s documented example uses a reporting-point role rather than a DP, so verify the exact role-name value in your installed Configuration Manager release before automating it. Prefer Remove-CMDistributionPoint for DP removal. See Remove-CMSiteRole.
What is and is not cleaned up
The supported operation removes the DP designation from Configuration Manager. Do not assume that it is a guaranteed secure wipe of every local content-library file, IIS setting, certificate, PXE file, or storage volume in every release and topology. If the server is being retired, separately follow your procedures for operating-system disposal, storage erasure, certificate revocation, monitoring removal, DNS, and Active Directory.
Recommended Free Tools
Removing a DP from a distribution point group is a separate action, and Microsoft says it does not remove content from that DP. Likewise, removing selected content is appropriate when the server should remain a DP but disk space is the problem.
Validate the removal
Configuration Manager checks
- Refresh the server in Servers and Site System Roles; verify that Distribution point is gone.
- Confirm the server remains only for roles you intentionally kept.
- Check distribution-point views and content-location assignments for stale references.
- Verify replacement DPs and boundary-group relationships.
Deployment checks
- Test an application and package/program deployment.
- Monitor software-update deployment.
- Run a task sequence or validate its content references.
- Test PXE or boot-media deployment if the removed DP was PXE-enabled.
- Check clients in the former DP’s branch or bandwidth-constrained boundary.
Logs
On the site server, review distmgr.log and SMSdpmon.log for distribution processing and DP state. Additional site-system logs may be relevant to a particular failure. The DP documentation lists these logs at Manage distribution points.
If the DP server is offline
Microsoft Q&A guidance indicates that you can remove the DP object from the Configuration Manager console even when the old server is unavailable. That removes the role from the site’s active configuration; it does not prove that data or infrastructure on the physical server was erased. If the machine may return to service, preserve the information needed for your retirement, recovery, and security procedures. See How to completely delete an old distribution point.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Remove, reassign, or use another action?
| Goal | Best action |
|---|---|
| Permanently retire the server | Remove the DP role, validate replacements, then follow server-decommissioning procedures. |
| Move the DP to another primary site | Consider DP reassignment when supported; it can preserve existing content and avoid large redistribution. |
| Perform temporary hardware work | Use maintenance mode, but do not remove the role while maintenance mode is enabled. |
| Free disk space while keeping the DP | Remove selected content from the DP. |
| End only a group relationship | Remove the DP from the DP group; this does not remove its content. |
Reassignment has limitations: the target server can host the DP role, but documented restrictions apply when it hosts another Configuration Manager server role. Review the DP management guidance before choosing it.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTroubleshooting common failures
The Remove Role command is unavailable
Confirm that you selected the Distribution point role itself, have sufficient administrative rights, and that the DP is not in maintenance mode. Refresh the console and verify that the site-system object is healthy.
Clients cannot download content afterward
The removed DP was probably the only usable location for those clients or their boundary group. Distribute required content to a replacement DP, correct boundary-group relationships and fallback, then retry the deployment. If necessary, reinstall the DP role on the original or replacement server and redistribute content.
The server still appears
Removing the DP role does not remove other roles or the site-system server object. Review the complete role list. If a role-removal operation is genuinely stuck, collect site-server and distribution-manager logs, check connectivity and console refresh, and use Microsoft support or an experienced Configuration Manager specialist. Do not delete site-database records or manipulate unsupported WMI objects.
Only the DP group was changed
Group membership changes do not remove the DP role or its content. Use the server’s Distribution point → Site Role → Remove Role action or Remove-CMDistributionPoint.
The Bottom Line
Remove the role only after proving that replacement content locations and boundary behavior cover every client and deployment. Use the console’s Remove Role action or the supported Remove-CMDistributionPoint cmdlet, then validate deployments and handle physical server retirement separately.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
