Install the Clients

Install Cisco Jabber for Windows

Cisco Jabber for Windows provides an MSI installation package that you can use in the following ways:

Install Option

Description

Use the Command Line

You can specify arguments in a command line window to set installation properties.

Choose this option if you plan to install multiple instances.

Run the MSI Manually

Run the MSI manually on the file system of the client workstation and then specify connection properties when you start the client.

Choose this option if you plan to install a single instance for testing or evaluation purposes.

Create a Custom Installer

Open the default installation package, specify the required installation properties, and then save a custom installation package.

Choose this option if you plan to distribute an installation package with the same installation properties.

Deploy with Group Policy

Install the client on multiple computers in the same domain.

Before you begin

You must be logged in with local administrative rights.

Administrative Rights

You must be logged in with local administrative rights to complete installation of Cisco Jabber for Windows.

Add Local Contacts from Microsoft Outlook

Cisco Jabber for Windows lets users search for and add local contacts in Microsoft Outlook. To enable this integration with Microsoft Outlook, you must enable Cached Exchange Mode on the Microsoft Exchange server.

To search for local contacts in Microsoft Outlook with the client, users must have profiles set in Microsoft Outlook. In addition, users must do the following:

  1. Select File > Options.

  2. Select the Integration tab (Calendar tab from release 11.0).

  3. Select either None or Microsoft Outlook.

To add local Microsoft Outlook contacts to contact lists in the client, local contacts must have instant message addresses in Microsoft Outlook.

To show contact photos in the client interface, local contacts in Microsoft Outlook must have instant message addresses.

To communicate with local contacts in Microsoft Outlook using the client, local contacts must have the relevant details. To send instant messages to contacts, local contacts must have an instant message address. To call contacts in Microsoft Outlook, local contacts must have phone numbers.

Microsoft Outlook Calendar Events

Applies to: Cisco Jabber for Windows

You must apply a setting in Microsoft Outlook so that calendar events display in Cisco Jabber for Windows.

Procedure

Step 1

Open the email account settings in Microsoft Outlook, as in the following example:

  1. Select File > Account Settings.

  2. Select the Email tab on the Account Settings window.

Step 2

Double-click the server name.

In most cases, the server name is Microsoft Exchange.

Step 3

Select the Use Cached Exchange Mode checkbox.

Step 4

Apply the setting and then restart Microsoft Outlook.

When users create calendar events in Microsoft Outlook, those events display in the Meetings tab.

Microsoft Outlook Presence Integration

Applies to: Cisco Jabber for Windows

To enable integration with Microsoft Outlook, you must specify SIP:user@cupdomain as the value of the proxyAddresses attribute in Microsoft Active Directory. Users can then share availability in Microsoft Outlook.

Use one of the following methods to modify the proxyAddresses attribute:

  • An Active Directory administrative tool such as Active Directory User and Computers

    The Active Directory User and Computers administrative tool allows you to edit attributes on Microsoft Windows Server 2008 or later.

  • ADSchemaWizard.exe utility

    The ADSchemaWizard.exe utility is available in the Cisco Jabber administration package. This utility generates an LDIF file that modifies your directory to add the proxyAddresses attribute to each user with the following value: SIP:user@cupdomain.

    You should use the ADSchemaWizard.exe utility on servers that do not support the edit attribute feature in the Active Directory User and Computers administrative tool. You can use a tool such as ADSI Edit to verify the changes that you apply with the ADSchemaWizard.exe utility.

    The ADSchemaWizard.exe utility requires Microsoft .NET Framework version 3.5 or later.

  • Create a script with Microsoft Windows PowerShell

    Refer to the appropriate Microsoft documentation for creating a script to enable presence in Microsoft Outlook.

Enable Presence with the Active Directory User and Computers Tool

Complete the following steps to enable presence in Microsoft Outlook for individual users with the Active Directory User and Computers administrative tool:

Procedure
Step 1

Start the Active Directory User and Computers administrative tool.

You must have administrator permissions to run the Active Directory User and Computers administrative tool.
Step 2

Select View in the menu bar and then select the Advanced Features option from the drop-down list.

Step 3

Navigate to the appropriate user in the Active Directory User and Computers administrative tool.
Step 4

