Initial ProLiant Support Pack Install

[Gordon Leonard]

Initial ProLiant Support Pack Install -- CMS Windows version

1. Confirm that SSH has been installed correctly by running a remote process against CMS. MX errors will occur if not configure/installed correctly. Reinstall SSH and ensure you take the extra step required on Windows 2003 (contained in a separate document).

For example execute:
Tools-->Command Line Tools-->Windows-->Dir

Make sure you select the CMS server.

2. Confirm the Version Control Repository is running by going directly into the agents and selecting Version Control Repository Manager.

3. When creating the task either log into the CMS with the account that was use to install SIM or create the task then go back and edit the job. When creating the job you will not be presented with the option of "Owner of Task" under the Schedule option. Go back and Edit the job, under the scheduling section you will now see "Owner of Task". Change the owner to the account for which SIM was initially installed. Failure to do so will generate an MX error.

4. DO NOT SELECT RUN JOB NOW - It will fail. Schedule the job to run in the future (remember to use the CMS clock not you local PC).

Part of the task build process will copy from the repository into the "PSP Install" directory. If you examine the directory you will see one or more uniquely named directories. These are created each time "Install Software and Firmware" or "Initial ProLiant Support Pack Install" task is created. If you delete the task from CMS it will leave the directory and all its contents - thus wasting space..

On task execution:

installPSP.bat > Acmdxxxx.bat > runsetupc.bat

"installPSP.bat" will launch to create a "Acmdxxxxx.bat" (the Acmd would actually be unique Acmd12563.bat for example). "installPSP.bat" uses the root "temp" directory to build the Acmd batch file. Upon completion the final Acmd batch is stored in the SIM "data" directory. After "installPSP.bat" completes its process it will not delete any files it created in the Temp directory. Files in the Temp directory will waste space and leave the login name and password exposed (part of the task creation the user must provide; log in name, password, and domain).

Acmdxxxxx.bat will now run. It sets the MX variables then passes setupc variables to a batch called "runsetupc.bat". Upon completion of Acmd it will remain in the "data" directory even if you delete the task from CMS. The "Acmd" batch leaves the user login name and password exposed (contained within the batch file).

Note: If deploying across dissimilar domains use a local account residing on each server and set the domain to "localhost". If you leave the domain blank as part of the task creation process it will fail to actually to deploy.