Migrating WebEx Connect Users to Cisco Jabber

Transcription

1 Planning Guide Migrating WebEx Connect Users to Cisco Jabber Information for System Administrators Introduction The Cisco WebEx Messenger service provides an instant messaging / chat based collaboration solution which customers access using the public internet. Cisco provides a choice of clients to access this service: Cisco Webex Connect Cisco Jabber for Windows Both clients provide IM capability and further provide the capability to integrate into Cisco s Unified communication manager enabling voice and video calling. Both clients also provide the ability to integrate with the WebEx Meeting center service. The WebEx Connect client is currently in maintenance mode with only bug fixes being provided. Cisco Jabber continues to be developed with a committed roadmap. Cisco is currently updating the WebEx Meeting Center server which will be complete by December This 2014 Cisco and/or its affiliates. All rights reserved. Page 1 of 11

2 update will require administrators to update the client their end users uses use to access the Messenger and Meeting Center service. Administrators can choose which clients to deploy. Cisco is strongly recommending they upgrade to Cisco Jabber at this time for long term support. The latest Cisco Jabber for Windows client, currently , has been listed in the org admin tool and can be made a baseline client for your organization. Please refer to the upgrade management instructions in the org admin guide for assistance with upgrading from the Connect client to the Cisco Jabber for Windows client. Those instructions can be found here: This document has been created for system administrators who wish to migrate their WebEx Connect client users to Cisco Jabber for Windows. It discusses the administrator consideration for client migration. The document is broken down into two main sections to align with Messenger functionality deployment. If you re current WebEx deployment is for an IM only service read section 1. If you re current WebEx deployment is also integrated to Cisco UC manager please review both section 1 and Cisco and/or its affiliates. All rights reserved. Page 2 of 11

3 Section 1 Migration Considerations for IM only and UC Manager integrated deployments This section will discuss baseline considerations for migration to Jabber for Windows. Service Discovery Cisco Jabber for Windows has been architected to connect to the cloud based WebEx Messenger service or on premise servers running Cisco IM and Presence server. To detect its operating mode by default uses a function called service discovery. Service discovery is designed to avoid an end user having to enter any service related information. Service discovery performs a number of steps to determine the presence domain for a user and determine if the presence domain is operating in cloud or on premise mode. It does this by querying both the WebEx Messenger service and local DNS servers to determine if it should connect to the WebEx service or on premise servers. If the process fails to identify a service the user will be prompted. The first time the Jabber client is started it will try to auto-detect the presence domain. The default method it will use to do this is to detect the user s windows domain and use this domain to locate the presence service. If the windows domain doesn t match your presence domain then initial service discovery will fail. If the Jabber client is unable to detect the domain it will prompt the user for the domain. If you don t want the end user to be prompted for the presence domain the administrator can pre-populate the installer with the required information. You have three options for Service discovery 1. Service discovery with auto discovery of domain Use this option if your windows workstations are in a domain and the domain name matches your WebEx messenger domain name 2. Customized Jabber installation (recommended if Windows/presence domain different) Use this option if Service discovery will not be able to resolve your presence domain. Using this method the administrator will pre-populate the installer with the correct domain name to discovery is not required. 3. Service discovery with user prompt for domain If the service domain is not detectable and the Jabber installer has not be customized the user can enter their domain. To customize the Jabber installer the administrator provides the WebEx domain. This is accomplished by specifying a SERVICES_DOMAIN in the installer. Specifying the SERVICES_DOMAIN causes service discovery to bypass the domain discovery and establishes the service for the specified SERVICES_DOMAIN. The administrator can configure the SERVICES_Domain either using: Command Line parameters Re-package custom MSI (using a tool such as Microsoft ORCA) 2014 Cisco and/or its affiliates. All rights reserved. Page 3 of 11