Double click the user to open the Properties dialog box.

Step 5

Select the Attribute Editor tab.

Step 6

Locate and select the proxyAddresses attribute in the Attributes list box.

Step 7

Select Edit to open the Multi-valued String Editor dialog box.

Step 8

In the Value to add text box, specify the following value: SIP:user@cupdomain.

For example, SIP:msmith@cisco.com.

Where the user@cupdomain value is the user's instant messaging address. cupdomain corresponds to the domain for Cisco Unified Presence or Cisco Unified Communications Manager IM and Presence Service.

Methods of Installation

Cisco Jabber for Windows provides an MSI installation package. You must be logged in as an administrator to complete installation. You can use this installation package in the following ways:
Use the Command Line

Specify arguments in a command line window to set installation properties.

Choose this option if you plan to install multiple instances.

Run the MSI Manually

Run the MSI manually on the file system of the client workstation and then specify connection properties when you start the client.

Choose this option if you plan to install a single instance for testing or evaluation purposes.

Create a Custom Installer

Open the default installation package, specify the required installation properties, and then save a custom installation package.

Choose this option if you plan to distribute an installation package with the same installation properties.

Deploy with Group Policy

Install the client on multiple computers in the same domain.

Use the Command Line

Specify installation arguments in a command line window.

Procedure

Step 1

Open a command line window.
Step 2

Enter the following command: 

msiexec.exe /i CiscoJabberSetup.msi
Step 3

Specify command line arguments as parameter=value pairs.

msiexec.exe /i CiscoJabberSetup.msi argument=value
Step 4

Run the command to install Cisco Jabber for Windows.

Example Installation Commands

Review examples of commands to install Cisco Jabber for Windows.

Cisco Unified Communications Manager, Release 9.x 
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1
Where:
  • CLEAR=1 — Deletes any existing bootstrap file.
  • /quiet — Specifies a silent installation.
Cisco Unified Communications Manager, Release 8.x in Default Mode 
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=CUP CUP_ADDRESS=1.2.3.4
Where:
  • CLEAR=1 — Deletes any existing bootstrap file.
  • AUTHENTICATOR=CUP — Sets Cisco Unified Presence as the authenticator.
  • CUP_ADDRESS=1.2.3.4 — Sets 1.2.3.4 as the IP address of the presence server.
  • /quiet — Specifies a silent installation.
Cisco Unified Communications Manager, Release 8.x in Phone Mode

If you are integrating with UDS when you are installing in phone mode, you must first define the <PresenceDomain>Domain address of your Presence server</PresenceDomain> parameter. 

msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 PRODUCT_MODE=Phone_Mode AUTHENTICATOR=CUCM TFTP=1.2.3.4 CTI=5.6.7.8
Where:
  • CLEAR=1 — Deletes any existing bootstrap file.
  • PRODUCT_MODE=Phone_Mode — Sets the client to phone mode.
  • AUTHENTICATOR=CUCM — Sets Cisco Unified Communications Manager as the authenticator.
  • TFTP=1.2.3.4 — Sets 1.2.3.4 as the IP address of the TFTP server that hosts the client configuration.
  • CTI=5.6.7.8 — Sets 5.6.7.8 as the IP address of the CTI server.
  • /quiet — Specifies a silent installation.
Cisco WebEx Messenger Service 
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=WEBEX
Where:
  • CLEAR=1 — Deletes any existing bootstrap file.
  • AUTHENTICATOR=WEBEX — Sets the Cisco WebEx Messenger service as the authenticator.
  • /quiet — Specifies a silent installation.
Cisco WebEx Messenger Service with SSO 
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=WEBEX
 SSO_ORG_DOMAIN=example.com
Where:
  • CLEAR=1 — Deletes any existing bootstrap file.
  • AUTHENTICATOR=WEBEX — Sets the Cisco WebEx Messenger service as the authenticator.
  • SSO_ORG_DOMAIN=example.com — Sets example.com as the single sign-on (SSO) domain.
  • /quiet — Specifies a silent installation.

Run the MSI Manually

You can run the installation program manually to install a single instance of the client and specify connection settings in the Advanced settings window.

Procedure

Step 1

Launch CiscoJabberSetup.msi.

The installation program opens a window to guide you through the installation process.
Step 2

Follow the steps to complete the installation process.
Step 3

Start Cisco Jabber for Windows.

Step 4

Select Manual setup and sign in.

The Advanced settings window opens.
Step 5

Specify values for the connection settings properties.
Step 6

Select Save.

Create a Custom Installer

You can transform the default installation package to create a custom installer.


Note

You use Microsoft Orca to create custom installers. Microsoft Orca is available as part of the Microsoft Windows SDK for Windows 7 and .NET Framework 4.

Download and install Microsoft Windows SDK for Windows 7 and .NET Framework 4 from the Microsoft website.

Procedure

  Command or Action Purpose
Step 1

Get the Default Transform File

You must have the default transform file to modify the installation package with Microsoft Orca.
Step 2

Create Custom Transform Files

Transform files contain installation properties that you apply to the installer.
Step 3

Transform the Installer

Apply a transform file to customize the installer.

Create Custom Transform Files

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.

Before you begin

Get the Default Transform File

Procedure
Step 1

Start Microsoft Orca.

Step 2

Open CiscoJabberSetup.msi and then apply CiscoJabberProperties.msi.

Step 3

Specify values for the appropriate installer properties.
Step 4

Generate and save the transform file.

  1. Select Transform > Generate Transform.

  2. Select a location on your file system to save the transform file.

  3. 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.

What to do next

Transform the Installer

Transform the Installer

Apply a transform file to customize the installer.


Note

Applying transform files will alter the digital signature of CiscoJabberSetup.msi. Attempts to modify or rename CiscoJabberSetup.msi will remove the signature entirely.

Before you begin

Create Custom Transform Files

Procedure
Step 1

Start Microsoft Orca.

Step 2

Open CiscoJabberSetup.msi in Microsoft Orca.

  1. Select File > Open.

  2. Browse to the location of CiscoJabberSetup.msi on your file system.

  3. 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.

Step 3

Remove all language codes except for 1033 (English).

Restriction 

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.

  1. Select View > Summary Information.

    The Edit Summary Information window displays.

  2. Locate the Languages field.

  3. Delete all language codes except for 1033.

  4. Select OK.

English is set as the language for your custom installer.

Step 4

Apply a transform file.

  1. Select Transform > Apply Transform.

  2. Browse to the location of the transform file on your file system.

  3. Select the transform file and then select Open.

Step 5

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.

Step 6

Specify values for the properties you require.

Step 7

Remove any properties that you do not require.

It is essential to remove any properties that are not being set, otherwise the properties being set will not take effect. Remove each property that is not needed one at a time.

  1. Right-click the property you want to remove.

  2. Select Drop Row.

  3. Select OK when Microsoft Orca prompts you to continue.

Step 8

Enable your custom installer to save embedded streams.

  1. Select Tools > Options.

  2. Select the Database tab.

  3. Select Copy embedded streams during 'Save As'.

  4. Select Apply and then OK.

Step 9

Save your custom installer.

  1. Select File > Save Transformed As.

  2. Select a location on your file system to save the installer.

  3. Specify a name for the installer and then select Save.

Deploy with Group Policy

Install Cisco Jabber for Windows with Group Policy using the Microsoft Group Policy Management Console (GPMC) on Microsoft Windows Server.


Note

To install Cisco Jabber for Windows with Group Policy, all computers or users to which you plan to deploy Cisco Jabber for Windows must be in the same domain.

Procedure

  Command or Action Purpose
Step 1

Set a Language Code

You must use this procedure and set the Language field to 1033 only if the MSI is to be modified by Orca in any way.
Step 2

Deploy the Client with Group Policy

Deploy Cisco Jabber for Windows with Group Policy.

Set a Language Code

Altering the installation language is not necessary in Group Policy deployment scenarios where the exact MSI file provided by Cisco will be used. The installation language will be determined from the Windows User Locale (Format) in these situations. You must use this procedure and set the Language field to 1033 only if the MSI is to be modified by Orca in any way.

Procedure
Step 1

Start Microsoft Orca.

Microsoft Orca is available as part of the Microsoft Windows SDK for Windows 7 and ,NET Framework 4 that you can download from the Microsoft website.

Step 2

Open CiscoJabberSetup.msi.

  1. Select File > Open.

  2. Browse to the location of CiscoJabberSetup.msi on your file system.

  3. Select CiscoJabberSetup.msi and then select Open.

Step 3

Select View > Summary Information.

Step 4

Locate the Languages field.

Step 5

Set the Languages field to 1033.

Step 6

Select OK.

Step 7

Enable your custom installer to save embedded streams.

  1. Select Tools > Options.

  2. Select the Database tab.

  3. Select Copy embedded streams during 'Save As'.

  4. Select Apply and then OK.

Step 8

Save your custom installer.

  1. Select File > Save Transformed As.

  2. Select a location on your file system to save the installer.

  3. Specify a name for the installer and then select Save.

What to do next

Deploy the Client with Group Policy

Deploy the Client with Group Policy

Complete the steps in this task to deploy Cisco Jabber for Windows with Group Policy.

Before you begin

Set a Language Code

Procedure
Step 1

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.

Step 2

Select Start > Run and then enter the following command: 

GPMC.msc

The Group Policy Management console opens.

Step 3

Create a new group policy object.

  1. Right-click on the appropriate domain in the left pane.

  2. Select Create a GPO in this Domain, and Link it here.

    The New GPO window opens.

  3. Enter a name for the group policy object in the Name field.

  4. 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.
Step 4

Set the scope of your deployment.

  1. Select the group policy object under the domain in the left pane.

    The group policy object displays in the right pane.

  2. Select Add in the Security Filtering section of the Scope tab.

    The Select User, Computer, or Group window opens.

  3. Specify the computers and users to which you want to deploy Cisco Jabber for Windows.

Step 5

Specify the installation package.

  1. Right-click the group policy object in the left pane and then select Edit.

    The Group Policy Management Editor opens.

  2. Select Computer Configuration and then select Policies > Software Settings.

  3. Right-click Software Installation and then select New > Package.

  4. Enter the location of the installation package next to File Name; for example, \\server\software_distribution.

    Important 

    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.

  5. Select the installation package and then select Open.

  6. 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.

Command Line Arguments

Review the command line arguments you can specify when you install Cisco Jabber for Windows.

Override Argument

The following table describes the parameter you must specify to override any existing bootstrap files from previous installations:

Argument

Value

Description

CLEAR

1

Specifies if the client overrides any existing bootstrap file from previous installations.

The client saves the arguments and values you set during installation to a bootstrap file. The client then loads settings from the bootstrap file at startup.

If you specify CLEAR, the following occurs during installation:

  1. The client deletes any existing bootstrap file.

  2. The client creates a new bootstrap file.

If you do not specify CLEAR, the client checks for existing bootstrap files during installation.

  • If no bootstrap file exists, the client creates a bootstrap file during installation.

  • If a bootstrap file exists, the client does not override that bootstrap file and preserves the existing settings.


Note
If you are reinstalling Cisco Jabber for Windows, you should consider the following:

  • The client does not preserve settings from existing bootstrap files. If you specify CLEAR, you must also specify all other installation arguments as appropriate.

  • The client does not save your installation arguments to an existing bootstrap file. If you want to change the values for installation arguments, or specify additional installation arguments, you must specify CLEAR to override the existing settings.

To override existing bootstrap files, specify CLEAR in the command line as follows:
msiexec.exe /i CiscoJabberSetup.msi CLEAR=1

Mode Type Argument

The following table describes the command line argument with which you specify the product mode:
Argument Value Description

PRODUCT_MODE

Phone_Mode

Specifies the product mode for the client. You can set the following value:

  • Phone_Mode — Cisco Unified Communications Manager is the authenticator.

    Choose this value to provision users with audio devices as base functionality.

When to Set the Product Mode
In phone mode deployments Cisco Unified Communications Manager is the authenticator. When the client gets the authenticator, it determines the product mode is phone mode. However, because the client always starts in the default product mode on the initial launch, users must restart the client to enter phone mode after sign in.

  • Cisco Unified Communications Manager, Release 9.x and Later — You should not set PRODUCT_MODE during installation. The client gets the authenticator from the service profile. After the user signs in, the client requires a restart to enter phone mode.

  • Cisco Unified Communications Manager, Release 8.x — You can specify phone mode during installation if you set Cisco Unified Communications Manager as the authenticator. The client reads the bootstrap file on the initial launch and determines it should start in phone mode. The client then gets Cisco Unified Communications Manager as the authenticator from the bootstrap file or manual settings. After the user signs in, the client does not require a restart.

