As Configuration Manager relies heavily on a working WMI on both clients and servers, a working WMI is really crucial for all activities performed.
The following post was just updated and I strongly recommend that you read it. http://blogs.technet.com/b/askperf/archive/2011/08/05/suggested-hotfixes-for-wmi-related-issue-on-windows-platforms.aspx
Here is the recommended updated for Windows 7 and Windows 2008 R2 from that post.
Hotfix list for Windows 7 and Windows Server 2008 R2
2705357 The WMI process stops sending events to WMI clients from a Windows 7-based or Windows Server 2008 R2-based server
2617858 Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7
2465990 “0x80041002 (WBEM_E_NOT_FOUND)” error occurs when you try to open a WMI namespace on a computer that is running Windows 7 or Windows Server 2008 R2
2492536 Msinfo32.exe takes a long time to display or export system information on a computer that has many MSI-X-supported devices and that is running Windows 7 or Windows Server 2008 R2
982293 The Svchost.exe process that has the WMI service crashes in Windows Server 2008 R2 or in Windows 7
974930 An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exception
Read the whole post here: http://blogs.technet.com/b/askperf/archive/2011/08/05/suggested-hotfixes-for-wmi-related-issue-on-windows-platforms.aspx