4 The following example demonstrates how to perform a custom installation specifying a SERVICES_DOMAIN. msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 SERVICES_DOMAIN=example.com In the above example the WebEx Messenger domain is example.com. With this parameter in place the jabber client will startup and attempt to locate a presence service for example.com rather than the Windows domain. This method of customization can be used with package management solutions such as Microsoft SCCM. It is also possible to customize the actual Jabber MSI file so that the SERVICES_DOMAIN is hardcoded into a new MSI file. In this case the command line parameters would not be required and a user could just run the new MSI file. To create a custom MSI file use a MSI editor such as Microsoft ORCA. For more details on creating custom MSI files please refer to the Jabber for Windows product documentation. A custom MSI file can also be deployed with a desktop package management solution. To install Jabber using command line settings see: To Create a custom installer see: installation-guide-ciscojabber/cjab_bk_d6497e98_00_deployment-installation-guide- ciscojabber_chapter_01010.html#jabw_tk_ue4fb9dd_00 Client Localization When installing the WebEx Connect client a user is prompted to select a language. provides an in application option to change the application operating language. WebEx Connect also installation-guide-ciscojabber/cjab_bk_d6497e98_00_deployment-installation-guide- ciscojabber_chapter_01010.html#jabw_tk_ibe959aa_00 Jabber for Windows doesn t prompt the end user for language selection during installation. Jabber will check the Windows system language settings and use that language for the Jabber user interface. This Jabber language setting can be overriden by the administrator by specficying additional parameters to the Jabber installer. Information on supported languages: Web Proxy Configuration WebEx Connect provided the user with the ability to configure a web proxy within the Connect application. When using Jabber for Windows the client will use the system proxy settings which can be accessed in 2014 Cisco and/or its affiliates. All rights reserved. Page 4 of 11

5 Internet Options in either Windows control panel or Internet Explorer. Office Integration Cisco Jabber provides integration into Microsoft Office in the same way as WebEx Connect. Jabber can drive presence information to be displayed in Microsoft Office applications and enabled chat and calling functions from Microsoft Office applications. For Jabber to provide presence and communication functions in Microsoft Office the Jabber userid must be made available to the Office applications. This information is made available to the Office applications by populating the ProxyAddress attribute in Active Directory. Populating the ProxyAddress attribute allows the global address list used by Microsoft Office to be used to resolve the Jabber ID. The ProxyAddress should be populated for all users in the format for example Administrator can populate this attribute using a number of methods, examples are: Active Directory Users and Computers tool Microsoft PowerShell script Cisco Bulk update tool (available in Jabber Administrator tools download on cisco.com) Information on supported Microsoft products: Information on ProxyAddress configuration: Desktop Share Desktop share allows Jabber users to display the contents of their screen to other users to collaborate. WebEx Connect provides a desktop share capability which leverages the WebEx Messenger cloud. Jabber for Windows 10.5 provides several methods for desktop sharing, these are: 1. Jabber P2P desktop share (including remote control and multi-party capability) 2. Video desktop share BFCP (supports Jabber to Jabber and Jabber to Telepresence) This method of desktop share is only available when using Cisco UC manager Cisco and/or its affiliates. All rights reserved. Page 5 of 11

6 3. WebEx Desktop share (provides same functionality as WebEx Connect client). When a user initiates a desktop share the Jabber client will attempt to establish a desktop share using the list above in priority order (i.e 1,2,3). The method that is selected is dependent on the capabilities the administrator has enabled and the remote client capability to support the method. If two Jabber for Windows uses attempt to establish a desktop share during an IM conversation the default share method is Jabber P2P desktop share. The traditional WebEx Messenger desktop share function would only be used if the remote client didn t support desktop share or the P2P desktop share has been disabled via installation settings. Note: Jabber P2P desktop share is not subject to desktop sharing policy configured in the OrgAdmin/WebEx Administrator web tool. If you require WebEx policy control of desktop share the administrator should disable P2P desktop share forcing the client to use WebEx desktop share. Jabber P2P is available between clients on the corporate network. The feature is not available for remote Expressway users or federated contacts outside the corporate network. Video desktop share configuration: Policy Management WebEx Connect will download policy settings from the OrgAdmin/WebEx Administration tool. Jabber provides additional settings which are not exposed in the WebEx admin tool. Many of these additional settings relate to UC manager integration can be configured in a configuration file downloaded from UC manager. The configuration file called jabber-config.xml can be created and uploaded to the UC manager by the administrator. Examples include: Outlook Searching: Disabled with the following config parameter: <Policies> <enablelocaladdressbooksearch>false</enablelocaladdressbooksearch></policies> SIPUriDialling: Disabled with the following config parameter: <Policies> < EnableSIPURIDialling >false</ EnableSIPURIDialling > </Policies> Telemetry: Disabled with the following config parameter: <Policies> < TelemetryEnabled >false</ TelemetryEnabled ></Policies> Webex Messenger Policy: Cisco and/or its affiliates. All rights reserved. Page 6 of 11

