The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Jabber for Windows provides an MSI installation package that you can use in the following ways:
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.
You must be logged in with local administrative rights.
You must be logged in with local administrative rights to complete installation of Cisco Jabber for Windows.
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 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.
You must apply a setting in Microsoft Outlook so that calendar events display in Cisco Jabber for Windows.
When users create calendar events in Microsoft Outlook, those events display in the Meetings tab.
To enable integration with Microsoft Outlook, you specify SIP:user@cupdomain as the value of the proxyAddresses attribute in Microsoft Active Directory. Users can then share availability in Microsoft Outlook.
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.
Refer to the appropriate Microsoft documentation for creating a script to enable presence in Microsoft Outlook.
Complete the following steps to enable presence in Microsoft Outlook for individual users with the Active Directory User and Computers administrative tool:
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 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.
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.
Install the client on multiple computers in the same domain.
Specify installation arguments in a command line window.
Review examples of commands to install Cisco Jabber for Windows.
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=CUP CUP_ADDRESS=1.2.3.4
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
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=WEBEX
msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=WEBEX SSO_ORG_DOMAIN=example.com
You can run the installation program manually to install a single instance of the client and specify connection settings in the Advanced settings window.
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. |
You must have the default transform file to modify the installation package with Microsoft Orca.
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.
The transform file you created is saved as file_name.mst. You can apply this transform file to modify the properties of CiscoJabberSetup.msi.
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. |
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. |
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.
Complete the steps in this task to deploy Cisco Jabber for Windows with Group Policy.
Group Policy installs Cisco Jabber for Windows on each computer the next time each computer starts.
Review the command line arguments you can specify when you install Cisco Jabber for Windows.
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. |
msiexec.exe /i CiscoJabberSetup.msi CLEAR=1
Argument | Value | Description |
---|---|---|
PRODUCT_MODE |
Phone_Mode |
|
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.
To change the product mode, you must change the authenticator for the client. The client can then determine the product mode from the authenticator.
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. |
To change product modes with Cisco Unified Communications Manager version 9.x and later, you change the authenticator in the service profile.
After the user restarts the client, the product mode change is complete.
To change product modes with Cisco Unified Communications Manager version 8.x, you must reinstall Cisco Jabber for Windows to change the authenticator.
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.
This section describes how you should handle two different TFTP server addresses in deployments that have a presence server.
Retrieves the address of the Cisco Unified Communications Manager TFTP service from the bootstrap file.
Gets device configuration from the Cisco Unified Communications Manager TFTP service.
Connects to the presence server.
Retrieves the address of the TFTP service that hosts the client configuration from the presence server.
Gets client configuration from the TFTP server.
This section describes how you should handle two different TFTP server addresses in phone mode deployments.
During installation, specify the address of the TFTP server that hosts the client configuration with the TFTP argument.
Specify the address of the TFTP server that hosts the device configuration in your client configuration file with the following parameter: TftpServer1.
Host the client configuration file on the TFTP server.
Retrieves the address of the TFTP server from the bootstrap file.
Gets client configuration from the TFTP server.
Retrieves the address of the Cisco Unified Communications Manager TFTP service from the client configuration.
Gets device configuration from the Cisco Unified Communications Manager TFTP service.
The following table describes command line arguments that are common to all deployments:
Argument | Value | Description | ||
---|---|---|---|---|
LANGUAGE |
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. 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. |
|||
FORGOT_PASSWORD_URL |
Specifies the URL where users can reset lost or forgotten passwords. This argument is optional but recommended.
|
|||
TFTP_FILE_NAME |
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. You can specify group configuration files in the Cisco Support Field on the CSF device configuration on Cisco Unified Communications Manager. |
|||
LOGIN_RESOURCE |
Controls user sign in to multiple client instances.
|
|||
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.
|
||
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. |
This section describes the command line arguments you can use to deploy Cisco Jabber for Windows with single sign on (SSO) capabilities.
These properties correspond to the installation arguments and have the same values.
|
|
|
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. |
Cisco Jabber for Windows supports Cisco Media Services Interface version 4.1.2 for Microsoft Windows 7 and later.
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. |
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.
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.
If the installer is not available on the file system, use the product code to remove Cisco Jabber for Windows.
The command removes Cisco Jabber for Windows from the computer.
Visit the Cisco Software Center to download the Cisco Jabber for Mac client.
Upgrading in the Mac OS X environment is performed automatically by the application, with permission from the user.