Previous Topic

Next Topic

Deploying a PSP using Windows PSP deployment scenario 2

To deploy a PSP stored in a centralized, network-based software repository from a command line prompt on a single-target system:

  1. Be sure that all minimum requirements are fulfilled as listed in "Minimum requirements for Microsoft Windows version 7.80 or earlier."
  2. Be sure that the software repository can be accessed by the administrative system.
  3. Map a drive letter to the network-based software repository that contains the PSP files.
  4. Preconfigure components using the RDU (SETUP.EXE). For more information, refer to "Component preconfiguration."
  5. Launch a command line prompt on the administrative system, and change to the subdirectory containing the Remote Deployment Console Utility.
  6. Launch the Remote Deployment Console Utility. For more information, refer to "Remote Deployment Console Utility for Microsoft Windows."

    NOTE: Command line help for the Remote Deployment Console Utility is accessible by running the SETUPC.EXE file from the command line. A screen displays all possible parameters that the utility accepts.

  7. Deploy the specified PSP file on the target system by pressing the Enter key.

When the utility deploys a PSP or individual components to the target system, each component writes installation information to the file CPQSETUP.LOG on the target system.

Be sure that the target system is accessible over the network connection and that all files that make up a PSP are present in the same directory. If the target system is not accessible over the network connection, one of the following error messages might appear:

If installation errors occur, the command line window might display an error message followed by a list of components and the errors that occurred.

IMPORTANT: You can stop a command line deployment on a local server at any time by pressing the Ctrl+C keys.

When the deployment process ends, control is returned to the command line prompt to run the Remote Deployment Console Utility on the next target server that must be deployed.

TIP: You can view the centralized installation log file on the remote target system by connecting to the remote target system over the network with Windows® Explorer and opening the CPQSETUP.LOG file. You can also view the file in a command prompt window on the administrative system by using the TYPE or MORE commands, followed by the network path and name of the remote installation log file.