Chat now with support
Chat mit Support

Quadrotech PST Flight Deck 8.1 - Deployment Guide

Options

Although only a single property needs to be passed to the PST Flight Deck Migration Agent for a successful installation, there are many options available when installing from a command line.

Property

Required

Description

WEBSERVICESERVERNAME

Yes

The server where PST Flight Deck IIS instance is hosted. Typically, the Core server is the desired target. DNS alias is preferred for this value.

REGISTERFILESCANNER

No

Inform Migration Agent install if PST Flight Deck Discovery Agent is to be started at user logon. To disable the file scanning set this property to “0”.

USE_HTTPS

No

For use when agents are required to communicate to PST Flight Deck using HTTPS. Specify “1” to enable this feature.

WEBSERVICEAPPNAME

No

Used to specify an alternate IIS hosted web application location other than the default one. Specify the name of the desired web application to enable this feature.

Examples

There are a number of configuration scenarios under which you may use a CLI in the deployment of a PST Flight Deck migration agent. The following examples utilize the MSIEXEC command and its switches to install and suppress any visibility of the installation (/q /i). For more information on options available to the MSIEXEC command, please refer to the Microsoft MSDN article on MSIEXEC.

Below are some common examples of CLI syntax using “xNN” to represent the architecture of the Migration Agent being installed, “PST Flight DeckAlias.somedomain.local” to represent the alias of the server where the PST Flight Deck IIS instance is hosted, and “X:\Path\To\” representing a path valid to the workstation where the installation is occurring.

The following example shows a standard installation of the Migration Agent. Typically, the Core server is the desired target of the WEBSERVICESERVERNAME and a DNS alias is preferred for this value.

msiexec /q /i “X:\Path\To\MigrationAgent_xNN.msi” WEBSERVICESERVERNAME=PST Flight DeckAlias.somedomain.local

 

The next example shows how to specify communication to be performed over the HTTPS protocol:

msiexec /q /i “X:\Path\To\MigrationAgent_xNN.msi” WEBSERVICESERVERNAME=PST Flight DeckAlias.somedomain.local USE_HTTPS=1

 

This final example shows a basic and typical installation which produces logging for troubleshooting:

msiexec /q /i “X:\Path\To\MigrationAgent_xNN.msi” WEBSERVICESERVERNAME=PST Flight DeckAlias.somedomain.local /l*x “X:\Path\To\InstallLog.txt”

 

Once the installation has completed you will see the Migration Agent represented amongst the installed applications on the workstation. The Migration Agent will not be functional until the next successful user logon to that workstation. For the Migration Agent to be immediately functional, you may wish to force a reboot as part of the installation process.

Next Steps

Once the first Migration Agent has been installed and a user has logged back in successfully, no user interaction is required to begin the discovery process. It is recommended to go through some initial testing  to confirm the Migration Agent is working as expected. The installer should validate the installation and configuration settings of the Migration Agent prior to executing future deployments. This testing will typically culminate in a successful end to end test to confirm full system functionality.

Application Streaming Wrapper

The PST Flight Deck Application Streaming Wrapper (ASW) is designed for environments that utilize virtual application streaming to provide Outlook to users. Due to the way application streaming is performed, a typical agent approach cannot be used. The system requirements of ASW are minor and typically covered by the requirements of the streaming solution and the Outlook application being streamed.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen