Let me preface this post with saying: running Office Communicator or Lync on Citrix is not ideal. Why? It's a presence application. Unless you're working directly in OCS or the Lync client, your session on the XenApp server is idle, there fore your 'available' or 'idle/away' indicators may be inaccurate.
That being said, it can be handy to have your IM client readily available on Citrix.
I had been running Office Communicator 2007 R2 successfully, but Lync 2010 was giving me error messages:
"Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Office Outlook and set it as the default mail client."
I had installed Outlook 2010 and launched it, checked the default mail client, all to no avail.
The problem? I had actually published the wrong exe.
This Citrix forum post tipped me off to the mistake. The correct application? "C:\Program Files (x86)\Microsoft Lync\communicator.exe"
http://forums.citrix.com/thread.jspa?messageID=1715879
Showing posts with label OCS. Show all posts
Showing posts with label OCS. Show all posts
Tuesday, February 19, 2013
Wednesday, October 31, 2012
Office Communicator 2007 R2: Tempermental with Patches
I run Office Communicator 2007 R2. It has been a bit finicky for me as a Microsoft security patch can break it (go figure).
If you install MS09-056 (aka KB974571), you will get an error that the Front-End service will not start with error code 1008124893. That's easy enough to fix, uninstall the hotfix and restart, and the problem is gone. I inadvertently applied that patch more than once, but a second mistake got me in the habit of avoiding that patch and keeping the server running.
When it came to apply Windows Server 2008 R2 Service Pack 1, however, the issue again returned. How could I remove the hotfix when it was a part of a service pack?
Googling the matter again, I came upon an alternative solution that worked for me.
http://support.microsoft.com/kb/982021
Item 5a includes file OCSASNFix.exe. This makes a quick registry fix. I have to confess that I originally manually applied the registry fix, and didn't get the desired result. Running this file, however, restored me to good working service.
If you install MS09-056 (aka KB974571), you will get an error that the Front-End service will not start with error code 1008124893. That's easy enough to fix, uninstall the hotfix and restart, and the problem is gone. I inadvertently applied that patch more than once, but a second mistake got me in the habit of avoiding that patch and keeping the server running.
When it came to apply Windows Server 2008 R2 Service Pack 1, however, the issue again returned. How could I remove the hotfix when it was a part of a service pack?
Googling the matter again, I came upon an alternative solution that worked for me.
http://support.microsoft.com/kb/982021
Item 5a includes file OCSASNFix.exe. This makes a quick registry fix. I have to confess that I originally manually applied the registry fix, and didn't get the desired result. Running this file, however, restored me to good working service.
Subscribe to:
Posts (Atom)