Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter >
> 
> 
SCEP 2012 XP clients not reporting Definition version

Answered SCEP 2012 XP clients not reporting Definition version

  • Wednesday, April 25, 2012 1:43 PM
     
     
    Sign In to Vote
    0

    Hi all,

    I have a stange error regarding clients not reporting there current definition version. All Windows 7 clients are reporting like they should. All Windows XP clients are not reporting the current definition version.

    Windows XP systems are online and when I logon to the systems it shows that EP is updating correctly.

    Hope someone can help me out with this one.

    Kind regards,

    Bart Timmermans

    Bart Timmermans | Consultant at inovativ
    Follow me @ My Blog | Linkedin | Twitter

    Please mark as Answer, if my post answers your Question. Vote as Helpful, if it is helpful to you.

     

All Replies

  • Thursday, April 26, 2012 9:28 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hello,
     
    Thank you for your question.

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
     
    Thank you for your understanding and support.

    Regards

    Rick Tan

    TechNet Community Support

     
  • Thursday, May 03, 2012 6:46 PM
     
     Answered
    Sign In to Vote
    0

    Hello Bart,

    Regarding the failure of the update version reporting from Windows XP clients, the problem may be due to WMI infrastructure and/or .Net Framework issues.  Check the baselines for the Windows XP clients.  The following information may rectify your issue.

    0) Review all Event logs and System Center Configuration Manager logs for errors or warnings.

    1) Troubleshoot and repair WMI if necessary

    2) Install WMI Hotfix 933062 to proactively address most known issues with WMI if WinXP client.
    933062 An update is available that improves the stability of the Windows Management Instrumentation repository in Windows XP
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;933062

    3) Repair .NET framework.
    To repair the MSI-based version of the .NET Framework 2.0 SP2 or 3.0 SP2 on Windows XP or Windows Server 2003, you must run the following command lines instead of using the repair option from Add/Remove Programs
    .NET Framework 2.0 SP2 - silent repair
    msiexec /fpecmsu {C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F} REINSTALL=ALL /l*v %temp%\netfx20sp2_repair_log.txt /qb
    .NET Framework 3.0 SP2 - silent repair
    msiexec /fpecmsu {A3051CD0-2F64-3813-A88D-B8DCCDE8F8C7} REINSTALL=ALL /l*v %temp%\netfx30sp2_repair_log.txt /qb

    4) Re-install .NET framwork
    908077 How to manually remove and then reinstall the.NET Framework 2.0
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;908077
    824643 How to troubleshoot Microsoft.NET Framework 1.1 installation issues in Windows XP or in Windows 2000
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;824643

    5: Data-loss-less repair of WMI: Rebuild Repository

    If your problem is not resolved using the information above, please call Microsoft support at 1-800-4900 to open a support incident to troubleshoot your issue.

    Regards,

    Al Knecht, MCSE 2008, MCTS Server 2008 & FCS, MCITP Server 2008, MCSA 2003, CISSP®

    Microsoft Security Support Engineer