locked
Weird issue RRS feed

  • Question

  • I've tried two clients now, an they dont seem to be retrieving policy from server.

    I force a policy refresh and just get this in CCMEXEC:

     

    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:9cc5fd8e-5d28-4551-a361-92fb3a046567";
     DateTime = "20111020094556.704000+000";
     HostName = "SCCM01.XXX.LOCAL";
     HRESULT = "0x00000000";
     ProcessID = 524;
     StatusCode = 0;
     ThreadID = 4160;
    };

    Nothing else happens, so I presume something is not right on the server itself?

    How to diagnose?

    Thursday, October 20, 2011 9:51 AM

Answers

All replies

  • I'm wondering if the server is really busy.

    The CCM.Log is realy busy and seems to be trying to connect to lots of machines what do not exist any more - AD isnt very tidy at the moment.

    Would it be a good idea to turn off Automatic Client Push? We are currently building machines by OSD TS whereby the client installs as part of the build.

    Anything outside of this I'm sure could be handled manually... is that a good idea?

     

    Thursday, October 20, 2011 9:57 AM
  • Have you enabled site wide client push? If your client installation is part of OSD then client push is not required right?

    May e you can go through http://blog.coretech.dk/kea/how-to-stop-a-client-push-installation-in-configuration-manager/

    Discussion thread on this forum http://social.technet.microsoft.com/Forums/en-CA/configmgrsetup/thread/ab7ce6d8-14b4-47ba-b07d-57fe6c8224fb


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Thursday, October 20, 2011 10:09 AM
  • I'm going to look at that, but in the meantime, I tried another PC that is an old build and that is resolving fine...

    Just two new builds, which have stopped working.

    How can I pinpoint an issue?

    Thursday, October 20, 2011 10:13 AM
  • If you are talking about build issue then checkout smsts.log whether the client is installed properly or not? clientidmanager.log and locationservices.log can provide you more details...

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Thursday, October 20, 2011 10:18 AM
  • I'm getting this in ClientIDManagerStartup.log:

     

    <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="11:21:57.344+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:1434">
    <![LOG[RegTask: Client registration is pending.]LOG]!><time="11:21:57.594+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:1458">
    <![LOG[RegTask: Client is pending registration. Sending confirmation request...]LOG]!><time="11:21:57.594+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:1530">
    <![LOG[RegTask: Server requested reset. Restarting client registration]LOG]!><time="11:21:57.657+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:1556">
    <![LOG[RegTask: Initial backoff interval: 1 minutes]LOG]!><time="11:21:59.671+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:1830">
    <![LOG[RegTask: Reset backoff interval: 257 minutes]LOG]!><time="11:21:59.671+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:1831">
    <![LOG[Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.]LOG]!><time="11:21:59.671+-60" date="10-20-2011" component="ClientIDManagerStartup" context="" type="1" thread="5052" file="regtask.cpp:146">

    Thursday, October 20, 2011 10:23 AM
  • there were conflicting records.

    All ok now

    Thursday, October 20, 2011 10:59 AM
  • On some machines I'm trying today, even ones which have been built for ages.

    I can run Machine Policy Retrieval, the machine gets the policy, see the following in CCMEXEC:

     

    Raising event:

    instance of CCM_CcmHttp_Status
    {
     ClientID = "GUID:9cc5fd8e-5d28-4551-a361-92fb3a046567";
     DateTime = "20111020094556.704000+000";
     HostName = "SCCM01.XXX.LOCAL";
     HRESULT = "0x00000000";
     ProcessID = 524;
     StatusCode = 0;
     ThreadID = 4160;
    };

     

    The following in EXECMGR:

     

    Execution Request for package XXX00103 program Uninstall state change from WaitingDependency to WaitingContent

     

    And it sits there for quite a while, been quite a few mins so far... its a very small package as well.

     

    How can I tell when the server is doing... or if its very busy?

     

    Friday, October 21, 2011 11:09 AM