In this release, Group Chat Server and Group Chat have been rebuilt to be compatible with the Microsoft Lync Server 2010 and Microsoft Lync 2010 code bases: Unified Communications Client Platform (UCCP) and Microsoft Unified Communications Managed API (UCMA) 3.0. Setup versioning has been updated to support Group Chat Cumulative Updates (CUs) and to help make upgrades in the future more seamless.

A new Microsoft System Center Operations Manager (formerly Microsoft Operations Manager) Management Pack for Group Chat Server supports health monitoring for a Group Chat installation and these critical Group Chat Server services:

• Channel service
  
  
• Lookup service
  
  
• Compliance service
  
  

The new Group Chat Server System Center Operations Manager Management Pack uses both Windows event logs and the state of the services.

For details about downloading the Lync Server 2010, Group Chat Monitoring Management Pack Group Chat, see “Lync Server 2010 Group Chat Monitoring Management Pack” at http://go.microsoft.com/fwlink/?LinkId=209888.

Content—for chat channel names and in-chat content—can now be entered in Unicode. You can name channels in full UTF-8, and users can participate in chat rooms and type messages in Chinese, Arabic, or other UTF-8 languages.

To preserve disk space, Group Chat does not generate log file entries, by default. You can change the logging level by changing the level value in %appdata%\Microsoft\Group Chat\Group Chat Client\GroupChatConsoleLogger.xml from “none” to “fatal,” “critical,” “error,” “warn,” “info,” “debug,” or “trace.” For example:

	Copy Code
<log4mgc> <file value="%userprofile%\tracing\GroupChatConsole.log" /> <maximumFileSize value="20" /> <!-- in MB, 2047 max--> <maxSizeRollBackups value="10" /> <filemode value="append" /> <level value="TRACE" /> </log4mgc>

Ego filtering includes the following enhancements to ignore common terms in user names. By default, the ego filter excludes any text between and including the following characters:

• “(” and “)”
  
  
• “[” and “]”
  
  
• “<” and “>”
  
  
• “{” and “}”
  
  

Note:
This affects only the default ego filter. You can still customize the filter.

The ego filter no longer triggers whenever you type the letters “IT”; for example, “Sara Davis (IT Dept)”. The text can be excluded only if the “words in brackets” are closed. For example:

• “Sara Davis (IT Dept)” becomes “Sara Davis”
  
  
• “Sara Davis (IT Dept” becomes “Sara Davis IT Dept”
  
  
• “Sara Davis [IT Dept (HR Unit)” becomes “Sara Davis IT Dept”
  
  

The Lync 2010 Group Chat user interface and its accompanying icons, including its emoticons, have been upgraded and resized to match the Lync 2010 user interface.

When Lync 2010 Group Chat is not the primary instant messaging (IM) and presence client and is running side-by-side with Lync, Group Chat will not violate the Lync Server 2010 presence privacy mode. For details about Lync Server presence privacy modes, see Administering Group Chat Server in the Operations documentation.

The Lync Server presence privacy mode for Group Chat operates under the following conditions:

• Stop Group Chat from doing any access control entry (ACE) bootstrapping when running side-by-side with Lync.
  
  
• If Group Chat already stops IM, presence, and Buddy List operations when running with Lync, stop bootstrapping as well in this mode.
  
  
• Presence privacy mode does not work if Group Chat is running in IM and presence mode.
  
  
• When running in presence privacy mode, Lync must be configured in its IM and presence disabled mode, or it reverts out of presence privacy mode.
  
  

Note:
Group Chat should always be running on the same computer as Lync for it to work side-by-side in presence privacy mode. You can run Group Chat without Lync and still run Lync in presence privacy mode on another computer, as long as you keep IM disabled on the computer running Group Chat. We do not recommend this scenario.