none
Client installed and discovered but unable to report on it?

    שאלה

  • O.K so I have the same problem as a lot of other SMS admins about 3% of my clients are showing up as...

    • Client =NO
    • Approved = N\A or Approved
    • Assigned = YES

    The clients are however installed...

    I can log into the clients and view the ConfigMgr app in the windows Control Panel, it will auto discover the Site Code and has all the expected Actions listed as are configured in the Client Agents site settings.

    I've inspected logs mentioned in other threads and these clients by all intents and purposes seem to be exchanging DDRs and speaking to the MP just fine but the Client Status still = NO

    I've "Updated the Collection Membership" loads of times in troubleshooting but these clients persist in beiong = NO

    Here are the actual problems I face...

    • In some cases the "Remote Tools" work...I can shadow and control the client. In other cases these tools do not work.
    • Clients are discovered in collections but I am unable to run "Client Status Reports" on them

    Anyone have any other trick to try and resolve these troublesome clients? I've done the whole stopping of services and "DelCert" thing too...no joy.

    Here is the total head scratcher...In some instances initiating the "Discovery Data Collection Cycle" will temporarily fix clients. I initiate the action, wait, update collection memebership and Client = YES then the next day Client = No again???? 


    • נערך על-ידי durrie יום שני 20 יוני 2011 11:05
    יום שישי 17 יוני 2011 13:09

