Installing P6 Professional on Terminal Services

To install P6 Professional, the Administrator or an account in the local Administrators group must log in to the Terminal Server.

Prerequisites

Install Oracle or SQL Server Client drivers as appropriate on the Windows Terminal Servers as described in their respective docs.

With Oracle database, confirm the Create Global Objects Windows Security Policy is set up on the Terminal Servers and add the domain Users or Groups of the end-users who will be accessing the published application. If the local security policy is not set up, complete the following steps to add the policy:

1. Click Start, Programs, Administrative Tools, and then click Local Security Policy.
2. Expand Local Policies, and then click User Rights Assignments.
3. In the right pane, double-click Create Global Objects.
4. In the Local Security Policy Setting dialog box, click Add.
5. In the Select Users or Group dialog box, select the user group that these end users are a part of, click Add, and then click OK.
6. Click OK.

With Oracle database, the Oracle client software also requires that you give the Authenticated User Group, Read and Execute privilege to the Oracle Home Directory and ALL its subdirectories and files on the Terminal Servers.

Installation Steps

1. Run the P6 Professional setup.

   Note: Terminal Services automatically runs setup in Terminal Services install mode.

2. Install P6 Professional.
3. When setup completes, click the Finish dialog to the Terminal Services install mode.
4. After configuring database connections as described in the installation documentation, deploy PrmBootStrapV2.xml to the ALLUsers appdata folder from the admin user's appdata folder, so that users who launch P6 for the first time will inherit the PrmBootStrap.xml file with existing database configurations. Change DeploymentVersion in the header of PrmBootStrap.xml file to force a new deployment of PrmBootStrap.xml.

   Note: Force a new deployment of the PrmBootstrapV2.xml file to users who have an existing PrmBootstrapV2.xml by incrementing the deployment version one number higher in the PrmBootstrap.xml, which exists in the ALLUSERS profile. Never change MajorVersion or MinorVersion. If the deployment version is not incremented and a user already has a PrmBootstrap.xml file in their local profile, it will use the existing file rather than deploy a new copy from the ALLUSERS profile. Example incrementing the deployment version from 0 to 1:

   <BootStrap MajorVersion="8" MinorVersion="2" PatchVersion="0" DeploymentVersion="1"

   Default PRMBootStrapV2.xml location:

   \%ALLUSERSPROFILE%\Oracle\Primavera P6\P6 Professional

5. Test the application by logging up to two users into the Terminal Server. If errors occur, contact Oracle Support for assistance.

   Note: The Citrix Administrator Application can also publish the application through Citrix.

See Also

Windows Terminal Services and Citrix

Pre-Installation Considerations

Setting PM.ini to Terminate a Current Session