Change Product Modes

To change the product mode, you must change the authenticator for the client. The client can then determine the product mode from the authenticator.

The method for changing from one product mode to another after installation, depends on your deployment.

Note

In all deployments, the user can manually set the authenticator in the Advanced settings window.

In this case, you must instruct the user to change the authenticator in the Advanced settings window to change the product mode. You cannot override the manual settings, even if you uninstall and then reinstall the client.

Change Product Modes with Cisco Unified Communications Manager Version 9.x and Later

To change product modes with Cisco Unified Communications Manager version 9.x and later, you change the authenticator in the service profile.

Procedure
Step 1

Change the authenticator in the service profiles for the appropriate users.

Change Default Mode > Phone Mode

Do not provision users with an IM and Presence service.

If the service profile does not contain an IM and presence service configuration, the authenticator is Cisco Unified Communications Manager.

Change Phone Mode > Default Mode

Provision users with an IM and Presence service.

If you set the value of the Product type field in the IM and Presence profile to:

  • Unified CM (IM and Presence) the authenticator is Cisco Unified Communications Manager IM and Presence Service.

  • Webex (IM and Presence) the authenticator is the Cisco Webex Messenger service.

Step 2

Instruct users to sign out and then sign in again.

When users sign in to the client, it retrieves the changes in the service profile and signs the user in to the authenticator. The client then determines the product mode and prompts the user to restart the client.

After the user restarts the client, the product mode change is complete.

Change Product Modes with Cisco Unified Communications Manager Version 8.x

To change product modes with Cisco Unified Communications Manager version 8.x, you must reinstall Cisco Jabber for Windows to change the authenticator.

Change Default Mode > Phone Mode
Set the following arguments, at a minimum:

  • CLEAR=1 to delete any existing bootstrap file.

  • AUTHENTICATOR=CUCM to set the authenticator to Cisco Unified Communications Manager.

  • PRODUCT_MODE=Phone_Mode to set phone mode as the product mode.

Change Phone Mode > Default Mode
Set the following arguments, at a minimum:

  • CLEAR=1 to delete any existing bootstrap file.

  • AUTHENTICATOR= one of the following:

    • CUP to set the authenticator to Cisco Unified Presence or Cisco Unified Communications Manager.

    • WEBEX to set the authenticator to the Cisco WebEx Messenger service.

Authentication Arguments

The following table describe the command line arguments you can set to specify the source of authentication:
Argument Value Description
AUTHENTICATOR

CUP

CUCM

Webex

Specifies the source of authentication for the client. This value is used if Service Discovery fails. Set one of the following as the value:

  • CUP—Cisco Unified Communications Manager IM and Presence Service. On-premises deployments in the default product mode. The default product mode can be either full UC or IM only.

  • CUCM—Cisco Unified Communications Manager. On-premises deployments in phone mode.
  • Webex—Cisco Webex Messenger Service. Cloud-based or hybrid cloud-based deployments.

In on-premises deployments with Cisco Unified Communications Manager version 9.x and later, you should deploy the _cisco-uds SRV record. The client can then automatically determine the authenticator.

CUP_ADDRESS

IP address

Hostname

FQDN

Specifies the address of Cisco Unified Communications Manager IM and Presence Service. Set one of the following as the value:

  • Hostname (hostname)

  • IP address (123.45.254.1)

  • FQDN (hostname.domain.com)

TFTP

IP address

Hostname

FQDN

Specifies the address of your TFTP server. Set one of the following as the value:

  • Hostname (hostname)

  • IP address (123.45.254.1)

  • FQDN (hostname.domain.com)

You should specify this argument if you set Cisco Unified Communications Manager as the authenticator.

If you deploy:

  • In phone mode—you should specify the address of the TFTP server that hosts the client configuration.

  • In default mode—you can specify the address of the Cisco Unified Communications Manager TFTP service that hosts the device configuration.

CTI

IP address

Hostname

FQDN

Sets the address of your CTI server.

