SMS 2.0 /Uninstall help

[microkluge]

In short: I need a way to completely remove all traces of SMS 2.0 from a W2K AD domain...below is a fuller explanation.

Hi,
We have a W2k AD domain. A primary site was established under a time-limited install. It worked. It was then decided that un-installing the "test" site and re-installing with the freshly bought version needed to happen. That is where the kluge started. I have determined that the original primary site never "un-installed" itself fully. Now security logs are full of invalid login attempts from the old primary site sms accounts/clients. That all being said, what I need and cannot find are the tools necessary to safely remove ALL traces of SMS from the DC and AD.
I have tried to utilize the Resource disk tools on test client boxes for client-agent removal. Manual at-the-box cleanings seem to work but trying to utilize login scripts for client removal doesn't...unless the user has local Admin privelege...not acceptable. So, any advice would be welcome and much appreciated. Thanks,
Microkluge

 

[PeterPeq]

I have been searching for documentation as well, on how to completely remove SMS 2.0 from NT - AD mixed mode environment. I managed to remove a secondary site, without any issues, but please shed some light if you have any ideas. Thanks.

 

[microkluge]

Wish I could add something additional. None of the 3 books I have on SMS address sanitizing the servers. I guess the moral of this story is that you set it up right the first time, leave it alone and pray it never needs to be removed.

 

[tbrennans]

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/deploy/spgsms03/spsms06.mspx

 

[microkluge]

Thanks a bunch for the link. Think I had seen this one before but since it looked geared towards NT I was still looking. There are far more SMS registry entries still hanging around than this KB would indicate. I used a scalpel and not an axe so I erred on the side of caution. Upon reboot I got this error message in my System log

Component: OS Information Agent
Error: The Agent could not access WMI.
Cause: The WMI support may have not been started or installed. Restart or Install WMI service and restart the agents.

Any ideas?