Product Version: 5.7
Expires on: 365 days from publish date
Updated: March 27, 2014
Cisco Communicator ( Jabber ) - settings not captured
After logging on for the second time you can not see changes made to the Jabber in previous session.
Most common issue is that the software does not run auto-authentication settings.
There are several items that should be in place to make sure Jabber keeps the settings.
- Redirect all AppData to a mapped drive (or VHD). Alternatively, It is possible to capture the settings with portability.
- No Jabber profile in the base (just an installation without per-user customization)
- App Launcher rule - If needed, it is possible to run Jabber every time user loggs on, but it will require a "Application Launcher" rule to achieve that (this setting can not be captured).
The below instructions show how to accomplish these 3 tasks.
Redirect AppData to either "mapped drive" or "VHD"or Portability
OPTION 1: Redirecting to a VHD drive
OPTION 2: Redirecting to a Mapped Drive
OPTION 3: Using Portability (Click on "Portability Management" and click on a red "create" button. Add the vales underneath the image into a red-marked area.)
Merge User Profile AppData\LocalLow\Microsoft
Merge User Profile AppData\Local\JabberWerxCPP
Merge User Profile AppData\Local\Microsoft\Windows\Credentials
Merge User Profile AppData\Local\Temp\JabberPRT.ini
Merge User Profile AppData\Roaming\Microsoft\Credentials
Merge User Profile AppData\Roaming\Microsoft\Protect
Merge User Profile AppData\Local\Cisco\Unified Communications\Jabber
Merge User Profile AppData\Roaming\Cisco\Unified Communications\Jabber
Exclude User Profile AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs
Exclude User Profile AppData\Local\Cisco\Unified Communications\Jabber\CSF\Voicemail
2. Nobody should log on to Jabber after installation of the Jabber on the gold image. That will prevent defaulting settings on other user's desktops.
3. Application Launcher rule - Without the Application Launcher rule the user will have to run jabber manually each time he logs in unless he/she gets the same machine at next logon. Therefore, if needed the Application Launcher rule can run the software each time user logs in.
C:\Program Files\Cisco Systems\Cisco Jabber\CiscoJabber.exe (32-bit)
C:\Program Files (x86)\Cisco Systems\Cisco Jabber\CiscoJabber.exe (64-bit)
Timing: "Run Asynchronously"