Resolving SCCM Client Offline Status Despite Network Connectivity

Explore Our MECM / SCCM Training →

Introduction

IT admins often encounter SCCM clients displaying an offline status despite having network connectivity. This post will guide you through common causes and solutions for these issues.

Common Causes

Despite working PING and DNS resolution, the following factors can lead to SCCM clients appearing offline:

• Client PKI certificate validity issues
• Management point selection logic problems
• LocationServices.log analysis required
• Client GUID registration issues in ClientIDManagerStartup.log

Resolving Certificate Issues

To check client PKI certificate validity, use certutil or the Microsoft Management Console certificates snap-in (Personal store). Renew expired certificates via SCEP or manual issuance.

Using Certutil

certutil -ca -n CN= -s  -e  -r
    

Using MMC Certificates Snap-in

1. Open the Microsoft Management Console (MMC).

2. Add the Certificates snap-in for the local computer account.

3. Navigate to Personal > Certificates > Personal Certificates.
4. Check if the SCCM client certificate is valid and not expired.

Management Point Selection Logic

Review LocationServices.log to confirm the client found a Management Point.

Inspecting Client GUID Registration Issues

Inspect ClientIDManagerStartup.log for client GUID registration issues.

HTTPS-only Sites

For HTTPS-only sites, run the LocationServices URL test (this should fail in HTTPS mode, that is expected).

Entra-joined Co-managed Devices

For Entra-joined co-managed devices, verify dsregcmd /status shows AzureAdJoined: YES.

Conclusion

By understanding these common causes and resolving them, you can bring your SCCM clients back online and ensure a smooth IT infrastructure. For more advanced Microsoft technologies training, visit ITP Training.

Explore Our MECM / SCCM Training →