General discussion

Locked

SMS 2.0 Questions

By bbuechler ·
1) When you configure Network Discovery, and it discovers all network resources, why does it install the client on all workstations automatically? Also- Once that has been done, is there any way to "shut them off"?

Meaning: We installed SMS on a server in order to test and evaluate it so that our admins could get a handle on its use etc. During the process of installing and discovering our network, SMS installed its client on all of our networked workstations.

We want to be able to reboot the server and reinstall SMS so that we can use it in a live environment, but now that the clients are talking to the server, we don't want to create a widespread problem of users calling the helpdesk due to system error messages.

Can someone please explain our options for the above scenario, as everyone at our facility is still learning the product.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

SMS 2.0 Questions

by -Q-240248 In reply to SMS 2.0 Questions

SMS is a beast, and I don't know if you'll find an expert here on it. Takes a lot of planning and preparation and resources. I do know that if you 'inventory' your network, then those PCs must become part of the SMS Domain inventory and hence must have the client software. Perhaps if you remove the workstation from inventory, the software will go with it...

Collapse -

SMS 2.0 Questions

by bbuechler In reply to SMS 2.0 Questions

Poster rated this answer

Collapse -

SMS 2.0 Questions

by Kevin Brown In reply to SMS 2.0 Questions

There is a utility on the Back Office resource kit that will clean the SMS client off the PC. it will be under the SMS\cleancli directory.

Hope this helps

Collapse -

SMS 2.0 Questions

by bbuechler In reply to SMS 2.0 Questions

Poster rated this answer

Collapse -

SMS 2.0 Questions

by McKayTech In reply to SMS 2.0 Questions

I work for a government agency right up the street from you in Phoenix and we have, over the past six months, rolled out SMS to about 1300 users.

You can only shut off the clients by running the clean client utility - it was deliberately made difficult to remove and it's just not practical any other way. It installs the client automatically by design - it is, after all, a program for discovering all your resources.

In regard to your options, I don't see a problem with re-installing SMS.In doing so, it will re-discover all the machines and add them to the new database and since it is a server-driven process, I don't see why there would be a lot of error messages at the desktop.

I would be glad to communicate with you off-the-forum and share whatever information I can from our experience with SMS. One thought I did have is that if you can accomplish the re-install during a low utilization period and use a few power users as the first to log on, any error messages they see can be summarized in a global e-mail so people know not to panic if they see similar messages and that should minimize the Help Desk impact.

paul

Collapse -

SMS 2.0 Questions

by bbuechler In reply to SMS 2.0 Questions

Poster rated this answer

Collapse -

SMS 2.0 Questions

by bbuechler In reply to SMS 2.0 Questions

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums