Every machine deployed with SCCM has WMI issues, preventing functions such as printer mapping within our logon script from working. We can resolve this by repairing the WMI with run winmgmt /resetrepositry but i don't understand whats causing this in the first place. The image was made by SCCM installing and capturing Windows 7 with no additional software installed, off a virtual machine. There is nothing else changed from the default capture operating system task sequence apart from the use of an unattend.xml to set the language and regional settings. Is this a case of bad luck? Should i make a new image and just hope it does'nt have the same issue?I would like to know what caused it so we can avoid a re-occurance. The error message I'm getting is: Event filter with query "SELECT * FROM_InstanceModificationEvent WITHIN 60 WHERE Targetinstans ISA "Win32_Processor" AND TargetInstance.LoadPercentage> 99" could not be reactivated in namespace "//./root/CIMV2" Becuase of error 0x80041003.Events cannot be delivered through this filter until this problem is corrected. Any pointers much appreciated.

do you have any GPO's or netlogon scripts that could be causing issues ? apps applications targetted to your box's that are installed and then cause the corruption ? when does the error message you found occur ? during the deployment of the captured image or after, and if after when ? is that co-incidental with some other gpo/software being installed ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

do you have any GPO's or netlogon scripts that could be causing issues ? apps applications targetted to your box's that are installed and then cause the corruption ? when does the error message you found occur ? during the deployment of the captured image or after, and if after when ? is that co-incidental with some other gpo/software being installed ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady It happens directly after windows first boots after being deployed with the image. At this point no software has been installed and the machine is not on the domain, so therefore there can be no issues regarding GPO or anything. The image itself has never been domain joined or had any software installed.