DEPLOYMENT REMEDIATION

SCCM Agent Restart.

Resolve stalled software deployments and force machine policy retrievals instantly. Safely restart the SMS Agent Host without forcing the user to reboot their computer.

SEE HOW IT WORKS
WinRM Dispatcher ● CONNECTED

[UHDC] RESTART SCCM AGENT: LAPTOP-US-4829

[i] Connecting to LAPTOP-US-4829 via WinRM...

> Stopping CcmExec service...

> Starting CcmExec service...

[UHDC SUCCESS] SCCM Agent restarted successfully!

[i] Note: It may take 2-3 minutes for the PC to check in with the Site Server.

Unstick the Software Center

When an application is permanently stuck on "Downloading 0%" or "Waiting to install," the standard help desk response is to ask the user to reboot and wait 15 minutes. This tool safely bounces the underlying service to resume the download immediately.

Service Decoupling

Establishes a remote PowerShell session over Port 5985 (HTTP) to execute a strict Stop-Service command against the CcmExec (SMS Agent Host) service.

Lock Release Buffer

Intentionally executes a 4-second thread sleep. The SCCM agent aggressively writes to dozens of local log files. This buffer ensures all file locks are cleanly released before the service spins back up.

Policy Retrieval

Executes a Start-Service command to bring the agent back online. This fresh initialization automatically triggers a machine policy check-in with the MECM Management Point.

INTERACTIVE TRAINING ENGINE
⭐ 100 XP

How Junior Techs Learn This Tool:

While the UHDC uses PowerShell to safely restart the service with a built-in delay, a junior technician should know how to bounce a service manually using classic command-line tools. The training engine teaches them how to utilize Sysinternals PsExec to remotely execute a chained CMD command as the SYSTEM account—stopping the 'CcmExec' service, using a classic loopback ping to create a 4-second delay (allowing log file locks to release), and then starting the service back up.

psexec \\$Target -s cmd.exe /c "net stop CcmExec & ping 127.0.0.1 -n 5 > nul & net start CcmExec"

The In-Person Equivalent

Opening Services (services.msc), locating 'SMS Agent Host', right-clicking it, and selecting 'Restart'. Alternatively, opening an elevated command prompt and typing the 'net stop' and 'net start' commands.

Technical Q&A

Q: Why not just use the `Restart-Service` cmdlet instead of Stop, Sleep, and Start?
The native Restart-Service cmdlet executes the stop and start commands almost instantaneously. Because the SCCM agent is a heavy, monolithic service that hooks deeply into WMI and local log files, an instantaneous restart frequently results in the service hanging in a "Starting" state. Manually separating the commands and injecting a 4-second sleep guarantees stability.
Q: Does this reinstall or repair a broken SCCM client?
No. This script simply restarts the existing service. If the SCCM client is fundamentally broken (e.g., WMI repository corruption or missing binaries), the service will fail to start. For deep corruption, you would need to use the UHDC's "Deep Storage Cleanup" tool to purge the cache, followed by a full client reinstall.
Q: Will the user see anything happen on their screen?
If the user has the Software Center window actively open on their screen, they might see it briefly flash or display a "Loading" spinner for a few seconds while the underlying service reconnects. Otherwise, the process is completely invisible to them.