Category Archives: 13173

How to delete duplicate Lync Contacts or Lync Contacts folders

A bug in previous versions of the Lync 2013 client caused Lync contacts to be duplicated in the Exchange Lync Clients folder. This makes it very annoying to work with contacts in Outlook, OWA, and mobile devices.

I wrote in an earlier article, Fix for Excessive Duplicate Contacts, that describes how to delete these contacts or folders using OWA or earlier versions of Outlook. This was possible because these older versions did not respect the flag that defines the Lync Contacts folder as a protected folder, like Inbox or Drafts.

You could use MFCMAPI to delete protected folders, as shown below, but this can be cumbersome if you have to do it to many mailboxes — not to mention the fact that you need to grant yourself full access to the target mailbox(es).

A better solution is to have the end-users do it themselves using OWA in Light mode. OWA Light bypasses the protected folder check and allows end users to delete some or all of the Lync contacts, or the entire Lync Contacts folder itself. The best part is that this works from all versions of OWA, even Office 365!

All you need to do is send a URL to the end-users to login to OWA Light with the steps to delete the folder or contacts:

Replace with your organization’s OWA FQDN, if necessary. By following this specially crafted URL, users can enter OWA Light to clean it up without affecting their current OWA Premium experience.

From OWA Light select the Contacts folder on the left pane. To delete the duplicate Lync Contacts folder click the link for Manage Contacts Folders, then click the Choose folder to delete drop down list and delete the duplicate folder.

If the user wants to delete Lync contacts from an existing folder, select the Lync Contacts folder and use the checkboxes to select them or use the checkbox at the top to select all the contacts displayed. Then click Delete.

Hopefully this will help those of you who were unable to delete these duplicates because you were running a newer version of Outlook 2013 or OWA. Special thanks to Greyson Mitchem for the tip.

Does your environment need an Exchange 2013 Edge Transport server?

I was asked to write an article for my friends at ENow Consulting, “Does your environment need an Exchange 2013 Edge Transport server?”  The standard consulting answer applies: “It depends.”

If you’re wondering if an Exchange Edge Transport server makes sense in your Exchange environment, I encourage you to head over to the ENow Consulting Blog to read the article.

SMTP Firewall Requirements for Exchange Online

Most of my Office 365 engagements are hybrid projects connecting Office 365 with Exchange on-premises, and most are with larger companies concerned with securing the hybrid deployment.

Exchange Online Protection servers send SMTP emails using a TLS connection usually to the hybrid or Edge Transport server to enable mail flow between cloud and on-prem users. Microsoft does not support any sort of SMTP gateway or appliance between EOP and the Edge or hybrid server. For this reason, customers normally have to open TCP port 25 on the firewall to the hybrid server from the Exchange Online Protection servers.

Companies can secure this SMTP traffic by configuring the perimeter firewall to allow inbound TCP 25 traffic only from Exchange Online Protection servers to the hybrid or Edge servers.

I’ve seen a number of articles that list the public IP addresses used by EOP to send SMTP emails to on-prem customers, but the one true list is maintained in the article, Exchange Online Protection IP Addresses. Currently, this article lists seven IPv4 blocks and one IPv6 block for SMTP delivery to on-prem:

  • 2a01:111:f400:7c00::/54
Microsoft tries hard to not make changes to this list, but if they do they will update the article. It’s important for firewall admins to know that EOP does not use URLs for root domain routing (also known as Top-Level Domains, or TLDs). You must use the IP addresses listed in the article above.

Up until April 2014, Microsoft used many other IP addresses to send emails from Office 365 tenants to on-prem customers. This is because they maintain another set of IP addresses for something called the High Risk Delivery Pool, which is used to protect the production Exchange Online namespace from “spammy” senders. EOP no longer uses the High-Risk Delivery Pool when sending emails between the customer’s tenant and their on-prem servers.

It’s nice to know that we now have a single source to point to when configuring firewalls for Office 365.

Reporting Outlook Client Versions Using Log Parser

