locked
Some clients are inactive/passed in the inactive client details report RRS feed

  • Question

  • We have some clients that don’t seem to attach to the site server properly at all – they show as inactive in the console even though they are on the same LAN segment as other healthy machines. They cannot perform any client actions (machine policy refresh etc)

    Things I have checked:

    1. All ccmexec client components installed and enabled.
    2. Correct site code, correct management point, pki certificate is valid, client certificate: pki, connection type: Currently intranet
    3. Client is approved
    4. Same guid on client as in console
    5. Provisioning mode is set to false
    6. Manually running ccmeval.exe produces a 'healthy' ccmeval.log - in particular: 'clients current MP is https://ourserver.domain.com and is accessible'

    This entry and the many subsequent failures looks interesting

    Queue 'mp_[http]mp_locationmanager' initialized with 45 messages.

    <![LOG[OutgoingMessage(Queue='mp_[http]mp_locationmanager', ID={2361C173-3188-4BCF-BC03-D1B3499708A3}): Will be discarded (expired).]LOG]!><time="11:48:51.567-60" date="10-01-2015" component="CcmMessaging" context="" type="3" thread="3664" file="messagequeueproc_outgoing.cpp:1647">

    and

    Failed to submit event to the Status Agent. Attempting to create pending event. ClientIDManagerStartup

    Thanks

    David


    • Edited by David b111 Friday, October 2, 2015 2:37 PM
    Friday, October 2, 2015 2:15 PM

Answers

  • Ended up reinstalling the client and it all started working again - probably some wmi corruption.  Shame that ccmeval didn't pick it up....
    • Marked as answer by David b111 Friday, October 9, 2015 3:29 PM
    Friday, October 9, 2015 3:29 PM

All replies

  • On the client can you look at the following log CcmMessaging.log to see what is the issue with the communication between the client and the MP.

    Friday, October 2, 2015 4:30 PM
  • Ended up reinstalling the client and it all started working again - probably some wmi corruption.  Shame that ccmeval didn't pick it up....
    • Marked as answer by David b111 Friday, October 9, 2015 3:29 PM
    Friday, October 9, 2015 3:29 PM