Prerequisites for Signing and Deploying P6 Professional Using ClickOnce

The staging computer must meet the following prerequisites in order for you to be able to configure ClickOnce:

• It must be running a version of Windows Server that we support. See: P6 EPPM Tested Configurations.
• The latest Java Development Kit (JDK) must be installed. See http://www.oracle.com/technetwork/indexes/downloads/index.html#java for details.
• Windows SDK is required for signing ClickOnce files. See: https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/ and https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/
• The location of the Windows SDK for .NET Framework must exist in the Path environment variable.

In addition, depending on the code signing method you will use, you must obtain either:

• a digital certificate from a certificate authority (for example, VeriSign) for signing the ClickOnce files. The certificate must be in Personal Information Exchange (PFX) format and must include the private key created on your staging computer.
• a hardware token from a suitable supplier (for example, YubiKey) for signing ClickOnce files. The hardware token must be connected to the staging computer.

System administrators should also update the following prerequisites on all client computers before upgrading or installing P6 Professional:

• Windows Operating System
• .NET Framework

If you do not have the required version of .NET, the ClickOnce installation will fail and you should contact your system administrator.

Tip:

You must ensure all client computers have .NET 4.6.2 installed. If .NET 4.6.2 is not installed on your client machines, the update will fail. System administrators should update .NET and other prerequisites on all client computers before upgrading or installing P6 Professional.