I’m doing a little cross-pollination today. Chris Lehr, one of my colleagues at ExtraTeam, worked up a Log Parser script that produces a report showing all the clients versions connecting to Exchange.  This is very helpful to show which clients are running Office versions in your organization that should be updated prior to migration.  Check out his blog post here.

Outlook Client Version Report

Clients will always get the best experience using the latest version of Office, currently Office 2013 SP1. The best practice is to always update your clients with the latest cumulative update prior to migration. this is especially true when you’re migrating to Office 365, since most updates pertain to Office 365, Exchange Online, and Exchange 2013 compatibility.

If you find that you need to upgrade clients to a new version of Office, I recommend that you install the x86 version of Office to provide the best compatibility with add-ons and third-party products. Some customers think they need to install Office x64 on Windows x64 operating systems, but that’s not the case. See 64-bit editions of Office 2013 for details on when it makes sense to install Office x64.

If you’re an Office 365 customer, I strongly recommend checking out using the Office 2013 ProPlus software deployment that’s most likely part of your Enterprise license. This version of Office 2013 can be installed on up to 5 PCs, iPads, tablets, etc. and is always up-to-date since it’s a cloud-managed service.

Fix for ASP.NET 4.0.30319.0 – 3005 Event message: An unhandled exception has occurred on Exchange 2013

I noticed after installing Windows Updates the following warning in the
Application Event log of all Exchange 2013 SP1 servers (abbreviated for

Event 1309, ASP.NET 4.0.30319.0

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          5/3/2014 9:31:25 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 5/3/2014 9:31:25 AM
Event time (UTC): 5/3/2014 4:31:25 PM
Event ID: 20e50da04e9745e1a73bf21fa1dbb509
Event sequence: 2
Event occurrence: 1
Event detail code: 0

Application information:
    Application domain: /LM/W3SVC/3/ROOT/owa-3-130436082719776031
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: EX2013-1

Process information:
    Process ID: 6068
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM

Exception information:
    Exception type: MapiExceptionIllegalCrossServerConnection
    Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring
mailbox [] with application ID [Client=OWA] is not allowed to make cross-server
calls from [] to []

connectionInfo, String mailboxDescription)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore
linkedStore, Boolean unifiedSession)

Request information:
    Request URL: https://localhost:444/owa/proxylogon.owa
    Request path: /owa/proxylogon.owa
    User host address: ::1
    User: contoso\SM_ce56bab178eb42fda
    Is authenticated: True
    Authentication Type: Kerberos
    Thread account name: NT AUTHORITY\SYSTEM

Thread information:
    Thread ID: 15
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at
connectionInfo, String mailboxDescription)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore
linkedStore, Boolean unifiedSession)

The text highlighted above steered me toward the Exchange Health Monitoring
Mailboxes, so I ran Get-Mailbox -Monitoring and got the following results:

Name                      Alias                ServerName      
—-                      —–                ———-      
HealthMailbox9a621ae8e… HealthMailbox9a62… ex2013-2         Unlimited
WARNING: The object Exchange System Objects/Monitoring
Mailboxes/HealthMailbox9a621ae8e6f341638c0c2161affa7645 has been corrupted, and
it’s in an inconsistent
 state. The following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.
HealthMailbox1cd7a25f1… HealthMailbox1cd7… ex2013-2         Unlimited
HealthMailboxde79dfaa0… HealthMailboxde79… ex2013-2         Unlimited
WARNING: The object Exchange System Objects/Monitoring
Mailboxes/HealthMailboxde79dfaa09604ffd8578527c2d3ffab1 has been corrupted, and
it’s in an inconsistent
 state. The following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.
HealthMailbox5e5bf093c… HealthMailbox5e5b… ex2013-2         Unlimited
HealthMailbox79f8d5d0e… HealthMailbox79f8… ex2013-2         Unlimited
WARNING: The object Exchange System Objects/Monitoring
Mailboxes/HealthMailbox79f8d5d0e02443d2a6acdc60bd0a026e has been corrupted, and
it’s in an inconsistent
 state. The following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.
HealthMailbox693969aae… HealthMailbox6939… ex2013-2         Unlimited
HealthMailboxab01377ba… HealthMailboxab01… ex2013-2         Unlimited
WARNING: The object Exchange System Objects/Monitoring
Mailboxes/HealthMailboxab01377bae994825ba08d083552e196e has been corrupted, and
it’s in an inconsistent
 state. The following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.
HealthMailbox7561b21db… HealthMailbox7561… ex2013-2         Unlimited
WARNING: The object Exchange System Objects/Monitoring
Mailboxes/HealthMailbox7561b21db2c642778177f4ab0a2be350 has been corrupted, and
it’s in an inconsistent
 state. The following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.
HealthMailboxb337fe270… HealthMailboxb337… ex2013-2         Unlimited
HealthMailboxfd8b0f99f… HealthMailboxfd8b… ex2013-2         Unlimited
HealthMailbox739cff7e6… HealthMailbox739c… ex2013-2         Unlimited
HealthMailboxd8337c5a1… HealthMailboxd833… ex2013-2         Unlimited
HealthMailboxa990ff65c… HealthMailboxa990… ex2013-1         Unlimited
HealthMailbox91e52135c… HealthMailbox91e5… ex2013-1         Unlimited
HealthMailboxf351943c2… HealthMailboxf351… ex2013-1         Unlimited
HealthMailbox23eb6e495… HealthMailbox23eb… ex2013-1         Unlimited
HealthMailbox1821ba284… HealthMailbox1821… ex2013-2         Unlimited

Besides the fact that some of the Health Mailboxes were missing the mandatory
Database parameter, there were far too many Health Mailboxes. The easy way to
correct this is to delete all the Exchange Health Mailboxes and recreate them.

Open Active Directory
Users and Computers and enable Advanced View. The Health Mailboxes are located under Microsoft Exchange System Objects \ Monitoring Mailboxes. Select all of the HealthMailbox objects, delete them, and replicate AD.

Microsoft Exchange System Objects \ Monitoring Mailboxes

Now that the Exchange Health Mailboxes are gone, restart the Microsoft
Exchange Health Manager
service on all Exchange 2013 servers to recreate the
necessary Exchange Health Mailboxes:

[PS] C:\>Restart-Service MSExchangeHM

Replicate AD again and you will see the new Exchange Health Mailboxes in the Exchange Management Shell and ADUC:

[PS] C:\>Get-Mailbox -Monitoring

Name Alias ServerName ProhibitSendQuota
—- —– ———- —————–
HealthMailbox7b3ef7a60… HealthMailbox7b3e… ex2013-1 Unlimited
HealthMailbox312d14677… HealthMailbox312d… ex2013-2 Unlimited
HealthMailbox1aec3204b… HealthMailbox1aec… ex2013-1 Unlimited
HealthMailboxa04a8b769… HealthMailboxa04a… ex2013-2 Unlimited
HealthMailbox04e954fc9… HealthMailbox04e9… ex2013-1 Unlimited
HealthMailboxd20957258… HealthMailboxd209… ex2013-2 Unlimited

Recreated Health Mailboxes

Two monitoring mailboxes are created for each mailbox database in your
organization: one for monitoring the health of site mailboxes and one for
monitoring the health of public folders. That should resolve the ASP.NET
4.0.30319.0 warnings.

Fix for Exchange ActiveSync Failures After Migration to Exchange 2013

There’s a bug in Exchange 2013 that causes Exchange
ActiveSync to fail for newly migrated users from Exchange 2010. It only affects migrated users who
already have a mobile device configured, not new users (i.e., test mailboxes). This issue was discussed in the Exchange Server forums back in August 2013.

The issue occurs because the IIS application pools on the
CAS 2013 servers do not automatically detect that the mailbox has been moved to
Exchange 2013. When the user’s mobile device connects to CAS 2013, CAS
2013 proxies the user back to CAS 2010 which responds with an error saying
the mailbox is corrupt or missing. If you run an Exchange ActiveSync test using ExRCA you will see the X-CalculatedBETarget value reported by CAS2013 is still pointing to the Exchange 2010 server. The problem usually resolves itself in 1-8 hours, depending on the Exchange 2013 build.