כל התגובות

  • Are there any errors logged in the client logfiles like ccmexec.log or Policyagent.log? I would try repairing WMI and then resintall the SCCM client. WMI is one of the most common problem out-there.

     

    Regards,
    Jörgen


    -- My System center blog ccmexec.com --
    יום שישי 17 יוני 2011 13:36
  • Hello durrie !


     Thank you for writing Microsoft TechNet Forums. For me it looks like that you are facing two different problems.

     

    I will try to explain what you can try while troubleshooting each of them.

     

    Where client install flag is marked : NO


    1. Check the ClientIdManagerSetup.log on the client where we have the client installed but in the console it's marked NO 

    2. This log should tell you either client is registered or not.

    3. If it's registered then it's not a client side issue and you probably look at the MP Logs where we can see if the Management Point is doing the work.

    4. Also check locationservices.log that will tell you which MP we are updating the client registration information.

    5. Make sure that the client is pointing to the correct MP; I have seen cases where client is updating the registration information on a old MP. Which may cause the same behavior.

    6. Also check the client actions in the ConfigMgr client applet and see if all the actions are listed under that.e.g. It Machine Policy, User Policy, Software Update scan and so on. If you are seeing only two actions only; then more or less the client unable to contact the Management Point.

     

    Troubleshooting Remote Tools


    1. Check the log created RemoteControl.log <install \ Ccmsetup \ client is having problems.
    2. Check the log RemoteTools.log created in% temp% in the computer that is initiating the connection.
    3. Verify that the ConfigMgr Remote Control Users group is correctly configured on the client.
    4. Check the security settings for DCOM are applied correctly.
    5. Ensure that ports TCP 2701, TCP 2702, TCP 135 are released into the firewall. If you are using Remote Desktop or Remote Assistance check if TCP port 3389 is released in the firewall.
    6. Make sure the file c: \ windows \ system32 \ RCAgent.exe is also released into the firewall.
    7. Make sure the file c: \ windows \ PCHealth \ HelpCtr \ binaries \ Helpsvc.exe is also released into the firewall or the File and Printer Sharing.
    8. Make sure the anti-virus is not blocking the remote connection.
    9. Verify that no other remote connection to the same customer.
    10. Groups linked with Remote Tools do not work, that is, one should place the main group.
    11. When capturing network packets by Wireshark, check for: isystemactivator
    a. For successful connection has only one pair of ISystemActivator RemoteGetClassObject ISystemActivator RemoteGetClassObject request and response
    b. To have connection without success:
    i. When the user does not have permission DCOM: ISystemActivator RemoteGetClassObject request and another could be DCERPC Fault: call_id: 10 ctx_id: 0 Status: nca_s_fault_access_denied
    ii. When the user has permission DCOM, there will be several times the double ISystemActivator RemoteGetClassObject request and another ISystemActivator RemoteGetClassObject response.
    12. See http://technet.microsoft.com/en-us/library/bb735873.aspx for a list of error codes using Remote Tools.
    Hope that helps !!!


    Anurag

    Please click the Check Mark As Answered Check Mark On This Page If this post helps to resolve your issue, as it helps others who need quick access to answers.
    יום ראשון 19 יוני 2011 16:24
  • Hi,

     

    You may check if the steps in the following blog helps:

     

    Troubleshooting issues where clients are not reporting

     

    Regards,

     

    Sabrina


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    יום שני 20 יוני 2011 07:06
  • Thank you all very much for your suggestions...

     

     

    Jörgen - I found and used the WMIDiag.vbs script to checkout the problem clients WMI. This turned out to be very confusing. Apparently this script doesn't properly recognise XP SP3 and it actually never reported the fact that my client PCs do infact have SP3 installed?

    The script flagged 3 x DCOM and 3 x WMI security errors on a problem client but these issues seem to be red-herrings as some working clients flagged the same DCOM and WMI issues??? The interesting bit is that I decided to do a WMI repository rebuild on three problem clients. The result was initially a positive one - a duplicate SCCM client record was created in the SCCM DB and showed up in the SCCM collection with Client = YES however this morning three days later one of those clients is once again = NO

    The CcmExec.log on this particular client reported a "Message Payload Transfer - Upload - Success" later on after I did the repository rebuild so I believe this client (and maybe some others) problem lies in one of two places - 1. The MP record 2. The AD record

     

     

    Anurag - Thanks for the very detailed reply. The remote tools issue is not a concern for now I merely mentioned it as a stange behaviour incase it indicated anything. I want the site to reflect the client status properly and report properly before I worry about remote tools but thanks very much for those pointers I have saved them for a later date.

    The ClientIDManagerStartup.log reported the client as registered. It reported this at a time after I did the WMI repository rebuild (fri 18-06-2011) as metioned above. The LocationServices.log reported the correct MP back from AD this morning (mon 20-06-2011)...however the Client = NO once again???

    When I log onto the client PC and check the ConfigMgr applet it all works perfectly? Site auto discovers and all the Actions and Site Components are listed as expected???

    Is this a "Site setup" issue I wonder...I've inherrited this role and system and the current setup has 3 x discovery methods enabled...Active Directory System Discovery \ Heartbeat Discovery \ Network Discovery

    As I understand it the Heartbeat Discovery does only an "update" job on existing client records. My "Heartbeat discovery" period is 1 day so it seems like this update job causing the client status to change? How do I check this?

     

     

    Sabrina - thanks for the blog referance I'm going through this now...on first glance it looks to be very helpful. I will report back any findings...

     


    יום שני 20 יוני 2011 10:07
  • UPDATE...

    I suspected this would \ could be due to stale records in either the MP or Active Directory...so I decided to try the following...

    • remove the client PC from the domain
    • delete the computer account from AD
    • delete the client record from SCCM

    Wait...then search for AD client PC record...none found so...

    • add client PC back to domain
    • enitiate - "Discovery Data Collection Cycle"
    • enitiate - "Machine Policy Retrieval & Evaluation Cycle"

    The result of this as described above is that this PC is now correctly showing up in SCCM as "Client = YES" "Approved = Approved" "Assigned = YES" but I don't quite know what this proves?

    Does it indicate the AD record was stale or the DDR on the SCCM MP? And how can we fix this by means of admin tasks instead of the long winded manual task?



    יום שני 20 יוני 2011 11:01
  • The next step, should be looking at the registration processing on the Manaement Point. Try checking the "MP_RegistrationManager.log" for the time when client sent the registration request. Try to see if it was processed :

     

    It should say something like this:

    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/28/2010 8:09:24 PM 472 (0x01D8)
    MP Reg: Failed to get client(GUID:BF96A7A8-2B8D-41E3-8B64-A5873C0E7094) public key: 0x80040238 MP_RegistrationManager 10/28/2010 8:09:48 PM 472 (0x01D8)
    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/28/2010 8:09:48 PM 472 (0x01D8)
    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/28/2010 8:11:49 PM 2492 (0x09BC)
    MP Reg: DDR file written to d:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\1628CIWS.RDR MP_RegistrationManager 10/28/2010 9:03:31 PM 2336 (0x0920)
    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/28/2010 9:03:31 PM 2336 (0x0920)
    MP Reg: Confirmation failed. MP_RegistrationManager 10/28/2010 9:03:31 PM 2336 (0x0920)
    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/28/2010 9:03:31 PM 2336 (0x0920)
    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/28/2010 9:13:30 PM 1744 (0x06D0)
    MP Reg: Message ReplyTo : direct:dummy:dummy MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    MP Reg: Message Timeout : 0 MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    MP Reg: Message Body : <ClientRegistrationRequest><Data RequestType="Registration" TimeStamp="2010-10-31T15:58:56Z" SMSID="GUID:D7CF5960-E8E0-4D4B-A389-CE1C6CF0B652"><AgentInformation AgentType="0" AgentVersion="4.00.6487.2000"/><Certificates><Signing Encoding="HexBinary">308205343082041CA003020102020A242B99C3000000000008300D06092A864886F70D0101050500304731133011060A0992268993F22C6401191603636F6D31163014060A0992268993F22C64011916064D616E426C72311830160603550403130F4D616E426C722D43533144432D4341301E170D3130313032383134303330355A170D3131313032383134303330355A301B311930170603550403131043533158502E4D616E426C722E636F6D30819F300D06092A864886F70D010101050003818D0030818902818100DF2B49703872ACFDB1797DED471901FBFDBE6F2E92D46C502DBD85684FBCC1470318D00C54EF4313917A96F432432815C2C25E766F70E71DF8EE0F77FDB880D985E69A82C5971F536A52BA3B581BAA8862914D2B8B6BB535F4599C9B2DF83048239709EBBC97294FEAC96D05D9352DCE6C882800B0DEFBEDCFA4C8D52192C06B0203010001A38202D0308202CC300E0603551D0F0101FF0404030205A0301D0603551D0E0416041437A2ED403FF54E494FC6758FDC97A0A31FC3FEB9301D06092B060104018237140204101E0E004D0061006300680069006E0065301F0603551D2304183016801432F3160FDCAEB807C66B2862D4062A2408E3D1B2308201020603551D1F0481FA3081F73081F4A081F1A081EE8681B36C6461703A2F2F2F434E3D4D616E426C722D43533144432D43412C434E3D43533144432C434E3D4344502C434E3D5075626C69632532304B657925323053657276696365732C434E3D53657276696365732C434E3D436F6E66696775726174696F6E2C44433D4D616E426C722C44433D636F6D3F63657274696669636174655265766F636174696F6E4C6973743F626173653F6F626A656374436C6173733D63524C446973747269627574696F6E506F696E748636687474703A2F2F63733164632E6D616E626C722E636F6D2F43657274456E726F6C6C2F4D616E426C722D43533144432D43412E63726C3082011706082B0601050507010104820109308201053081AD06082B060105050730028681A06C6461703A2F2F2F434E3D4D616E426C722D43533144432D43412C434E3D4149412C434E3D5075626C69632532304B657925323053657276696365732C434E3D53657276696365732C434E3D436F6E66696775726174696F6E2C44433D4D616E426C722C44433D636F6D3F634143657274696669636174653F626173653F6F626A656374436C6173733D63657274696669636174696F6E417574686F72697479305306082B060105050730028647687474703A2F2F63733164632E6D616E626C722E636F6D2F43657274456E726F6C6C2F43533144432E4D616E426C722E636F6D5F4D616E426C722D43533144432D43412E637274301D0603551D250416301406082B0601050507030206082B06010505070301301B0603551D1104143012821043533158502E4D616E426C722E636F6D300D06092A864886F70D010105050003820101000A2799809524EBE0BDAA9946667A68F1CD63B68D19D40DB78EA77C9851DB3A33A955B79FCB0F82EF0843885F42FEE53F94FAC5874374C6B1604538643DCF8C99557819817A1B3CFDDFFF3D245102513AF6F4F486D76E8B8272DB3D96DEA59B8D06CC1D7DEB420979D0D63BF5138036C5483FCAC474F7BF697C1A94DFE28229FB936E90CA2E5526510C002AD270EEFF3D1973EFE4C009FBD2790C08C5D6976A94991C06327FF495A753BF276A1F6AF32639BCC6D856F75D37FC1E030A5A39F34BCD3C14163FAD00FDCAE1BFF7F12E1806880E101DAE0DFF86CD9BB68E18E70042D2746CC284EDE92FDA2FFD8D91BA080F87A610D78BD19048D76669B340E2BBE6</Signing></Certificates><DiscoveryProperties><Property Name="Netbios Name" Value="CS1XP"/><Property Name="FQ Name" Value="CS1XP.ManBlr.com"/><Property Name="Locale ID" Value="1033"/><Property Name="InternetFlag" Value="0"/><Property Name="HardwareID1" Value="2:FCCC3CB826713084FDA9D5BB14878997279E5CE5"/></DiscoveryProperties><RegistrationHint/></Data><Signature><SignatureValue>66C3670F5EC4DDC465A141EBAC4DB18577B89070B200415FDFDA36A65B361AB7A64A7E494B3512D0A1DDC3E1BC0EAD3618529ECED60E97BEFA06CD69E7691D0FA3A0CD18E919FDEB6DC8DCF382AE216C00CEF6518BEF4C04338E700A0ABB4D572942EE753384157A183BBD78021C742A1C6FB1CEFEFDD79B17F53D98B2706DDE</SignatureValue></Signature></ClientRegistrationRequest>
     MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Parsing done. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Successfully created certificate context. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    MP Reg: Successfully created context from the raw signing certificate. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Creating CTL context. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    GetMPWebSite: MP is installed under web site <IIS://LocalHost/W3SVC/1> MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    hrGet, HRESULT=800cc801 (e:\nts_sms_fre\sms\framework\core\ccmcore\checkaccess.cpp,166) MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    GetIISWebServiceStringProperty( 5512, sWebSite, sCtlIdentifier ), HRESULT=800cc801 (e:\nts_sms_fre\sms\framework\core\ccmcore\checkaccess.cpp,519) MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    S_OK == LookupIISSslCtlIdentifier( sCtlIdentifier ), HRESULT=00000001 (e:\nts_sms_fre\sms\framework\ccmutillib\ccmctl.cpp,127) MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    The Ssl ctl identifier is ''. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Failed to read CTL from IIS metabase, try reading from the registry. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    CCMKey.GetMultiString( szRegEntryName, saValues ), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\ccmutillib\ccmctl.cpp,50) MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Failed to read the CTL from the registry. MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Detecting if CRL check enabled through IIS.  MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    GetMPWebSite: MP is installed under web site <IIS://LocalHost/W3SVC/1> MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    CRL check enabled.  MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Registration Signature: 66C3670F5EC4DDC465A141EBAC4DB18577B89070B200415FDFDA36A65B361AB7A64A7E494B3512D0A1DDC3E1BC0EAD3618529ECED60E97BEFA06CD69E7691D0FA3A0CD18E919FDEB6DC8DCF382AE216C00CEF6518BEF4C04338E700A0ABB4D572942EE753384157A183BBD78021C742A1C6FB1CEFEFDD79B17F53D98B2706DDE MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    MP Reg: DDR file written to d:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\RC10EJTB.RDR MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    Mp Reg: Reply message <ClientRegistrationResponse ResponseType="Registration" TimeStamp="2010-10-31T15:58:56Z" Status="1" SMSID="GUID:D7CF5960-E8E0-4D4B-A389-CE1C6CF0B652"/>
     MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    MP Reg: Processing completed. Completion state = 0 MP_RegistrationManager 10/31/2010 9:28:56 PM 3448 (0x0D78)
    MP Reg: Message ReplyTo : direct:dummy:dummy MP_RegistrationManager 10/31/2010 9:28:57 PM 3448 (0x0D78)
    MP Reg: Message Timeout : 0 MP_RegistrationManager 10/31/2010 9:28:57 PM 3448 (0x0D78)
    MP Reg: Message Body : <ClientRegistrationRequest><Data RequestType="Confirmation" TimeStamp="2010-10-31T15:58:57Z" SMSID="GUID:D7CF5960-E8E0-4D4B-A389-CE1C6CF0B652"><AgentInformation AgentType="0" AgentVersion="4.00.6487.2000"/></Data><Signature><SignatureValue>328BE40F3C99DFF218E85DED2D30DD4FDDAD0CF836F2CFF37A8DC8B8A77AFA78E501A8C960C63295D99778A6635EB97E312B1B8343CEFB574043C8E20B25C0E36551E577D073E999FEDC7DD00C4386CA2CD726BC4AB08359BF4BE4000DFCFB604A8BC793C6499D2BCB42098684B152656D94B06B88A95054AE52BD9BD10CE769</SignatureValue></Signature></ClientRegistrationRequest>
     MP_RegistrationManager 10/31/2010 9:28:57 PM 3448 (0x0D78)
    Parsing done. MP_RegistrationManager 10/31/2010 9:28:57 PM 3448 (0x0D78)

     

    That should point us to the real issue.

     

    Hope that helps.

     

     

     



    Anurag

    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    יום שלישי 21 יוני 2011 13:05
  • Hi Technical Express...

    Since this update yesterday the gremlins are back...this very same client PC that I did the above steps of removal from Domain and SCCM and then rejoined to Domain and run the inventory actions on is once again today showing up as Client = NO...???

    The confusing bit is that there is no entry in this log at around about the time that I did the above steps to the Client in question which was at around about 10:00 - 11:00

    My MP_RegistrationManager.log file is NOTHING like yours...it never mentions stuff like the Agent Version, Certificates or Parsing...

    This below is the data from my log file..all I have in that log is days and days of this...???

    _____________________________________________________________________________________________________________________________

    MP Reg: DDR file written to D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\1YI2CZQM.RDR]LOG]!><time="09:55:52.465+-60" date="06-18-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="4672" file="regtask.cpp:654">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:55:52.465+-60" date="06-18-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="4672" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:55:52.731+-60" date="06-18-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="2036" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="22:57:34.020+-60" date="06-19-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="1744" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="01:20:09.113+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="08:43:27.574+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="1744" file="regtask.cpp:196">

    MP Reg: DDR file written to D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\UUP7YJI4.RDR]LOG]!><time="09:01:43.003+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="1328" file="regtask.cpp:654">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:01:43.003+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="1328" file="regtask.cpp:196">

    MP Reg: Failed to get client(GUID:0BD81191-5757-418D-81F1-E5D92F784288) public key: 0x80040238]LOG]!><time="09:01:43.268+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="3" thread="6120" file="regtask.cpp:1321">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:01:43.284+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:02:43.375+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:14:19.402+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="09:36:42.973+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="1328" file="regtask.cpp:196">

    MP Reg: DDR file written to D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\4T3BVBSA.RDR]LOG]!><time="11:44:15.175+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:654">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="11:44:15.191+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:196">

    MP Reg: Failed to get client(GUID:636ED0EB-383A-4082-B088-670AC00756E6) public key: 0x80040238]LOG]!><time="11:44:15.831+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="3" thread="1744" file="regtask.cpp:1321">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="11:44:15.847+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="1744" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="11:45:16.016+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="5532" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="15:03:34.850+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="6120" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="15:38:49.086+-60" date="06-20-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="4988" file="regtask.cpp:196">

    MP Reg: DDR file written to D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\FIF342JJ.RDR]LOG]!><time="12:48:33.578+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="5812" file="regtask.cpp:654">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="12:48:33.594+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="5812" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="12:48:33.781+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="4988" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="14:17:09.884+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="5812" file="regtask.cpp:196">

    MP Reg: DDR file written to D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\T8ATD5B5.RDR]LOG]!><time="17:59:53.986+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="3476" file="regtask.cpp:654">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="17:59:54.002+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="3476" file="regtask.cpp:196">

    MP Reg: Failed to get client(GUID:B7EBB21E-3207-46F4-8AC9-D931439264B4) public key: 0x80040238]LOG]!><time="17:59:54.549+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="3" thread="3476" file="regtask.cpp:1321">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="17:59:54.565+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="3476" file="regtask.cpp:196">

    MP Reg: Processing completed. Completion state = 0]LOG]!><time="18:00:54.721+-60" date="06-21-2011" component="MP_RegistrationManager" context="Registration" type="1" thread="5168" file="regtask.cpp:196">


    • הוצע כתשובה על-ידי otieno יום שישי 24 יוני 2011 12:09
    • הצעה כתשובה בוטלה על-ידי durrie יום שישי 24 יוני 2011 15:54
    יום שלישי 21 יוני 2011 17:09
  • The first thing to do is to check your event log if you have some DCOM event 10009 this could be a DNS problem try ping the machine IP with -a from the server

    next check firewall settings

    next check in the Sccm SQL DB if you have duplicate client GUID

     


    patrik
    יום שישי 24 יוני 2011 12:14
  • Hi Patrick...

    Thanks so much for your reply...

    I have got lots and lots of "DCOM 10009" errors in the SYSTEM event log on my Site Server. The wired thing is that a ping -a replies in a timely and normal fashion when pinging one of the same problem clients in question???

    Windows firewall is disabled on both the server and client because we do this via GPO...we do this because we use McAfee Enterprise Virus scan for security and firewall.

    Having said that I will speak to my colleague who manages McAfee and the EPO server to see if we can identify any strange behaviour showing up for these problem clients on the EPO logs...

    Thanks for the suggestions...

     

    יום שישי 24 יוני 2011 15:46
  • In addition to Jorgen's advice, I would ask you to try below things on affected client machines-

    repair WMI>uninstall sccm client>reinstall client

    update the collection membership once you think client is having communication with MP properly. I have faced such kind of issues and this is how I fixed them.

    there might be some other case in the situation stated by you so I won't say this is the main solution step but I assume that it can help you.

    Thanks.  

    יום שלישי 10 אפריל 2012 09:52