Users Guide
Table Of Contents
- Introduction
- Setup and Administration
- Security Management
- Assigning User Privileges
- Disabling Guest and Anonymous Accounts in Supported Windows Operating Systems
- Configuring the SNMP Agent
- Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems
- Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux
- Configuring the SNMP Agent on Systems Running Supported SUSE Linux Enterprise Server
- Configuring the SNMP Agent on Systems Running Supported VMware ESX 4.X Operating Systems to Proxy VMware MIBs
- Configuring the SNMP Agent on Systems Running Supported VMware ESXi 4.X Operating Systems
- Firewall Configuration on Systems Running Supported Red Hat Enterprise Linux Operating Systems and SUSE Linux Enterprise Server
- Using Server Administrator
- Server Administrator Services
- Working With Remote Access Controller
- Overview
- Viewing Basic Information
- Configuring the Remote Access Device to use a LAN Connection
- Configuring the Remote Access Device to use a Serial Port Connection
- Configuring the Remote Access Device to use a Serial Over LAN Connection
- Additional Configuration for iDRAC
- Configuring Remote Access Device Users
- Setting Platform Event Filter Alerts
- Server Administrator Logs
- Setting Alert Actions
- Setting Alert Actions for Systems Running Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems
- Setting Alert Actions in Microsoft Windows Server 2003 and Windows Server 2008
- Setting Alert Action Execute Application in Windows Server 2008
- BMC/iDRAC Platform Events Filter Alert Messages
- Understanding Service Names
- Troubleshooting
- Frequently Asked Questions
- Index

24 Setup and Administration
• Server Administrator uses the default operating system user privilege, if a
user is degraded in the
omarolemap
file.
• Do not use the loop back address for
<Host_Name>
, for example:
localhost or 127.0.0.1.
• After the connection services are restarted and the changes do not take
effect for the
omarolemap
file, see the command log for the errors.
•When
omarolemap
file is copied from one machine to another machine,
file permissions and the entries of the file needs to be rechecked.
•Prefix the
Group Name
with
+
.
• Server Administrator uses the default operating system user privileges,
if there are duplicate entries of user names or user groups along
with same
<Host_Name>
.
• You can also use
Space
as a delimiter for columns instead of
[Tab].
Creating Server Administrator Users for VMware ESX 4.X and ESXi 4.X
To add a user to the Users table:
1
Log in to the host using the vSphere Client.
2
Click the
Users & Groups
tab and click
Users
.
3
Right-click anywhere in the Users table and click
Add
to open the
Add
New User
dialog box.
4
Enter a login, a user name, a numeric user ID (UID), and a password;
specifying the user name and UID are optional. If you do not specify the
UID, the vSphere Client assigns the next available UID.
5
To allow a user to access the ESX/ESXi host through a command shell,
select
Grant shell access to this user
. Users that access the host only
through the vSphere Client do not need shell access.
6
To add the user to a group, select the group name from the
Group
drop-
down menu and click
Add
.
7
Click
OK
.
book.book Page 24 Tuesday, July 6, 2010 12:01 PM