On a Windows machine
(Windows 2000, Windows XP, Windows 2003
Server), the Optim™ Server can
be run as a process or a service.
When it is run as a process, the Server
uses the credentials of the current user ID. When it is run as a service
and an explicit user ID is used, the Server requires the user ID to
have the following privileges:
- Act as part of the operating system
- Bypass transverse checking
- Increase quotas
- Log on as a batch job
- Replace a process level token.
Local Security Policy
You must access the Local Security Policy to grant these
privileges to the user. You can access the Local Security Policy as
follows.
Note: You must be logged on to the Windows machine with a user ID that has administrator
rights.
- From the Control Panel, access the Local Security
Policy applet:
- From the Local Security Policy window, select the
menu entry:
- On the User Rights Policy window, select the following
entry in the left pane:
- Repeat the following steps for each of the five
privileges listed above.
- Select a privilege from the right pane of the Local
Security Settings window.
- If the user (or group) is not already listed in
the Assign To list box, select Add to
add the user (or group) to the list.
- Ensure that the Local Policy Setting check
box is checked for the user (or group).
- Select OK to apply the changes
and close the Local Security Policy Setting window.
UNIX Server
For UNIX, Super-User
Server credentials are required to change the effective user ID and
group ID. During startup, if the filelogon parameter is set to client
or server, the effective user ID that started the daemon must be a
Super-User (zero).