Lync 2013 Client and Group Chat 2010–Co-existence Issue

An interesting co-existence problem came up yesterday. It appears that there is a known issue with the Lync 2010 client and Windows 8, where it is possible to fire off multiple instances of communicator.exe, which then causes the Lync 2010 client not to even launch.

Well, the Lync 2013 client has some new coding that prevents multiple instances from starting. Now, this is a bit interesting because, in the past, OCS/Lync clients have never been backwards compatible. In case of Lync 2013, it does work with Lync 2010. Until… you add in Group Chat 2010 in the mix.

The Lync 2013 client will, as a single client, work with Lync Server 2013 and Persistent Chat. One of the nice selling points is that running 2013 means reducing the need for a separate chat client.

Well, the thought was, why not deploy Lync 2013 to connect to Lync Server 2010, andclip_image002 continue using the Group Chat 2010 client to connect to the Group Chat server? Well, the answer is that the Group Chat 2010 client doesn’t recognize that the Lync 2013 client is running and this causes the Group Chat 2010 client to not only display all rooms, but also display all contacts as shown here. Yes, I had to hack this one up to protect the innocent. Smile

Anyway, as you can see from the image, it is possible to send/receive IMs in the Group Chat 2010 client, even though the Lync 2013 client is also running. What is the answer? I have no idea…

Advertisements
This entry was posted in Lync. Bookmark the permalink.

One Response to Lync 2013 Client and Group Chat 2010–Co-existence Issue

  1. Peter Davis says:

    Answer: Create a registry key if necessary for Computer\HKEY_CURRENT_USER\Software\Policies\Microsoft\GroupChatConsole\Permissions, and set a DWORD DisableIM=1. Note that it disables all IM functionality in Group Chat since it still can’t “see” Lync 2013. (Double clicking a contact in a chat will fail.)

    Answer adapted from here. The original question was how to *make* Group Chat be the default IM client (who would want that??? It’s awful!). The difference is just setting the DisableIM=1 instead of 0.
    https://blogs.technet.microsoft.com/nexthop/2011/07/15/how-to-make-lync-group-chat-client-the-preferred-im-client/

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s