MiVoice Office Application Suite - Technical Manual
Unattended Installations
There are various techniques to enable rapid deployment of Phone Manager or deployment on a large scale:
The choice of deployment method will depend on the customer's infrastructure and experience. Whichever method is chosen the customer will need to use the setup / msi command-line arguments to perform a silent installation and pass the necessary configuration information for a unattended installation.
The Phone Manager installations are MSI based installations that are embedded inside an executable that will ensure the prerequisites are installed correctly.
To roll out Phone Manager using group policy the MSI must first be extracted from the setup executable. To do this the following command-line arguments need to be passed to the executable:
setup_phonemanager_exex64_vX.X.XXXX.X.exe /a /s /v"/qn TARGETDIR=\"C:\Temp\""
The TARGETDIR can be replaced with any location, this will be where the MSI file is extracted to. The executable name in the example above needs to be replaced with the executable version being used.
The extracted MSI is called setup.msi. This process will have to be repeated for both 32bit and 64bit versions if required. Take care to use a different TARGETDIR for the 32bit and 64 bit versions as they will both generate an MSI with the same name, i.e. setup.msi.
The following command-line arguments can be passed to the executable or MSI to customize the installation.
Used to ensure the end-user does not see any part of the installation while it is in progress.
/S /v/qn
Used to specify the location of the Communication Service during the installation. This can be the IP address or hostname.
/VXDISCOVERYSERVER=
The options detailed in the table below are used to specify one of the three extension mapping types:
| Parameter | Description | Usage |
|---|---|---|
| dynamicwithendpoint | Use the extension assigned to the computer, each different user that sits at the computer uses the same extension. If no extension is supplied using a ‘/VXENDPOINT’ parameter, then an extension for the computer is prompted for and saved the first time Phone Manager is run. | User of Agent Hot Desking or general ACD users that move between phones. |
| static | Use the extension assigned to the User on the Communication Service. If no extension has been assigned to a user centrally then they will be prompted and have one assigned the first time they log in. | Users of native Hot Desking or people that sit at the same desk every day. |
| dynamic | Prompts the user for an extension each time Phone Manager starts up. | Users of Terminal Services or thin clients where there is no correlation between the Phone Manager UI and the extension. |
/VXENDPOINTMAP=dynamicwithendpoint
or
/VXENDPOINTMAP=static
or
/VXENDPOINTMAP=dynamic
Used to define the extension number for the computer during installation.
/VXENDPOINT=XXXX
The options detailed in the table below are used to control the various features that can be installed. By default if no features are passed to the installation the features in bold will be installed.
| Feature Name | Description |
|---|---|
| Client | Core Phone Manager Software. |
| Outlook | Phone Manager Outlook plug in Software. |
| Shortcut_Startup | Shortcut for Phone Manager in the start up folder. |
| Shortcut_Desktop | Shortcut for Phone Manager on the desktop. |
| TAPIx64 | Phone Manager TAPI driver for 64bit systems. |
| TAPI | Phone Manager TAPI driver for 32bit systems. |
| URLProtocolsx64 | Sets Phone Manager as the target for “tel://, dial://, callto://, sip://, dialfrompm://” URI’s in the Client PC Registry. When set, any telephone number (formatted with one of the supported URI’s) in a web page will use Phone Manager to dial the number when clicked. |
| URLProtocols | Sets Phone Manager as the target for “tel://, dial://, callto://, sip://, dialfrompm://” URI’s in the Client PC Registry. When set, any telephone number (formatted with one of the supported URI’s) in a web page will use Phone Manager to dial the number when clicked. |
| Plantronics | Support for manufacturer specific headsets. |
| CallRecorderClient | Installs the Call Recorder Client to control muting of recordings |
To Add:
/VADDLOCAL=featurename
Removing Features:
Features cannot be individually removed once installed. To remove features the entire application must be uninstalled.
setup.exe /S /v/qn
setup.exe /S /v/qn /VADDLOCAL=TAPIx64, Plantronics
setup.exe /S /v/qn /VXDISCOVERYSERVER=192.168.100.2
setup.exe /S /v/qn /VXENDPOINTMAP=static /VXDISCOVERYSERVER=192.168.100.2
If using an msi then the /V in front of the parameter is not used (as /V is the command to pass the parameter to the msi from setup.exe) so in the last example if would be:
msiexec /i setup.msi /S /v/qn XENDPOINTMAP=static XDISCOVERYSERVER=192.168.100.2