The workaround is to manually recycle the
MSExchangeAutodiscoverAppPool and MSExchangeSyncAppPool application pools in
IIS on all CAS2013 servers.

I wrote a PowerShell script for this called Recycle-AppPools.ps1:

#Use this script to recycle IIS Application Pools to overcome Exchange 2013 SP1 ActiveSync bug for migrated users

#Get all Exchange 2013 CAS servers
$CASServers = Get-ClientAccessServer | where {$_.WorkloadManagementPolicy -ne $null}

#Loop through each CAS2013 and recycle the IIS App Pools
foreach ($CAS in $CASServers) {
Write-Host “Recycling App Pools on $CAS…”
$appPool = Get-WmiObject -Authentication PacketPrivacy -Impersonation Impersonate -ComputerName $CAS -namespace “root/MicrosoftIISv2″ -class IIsApplicationPool | Where-Object {$_.Name -eq “W3SVC/AppPools/MSExchangeAutodiscoverAppPool” }
$appPool = Get-WmiObject -Authentication PacketPrivacy -Impersonation Impersonate -ComputerName $CAS -namespace “root/MicrosoftIISv2″ -class IIsApplicationPool | Where-Object {$_.Name -eq “W3SVC/AppPools/MSExchangeSyncAppPool” }

You will need to run the script after an EAS user or batch of users have been
migrated. There is no outage associated with recycling the app pools and
it recycles very quickly. A fix is scheduled for Exchange 2013 CU5.

Tips for Connecting to Office 365 using PowerShell in Hybrid Environments

The Office 365 portal and Exchange Admin Console are fairly powerful to allow you to manage your tenant and on-premises environments. But as you are no doubt aware, there are many administrative tasks that require you to use PowerShell.

The sequence you usually find on the web to connect to Office 365 via PowerShell is:

[PS] C:\>$LiveCred = Get-Credential -credential
[PS] C:\>$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection
[PS] C:\>Import-PSSession $Session

If you are in a hybrid environment with Exchange and Office 365 you will discover that both environments have a lot of the same cmdlets, such as Get-Mailbox, Set-DistributionGroup, etc. This causes a conflict when the Office 365 PowerShell cmdlets are loaded within the Exchange Management Shell. You either need to connect to Office 365 PowerShell from a regular PowerShell console (separate window) or you need to use the -AllowClobber parameter, which overwrites the existing EMS cmdlets with the Office 365 versions. This is not ideal if you are working with both on-prem and cloud objects at the same time.

Proxy creation has been skipped for the following command … Use the AllowClobber parameter if you want to shadow existing local commands

I wrote a PowerShell script called Connect-Office365.ps1 that overcomes these conflicts by using the -Prefix parameter with the Import-PSSession cmdlet. The Prefix parameter tells PowerShell to add the specified prefix to all cmdlets it loads from Office 365. For example, if you set the prefix to “cloud” the Get-Mailbox cmdlet for Office 365 becomes Get-cloudMailbox and the Get-Mailbox cmdlet still applies to on-prem. This way you can use both sets of cmdlets in the same EMS console. The script also connects to the MSOLService so you can use the MSOL cmdlets to manage Azure AD.

Connect-Office365.ps1 with “cloud” prefix

Here’s the four line Connect-Office365.ps1 script:

$LiveCred = Get-Credential -credential “”
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection

Import-PSSession $Session -WarningAction SilentlyContinue -Prefix cloud

Connect-MsolService -Credential $LiveCred

I usually copy the script to the C:\Windows folder on my Exchange servers and my management computer so it can be run from any directory whenever I need it.

The ‘Heartbleed’ Security Flaw – Are You Affected?

(CNN) — A major online security vulnerability dubbed “Heartbleed” could put your personal information at risk, including passwords, credit card information and e-mails.

Heartbleed is a flaw in OpenSSL, an open-source encryption technology that is used by an estimated two-thirds of Web servers. It is behind many HTTPS sites that collect personal or financial information. These sites are typically indicated by a lock icon in the browser to let site visitors know the information they’re sending online is hidden from prying eyes.

Cybercriminals could exploit the bug to access visitors’ personal data as well as a site’s cryptographic keys, which can be used to impersonate that site and collect even more information.

You can use the Heartbleed Test website ( to test your external websites and external-facing web appliances to see if they are vulnerable. I encourage you to make a quick test of your systems ASAP.

Notes on the Windows 8.1 Update for Windows Server 2012 R2

Microsoft has released the Windows 8.1 Update to MSDN subscribers and is due to be released today to the general public. This update also applies to Windows Server 2012 R2 servers and includes some important updates, including one that will be required so that Windows 8.1 and Windows Server 2012 R2 computers will continue to receive important security updates.

The Windows 8.1 Update (no number, as if there will never be another) is actually a series of 6 updates which should be installed in a certain order.  I created an installer batch file that installs the updates for Windows Server 2012 R2 in the recommended order with minimal output.

Copy the following text to Notepad and save it as Install.bat in the same folder as all the x64 patch files:

start /wait Windows8.1-KB2919442-x64.msu /quiet /norestart
start /wait Windows8.1-KB2919355-x64.msu /quiet /norestart
start /wait Windows8.1-KB2932046-x64.msu /quiet /norestart
start /wait Windows8.1-KB2937592-x64.msu /quiet /norestart
start /wait Windows8.1-KB2938439-x64.msu /quiet /norestart
start /wait Windows8.1-KB2949621-v2-x64.msu /quiet /norestart
@echo Please restart the computer now.

And here’s a version for Windows 8.1 x86:

start /wait Windows8.1-KB2919442-x86.msu /quiet /norestart
start /wait Windows8.1-KB2919355-x86.msu /quiet /norestart
start /wait Windows8.1-KB2932046-x86.msu /quiet /norestart
start /wait Windows8.1-KB2937592-x86.msu /quiet /norestart
start /wait Windows8.1-KB2938439-x86.msu /quiet /norestart
start /wait Windows8.1-KB2949621-v2-x86.msu /quiet /norestart
@echo Please restart the computer now.

Once you install the update and restart the computer you’ll immediately notice that the Windows App Store icon is on your taskbar.

Windows App Store is added to the Windows 2012 R2 Taskbar
If you’re running Windows Server 2012 R2 and signed in the the Admin account you’ll find that the Store won’t open and gives the error, “This app can’t open. Store can’t be opened using the Built-in Administrator account. Sign in with a different account and try again.” Doh! Right-click the icon and unpin it from the taskbar to recover that real estate.

This dawg won’t hunt

It’s interesting to see Microsoft slowly unraveling the “Modern UI” to behave more like the desktop UI. They’ve added a power button to the Modern UI desktop so users can easily shutdown or restart the computer and added a search icon because users didn’t intuitively know that they can just start typing to search.

Pending Messages in Exchange Online Will Not Be Delivered

There’s a pretty big unpublicized bug in Office 365 transport that you need to be aware of.
Messages from Exchange Online Protection (EOP) that cannot be delivered to an on-prem Exchange hybrid server due to a transport problem will be marked as Deferred or Pending.  These messages will NEVER be delivered, even after the transport issue is resolved.
The following example shows a message that was sent at 2:46PM UTC and the status shows as Pending. The last event for this message shows DEFER at 3:29PM UTC with the detail, “The last attempt to deliver the message encountered an error”.
Sample Message Trace from Office 365
For example, say the TLS
certificate expires on your hybrid server. Inbound messages from EOP to the hybrid server will queue because the Outbound Connector is using Forced TLS, but the certificate is invalid. If you resolve the problem by renewing the cert or reconfiguring the Office 365 Outbound Connector to use opportunistic TLS the problem is solved for new emails – they get delivered right away, but the Pending messages will
never get resubmitted and eventually expire (after 48 hours).
Incredibly, there currently is no way for Microsoft to resubmit these messages like there is for on-prem Exchange. After opening a high-priority case with Microsoft Online, the only “solution” they could give is to contact all the senders and ask them to resend their emails.