7 ciscojabber_chapter_01001.html#cjab_rf_c6a82d75_00 Jabber Configuration Policy Contact Photos WebEx Connect and Cisco Jabber both provide the ability to display contact photos. It should be noted that contact photos loaded in to WebEx Messenger before 1 st January 2012 won t be displayed in Jabber for Windows. A user can upload a new photo using the Jabber client is necessary Cisco and/or its affiliates. All rights reserved. Page 7 of 11

8 Section 2 Migration Consideration for UC Manager integrated deployments This section has been created for WebEx Connect administrator who is also using UC manager integration. Jabber for Windows provides a single installer that provides both WebEx Messenger support and integration to UC manager. Jabber provides both desk phone control and soft phone modes of operation. Jabber also provides many UC manager features not previously offered by WebEx Connect. These include: Video calling when using UC manager Extend and Connect (provides control of PSTN or non-cisco PBX Phone) BFCP video desktop sharing Hunt Group and Call Pickup Jabber doesn t provide integration to UC Manager Express, Cisco TelePresence Video Communication server (VCS) or WebEx Connect Click-to-Call (Web Dialer) Jabber doesn t support Audio and Video dialing without integration to Cisco UC Manager. Certificate Validation Cisco Jabber has additional certificate requirements to WebEx Connect. Cisco Jabber will attempt to validate all service connections are secured and trusted. The Jabber client does this by validating certificates provided by WebEx Messenger, UC manager, Unity Connection and Cisco telemetry. If certificates can t be validated then the user will be prompted to accept connections without a valid certificate. This prompt will be repeated for each certificate that Jabber is unable to trust. UC manager and Unity Connection are installed by default with self-signed certificates. For Jabber to trust certificates presented by UC manager the following are required: A private or public certificate authority needs to be in place 2014 Cisco and/or its affiliates. All rights reserved. Page 8 of 11

9 CA root certificates must be installed on UC manager cluster UC Manager self-signed certificates should be replaced with CA issued certificates on each node of the cluster. Later versions of UC manager support certificates with SAN set allowing a common certificate to be used Workstation must have CA root certificate installed so they trust CA issued certificates Workstation must have access to revocation list on Certificate authority Note: To access the WebEx Messenger service Jabber also expected the following root certificates to be trusted by the workstation: o VeriSign Class 3 Secure Server CA - G3 (intermediate-cert) o VeriSign Class 3 Public Primary Certification Authority - G5 (root) Jabber may also provide telemetry data back to Cisco. If this is enabled the following certificate will be used to valid the connection. o GoDaddy Class 2 Certification Authority Root Certificate Certificate Validation: UC Cluster Configuration Jabber will read UC cluster information from the WebEx messenger configuration source. No settings changes are required to migrate to Cisco Jabber. The Jabber client will download the configuration defined in the Unified Communication Cluster settings and register to the UC manager. WebEx Connect and Jabber for Windows use the same method to register voice and video services. The administrator is not required to change device, user or group information on the UC manager. Your administration screen will align to one of the following views depending on the version of administration in use Cisco and/or its affiliates. All rights reserved. Page 9 of 11

10 Example A: Example B: Audio and Video Settings When migrating to Jabber for Windows users may be required to select audio and video devices when they first run Jabber. If a user has a single sound device and/or video camera these will be used by default. If the 2014 Cisco and/or its affiliates. All rights reserved. Page 10 of 11

11 user has multiple devices they will need to select the devices in the Jabber options window. Jabber also provides the ability to define a priority list for devices selection. This can be useful for a laptop user who has additional audio devices in a docking station. This can be configured in the Advanced tab in audio and video options. Profile Details When using Jabber for Windows you may see the telephone numbers in a user s WebEx profile update. As Jabber for Windows registers to UC manager it will attempt to add the UC manager registered directory number to the users WebEx Messenger profile. If your client is registered with a SIP URI the client will attempt to add this WebEx Messenger profile. The number will appear in as a work number. Unity Connection Voic WebEx Connect and Jabber for Windows are both able to integrate to Cisco Unity Connection to provide visual voice mail functionality. If you are using Unity Connection in your environment the WebEx Connect administrator will need to update the Unity Connection settings. Jabber for Windows uses HTTP protocol to connect to the Unity server where WebEx Connect used IMAP protocol. Jabber is accessing a different service on the Unity Connection server to display voic . The Unity Connection administrator may be required to make changes to the class of service used by users migrating to Jabber for Windows. In the UC configuration the Voic port should be configured as 443 for HTTPS rather than 143 for IMAP Cisco and/or its affiliates. All rights reserved. Page 11 of 11