The tables column on the left hand side will get populated.Ĭlick Transform and then Apply Transform. Open the MSI file using Microsoft Orca by clicking File then Open. Extract both zip files under a common folder. You will need to download and install Microsoft Orca for the customisation process.įirst download the Jabber version you want to customise including the administrator package. But the customisation should work with version 9.0 or higher. Svr hostname = IP or FQDN of your Cisco Unified Presence serverįor the purposes of this post I will be customising the latest version of the Jabber application, version 10.5. Svr hostname = IP or FQDN of your Cisco Unified Communications Manager serverĬisco Unified Communications Manager Version 8.x Depending on your version of Call Manager (in our environment we use 9.1), add the following SRV records, some environments may require both records:Ĭisco Unified Communications Manager Version 9.x You need to add a SRV record on your local DNS server for the Auto Discovery to work. The solution was to customise the MSI file and prevent the installed Jabber application from trying to authenticate against a Webex Connect server. Since there was no WebEx Messenger subscription, the login process was failing.

The deployment was successful however we ended up getting a lot of complaints from the users about not being able to login.Īfter some troubleshooting together with support, we established that the GPO deployed Jabber application was trying to authenticate against a WebEx Connect server on the cloud rather than the Unified Communication server based locally in the LAN. We deployed Cisco Jabber via Microsoft group policies using the standard MSI file provided by Cisco. Last year we moved on to a Cisco based telephony infrastructure and installed Cisco Jabber on our client machines.

Install cisco jabber for windows