RE: WMI Repository Rebuild on Site Server



I would try everything else first before *calling Microsoft* and asking the
right way to fix the problem.

If you are hesitant to open up call, what are your "issues with HINV" on
this box? Maybe we can help you fix that without doing anything drastic,
like rebuilding WMI on your site server (and then perhaps needing to rebuild
the server and restore from backup, because messing w/WMI on your site server
sounds like a site killer IMO)
--
Standardize. Simplify. Automate.


"nhsno@xxxxxxxxx" wrote:


I have a site server that is having issues with HINV. I suspect that
WMI is corrupt and the repository needs to be rebuilt. I have done
this on a number or workstations with success but am hesitant to do
this on a SMS Site Server. Any problems rebuilding the repository on
a Site Server?



.



Relevant Pages

  • RE: EVENT ID 4100 problem
    ... containing this fix. ... > the subscriber ... > CoCreateInstanceEx returned HRESULT ... on my site server I'm getting these error ...
    (microsoft.public.sms.admin)
  • Re: Q313450 and Q319733 breaks Microsoft Site Server 3.0 membership authentication (additional info
    ... > After Q313450 installed Membership authentication via LDAP supported by ... > Microsoft Site Server 3.0 doesn't work. ... Membership authentication after installing Q319733. ... boot in Safe Mode to apply the fix. ...
    (NT-Bugtraq)
  • Re: AutoDiscover Site Errors
    ... Using the command line was unsuccessful. ... At this point I am rebuilding the ... I am having problems with the Advanced Client recognizing the new site ... > Do you have any errors in the Mpcontrol.log on the site server? ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client in mixed NT/AD Domain Help
    ... I am having the same problem, but it only started occuring after i ... To fix it, I moved it back to my site server, watched the ...
    (microsoft.public.sms.admin)
  • SMS security update (mssecure.cab)
    ... OK I think I know whats happening, however I am not sure how to fix this ... I look at the mssecure.cab file on the site server and it is the ... but on my clients machines within the vpcache folder it ...
    (microsoft.public.sms.misc)