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 |
---|---|
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 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. |
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.
-
Select
. -
Select the Integration tab (Calendar tab from release 11.0).
-
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:
|
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. |
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
- 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:
|
Step 3 |
Specify command line arguments as parameter=value pairs.
|
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
- 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
- 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
- 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
- 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
- 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 |
You must have the default transform file to modify the installation package with Microsoft Orca. |
|
Step 2 |
Transform files contain installation properties that you apply to the installer. |
|
Step 3 |
Apply a transform file to customize the installer. |
Get the Default Transform File
You must have the default transform file to modify the installation package with Microsoft Orca.
Procedure
Step 1 |
Download the Cisco Jabber administration package from Software Download page. |
Step 2 |
Copy CiscoJabberProperties.msi from the Cisco Jabber administration package to your file system. |
What to do next
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
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.
|
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
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
Procedure
Step 1 |
Start Microsoft Orca. |
||
Step 2 |
Open CiscoJabberSetup.msi in Microsoft Orca.
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).
English is set as the language for your custom installer. |
||
Step 4 |
Apply a transform file.
|
||
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.
|
||
Step 8 |
Enable your custom installer to save embedded streams.
|
||
Step 9 |
Save your custom installer.
|
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 |
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 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.
|
Step 3 |
Select . |
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.
|
Step 8 |
Save your custom installer.
|
What to do next
Deploy the Client with Group Policy
Complete the steps in this task to deploy Cisco Jabber for Windows with Group Policy.
Before you begin
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 and then enter the following command:
The Group Policy Management console opens. |
Step 3 |
Create a new group policy object. |
Step 4 |
Set the scope of your deployment. |
Step 5 |
Specify the installation package. |
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. |
-
The client deletes any existing bootstrap file.
-
The client creates a new bootstrap file.
-
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 |
|
msiexec.exe /i CiscoJabberSetup.msi CLEAR=1
Mode Type Argument
Argument | Value | Description |
---|---|---|
PRODUCT_MODE |
Phone_Mode |
|
When to Set the Product 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.
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.
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.
|
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
Argument | Value | Description |
---|---|---|
AUTHENTICATOR |
CUP CUCM Webex |
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 |
|
TFTP |
IP address Hostname FQDN |
You should specify this argument if you set Cisco Unified Communications Manager as the authenticator.
|
CTI |
IP address Hostname FQDN |
Sets the address of your CTI server.
|
CCMCIP |
IP address Hostname FQDN |
Sets the address of your CCMCIP server.
Cisco
Unified Communications Manager release 9.x and earlier—If you enable Cisco
Extension Mobility, the
|
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 |
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 |
|
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:
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 |
Example installation command:
|
TFTP Server Address
-
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.
-
Specify the address of the TFTP server that hosts the client configuration on the presence server.
-
During installation, specify the address of the Cisco Unified Communications Manager TFTP service with the TFTP argument.
-
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.
Phone Mode Deployments
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.
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.
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 . |
||
FORGOT_PASSWORD_URL |
URL |
Specifies the URL where users can reset lost or forgotten passwords. This argument is optional but recommended.
|
||
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.
|
||
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.
|
||
LOGIN_RESOURCE |
WBX MUT |
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. 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
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.
|
Installer Properties
-
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
.
|
|
|
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. |
-
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
-
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:
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. |
Step 2 |
Open a command line window. |
Step 3 |
Enter the following command:
Where /quiet specifies a silent uninstall.
|
The command removes Cisco Jabber for Windows from the computer.