locked
Issues with XP Agents RRS feed

  • Question

  • Hello Everyone,

    I'm new to SCCM, I've been an Altiris user for many years, so I apologize if my knowledge isn't up to snuff on all of this yet.  I'm working with a consultant right now and we're pushing the agents out to all of our machines.  The client installs fine on both XP SP3 and Windows 7 machines but it doesn't receive all the 'actions' for the XP clients so it is not reporting back it's inventory and many other things properly.  Any ideas on what to check?  We're also in the process of migrating our 2003 Domain to a new 2008 Domain so we have a domain-wide trust set up currently..........clients are in the old domain and SCCM is in the new domain.

    Thanks!

    Monday, June 18, 2012 2:25 PM

Answers

All replies

  • There will only be two client actions listed if the client is not able to retrieve policies from the management point. See clientlocation.log and locationservices.log. Also double check if the client is set to "approved = yes" in the console.


    Torsten Meringer | http://www.mssccmfaq.de

    Monday, June 18, 2012 2:31 PM
  • The client installatio and assignment process is a two-step process. If you do not see any actions (besides the two default) in the client properties then the assignment phase is not finished correctly. As Torsten says there are some log files that can assist you. Besides the once mentioned by Torsten, be sure to also check the clientidstatrupmanager.log

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

    Monday, June 18, 2012 4:10 PM
  • Thanks for the replies.

    I see these errors in 'ClientIDManagerStartup.log:'

    Failed to open to WMI namespace '\\.\root\ccmvdi' (8007045b) ClientIDManagerStartup 6/14/2012 6:10:13 PM 2376 (0x0948)

    [RegTask] - Client is not registered. Sending registration request for GUID:B3C2DE0E-D758-4F9E-8376-20E213017678 ... ClientIDManagerStartup 6/15/2012 9:55:32 AM 2864 (0x0B30)
    RegTask: Failed to send registration request message. Error: 0x8000000a ClientIDManagerStartup 6/15/2012 9:55:32 AM 2864 (0x0B30)
    RegTask: Failed to send registration request. Error: 0x8000000a ClientIDManagerStartup 6/15/2012 9:55:32 AM 2864 (0x0B30)

    I see these warnings in 'LocationServices.log:'

    Failed to refresh security settings over AD with error 0x87d00215. LocationServices 6/16/2012 3:17:29 AM 3848 (0x0F08)
    DhcpGetOriginalSubnetMask entry point not supported. LocationServices 6/16/2012 3:17:29 AM 3848 (0x0F08)
    Failed to refresh Site Signing Certificate over AD with error 0x87d00215. LocationServices 6/16/2012 3:18:20 AM 3848 (0x0F08)
    1 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 6/16/2012 3:18:24 AM 2400 (0x0960)

    Monday, June 18, 2012 4:24 PM
  • Looks like a WMI related problem, check http://trevorsullivan.net/2009/11/06/wmi-repository-corruption-sccm-client-fix/


    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

    Monday, June 18, 2012 4:32 PM
  • Looks like 'approving' the client made it work.  Is there a reason the XP clients need to be approved by default?  Is there a way to change this behavior?  I have a lot of clients and I don't want to have to change that individually. 

    Thanks!

    Monday, June 18, 2012 4:43 PM
  • Approval is not a matter of the client OS. Just check the approval settings. See http://technet.microsoft.com/en-us/library/gg682161.aspx#BKMK_Security_Cliients


    Torsten Meringer | http://www.mssccmfaq.de


    Monday, June 18, 2012 5:10 PM