Exchange 2010 SP2 Update Rollup 3 Available

An update for Exchange 2010 SP2 has just released and can be downloaded at: Exchange 2010 SP2 Update Rollup 3 Download.

This will take you Exchange version up to 14.2.309.2

For a description of all the included fixes, see KB 2685289

For those of you running DAGs, please see the following article: Applying Updates to Exchange 2010 SP1 and SP2

If you are running third party products (like anti-virus, etc), it is important that you disable them before updating.

More information can be found on the Exchange Team Blog site.

Enabling Federated Group Chat Rooms

Ohhhh….Group Chat.  You get ignored sometimes.  Group Chat can be a powerful add-on to the Lync solution.  I call it an add-on because of the disconnected experience both from a user and server perspective (hopefully this will get better in the future).  But let’s not go into that today.

This post assumes that you have a functioning Group Chat deployment and will describe how to enable specific chat rooms to allow for federated user access.  This will enable specific users and domains outside of your organization the ability to participate in your internal Group Chat solution.  Note: You must have a functioning Edge Server deployment for federation to work with Group Chat.

Step 1 – Create Federated Group

You must manually configure a federated group and specify federated users for this group.  This can be done by clicking the File –> Manage Users… from the Group Chat Admin Tool.

This will open the Manage Users and User Groups tool.  Once the tool is open, click File –> Create a New Federated User Group…

Name the group and select OK:

Once the group is created, click on the group and right-click in the Members tab area and select Add User…  Fill out the federated user information:

Once the user is created, you can right-click on the user and select Manage User… This will enable you to change any user information, disable/enable the user, and change file upload permissions:

Step 2 – Add Federated Group To Chat Room

Now you can go back to the main Group Chat Admin Tool.  You will notice that the newly created group is added automatically to the Root Scope:

This will enable you to add the FederatedUsersGroup to the desired chat rooms.  Navigate to the chat room and click on the Members tab.  Then click the Add button and add the group:

Once the added group shows in the Members tab, click Apply.

Step 3 – Federated Users Adds Chat Room To Client

Once all administration is complete, the federated user can now add the chat room to their client.  If invitations were enabled, then the user should receive a typical Group Chat invite.  If not, the user can search for the room manually.  This can be done by adding the federated domain to the search list in the client.  Click File –> Join a Chat Room…

On the Domain drop-down, click Edit Domains and add the federated domain to the list:

Now you will be able to search for available rooms in the federated domain.  Find the chat room and select Join:

Now you will have the federated chat room in your list of rooms.  You will notice that the room is designated with the federation globe icon much like federated contacts within the Lync client:

Extra Notes

If you want federated users to be able to upload/download files within the chat room, you need to make sure that the URL associated with the Web Service is published via reverse proxy and has a trusted/public certificate associated with the IIS bindings.  You can view the URL by opening the Group Chat configuration tool and selecting the File Repository tab from the System Wide settings:

I hope that this post helps you set up federation for your Group Chat rooms.

Changing DTMF Control Mappings for Audio Conferencing in Lync

Many companies are learning the extreme value of Lync these days.  One of the easiest ways to gain immediate ROI is to replace your hosted audio conferencing service with Lync dial-in conferencing.  If you have been a user of any hosted service, you are most likely familiar with managing the roster meeting participants through DTMF key mappings.  Most likely the Lync DTMF mappings are not going to match exactly what you are used to and you may need to adjust some of the key mappings.

From the Outlook invite, users can view the dial-in conferencing information by clicking the “Find local number” link or by browsing to the Simple URL that was assigned in the Lync topology.

Outlook Invite:

Topology Builder:

By clicking the references above, the Dial-in Conferencing web Page will show the default DTMF mappings:

Administrators can view and configure the current mappings from the Lync Management Shell.  To view the current configuration, run Get-CsDialInConferencingDtmfConfiguration

Note, you can have different DTMF configuration mappings defined on a Global or Site scope level.  To create a site scope for DTMF mappings, use the New-CsDialInConferencingDtmfConfiguration cmdlet.

An administrator can change the mappings by using the Set-CsDialinConferencingDtmfConfiguration cmdlet.  The following are valid configurations:

• Command Character: # or *
• Commands: single digit 0-9

In my example, I am going to change the Mute/Unmute command to “2” and the Admit All command to “0”.  I will also change the Command Character to #.  The following command will make my configuration settings:

Set-DialInConferencingDtmfConfiguration –CommandCharacter “#” –MuteUnmuteCommand 2 –AdmitAll 0

Now the new configuration can be seen in the powershell or Dial-in conferencing web page:

This post shows how to change the default DTMF mappings used for managing audio conferences.