Users that reserve systems using Reservation Manager must know the user name and password to access the reserved systems. By default, Reservation Manager includes the user name and password in the reservation notification email. Reservation Manager must determine what user name and password to include in this email.
Reservation Manager also must know the user name and password to deploy software to systems. The administrator account name used to deploy software is a privileged user that is 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 system environment (for example, Windows). This single account name is used when accessing a newly imaged system to deploy software. For any operating system environment, if 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 system environment. Alternatively, do not allow your end users to install software when choosing that system image.
The following sections describe how Reservation Manager determines the valid credentials.
|
Copyright © 2014 CA.
All rights reserved.
|
|