We have been facing a weird issue since last november.
Users who use Office 2013 Home and Business cannot search their personal contacts through J4W (All versions tested).
When I install Professional Plus version to test, the search works ok.
I opened a case with tac on november and by now we have no idea of what could be going on.
Anyone has any idea?
Any help will be welcome.
I see that this problem still has no response. One of my users is experiencing the same problem.
We have installed Jabber 9.7.2 on a Windows 8 machine with Outlook 2013 installed. When searching in Jabber it does not return any results for personal Outlook contacts.
C2C (click-2-call) functionality still works in Outlook 2013 so the plug-in must be working in some way.
What version of Jabber are you using? I am having the problems and I have 8.1 64bit and outlook 2013 64bit.
Outlook is updated to 15.0.4615.1002
Windows is 6.3.9600 Build 9600
Alexander, I checked the registry key and that is fine as per your screenshot.
I might have to run up a new pc as per your spec's Sirk and see if that makes a difference.
I am starting to wonder if it's some type of regional setting on the PC or maaybe a slight difference in our xml config.
This is my jabber-config.xml being downloaded from the Call Manager:
<?xml version="1.0" encoding="UTF-8"?>
<SearchBase2>OU=User policy OU Laptops,DC=jarvisnet,DC=com,DC=au</SearchBase2>
<SearchBase3>OU=User Policy OU PC,DC=jarvisnet,DC=com,DC=au</SearchBase3>
i think its not the config file.. i use at the moment a users file on the client and all config are set correctly on another pc's works fine.
I hope the Tac can locate the error, but i think its not so easy.
** Update ** I have get the Information from TAC that CSCup00769 Enhancement to support Outlook 2013 Home & Business edition for Jabber
Did you get a response from your TAC? Also that link you have posted needs fixing.
Just installed Jabber 10.5 for windows and still isn't working, are you running domain PC's?
Mark Hamilton suggested
But i already have this in my config and the clients are getting it.
I updated my jabber-config.xml file on the TFTP server to include the following:
The affected users have reported that the issue has been resolved.