To control the actions a user can perform in the up.time interface, define a User Role that sets the appropriate permissions and then assign that Role to an existing User:
|
WMI User Permissions | Rating | Views | |
---|---|---|---|
If there are security concerns related to the privileges granted to the up.time application, a user account with simple read-access to the performance counters should be sufficient to enable WMI... By: uptime Support | Date Created: 1-13-2012 | Last Modified: 4-6-2012 | Index: 573 |
4389 |
Changing Linux Agent port or permissions | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 10-14-2005 | Last Modified: 7-24-2013 | Index: 011 |
6806 |
Common User Agent Strings | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 6-26-2007 | Last Modified: 6-28-2011 | Index: 203 |
5306 |
Linux Agent filesystem permissions | Rating | Views | |
---|---|---|---|
Listed below are the set of post-install chmod and chown commands used to set permissions on the agent's installed files. chmod -R u+rx /opt/uptime-agent/bin chmod go+rx /opt/uptime-agent chmod... By: uptime Support | Date Created: 7-7-2011 | Last Modified: 8-11-2011 | Index: 536 |
2648 |
What permissions does up.time require for ESX monitoring? | Rating | Views | |
---|---|---|---|
We recommend using the root account for ESX 3 monitoring. If the root account is not available you can add a user for up.time using the instructions below.1. SSH login to the ESX system as root2. C... By: uptime Support | Date Created: 7-7-2008 | Last Modified: 8-12-2011 | Index: 309 |
3262 |