Specify this argument if:

  • You set Cisco Unified Communications Manager as the authenticator.

  • Users have desk phone devices and require a CTI server.

CCMCIP

IP address

Hostname

FQDN

Sets the address of your CCMCIP server.

Specify this argument if:

  • You set Cisco Unified Communications Manager as the authenticator.

  • The address of your CCMCIP server is not the same as the TFTP server address.

    The client can locate the CCMCIP server with the TFTP server address if both addresses are the same.

Cisco Unified Communications Manager release 9.x and earlier—If you enable Cisco Extension Mobility, the Cisco Extension Mobility service must be activated on the Cisco Unified Communications Manager nodes that are used for CCMCIP. For information about Cisco Extension Mobility, see the Feature and Services guide for your Cisco Unified Communications Manager release.

SERVICES_DOMAIN

Domain

Sets the value of the domain where the DNS SRV records for Service Discovery reside.

This argument can be set to a domain where no DNS SRV records reside if you want the client to use installer settings or manual configuration for this information. If this argument is not specified and Service Discovery fails, the user will be prompted for services domain information.

VOICE_SERVICES_DOMAIN

Domain
In Hybrid Deployments the domain required to discover Webex via CAS lookup may be a different domain than where the DNS records are deployed. If this is the case then set the SERVICES_DOMAIN to be the domain used for Webex discovery (or let the user enter an email address) and set the VOICE_SERVICES_DOMAIN to be the domain where DNS records are deployed. If this setting is specified, the client will use the value of VOICE_SERVICES_DOMAIN to lookup the following DNS records for the purposes of Service Discovery and Edge Detection:
  • _cisco-uds
  • _cuplogin
  • _collab-edge

This setting is optional and if not specified, the DNS records are queried on the Services Domain which is obtained from the SERVICES_DOMAIN, email address input by the user, or cached user configuration.

EXCLUDED_SERVICES

One or more of:
  • CUP
  • Webex
  • CUCM

Lists the services that you want Jabber to exclude from Service Discovery. For example, you may have done a trial with Webex which means that your company domain is registered on Webex, but you do not want Jabber users to authenticate using Webex. You want Jabber to authenticate with an on-premises CUP CUCM server. In this case set:

  • EXCLUDED_SERVICES=WEBEX

    Possible values are CUP, CUCM, Webex

To exclude more than one service, use comma separated values. For example, to exclude CUP and CUCM, specify: EXCLUDED_SERVICEs=CUP,CUCM. To exclude all services, specify: EXCLUDED_SERVICES=CUP,CUCM,WEBEX

If you exclude all services, you need to use manual configuration or bootstrap configuration to configure the Jabber client.

UPN_DISCOVERY_ENABLED

true

false

Allows you to define whether the client uses the User Principal Name (UPN) of a Windows session to get the User ID and domain for a user when discovering services.

  • true (default)—The UPN is used to find the User ID and the domain of the user, which is used during service discovery. Only the user discovered from UPN can log in to the client.

  • false—The UPN is not used to find the User ID and domain of the user. The user is prompted to enter credentials to find the domain for service discovery.

Example installation command: msiexec.exe /i CiscoJabberSetup.msi /quiet UPN_DISCOVERY_ENABLED=false

TFTP Server Address
Cisco Jabber for Windows retrieves two different configuration files from the TFTP server:

  • Client configuration files that you create.

  • Device configuration files that reside on the Cisco Unified Communications Manager TFTP service when you provision users with devices.

To minimize effort, you should host your client configuration files on the Cisco Unified Communications Manager TFTP service. You then have only one TFTP server address for all configuration files and can specify that address as required.

You can, however, host your client configuration on a different TFTP server to the one that contains the device configuration. In this case, you have two different TFTP server addresses, one address for the TFTP server that hosts device configuration and another address for the TFTP server that hosts client configuration files.

Default Deployments

This section describes how you should handle two different TFTP server addresses in deployments that have a presence server.

You should do the following:

  1. Specify the address of the TFTP server that hosts the client configuration on the presence server.

  2. During installation, specify the address of the Cisco Unified Communications Manager TFTP service with the TFTP argument.

