Tuesday, May 22, 2012

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.

Lync GC Fed - Manage

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

Lync GC Fed - Create group

Name the group and select OK:

Lync GC Fed - Create group2

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:

Lync GC Fed - Add user

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:

Lync GC Fed - Manage user

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:

Lync GC Fed - 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:

Lync GC Fed - add group to room

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…

Lync GC Fed - join menu

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

Lync GC Fed - edit domain

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

Lync GC Fed - domain search

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:

Lync GC Fed - chat room

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:

Lync GC Fed - web url

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

Tuesday, May 1, 2012

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:

Lync DTMF - Outlook invite - markup

Topology Builder:

Lync DTMF - TB URL - markup

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

Lync DTMF - default - markup

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

Lync DTMF - default - PS

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

Lync DTMF - PS change

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

Lync DTMF - change - PS

Lync DTMF - web change

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

Monday, April 16, 2012

Exchange 2010 SP2 Update Rollup 2 Available

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

This will take you Exchange version up to 14.2.298.4

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

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.

Exchange 2007 SP3 Update Rollup 7 Available

An update for Exchange 2007 SP3 has just released and can be downloaded at: Exchange 2007 SP3 Update Rollup 7 Download

This brings the build number to: 8.3.264.0

  • For a description of all the included fixes, see KB 2655203

If you have a clustered environment, please see this article: Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers

Remember to disable or remove all third party software during the upgrade (like antivirus, backup agents, disclaimers, etc.)

Tuesday, April 10, 2012

Two Great FREE Lync Training Opportunities

LyncServer-logo

Microsoft is sponsoring two different Lync virtual training sessions.  This is a great opportunity to become more familiar with Lync and to get certified.  Here are the details…go register.

Deploying, Configuring, and Administering Microsoft Lync Server 2010

When: April 17-19, 9:00A – 4:00P PST

More Info and Registration

Planning and Designing a Microsoft Lync Server 2010 Solution

When: April 24-26, 9:00A – 4:00P PST

More Info and Registration

Tuesday, April 3, 2012

Three Ways to Determine What Version of Lync Server Components are Installed

Microsoft releases updates to Lync components periodically and only updates the version level of the components that actually get the update.  Because of this, various components of your Lync infrastructure will be running at different versions.  To help with keeping the components at the latest versions, Microsoft has released a single tool to perform updates to your Lync environment.  If you download and run the LyncServerUpdateInstaller.exe, this will check your Lync server and install the updated components that are needed.  Note, that you will need to periodically download the latest version of the installer as the download doesn’t actively check for updates.

So how do we determine the exact versions of the Lync components that we are running?  There are basically three different ways:

  1. Powershell
  2. Run the LyncServerUpdateInstaller.exe tool
  3. Check Windows “Programs and Features”

Powershell

There isn’t a great native one-liner within Lync to gather this information.  You would think running Get-CsServerVersion would return this, but it only returns the base version level:

Lync Version - Get-CsServerVersion

Premal Gandhi blogged a while back about a powershell command that can be used to find this information by using WMI to query the different Lync components.  A commenter to the post modified the original command that I am using below.  The versions can be found by running:

Get-WmiObject –query ‘select * from win32_product’ | where {$_.name –like “Microsoft Lync Server*”} | ft Name, Version –AutoSize

Lync Version - PS Table

This will list all components associated with Lync Server, even the tools installed like the Resource Kit and Best Practices Analyzer.

Run the LyncServerUpdateInstaller.exe

Why not use the tool itself to see what components and versions are installed on a server?  When running the LyncServerUpdateInstaller.exe, it will list what versions are installed and what versions need to be updated.  Sure, this tool can be used to actually update the components, but can also be used just to see what versions are installed.

Lync Version - installer - markup

Check Windows “Programs and Features”

You can also see what versions of Lync components are installed by opening “Programs and Features” within Windows.  By scrolling down to the “Microsoft Lync Server 2010” section you can view the version installed.

Lync Version - Programs and Features - markup

Hopefully this helps you get some clarification on what exact versions of Lync components are installed in your environment.

Sunday, April 1, 2012

Lync March 2012 Server and Client Updates Released

This round of updates came quicker than normal.  The Lync team has released server and client updates for March 2012. Here are all the details of what was updated this round:

Server Updates (7577.197) – Download – KB 2493736

Note: Use the cumulative LyncServerUpdateInstaller.exe to install the updates to make sure all needed updates are applied.

Clients (7577.4087)