SCCM Client Agent Not responding

全部回复

• 2012年6月7日 19:04

   

   
  

  0

  This should help you resolve this issue.This is more to do with the WMI Issue

  http://trevorsullivan.net/2009/11/06/wmi-repository-corruption-sccm-client-fix/

  Let me know if this works.

  Thanks

  Arvind

  
  

  • 已建议为答案 ArvindBS 2012年6月7日 19:04
  • 已编辑 ArvindBS 2012年6月7日 19:08 updated
  • 取消建议作为答案 Rob Marshall - MVPMVP, Moderator 2012年6月8日 18:56
  •  
  • 回复
  • 引用

   
• 2012年6月8日 11:01

   

   
  

  1

  Error 8007007e translates to:

  The specified module could not be found.

  This seems to indicate that the WMI repository is corrupt.

  However, you mentioned that every single machine you try to install the SCCM client on shows this error, so unless all machines in your organization are clones of one another (ghost/wim/whatever), I would say the chances that every single machine on the organization having a corrupt WMI repository are quite slim.

  I would probably start by doing a few wbemtests on classes under root\cimv2 before and after the SCCM client installation.

  If you have problems both before and after the installation of the client on the root\cimv2 classes, then the problem has nothing to do with the SCCM client and it's something that was already there before.

  If you don't have problems before nor after on the root\cimv2 classes, then I would say that the client installation failed to properly register the SCCM WMI classes and that the problem is in the client installation.

  If you don't have problems before but have problems after on the same root\cimv2 classes, then there's something corrupting your WMI during the time that the client is installing.

  To do a wbemtest on the workstations do the following:

  To do this, run an elevated "wbemtest.exe" on the affected machine
  Click on ConnectUnder namespace, ensure you have "root\cimv2" and click on Connect.
  This should take you back to the previous screen. Click on Enum Classes and OK on the Superclass Info window
  On the new window that appears, locate and double click Win32_USBDevice.
  Finally, on the new window that appears, click on instances.

  If you can do all of the steps above without any errors then the root\cimv2 namespace is fine and you probably do not need to rebuild the WMI repository.

  Post the results of those tests here and we'll take it from there.

  • 已建议为答案 Sabrina ShenModerator 2012年6月11日 8:05
  • 已标记为答案 Moiz Rassiwala[MSFT]Microsoft Employee, Moderator 2012年6月11日 16:31
  •  
  • 回复
  • 引用

   
• 2012年6月8日 14:42

   

   
  

  0

  
  Just try to isolate the issue by resolving the problem on one machine in your environment. Just check the below steps if want to give a try.

  Repair WMI, if no use

  Change the SMSGUID and see, if no use

  Repair SCCM Client and see if this helps.

  • 回复
  • 引用