Share via

SCCM Client icon shows Question mark in SCCM Console

NUNI RAMESH RAJU 16 Reputation points
2026-01-23T12:33:13.3633333+00:00

SCCM Client icon shows Question mark in SCCM Console.in sccm client is showing only two cycles.Machine Policy Retrieval & Evaluation Cycle User Policy Retrieval Cycle

SERVER DETAILS:

SCCM Server: MECM2403 with MP is configured EHTTP.( On prem Server -Domain Joined)

Client: Windows Server 2016 ( AWS Server _ Domain Joined)

On‑prem domain‑joined servers work fine but AWS domain‑joined servers fail to activate the SCCM client under SCCM 2403 with Enhanced HTTP (EHTTP) points to a few common pitfalls:

CCMSETUP.LOG FILE ATTCHED. CCMNOTIFICATION AGENT LOG:

![LOG[Received notification for ClientID change]LOG]!><time="17:27:40.708-330" date="12-29-2025" component="BgbAgent" context="" type="1" thread="15396" file="agentendpoint.cpp:177">

<![LOG[The controller is either NOT started yet or already stopped.]LOG]!><time="17:27:40.728-330" date="12-29-2025" component="BgbAgent" context="" type="2" thread="15396" file="bgbcontroller.cpp:184">

<![LOG[===========================================================]LOG]!><time="17:27:42.897-330" date="12-29-2025" component="BgbAgent" context="" type="1" thread="18056" file="agentendpoint.cpp:237">

<![LOG[Bgb client agent is starting...]LOG]!><time="17:27:42.898-330" date="12-29-2025" component="BgbAgent" context="" type="1" thread="18056" file="agentendpoint.cpp:238">

<![LOG[Bgb client agent is disabled]LOG]!><time="17:27:42.903-330" date="12-29-2025" component="BgbAgent" context="" type="2" thread="18056" file="agentendpoint.cpp:242">

<![LOG[TCP Listener is disabled.]LOG]!><time="17:27:42.909-330" date="12-29-2025" component="BgbAgent" context="" type="2" thread="18056" file="agentendpoint.cpp:247">

<![LOG[BgbController main thread is started with settings: {bgb enable = 0}, {tcp enabled = 0}, {tcp port = 0} and {http enabled = 0}.]LOG]!><time="17:27:42.921-330" date="12-29-2025" component="BgbAgent" context="" type="1" thread="18056" file="bgbcontroller.cpp:128">

<![LOG[Wait 3600 seconds for event notification.]LOG]!><time="17:27:42.943-330" date="12-29-2025" component="BgbAgent" context="" type="1" thread="14296" file="bgbcontroller.cpp:455">

<![LOG[Wait 3600 seconds for event notification.]LOG]!><time="18:27:42.985-330" date="12-29-2025" component="BgbAgent" context="" type="1" thread="14296" file="bgbcontroller.cpp:455">

System Center Virtual Machine Manager
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. mert efe kanlikilic 85 Reputation points
    2026-01-28T12:33:00.44+00:00

    Hello @NUNI RAMESH RAJU

    The issue points to Enhanced HTTP (EHTTP) connectivity or certificate trust between your AWS servers and the on-prem SCCM MP, since on-prem servers work fine.

    Things to Check:

    1. Network Connectivity Verify port 443 is open between AWS and your on-prem SCCM server:

    powershell

    Test-NetConnection MECM2403.yourdomain.com -Port 443

    2. Management Point Discovery Check if the AWS client can discover and reach the MP:

    • Review LocationServices.log on the client for MP discovery issues
    • Verify DNS resolution of the MP FQDN from AWS

    3. Certificate Trust (EHTTP) EHTTP uses self-signed certificates. AWS clients may not trust the SCCM-issued certificate:

    • Verify the SCCM root certificate is in the client's Trusted Root Certification Authorities store
    • Check ClientIDManagerStartup.log for certificate registration errors

    4. Boundary Configuration

    • Confirm the AWS subnet is defined as a boundary in SCCM
    • Verify that boundary is assigned to a boundary group containing your MP

    5. Client Registration Check ClientLocation.log for registration failures with the MP.

    The "?" icon and limited cycles indicate the client isn't fully communicating with the site. Focus on connectivity and certificate trust first.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.