When the client starts for the first time, it:

  1. Retrieves the address of the Cisco Unified Communications Manager TFTP service from the bootstrap file.

  2. Gets device configuration from the Cisco Unified Communications Manager TFTP service.

  3. Connects to the presence server.

  4. Retrieves the address of the TFTP service that hosts the client configuration from the presence server.

  5. Gets client configuration from the TFTP server.

Phone Mode Deployments

This section describes how you should handle two different TFTP server addresses in phone mode deployments.

You should do the following:

  1. During installation, specify the address of the TFTP server that hosts the client configuration with the TFTP argument.

  2. Specify the address of the TFTP server that hosts the device configuration in your client configuration file with the following parameter: TftpServer1.

  3. Host the client configuration file on the TFTP server.

When the client starts for the first time, it:

  1. Retrieves the address of the TFTP server from the bootstrap file.

  2. Gets client configuration from the TFTP server.

  3. Retrieves the address of the Cisco Unified Communications Manager TFTP service from the client configuration.

  4. Gets device configuration from the Cisco Unified Communications Manager TFTP service.

Common Installation Arguments

The following table describes command line arguments that are common to all deployments:

Argument Value Description

LANGUAGE

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.

See the LCID for Languages topic for a full list of the languages that you can specify.

This argument is optional.

If you do not specify a value, Cisco Jabber for Windows uses the regional language for the current user as the default.

From Release 11.1(1) onwards, if you do not specify a value, Cisco Jabber for Windows checks the value for the UseSystemLanguage parameter. If the UseSystemLanguage parameter is set to true, the same language is used as for the operating system. If the UseSystemLanguage parameter is to set to false or not defined, then the client uses the regional language for the current user as the default.

The regional language is set at Control Panel > Region and Language > Change the date, time, or number format > Formats tab > Format dropdown.

FORGOT_PASSWORD_URL

URL

Specifies the URL where users can reset lost or forgotten passwords.

This argument is optional but recommended.

Note 
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.

AUTOMATIC_SIGN_IN

true

false

Applies to Release 11.1(1) onwards.

Specifies whether the Sign me in when Cisco Jabber starts check box is checked when the user installs the client.

  • true—The Sign me in when Cisco Jabber starts check box is checked when the user installs the client.

  • false (default)—The Sign me in when Cisco Jabber starts check box is not checked when the user installs the client.

TFTP_FILE_NAME

Filename

Specifies the unique name of a group configuration file.

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.

Remember 

You can specify group configuration files in the Cisco Support Field on the CSF device configuration on Cisco Unified Communications Manager.

LOGIN_RESOURCE

WBX

MUT

Controls user sign in to multiple client instances.

By default, users can sign in to multiple instances of Cisco Jabber at the same time. Set one of the following values to change the default behavior:

  • WBX—Users can sign in to one instance of Cisco Jabber for Windows at a time.

    Cisco Jabber for Windows appends the wbxconnect suffix to the user's JID. Users cannot sign in to any other Cisco Jabber client that uses the wbxconnect suffix.

  • MUT—Users can sign in to one instance of Cisco Jabber for Windows at a time, but can sign in to other Cisco Jabber clients at the same time.

    Each instance of Cisco Jabber for Windows appends the user's JID with a unique suffix.

LOG_DIRECTORY

Absolute path on the local filesystem

Defines the directory where the client writes log files.

Use quotation marks to escape space characters in the path, as in the following example:

"C:\my_directory\Log Directory"

The path you specify must not contain Windows invalid characters.

The default value is %USER_PROFILE%\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs

CLICK2X

DISABLE

Disables click-to-x functionality with Cisco Jabber.

If you specify this argument during installation, the client does not register as a handler for click-to-x functionality with the operating system. This argument prevents the client from writing to the Microsoft Windows registry during installation.

You must re-install the client and omit this argument to enable click-to-x functionality with the client after installation.

Telemetry_Enabled

true

false

Specifies whether analytics data is gathered. The default value is true.

To improve your experience and product performance, Cisco Jabber may collect and send non-personally identifiable usage and performance data to Cisco. The aggregated data is used by Cisco to understand trends in how Jabber clients are being used and how they are performing.

Full details on what analytics data Cisco Jabber does and does not collect can be found in the Cisco Jabber Supplement to Cisco’s On-Line Privacy Policy at http://www.cisco.com/web/siteassets/legal/privacy_02Jun10.html.

