|
|
|
Users that reserve systems through the Reservation Manager must know the user name and password to access the systems. By default, the Reservation Manager communicates the user name and password in the email that is sent when the systems are ready. Reservation Manager must be able to determine what user name and password to include in this email.
To deploy software to systems being prepared for users, the Reservation Manager also must know the user name and password. The administrator account name used to deploy software is a privileged user, defined to Reservation Manager as the superuser. The superuser account names and passwords can be defined during installation or later using the dpmutil –set –superuser command. A superuser account name must be defined for each operating system. However, only one superuser account name can be defined for a single operating environment (for example, Windows). This single account name is used when accessing a newly imaged system to deploy software. If, for any operating environment, systems are configured with different administrator account names, attempts to deploy software to systems that are not configured with the defined superuser account name known to Reservation Manager will fail. To avoid deployment problems, we recommend that you set up an account to support the account name defined as the superuser for that operating environment. Alternatively, do not allow your end users to install software when choosing that system image.
How the Reservation Manager determines the valid credentials is described in the following sections.
| Copyright © 2013 CA. All rights reserved. |
|