Hello All, There is very famous script to repair WMI. Can anyone share it so that I can repair my WMI and instlal clients. Thanks.

Renaming WMI is not a best think to do. I would suggest to keep this as last option. 1. Use WMIDIAG tool to identify the problem. 2. Try to repair it and If it's hapening again and again then find out the reason. 3. If no other option left then goahead with the rename/deletion of the repositiry. If the WMI correction is pretty regular in your environment then I would suggest you to check the antivirus software scanning on repository is not causing the issue.Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

@Jason: The client center does not allow does not connect to the client so one cannot repair the WMI through that? or can we? @Anoop: Running WMIDIAG on scores of machines is very tedious. Are you referring to c:\windows\system32\wbem directory to be excluded from antivirus?

@Jason: The client center does not allow does not connect to the client so one cannot repair the WMI through that? or can we? WMI can also be repaired on remote machines using client center.Torsten Meringer | http://www.mssccmfaq.de

Thanks for the reply Torsten, but WMI Repair option does not highlight until SCCM Client Center is connected to the client. And since it cannot connect to the client due to WMI Error, I cannot repair the WMI for the client. And if I connecting wrongly do suggest.

I use normally use's...CHRISTJAN'S CAT tool http://blog.itminutes.net/?p=515 This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the reply Paddy. I have that in place, but at the end, it fails to repair. I do not know why, have used it before as well, but this time, it is failing to repair WMI. I do not know why.

Howmany systems you have with this situation ? If above all failed to repair the WMI.. only option is to Rebuild the system. if you don't agree then you might need to contact the Ms Support to resolve that issue. I am sure ..that above all mentioned steps would resolve your issues... before opting the support make sure that you have done these below .. http://myitforum.com/cs2/blogs/socal/archive/2007/08/22/troubleshooting-wmi-with-wmidiag.aspx http://windowsxp.mvps.org/repairwmi.htm This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Well, it all with client nto being installed on those machines. When I looked into ccm.log, it showed WMI connection error. Port 135 is accessable on client so it is not a firewall issue. The SCCM Client Center does not connect to the client so that repair can be done. The CAT does not fix it too. :(

Clients are on the WAN so any port that I might be missing?

what os does the client have?AMIM MUHAMMAD KHAN | CTTCNET USER GROUP LEAD | EVENT SPEAKER, MCT, MCTS, MCITP-ENTERPRISE, MCSA http://amimkhan.wordpress.com

XP AND 7.

Jason Sandys has a ConfigMgr client health startup script that I'd recommend checking out: http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx Cheers, TrevorIf this post was helpful, please click the little "Vote as Helpful" button :) Trevor Sullivan http://trevorsullivan.net

Thanks for the reply. How would it help my cause. The client is not installed on the clients. Please advise.

What you can do is try a windows repair on one of the machines and see if it helps solves your problem if it does then we can furthur investigate. Regards, Amim Muhammad KhanAMIM MUHAMMAD KHAN | CTTCNET USER GROUP LEAD | EVENT SPEAKER, MCT, MCTS, MCITP-ENTERPRISE, MCSA http://amimkhan.wordpress.com

That is not fun mate. There are scores of machines and besides there is nothing wrong with the operating system, sometimes WMI gets corrupted so was just looking for the WMI Repair script.

I think, the first should be your clients and environment should be updated with the hotfixes available to fix the WMI errors? Have you tried to install them? Go through the below blog post and see this is applicable to you or not. Suggested hotfixes for WMI related issue on Windows platforms Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Dear blogpost missing?

It was hyperlinked, viewing....

Most of them are covered dear. I am really tempted now to test the script? Any suggestions?

Yes: test, test, test before deploying it into production.Torsten Meringer | http://www.mssccmfaq.de

Im my experience, even if connecting using SCCM Client Center fails due to WMI etc, in most cases you can still use it to repair WMI. Make sure the account you use in SCCM Client Center has admin rights on the PC. Click on the folder icon beside "Repair WMI" button. If "admin$\Temp" opens on the Client you are trying to fix... then "Repair WMI" should work.

I can say that 9 times out of the 10 I have to do the wmi rename and repair option. The xp clients even after using a migration tool seem to have some real issues after a while. However, the clients before could have had issues as well but most of the time I end up spending time on these machines fixing ccm and fixing the wmi. I have a collection that will do the resinstall and working on a batch for the WMI as well. It seems though that it always comes back to the machines having configuration problems with the NIC cards, updated drivers and such. Also see lots of problems with the secedit file getting corrupt, after the fix which is adding a couple of reg entries in the batch and deleting the secedit, (which microsoft told us not to) but it fixes the issues that we were having as well. Again 9 times out of the 10 it seems to be related to ADMT migrations that we have done. I would not want to do that again and use that tool, image the machines and start fresh.Patrick Clark

Thats not entirely true about deleting the WMI, it does not say NEVER delete. There are some cases where this has to happen with corruption and such.. Don't delete the repository (though it may make problems seem to go away). Rebuilding the WMI repository is a destructive operation that can lead to data loss, applications breaking, and a whole host of slow to appear, difficult to diagnose problems. Generally speaking, the only time this operation should ~really~ be necessary is in the case of true corruption as indicated by tools such as WMIDiag or Winmgmt /verifyrepository. Can lost WMI data be recovered? Probably, but that's never a good state to be in. Therefore, I say avoid this operation whenever possible. On the flip side, I certainly recognize there is a tradeoff between operational needs and individual investigations. Over time some customers have seen that rebuilding the repository makes a problem seem to go away quickly. Typically this also comes with a loss of ability to find root cause, could mask other problems, and may not actually solve anything long term. On the whole I strongly recommend against deleting the repository folder as a means to resolving WMI issues. Patrick Clark