SSO Arguments

This section describes the command line arguments you can use to deploy Cisco Jabber for Windows with single sign on (SSO) capabilities.

Cloud-Based SSO Arguments
The arguments in the following table apply to cloud-based deployments only:

Argument

Value

Description

SSO_ORG_DOMAIN

Domain name

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.

Note 

You specify the URL for the SSO service as the value of the Customer SSO Service Login URL in the Cisco WebEx Administration Tool.

Installer Properties

The following are the properties you can modify in a custom installer:

  • CLEAR

  • PRODUCT_MODE

  • AUTHENTICATOR

  • CUP_ADDRESS

  • TFTP

  • CTI

  • CCMCIP

  • LANGUAGE

  • TFTP_FILE_NAME

  • FORGOT_PASSWORD_URL

  • SSO_ORG_DOMAIN

  • LOGIN_RESOURCE

  • LOG_DIRECTORY

  • CLICK2X

  • SERVICES_DOMAIN

These properties correspond to the installation arguments and have the same values.

Supported Languages

Cisco Jabber for Windows uses the regional language for the current user as the default. The regional language is set at Control Panel > Region and Language > Change the date, time, or number format > Formats tab > Format dropdown.

The following table lists the languages that Cisco Jabber for Windows supports.
  • Arabic
  • Bulgarian
  • Catalan
  • Croatian
  • Czech
  • Danish
  • German
  • Greek
  • English
  • Spanish
  • Finnish
  • French
  • Hebrew
  • Hungarian
  • Italian
  • Japanese
  • Korean
  • Norwegian
  • Dutch
  • Polish
  • Portuguese - Brazil
  • Portuguese - Portugal
  • Romanian
  • Russian
  • Serbian
  • Slovak
  • Slovenian
  • Swedish
  • Thai
  • Turkish
  • Chinese - China
  • Chinese - Taiwan

Note

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.

See the following documentation for more information about Locale IDs:

  • Microsoft Windows Locale Code Identifier (LCID) Reference

  • Locale IDs Assigned by Microsoft

Cisco Media Services Interface

Cisco Jabber for Windows supports Cisco Media Services Interface version 4.1.2 for Microsoft Windows 7 and later.

Desk Phone Video Capabilities

You must install Cisco Media Services Interface to enable desk phone video capabilities. Cisco Media Services Interface provides a driver that enables Cisco Jabber for Windows to do the following:

  • Discover the desk phone device.

  • Establish and maintain a connection to the desk phone device using the CAST protocol.

Install Cisco Media Services Interface

Procedure
Step 1

Download the Cisco Media Services Interface installation program from the download site on cisco.com.

Step 2

Install Cisco Media Services Interface on each computer on which you install Cisco Jabber.

See the appropriate Cisco Medianet documentation for installing Cisco Media Services Interface.

Uninstall Cisco Jabber for Windows

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.

Procedure
Step 1

Open a command line window.
Step 2

Enter the following command:

msiexec.exe /x path_to_CiscoJabberSetup.msi
For example, 
msiexec.exe /x C:\Windows\Installer\CiscoJabberSetup.msi /quiet
Where /quiet specifies a silent uninstall.

The command removes Cisco Jabber for Windows from the computer.

Use the Product Code

If the installer is not available on the file system, use the product code to remove Cisco Jabber for Windows.

Procedure
Step 1

Find the product code.

  1. Open the Microsoft Windows registry editor.

  2. Locate the following registry key: HKEY_CLASSES_ROOT\Installer\Products

  3. Select Edit > Find.

  4. Enter Cisco Jabber in the Find what text box in the Find window and select Find Next.

  5. Find the value of the ProductIcon key.

    The product code is the value of the ProductIcon key, for example, C:\Windows\Installer\{product_code}\ARPPRODUCTICON.exe.

    Note 

    The product code changes with each version of Cisco Jabber for Windows.
Step 2

Open a command line window.
Step 3

Enter the following command:

msiexec.exe /x product_code
For example, 
msiexec.exe /x 45992224-D2DE-49BB-B085-6524845321C7 /quiet
Where /quiet specifies a silent uninstall.

The command removes Cisco Jabber for Windows from the computer.