Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
removing sms 3
- Thread starter chud
- Start date
In the %windir%\ms\sms\core\bin\00000409 directory on each client is a program named Smsman.exe that can be run to remove the client components. It takes around 5 minutes to clear out the components. <p>Tom Thaden<br><a href=mailto:thadents@usano.ksc.nasa.gov>thadents@usano.ksc.nasa.gov</a><br><a href= > </a><br>
-
2
- #3
Removing the clients can be done by running the 20clicln.bat which is on the BackOffice resource kit and I think on the SMS distribution CD. This is supposed to do a better job than running smsman to remove (although I'm not sure what, if any additonal steps it does). <br>
<br>
The real trick is to get get it off your Domain controllers, especially if you ever want to reinstall. I put the trial in a few months ago and turned it off. I deleted the clients but did not do anything to my DCs. I now decided to install the full product. I had some real difficulties getting things to go in correctly. At the least you should delete the SMSLOGON share and directory from all of your DCs. Use the NT resource kit utility to delete the various SMS services that have been installed on the DCs. I have seen some references in newsgroups to removing Registry settings but I didn't bother with those. Once I did this, I was able to successfully reinstall SMS 2.0 with Service PK1 and everything is going well
<br>
The real trick is to get get it off your Domain controllers, especially if you ever want to reinstall. I put the trial in a few months ago and turned it off. I deleted the clients but did not do anything to my DCs. I now decided to install the full product. I had some real difficulties getting things to go in correctly. At the least you should delete the SMSLOGON share and directory from all of your DCs. Use the NT resource kit utility to delete the various SMS services that have been installed on the DCs. I have seen some references in newsgroups to removing Registry settings but I didn't bother with those. Once I did this, I was able to successfully reinstall SMS 2.0 with Service PK1 and everything is going well
-
1
- #4
Windows NT:<br>
<br>
1. Use Regedit.exe to add the string value "SMS Client Deinstall" to the client<br>
registry under the following key and set it to TRUE:<br>
<br>
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Client\Configuration\Client Properties<br>
<br>
2. Stop and start the SMS Client Service to start a CCIM maintenance cycle.<br>
<br>
or delete all you site boudaries: you clients will be deinstall
<br>
1. Use Regedit.exe to add the string value "SMS Client Deinstall" to the client<br>
registry under the following key and set it to TRUE:<br>
<br>
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Client\Configuration\Client Properties<br>
<br>
2. Stop and start the SMS Client Service to start a CCIM maintenance cycle.<br>
<br>
or delete all you site boudaries: you clients will be deinstall
- Status
Similar threads
- Locked
- Question
- Locked
- Question