A Configuration Manager (ConfigMgr/SCCM) site reset is a supported maintenance operation for repairing the existing site installation. It can restore ConfigMgr-managed files, registry permissions, services, shares, and site-system components while retaining database-backed site configuration. It is not a universal fix and should be performed only after you have ruled out SQL, networking, WSUS, IIS, certificate, Active Directory, and operating-system causes.
For a current-branch primary site or CAS, the documented path is: run setup binaries that match the installed site version, choose Perform site maintenance or reset this site, select Reset the site without configuration changes, and confirm. Then validate services, logs, status messages, and the affected workload.
As an Amazon Associate I earn from qualifying purchases.
What a ConfigMgr site reset does
Microsoft describes site reset as a repair and reinstallation operation for an existing site, not a new-site deployment. It re-establishes the local and remote ConfigMgr resources that make up the site installation.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Area | Expected effect |
|---|---|
| ConfigMgr files and directories | Restores the default Configuration Manager file tree, files, and subdirectories. |
| Registry | Restores SMS/NAL keys, default subkeys, and default ConfigMgr registry permissions. |
| Services | Installs or reinstalls SMS_EXECUTIVE and SMS_SQL_MONITOR; restarts the relevant components. |
| Site components and roles | Reinstalls the site components and site-system roles managed by the affected site. |
| Shares | Deletes and recreates relevant ConfigMgr site-system shares on local and remote site systems. |
| Site database configuration | Database-backed site configuration is expected to remain; this is not a database deletion operation. |
| Custom operating-system changes | Custom permissions on ConfigMgr-managed files, folders, shares, or registry keys can be returned to defaults. |
The reset does not repair unrelated objects or dependencies. SQL Server, WSUS, IIS, WMI, DNS, firewall rules, certificates, Active Directory, and third-party integrations must still be healthy.
#1 Best Overall
See Microsoft’s procedure and scope details at Modify your infrastructure.
Site reset versus other ConfigMgr actions
| Operation | Use it for | What it changes |
|---|---|---|
| Site reset | Broad damage to ConfigMgr-managed installation resources | Site components, roles, services, files, registry permissions, and shares |
| Reset Counts | Clearing or recalculating status counters | Status display only; it does not repair a component |
| Update Reset Tool | Stuck or failed in-console updates | Update package state and update download or replication problems |
| Targeted role reinstall | One damaged role, such as an MP, DP, SUP, or reporting point | The selected role rather than the whole site installation |
| Site recovery | Site-server failure or a lost or corrupted database | Recovery of the site server, database, or complete site |
| Uninstall/reinstall | Removing and rebuilding the site | The site installation and potentially the hierarchy |
ConfigMgr status is a summarization and monitoring system. A green result after Reset Counts does not prove that the service or role is healthy; inspect status messages and component logs. See Use the status system.
When a site reset is reasonable
- Several related components fail after an interrupted upgrade or maintenance operation.
- ConfigMgr-managed files, registry values, services, or shares are missing or have incorrect permissions.
SMS_EXECUTIVEorSMS_SITE_COMPONENT_MANAGERis incorrectly installed, cannot start, or repeatedly fails after prerequisites are corrected.- A site role repeatedly fails installation and evidence points to a damaged local ConfigMgr installation rather than an external dependency.
- A supported Microsoft procedure specifically directs you to reset the site.
The strongest case is broad, related corruption of the site installation. A single red component with a clear external error usually calls for a narrower fix.
Recommended Free Tools
When not to start with a site reset
- SQL connectivity, permissions, database availability, or transaction-log problems are unresolved.
- DNS, firewall, SMB, RPC, WinHTTP, certificate, or Active Directory publishing and discovery failures remain.
- IIS, WMI, .NET, Windows services, disk space, service accounts, or expired passwords are the likely cause.
- WSUS synchronization or its database is failing.
- Only one role is affected and a targeted role reinstall is available.
- The site is in an upgrade, recovery, or another Setup operation.
- Remote site systems are offline or inaccessible.
- The only evidence is stale status counters with no current component errors.
For a failed or stuck in-console update, use Microsoft’s Configuration Manager Update Reset Tool. On supported current-branch versions it is in cd.latestSMSSETUPTOOLS; it is not a general site reset.
Prerequisites and safety checklist
Required permissions
- CAS: local Administrator on the CAS server and permissions equivalent to the ConfigMgr Full Administrator role.
- Primary site: local Administrator on the primary-site server and Full Administrator-equivalent ConfigMgr permissions. If it belongs to a CAS hierarchy, also have local Administrator rights on the CAS.
Before opening Setup
- Identify the target as a CAS or primary site and record its installed ConfigMgr version.
- Prepare matching setup media or use the site’s own installation binaries.
- Review Component Status, Site Status, recent messages, and the failing component’s logs.
- Take or confirm recent ConfigMgr and SQL backups.
- Document custom file, folder, share, registry, certificate, service-account, and integration settings.
- Record current site-system health and ensure remote systems are online and reachable.
- Reserve a maintenance window, notify owners of MPs, DPs, SUPs, reporting, and integrations, and confirm free disk space.
- Do not start while another upgrade, recovery, or Setup operation is active.
A reset is generally non-destructive to database-backed site configuration, but it changes services, files, registry settings, shares, and remote role installations. Treat it as controlled maintenance, not a risk-free button click.
How to perform the site reset
1. Start matching Setup binaries
Run Setup locally on the site server from matching media:
<Configuration Manager installation media>SMSSETUPBINX64setup.exeAlternatively run:
<Configuration Manager installation directory>BINX64setup.exeYou can also use the Configuration Manager Setup shortcut in the Start menu. Do not casually use older or newer media; Microsoft requires setup binaries that match the installed site version. The documented procedure is at Modify your infrastructure.
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 reinstall2. Choose the reset mode
- Review Before You Begin.
- On Getting Started, select Perform site maintenance or reset this site.
- On Site Maintenance, select Reset the site without configuration changes.
- Select Yes to begin.
- Let Setup finish. Do not kill
setup.exe, reboot the server, or manually manipulate related services while Setup is working unless a documented recovery procedure requires it.
What to monitor while Setup runs
C:ConfigMgrSetup.logas the primary Setup log.sitecomp.logfor site-component and site-system installation activity.smsexec.logfor Executive startup and component processing.- The role-specific log for the original failure.
- Windows Event Viewer.
- The
SMS_EXECUTIVE,SMS_SITE_COMPONENT_MANAGER, andSMS_SQL_MONITORservice states. - Remote site-system installation activity, disk space, and network connectivity.
Post-reset validation
- Confirm Setup completed successfully and review
C:ConfigMgrSetup.logfor errors and warnings. - Verify the three core services are installed and running.
- Review
sitecomp.log,smsexec.log, and the affected role log after the reset time. - In the console, open Monitoring > System Status > Site Status.
- Open Monitoring > System Status > Component Status, choose Show Messages, and restrict the period to the reset window.
- Test the affected function: console/provider access, management-point health, content distribution, software-update synchronization, reporting, or client policy and status processing.
- Confirm documented custom permissions and integrations still work. Reapply only settings that are genuinely required.
- Keep Setup and component logs with the change record.
Do not treat a green rollup alone as proof of recovery; combine status evidence with logs and a real workload test.
If the reset completes but the failure returns
A recurring critical component after a successful reset is evidence that the cause may be external or deeper than the local installation. Compare the post-reset error with the original and then check:
- Service-account credentials and permissions.
- SQL connectivity and database health.
- DNS, firewall, SMB, RPC, IIS, WMI, and certificate access.
- Required Windows roles and features.
- Disk space and remote site-system availability.
Do not repeatedly run resets without new evidence. Move to targeted role remediation, site recovery, or Microsoft support when the logs identify a dependency or when the site remains unstable.
Common edge cases
- Custom permissions disappeared: This can be expected for ConfigMgr-managed objects. Verify the business need before reapplying them; do not add broad permissions blindly.
- Remote site system is offline: Bring it online and verify administrative access, name resolution, SMB/RPC, and firewall rules before retrying.
- Setup will not run remotely: Run it locally on the relevant site server.
- Data loss or database corruption: Follow the site-recovery procedure, not routine maintenance. See Recover sites.
- CAS removal or hierarchy restructuring: These are separate Setup operations with their own prerequisites; a normal reset does not remove a CAS. See Remove the central administration site.
Bottom line
Use a ConfigMgr site reset when multiple failures point to damaged ConfigMgr-managed files, permissions, services, shares, or site components, and external dependencies have been checked. Run matching Setup binaries during a controlled window, document custom changes, and validate with Setup logs, component logs, status messages, service state, and an end-to-end workload test. It is broader than a role reinstall but narrower than site recovery or rebuilding the hierarchy.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Frequently Asked Questions
Does a site reset delete the ConfigMgr database?
A normal reset is intended to repair the existing site while retaining database-backed configuration; it is not the site-recovery or uninstall/reinstall workflow.
Best Value
Does a site reset reset clients or deployments?
The operation repairs the site installation and managed site-system resources. Validate client policy, content, updates, and reporting afterward rather than assuming every workload is healthy.
Can a site reset repair WSUS?
No. It may refresh ConfigMgr-managed SUP installation resources, but WSUS, its database, synchronization, and upstream update problems can remain.
Is a site reset risk-free?
No. Custom permissions on ConfigMgr-managed files, folders, shares, and registry keys can return to defaults, and the operation disrupts services and role installations.
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.
