I'm seeing a number of customers that have a mix mash of SCCM 2007 client issues and with SCCM 2012, I can't find anything that says these things go away. Duplicate GUIDs - should they be fix prior to migration to SCCM 2012 or will the new client "Fix" itself 8) Win XP WMI corruption - Yes, customers still have XP and yes corruption is still an issue. Not an SCCM issue but ... Looking to provide guidance to customers who have SCCM deployments that are "marginally successfull" and reasons to migrate them to 2012. Thx Tim M.

ConfigMgr can't fix the root cause for WMI corruption, but the client health feature can mitigate that.Torsten Meringer | http://www.mssccmfaq.de

Hi, To add to Torstens answer the client's WMI must be working correctly when migrating to SCCM 2012, the client installation has no feature to repair WMI, the SCCM 2012 client must be installed on a healthy client with working WMI. If WMI becomes corrupt after that the SCCM 2012 client mitigate that as Torsten writes. Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec