Category Archives: 13669

Fix for Excessive Duplicate Contacts

If you’re running Lync in your environment you may notice that you have multiple duplicate contacts in your contacts list.

This issue also affects your ActiveSync mobile devices, such as the iPhone.

If you open one of these duplicate contacts, you will notice that the Notes field says the contact was added by Lync 2013.

This a caused by a bug in the Lync client, which adds a duplicate contact item every time you have do an IM with this contact.  The bug will be fixed in the next cumulative update (CU) for the Lync 2013 client.  In the meantime, here’s how you can fix it.
The duplicate contacts are stored in a contacts folder called Lync Contacts.  This folder is protected by Outlook so you can’t delete it from there.  You need to delete it from Outlook Web App, which does not treat it as protected.

  • Log into OWA and view your contacts.
  • Right-click the Lync Contacts folder and select Delete.
  • Click Yes to confirm you want to delete the selected folder and move all contents into the Deleted Items folder.  You can then sign out of OWA.
  • From the Outlook client you’ll need to empty your Deleted Items folder to finish getting rid of all the duplicate contacts.  You’ll then be free of them!

Messageware OWA Desktop Review

I don’t normally do product reviews, but I had the opportunity to work with Messageware’s new product OWA Desktop and thought I’d share my thoughts.  This software extends Outlook Web App’s functionality so that it behaves even more like the real Outlook client and integrates OWA into the Windows desktop environment.

OWA Desktop was awarded the prestigious Best of TechEd 2011 award by Microsoft TechEd attendees this year in Atlanta, GA.  Messageware, a Toronto based company, has been extending OWA functionality since 2003.  Their goal is to make OWA as close to Outlook as possible.  This makes it extremely useful for companies that can’t or don’t want to deploy a full blown Outlook client on desktop workstations.

OWA Dekstop runs in the Windows notification area whenever the user logs on and gives one click access to most OWA functions.

Right-click OWA functionality from the Windows notification area

With a single click users can open the full OWA application, compose a new email, create an appointment or meeting, change settings, etc.  Notice in the screenshot below that OWA Desktop opens like an HTA application.  There are no browser controls, such as the address bar, forward or back buttons, or browser menus.  This gives OWA Desktop a clean look and better use of screen real estate.

The OWA Desktop application

New message notifications come in two flavors.  One option uses balloon pop-ups in the notification area. Balloon pop-ups can optionally provide a text preview of the new message.  A single click opens the full message using OWA Desktop. 

Balloon pop-up with message preview

The other option displays a “View Unread” scrollable window that displays all the unread messages in the Inbox.  Here you can open an item, reply/reply all to an item, mark an item as read/unread, or open the full OWA Desktop application.

“View Unread” window pop-up

One of the other nice features is the ability for users to import and export data using OWA.  By right-clicking the OWA Desktop icon, you can import holidays for dozens of countries or import/export contacts.  This is very useful for Office 365 users.

OWA mport/export functions

The OWA Desktop MSI package is only about 6.5MB in size (much smaller than 258MB used by Outlook 2010) and is easily deployed using System Center Configuration Manager (SCCM) or Group Policy software distribution.  There are no server-side components required.

User account setup uses Exchange Autodiscover for easy setup and configuration.  You can also configure multiple OWA Desktop accounts to be open simultaneously on the same computer.  The screenshots in this article show two different colored icons in the notification area, one for each Exchange email account.  Traveling mobile users will appreciate the ease of changing timezones in Options.

Account Setup uses Exchange Autodiscover

Because OWA Desktop runs in the notification area when users login to Windows, they are unlikely to close OWA accidentally.  OWA Desktop runs in a discreet browser window so users don’t need to continually login to OWA when they close their browser.

Messageware also created an OWA Desktop Deployment Pack which allows deployment customization and branding to personalize the look of OWA Desktop.

I’ve worked with Messageware for a few years, primarily with their OWA PlusPack product for OWA 2003 and OWA 2007.  This new product provides easy access to OWA right from within Windows.  You really should check it out.

How to Enable Appear Offline Status in Lync Server

You may wish to allow users to set their status to “Appear Offline”. This was a status available by default in OCS 2007, but is not enabled by default in Lync Server 2010.

To enable the “Appear Offline” status for all users, run the following command from the Lync Server Management Shell:

Get-CSClientPolicy | Set-CSClientPolicy -EnableAppearOffline:$true

Users will need to sign out and back into Lync to see the new status for the first time.

Strangely, users are unable to sign into Lync using the “Appear Offline” status.  They must sign in first (preferably as “Away”), then set their status as “Appear Offline”.  Also be aware that this status is not available when users sign in using Exchange Outlook Web App (OWA).

How to Integrate Lync Server 2010 with Exchange 2010 SP1 OWA

Lync Server 2010 can be integrated with Exchange 2010 SP1, so that Exchange Outlook Web App can also act as a Lync web client.  Once integrated, users will automatically log into Lync when they log into OWA.  The OWA interface changes to include the following new features:

  • Sign In and Sign Out – Users can sign in or sign out of instant messaging from OWA.  Once signed in, the user will automatically sign into IM every time they sign into OWA.
  • Presence – User presence information is available for Lync users, showing a colored chicklet indicating their availability.
  • Contact List – The user’s Lync IM contact list is made available in the OWA folder pane.  Users can be added and removed, and contact groups can be managed directly from OWA.
  • Instant Messaging – Lync users can chat with other Lync users using instant messaging directly from OWA.
  • Right-Click Functionality – Right-click menus and actions are updated to include new Lync features.  For example, right-click an email address to chat with the user or add them to an IM contact list.

All of these new OWA features can be seen in the screenshot below:

An instant messaging chat session can be started from OWA by double-clicking a contact in the Contact List or right-clicking an email address and choosing Chat.

This article explains how to configure Lync Server 2010 RC integration with Exchange 2010 SP1.  I will assume that you have functional Lync Server 2010 RC and Exchange Server 2010 SP1 servers already set up.  Let’s get started.
Download and install the Microsoft Office Communications Server 2007 R2 Web Service Provider from on your Client Access Server.  This MSI package contains the installation programs to the local hard drive.  Normally it will put them in C:\Web Service Provider Installer Package, but I’ve also seen it install to a different drive.  Make note of the location it uses during installation.
The package will install the following files:
Next, download and save the OCS 2007 R2 Web Service Provider Hotfix KB 981256 from to the same C:\Web Service Provider Installer Package folder.
Download and save the Unified Communications Managed API 2.0 Redist (64 Bit) Hotfix KB 2400399 from to the same C:\Web Service Provider Installer Package folder.
If your CAS server is running Exchange 2010 SP1 on Windows Server 2008 R2, you need to download and save the UcmaRedist.msp patch in Microsoft Office Communications Server 2007 R2 Hotfix KB 968802 from  The tricky part here is that the file name (UcmaRedist.msp) is the same as the Communications Managed API 2.0 Redist (64 Bit) Hotfix KB 2400399 you just downloaded.  Just rename this file name to something like UcmaRedist-R2.msp.
Now install the following files as Adminstrator in this order:
  1. vcredit_x64.exe
  2. UcmaRedist.msi
  3. UcmaRedist.msp
  4. UcmaRedist-R2.msp, if your CAS is running on Windows Server 2008 R2
  5. CWAOWASSP.msi
  6. CWAOWASSP.msp
  7. dotnetfx35setup.exe, if the .NET Framework 3.5 is not installed on Windows Server 2008.  For Windows Server 2008 R2, install the .NET Framework 3.5.1 feature from Server Manager.
Note that the MSI and MSP packages have a limited GUI during setup and don’t indicate that they’ve installed successfully.
Next we need to configure the Exchange 2010 SP1 Client Access Server for Lync Server integration.  Run the following two commands from the Exchange Management Shell on the CAS:

$cert = (Get-ExchangeCertificate |  Where {$_.Services -ilike “*IIS*}).Thumbprint

Get-OWAVirtualDirectory | Set-OWAVirtualDirectory -InstantMessagingType OCS -InstantMessagingEnabled:$true -InstantMessagingCertificateThumbprint $cert -InstantMessagingServerName

Be sure to change the InstantMessagingServerName value in the command above to the FQDN of your Lync Server pool.

Now we need to configure the Lync 2010 RC server.  Use the Lync Server Topology Builder to add a new Trusted Application Pool, as follows:
  • Open the existing topology.
  • Expand your Lync Server 2010 (RC) > your sitename.
  • Right-click Trusted application servers and select New Trusted Application Pool.
  • Enter your CAS server or CAS array’s FQDN in the Pool FQDN field, select Single Computer Pool and click Next.
  • Select the Front End Pool for the Trusted Application Pool.
  • Click Finish.
  • Right-click the new Trusted Application Server and select Edit Properties.
  • Clear the checkbox for Enable replication of configuration data to this pool and click OK.
  • Publish the new topology.
The final step is to create a new CsTrustedApplication using the Lync Server Management Shell on the Lync 2010 RC server.  Run the following command from the management shell:

New-CsTrustedApplication -ApplicationID ExchangeOutlookWebApp -TrustedApplicationPoolFqdn -Port 9999


Be sure to change the TrustedApplicationPoolFqdn value in the command above to the FQDN of your CAS server or CAS array.

Now login to Outlook Web App and enjoy the new Lync Server goodness!

