I would suggest installing Office on the GI and Jabber as an appstack.
I have seen Outlook integration working with Jabber in this situation.
Do make sure that your packaging machine has Office installed when you package Jabber.
Also, it could be that the Outlook integration of Jabber is being created in the HKCU key, Appstacks do not add that infomation into the appstack. If so, use a tool like DEM to add the Add-in load behaviour registry key.
Installing office is not an option. We have Office, Visio and Project and that would mean we would have to have four separate images and 4 different pools for people based upon what Office they get. We just aren't going to do that.
Also, Jabber Outlook Integration actually works it just throws an error
This only happens in 12.x version of Jabber. 11.x it works fine. The keys needed are there since it actually works, but it throws the error.
1 person found this helpful
So we found the solution. There are two things that need to be done. First you need to reboot the provisioning machine after install of Jabber and before finishing the provisioning or possibly creating the following registry key by hand:
Next you also have to make sure you have these keys set/captured via DEM
[HKEY_CURRENT_USER\Software\IM Providers\Cisco Jabber]