Consider the following scenario:
- You install Microsoft Office Communications Server 2007 R2, Group Chat and Office Communicator 2007 R2 on a terminal server.
- You configure the DisableIM Group Chat Group Policy to only allow users to use Office Communicator to send instance messages (IM) on the terminal server.
- User A and user B use the Terminal Services or Remote Desktop Protocol session to log on to the terminal server.
- User A signs in to an Office Communications Server 2007 R2, Group Chat client and does not sign in to Office Communicator R2.
- User B signs in to an Office Communications Server 2007 R2, Group Chat client and an Office Communicator R2 client.
- Both user A and user B join a chat room in Group Chat.
- User A right clicks user B in the chat room, and selects Send an Instant Message.
This issue occurs because the API that is used by the Group Chat console detects that there is already a running the Communicator.exe process on the terminal server. Therefore, the Group Chat console does not start a Communicator.exe process in user A's session.
Article ID: 2653953 - Last Review: Jan 19, 2012 - Revision: 1