Fix for OWA always uses Light Mode for some users

This article explains the difference between OWA Light Mode and Premium Mode and why some users may only see the Light Mode client, even though they haven’t selected it at logon.
Exchange 2007 Outlook Web Access and Exchange 2010 Outlook Web App offer two different modes for viewing OWA – Premium Mode, with all the bells and whistles that Internet Explorer can muster, and Light Mode, which provides fewer features and is sometimes faster.  You would usually use the Light client if you are on a slow connection or using a computer with unusually strict browser security settings.
If you are using a browser other than Internet Explorer 6 or later for OWA 2007, you can only use the Light client.  OWA 2010 supports the full Outlook Web App experience (aka Premium Mode) on Internet Explorer 7 and some other browsers on Windows, Mac, and Linux computers.  To check out all the supported browsers and operating systems for OWA 2010, click here.

Here’s a comparison between the Outlook Web Access 2007 Light and Premium clients:

And here’s a comparison between the Outlook Web App 2010 Light and Premiun clients:
Normally, users will default to use the Premium Mode client if they are using IE6 or better for OWA 2007 or IE7 or better for OWA 2010.  However, you may hear complaints from some users that they always get the Light Mode client, regardless of whether they selected to use it or not when they logged in.  This happens if the user selected to use “the blind and low vision experience” when logging into OWA for the first time.
To disable this mode and allow IE to use the Premium Mode, have the user login to OWA and open Options in the upper right corner.  Then select Accessibility and clear the checkbox for Use the blind and low vision experience, as shown below.
Now have the user sign out of OWA and sign back in.  They should be using OWA Premium Mode, providing they are using a supported browser.

How to add a "Sign In Again" button to the Exchange 2010 OWA Sign Out page

Note: Click here to view how to add the Log On Again button to Exchange Server 2007.

By default when you click “Sign Out” in OWA 2010, Exchange 2010 directs you to a page that explains that you have successfully logged off from Outlook Web Access.  The only button available, “Close Window“, closes the existing browser window or tab.  This article explains how to add a “Sign In Again” button to the logoff.aspx page, as shown below:

To add the Sign In Again button, follow these steps on each Exchange 2010 Client Access Server (CAS):

  • Logon to the CAS using a local Administrator account.
  • Using Windows Explorer, navigate to the  %ProgramFiles%\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth folder and make a copy of the logoff.aspx file for backup.
  • Edit the logoff.aspx file using Notepad.
  • Use Find to search for the word logoffclose.  In Exchange 2010 SP1 beta this will be line 123.
  • Insert the following code before this line, as a single line:

<input id=”btnCls” type=”submit” class=”btn” title=”Click here to log on again” value=”Log On Again” onclick=”window.navigate(‘‘)” onmouseover=”this.className=’btnOnMseOvr'” onmouseout=”this.className=’btn'” onmousedown=”this.className=’btnOnMseDwn'”>

  • Edit the line above to use your company’s URL for OWA. 
  • Save the logoff.aspx file.
  • Copy the new logoff.aspx file to the same file path on all your 2010 CAS servers.

Remember that applying any Exchange 2010 Service Pack or Update Rollup to your CAS servers will overwrite the login changes you made, so create a copy of the edited logoff.aspx file to reapply the Logon Again button after the update.  Also know that Service Packs and Update Rollups could possibly include changes to the logoff.aspx page, so you may need to follow these steps again to edit the new page included in the update.

No Access to Online Archive in Outlook 2010 Professional Plus?

It seems that you cannot access the Exchange 2010 Online Archive using Microsoft Outlook 2010 in the MSDN or TechNet versions of Microsoft Office Professional Plus 2010 RTM.  This may be due to the product IDs provided on MSDN or TechNet.

The Online Archive is an Exchange 2010 feature that creates an optional associated archive mailbox for a user.  Exchange move policies can be created to move content into the archive based on various critieria.  Exchange 2010 RTM hobbled Online Archives by requiring that they exist in the same database as the associated mailbox, making their use limited.  Exchange 2010 SP1 will improve Online Archives by allowing you to create remote Online Archives on a different server (perhaps with slower, cheaper storage).  The Online Archive feature requires Exchange 2010 Enterprise Client Access Licenses (CALs).

The images below show the behavior in both Outlook 2010 Professional Plus (on the left) and Outlook Web App 2010 (on the right).  Note the lack of of the Online Archive in Outlook.

I’ve confirmed this on several machines, running both Windows 7 x64 and Windows Server 2008 R2.  I’ve completely uninstalled and reinstall Office 2010 Professional Plus with no effect.  I also confirmed there is no change when using Outlook in Cached Exchange mode or online mode.

If you notice different behavior, I’d love to hear from you.  Leave a comment below.