Back to Troubleshooting

Configuration Manager Issues

Diagnose and resolve SCCM client communication, deployment, and configuration problems affecting Software Center functionality.

Common Configuration Manager Issues

Client Communication

  • • Can't connect to management point
  • • Certificate authentication errors
  • • Network connectivity issues
  • • Firewall blocking SCCM ports
  • • DNS resolution problems

Deployment Problems

  • • Applications not appearing in Software Center
  • • Deployment policies not updating
  • • Machine policy retrieval failures
  • • Software updates not downloading
  • • Collection membership issues

Quick SCCM Health Check

Essential Status Checks

System Status Verification:

  1. 1. Check SCCM client installation: C:\Windows\CCM
  2. 2. Verify SMS Agent Host service is running (services.msc)
  3. 3. Check last policy refresh in Software Center → Options
  4. 4. Review SCCM client logs: C:\Windows\CCM\Logs
  5. 5. Test network connectivity to management point
  6. 6. Verify client certificate validity

Configuration Manager Troubleshooting

1

Client Service Reset

Best for: Basic communication issues, stale policies

Service Restart Process:

  1. 1. Press Windows + R, type services.msc
  2. 2. Find "SMS Agent Host" service
  3. 3. Right-click → "Restart" (or Stop, wait 10 seconds, Start)
  4. 4. Check that service starts successfully
  5. 5. Open Software Center and trigger policy refresh (Options → Computer Maintenance)
  6. 6. Wait 5-10 minutes for policies to update
  7. 7. Check if applications appear in Software Center
Success rate: ~65% for temporary communication glitches
2

Force Policy Retrieval

Best for: Missing applications, outdated policies

Manual Policy Refresh:

  1. 1. Open Software Center
  2. 2. Go to "Options" tab
  3. 3. Click "Computer Maintenance"
  4. 4. Select "Sync Policy" and click "Run"
  5. 5. Wait for completion (may take several minutes)
  6. 6. Also run "Application Deployment Evaluation Cycle"
  7. 7. Restart Software Center and check for new applications

Alternative: PowerShell Method

Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name TriggerSchedule -ArgumentList "{00000000-0000-0000-0000-000000000021}"
3

Network and Certificate Issues

Best for: Connection errors, authentication failures

Connectivity Troubleshooting:

Network Connectivity Test
  1. 1. Open Command Prompt as administrator
  2. 2. Test DNS resolution: nslookup [management_point]
  3. 3. Test connectivity: telnet [management_point] 80
  4. 4. Check firewall: netsh advfirewall show allprofiles
Certificate Validation
  1. 1. Open Certificate Manager: certlm.msc
  2. 2. Check Personal → Certificates for SCCM client cert
  3. 3. Verify certificate hasn't expired
  4. 4. Check trusted root certification authorities
4

Client Repair and Reinstallation

Best for: Corrupted client, persistent communication failures

SCCM Client Repair:

  1. 1. Open Command Prompt as administrator
  2. 2. Navigate to: cd C:\Windows\ccmsetup
  3. 3. Run repair: ccmsetup.exe /mp:[MP_NAME] SMSSITECODE=[SITECODE] RESETKEYINFORMATION=TRUE
  4. 4. Wait for repair process (10-20 minutes)
  5. 5. Restart computer when prompted
  6. 6. Verify client registration after restart
  7. 7. Test Software Center functionality

Note: You'll need your organization's Management Point name and Site Code. Contact IT if unknown.

SCCM Log Analysis

Key Log Files and Common Errors

ClientLocation.log

Management point discovery and assignment

Common errors:

  • • "Failed to get management point" - Network/DNS issues
  • • "Certificate verification failed" - PKI problems
  • • "Site assignment failed" - Site boundary issues

PolicyAgent.log

Policy download and processing

Common errors:

  • • "Policy download failed" - Communication issues
  • • "Policy processing error" - Corrupted policies
  • • "Authentication failed" - Certificate problems

AppDiscovery.log

Application discovery and evaluation

Common errors:

  • • "Application not found" - Deployment targeting issues
  • • "Detection rule failed" - Application requirements
  • • "Content location failed" - Distribution point issues

CCMExec.log

Main SCCM client service activity

Common errors:

  • • "Service failed to start" - Client installation issues
  • • "WMI query failed" - WMI corruption
  • • "Memory allocation failed" - System resource issues

Advanced Diagnostic Tools

Built-in SCCM Diagnostic Tools

Policy Spy Tool

Location: C:\Windows\CCM\PolicySpy.exe

View and analyze client policies in real-time

Client Center

Third-party tool for comprehensive client management

Provides detailed client information and troubleshooting

WMI Tools

Check SCCM WMI classes and methods

wbemtest.exe

CM Trace

Microsoft's log viewer for SCCM logs

Better formatting and filtering than Notepad

Client Health Monitoring

Ongoing Health Checks

Automated Monitoring Script

PowerShell script to check client health regularly:

Get-WmiObject -Class SMS_Client -Namespace root\CCM | Select-Object ClientVersion, LastPolicyRequest

Key Health Indicators

  • • SMS Agent Host service running consistently
  • • Policy requests completing within last 24 hours
  • • No certificate expiration warnings
  • • Management point connectivity stable
  • • Application catalog accessible
  • • Software distribution working properly

Site System Component Issues

Common Infrastructure Problems

Some issues may be related to SCCM server-side components:

Management Point Issues

  • • Service down or restarting
  • • Certificate expiration
  • • IIS configuration problems
  • • Database connectivity issues

Distribution Point Issues

  • • Content not distributed
  • • Bandwidth throttling
  • • Storage space problems
  • • Network latency issues

📞 Note: Infrastructure issues require SCCM administrator intervention and cannot be resolved by end users.

When to Contact SCCM Administrators

Contact your SCCM/IT team immediately if:

  • Client repair attempts fail repeatedly
  • Multiple computers in your area have the same issues
  • Certificate-related errors that you cannot resolve
  • Management point or distribution point connectivity failures
  • Site assignment issues or boundary problems
  • Group policy conflicts affecting SCCM functionality
;