Review the options for installation and learn about different methods for installing Cisco Jabber for Windows. Understand the requirements for successful deployments before you start the installation procedure.
To create a custom installer, you use a transform file. Transform files contain installation properties that you apply to the installer.
The default transform file lets you specify values for properties when you transform the installer. You should use the default transform file if you are creating one custom installer.
You can optionally create custom transform files. You specify values for properties in a custom transform file and then apply it to the installer.
Create custom transform files if you require more than one custom installer with different property values. For example, create one transform file that sets the default language to French and another transform file that sets the default language to Spanish. You can then apply each transform file to the installation package separately. The result is that you create two installers, one for each language.
Start Microsoft Orca.
Open CiscoJabberSetup.msi and then apply CiscoJabberProperties.mst.
Specify values for the appropriate installer properties.
Generate and save the transform file.
Select Transform > Generate Transform.
Select a location on your file system to save the transform file.
Specify a name for the transform file and select Save.
The transform file you created is saved as file_name.mst. You can apply this transform file to modify the properties of CiscoJabberSetup.msi.
Transform the Installer
Apply a transform file to customize the installer.
Applying transform files does not alter the digital signatures of CiscoJabberSetup.msi.
Start Microsoft Orca.
Open CiscoJabberSetup.msi in Microsoft Orca.
Select File > Open.
Browse to the location of CiscoJabberSetup.msi on your file system.
Select CiscoJabberSetup.msi and then select Open.
The installation package opens in Microsoft Orca. The list of tables for the installer opens in the Tables pane.
Remove all language codes except for 1033 (English).
You must remove all language codes from the custom installer except for 1033 (English).
Microsoft Orca does not retain any language files in custom installers except for the default, which is 1033. If you do not remove all language codes from the custom installer, you cannot run the installer on any operating system where the language is other than English.
Select View > Summary Information.
The Edit Summary Information window displays.
Locate the Languages field.
Delete all language codes except for 1033.
English is set as the language for your custom installer.
Apply a transform file.
Select Transform > Apply Transform.
Browse to the location of the transform file on your file system.
Select the transform file and then select Open.
Select Property from the list of tables in the Tables pane.
The list of properties for CiscoJabberSetup.msi opens in the right panel of the application window.
Specify values for the properties you require.
Values are case sensitive. Ensure the value you enter matches the value in this document.
Drop any properties you do not require.
Right-click the property you want to drop.
Select Drop Row.
Select OK when Microsoft Orca prompts you to continue.
Enable your custom installer to save embedded streams.
Select Tools > Options.
Select the Database tab.
Select Copy embedded streams during 'Save As'.
Select Apply and then OK.
Save your custom installer.
Select File > Save Transformed As.
Select a location on your file system to save the installer.
Specify a name for the installer and then select Save.
Complete the steps in this task to deploy Cisco Jabber for Windows with Group Policy.
Copy the installation package to a software distribution point for deployment.
All computers or users to which you plan to deploy Cisco Jabber for Windows must be able to access the installation package on the distribution point.
Select Start > Run and then enter the following command:
The Group Policy Management console opens.
Create a new group policy object.
Right-click on the appropriate domain in the left pane.
Select Create a GPO in this Domain, and Link it here.
The New GPO window opens.
Enter a name for the group policy object in the Name field.
Leave the default value or select an appropriate option from the Source Starter GPO drop-down list and then select OK.
The new group policy displays in the list of group policies for the domain.
Set the scope of your deployment.
Select the group policy object under the domain in the left pane.
The group policy object displays in the right pane.
Select Add in the Security Filtering section of the Scope tab.
The Select User, Computer, or Group window opens.
Specify the computers and users to which you want to deploy Cisco Jabber for Windows.
Specify the installation package.
Right-click the group policy object in the left pane and then select Edit.
The Group Policy Management Editor opens.
Select Computer Configuration and then select Policies > Software Settings.
Right-click Software Installation and then select New > Package.
Enter the location of the installation package next to File Name; for example, \\server\software_distribution.
You must enter a Uniform Naming Convention (UNC) path as the location of the installation package. If you do not enter a UNC path, Group Policy cannot deploy Cisco Jabber for Windows.
Select the installation package and then select Open.
In the Deploy Software dialog box, select Assigned and then OK.
Group Policy installs Cisco Jabber for Windows on each computer the next time each computer starts.
Cisco Media Services Interface
Cisco Jabber for Windows supports Cisco Media Services Interface version 3.2.2 or later.
Cisco Jabber for Windows does not support Cisco Media Services Interface on Microsoft Windows Vista.
Cisco Media Services Interface provides a Microsoft Windows service that works with Cisco Prime Collaboration Manager and Cisco Medianet-enabled routers to ensure that Cisco Jabber for Windows can send audio media and video media on your network with minimum latency or packet loss.
Before Cisco Jabber for Windows sends audio media or video media, it checks for Cisco Media Services Interface.
If the service exists on the computer, Cisco Jabber for Windows provides flow information to Cisco Media Services Interface.
The service then signals the network so that routers classify the flow and provide priority to the Cisco Jabber for Windows traffic.
If the service does not exist, Cisco Jabber for Windows does not use it and sends audio media and video media as normal.
Cisco Jabber for Windows checks for Cisco Media Services Interface for each audio call or video call.
Prepare Your Network
To install Cisco Media Services Interface for traffic marking, you must prepare your network.
Install Cisco Prime Collaboration Manager.
Install routers or switches enabled for Cisco Medianet where appropriate.
Configure your network to handle the metadata attributes that Cisco Media Services Interface applies to applications.
Not all devices on your network must support Cisco Medianet.
The first hop should prioritize traffic based on the metadata attributes from Cisco Media Services Interface. As the traffic traverses the network, all other devices should also prioritize that traffic unless you configure policies on those devices to handle the traffic differently.
Install Cisco Media Services Interface
Download the Cisco Media Services Interface installation program from the download site on Cisco.com.
Install Cisco Media Services Interface on each computer on which you install Cisco Jabber for Windows.
See the appropriate Cisco Medianet documentation for installing Cisco Media Services Interface.
You can uninstall Cisco Jabber for Windows using either the command line or the Microsoft Windows control panel. This document describes how to uninstall Cisco Jabber for Windows using the command line.
Use the Installer
If the installer is available on the file system, use it to remove Cisco Jabber for Windows.
The command removes Cisco Jabber for Windows from the computer.
Command Line Arguments
Command line arguments are case sensitive. The arguments and values you specify during installation must match the cases in this document.
The following table describes the command line arguments you can use to install Cisco Jabber for Windows:
Defines the type of presence server. Set one of the following values:
Cisco Unified Presence or Cisco Unified Communications IM and Presence
Cisco WebEx Messenger
Specifies the address of your presence server. Set one of the following as the value:
IP address (188.8.131.52)
You must specify a value for this argument if your presence server does not support domain name system service records (DNS SRV). For example, Cisco Unified Presence 8.5.2 does not support DNS SRV.
Identifies the domain name of the presence server. Specify the domain name as the value of this argument; for example, domain.com.
You must specify this argument if the domain of the presence server is not the same as the domain of the workstations on which the client is installed.
You can verify the domain of your presence server as follows:
Do one of the following:
Cisco Unified Presence: Open the Cisco Unified Presence Administration interface.
Cisco Unified Communications IM and Presence: Open the Cisco Unified CM IM and Presence Administration interface.
Select System > Cluster Topology.
Note the domain name as the value of the Domain Name field.
LCID in decimal
Defines the Locale ID (LCID), in decimal, of the language that Cisco Jabber for Windows uses. The value must be an LCID in decimal that corresponds to a supported language.
For example, you can specify one of the following:
1033 specifies English.
1036 specifies French.
This argument is optional. If you do not specify a value, Cisco Jabber for Windows uses the system locale language as the default.
See the Supported Languages topic for a full list of the languages you can specify.
Specifies the URL where users can reset lost or forgotten passwords.
This argument is optional but recommended.
In cloud-based deployments, you can specify a forgot password URL using the Cisco WebEx Administration Tool. However, the client cannot retrieve that forgot password URL until users sign in.
Specifies the domain name for the Cisco WebEx Org that contains the URL for the SSO service.
Cisco Jabber for Windows uses this argument to retrieve the URL of the SSO service from the Org. When Cisco Jabber for Windows gets the SSO service URL, it can request login tokens to authenticate with Cisco WebEx Messenger.
You specify the URL for the SSO service as the value of the Customer SSO Service Login URL in the Cisco WebEx Administration Tool.
This argument is required to use SSO with Cisco WebEx Messenger and applies to cloud-based deployments only.
Specifies a unique name for group configuration files if users have desk phone devices only.
If users have CSF devices, you should specify group configuration files in the Cisco Support Field on the CSF device configuration in Cisco Unified Communications Manager.
You can specify either an unqualified or fully qualified filename as the value. The filename you specify as the value for this argument takes priority over any other configuration file on your TFTP server.
This argument is optional.
The following are the properties you can modify in a custom installer:
These properties correspond to the installation arguments and have the same values.
The following table lists the languages that Cisco Jabber for Windows supports:
Portuguese - Brazil
Portuguese - Portugal
Chinese - China
Chinese - Taiwan
Cisco Jabber for Windows does not support Locale IDs for all sub-languages. For example, if you specify French - Canada, Cisco Jabber for Windows uses French - France.
As of this release, Cisco Jabber for Windows supports the Locale IDs for Chinese - China and Chinese - Taiwan only. Cisco Jabber for Windows does not support any other Locale IDs for Chinese sub-languages. For example, if you specify Chinese - Singapore, Cisco Jabber for Windows uses English.
See the following documentation for more information about Locale IDs:
Microsoft Windows Locale Code Identifier (LCID) Reference