Now, I could be wrong on this but...
SMS Rules set on the SMS site server are applied to the entire site. No exceptions. For example, if you have a site rule that say Client remote control settings are set at server, then all clients in the site will not be able to change thier remote control settings (these are set at the site.)
The above example may cause some problems. Here's another example: Say you want to set your Remote Control options at the site level. You do this because users may have important excel documents open with salary information on them...or something like that...you wouldn't want a help desk person to accidentally see this information. So you create a rule at the site level stating that the end user must give permission in order for remote control to occur (ask for permission.)
Fine this is great. However, because your servers are in the same site, your help desk gets prompted with "waiting for user to give permission" when they try to remote control the server. Uh oh....we have a problem...the servers are locked up. No one is there to give permission...
This is one example.
To work around this, you would have to create more than one site. For instance, one site for your servers and one site for you users. Now you can create two different set of rules based on servers or workstations.
I hope this helps...
(By the way, there is a manual registry hack that will work around this example. You can hack the registry so that your servers do not require the ASK for PERMISSION during remote control sessions. In this way, you can have one site rule. But you will have to take an additional step and perform a registry hack to disable the ask for permission feature.) Joseph L. Poandl
MCSE 2000
