cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
abarker5
Engaged Sweeper II
The current options for supplying credentials when deploying scripts or software are limited. We have users that need to be able to deploy to computers, but not servers. We need a way to limit the ability to deploy to just computers. This could be done by having the option to prompt for credentials when running a deployment task. Or maybe have the option to specify what credentials particular user groups have to run deployment tasks as.

For example, if a user is in Active Directory group "A", their deployment account is "DOMAIN\InstallA". If another user is in Active Directory group "B", then their deployment account is "DOMAIN\InstallB". One group would have rights to install on computers, and the other on servers.

However it is done, we need to be able to separate computer admins with server admins and prevent computer admins from deploying to servers.
1 REPLY 1
Susan_A
Lansweeper Alumni
Not just for deployment purposes, we do plan on adding a feature that will allow you to restrict specific users' access to specific assets. We don't have a release date for this though.