Endpoint Encryption

Hi All,

I'm trying to install the PGP Command Line 10.1.0.52 (Win32) on Windows 2003 Ent. SP2 32bit, but it doesn't prompt at all for install dir. It justs installs on C: drive.

But I need to install it on Cluster (with 2 nodes) so I need to install it on drive D: or E: which is clustered resource.

I tried to run PGPCommandLine-10.1.0.52--Win32.msi /help but no option is given to select other drive. See below.

______________________________________________________________________

Windows ® Installer. V 3.01.4000.3959

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
    </package | /i> <Product.msi>
        Installs or configures a product
    /a <Product.msi>
        Administrative install - Installs a product on the network
    /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
        Advertises a product - m to all users, u to current user
    </uninstall | /x> <Product.msi | ProductCode>
        Uninstalls the product
Display Options
    /quiet
        Quiet mode, no user interaction
    /passive
        Unattended mode - progress bar only
    /q[n|b|r|f]
        Sets user interface level
        n - No UI
        b - Basic UI
        r - Reduced UI
        f - Full UI (default)
    /help
        Help information
Restart Options
    /norestart
        Do not restart after the installation is complete
    /promptrestart
        Prompts the user for restart if necessary
    /forcerestart
        Always restart the computer after installation
Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
        i - Status messages
        w - Nonfatal warnings
        e - All error messages
        a - Start up of actions
        r - Action-specific records
        u - User requests
        c - Initial UI parameters
        m - Out-of-memory or fatal exit information
        o - Out-of-disk-space messages
        p - Terminal properties
        v - Verbose output
        x - Extra debugging information
        + - Append to existing log file
        ! - Flush each line to the log
        * - Log all information, except for v and x options
    /log <LogFile>
        Equivalent of /l* <LogFile>
Update Options
    /update <Update1.msp>[;Update2.msp]
        Applies update(s)
    /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
        Remove update(s) for a product
Repair Options
    /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
        Repairs a product
        p - only if file is missing
        o - if file is missing or an older version is installed (default)
        e - if file is missing or an equal or older version is installed
        d - if file is missing or a different version is installed
        c - if file is missing or checksum does not match the calculated value
        a - forces all files to be reinstalled
        u - all required user-specific registry entries (default)
        m - all required computer-specific registry entries (default)
        s - all existing shortcuts (default)
        v - runs from source and recaches local package
Setting Public Properties
    [PROPERTY=PropertyValue]

______________________________________________________________________

The old version 9.8 actually promts for install dir.

The install document also doesn't tell how to do this...

Why this has changed in newer version?

Do you know how to install it on other drive than C:?

Constantin,

Thanks
 

This is a known limitation with PGP Command Line installation on Windows.

In the bugzilla entry for this issue, the following possible workarounds are noted, though I could not tell you how well they actually work:

2.  Our product will install onto the system drive.

Thanks David for suggestions.

Just opened with ORCA the MSI and in the Properties section there is no explicit reference to C: drive.

Please could you advise what variable should be changed instead to point it to other drive?

Hm, perhaps that information is not applicable to newer installation packages.  I'm sorry about that.  That actually makes sense given the other comment in the incident, that we install on the system drive.