So there’s an issue, basically we didn’t add the server to our wild card cert. So added the server names as Subject alternative names and imported it using PowerShell onto both Client access servers and then rebooted:

<TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord"Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-GB/library/System.ServiceModel.Diagnostics.EventLog.aspx</TraceIdentifier><Description>Wrote to the EventLog.</Description><AppDomain>/LM/W3SVC/1/ROOT/EWS-1-131788827699531225</AppDomain><ExtendedData xmlns="http://schemas.microsoft.com/2006/08/ServiceModel/DictionaryTraceRecord"><CategoryID.Name>WebHost</CategoryID.Name><CategoryID.Value>5</CategoryID.Value><InstanceID.Name>WebHostFailedToProcessRequest</InstanceID.Name><InstanceID.Value>3221356547</InstanceID.Value><Value0>System.ServiceModel.ServiceHostingEnvironment+HostingManager/39086322</Value0><Value1>System.ServiceModel.ServiceActivationException: The service '/EWS/Exchange.asmx' cannot be activated due to an exception during compilation. The exception message is: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection.

So the long and short of it is they think IIS is broken. The traffic is being passed to the Group2 services but these services are not passing the information back up the stream.

MS decided they wanted swap out the EWS web.config with a new one from:

If you ever get this annoying message when opening an Email Address book policy:

1

The specifiede-mail address policy couldn&#039;t be edited. E-mail address polices created with legacy versions of Exchange must be upgraded using the &#039;Set-EmailAddressPolicy&#039; task, with the Exchange 2010 Recipient Filter specified.

This means the policies were created with old versions of Exchange, in my case Exchange 2003, you can find them all, looking for the word Legacy:

As you can this will show the ldap query too, the problem is if you run the Set-EmailAddressPolicy against this then you’ll break it, all custom filters (LDAP queries) will be reset to “mailnickname=*” which can result significant email outages.

Had a crazy problem recently, a company Contoso.com was using Exchange 2010 (CAS, Hubs and Mailbox servers) with all the latest patches and roll-ups and had users on their domain using Outlook Anywhere perfectly.

The problem was their sub domain SubDomain.Contoso.com is also big company, they have their own Exchange 2010 servers (CAS, Hubs and Mailbox servers) with all the same patches and roll-ups except they’re “downstream” of Contoso.com. The problem is all users in SubDomain.Contoso.com couldn’t use Outlook Anyhwere, i.e. RPC proxy redirection wasn’t working:

The setup:

So all in all it was weird, we checked everything, firewall blocks, routing problems etc etc, even https://testconnectivity.microsoft.com/

So finally we logged a call with MS and after some lengthy troubleshooting they found the underlying issue:

A friend came across this issue while migrating from Exchange 2010 to 2013. Users were unable to receive/send email from their mobile device after migration. This continues for up to 4 hours or so then starts working out of the blue.

It’s actually a bug with certain versions of Exchange 2013.

To fix, simply recycle the following App Pools in IIS on the CAS server:

MSExchangeAutodiscoverAppPool

MSExchangeSyncAppPool

A fix is in place for CU5, so if you are on that version or higher this fix “shouldn’t” apply…….

When you install Microsoft Skype on a Windows-based computer that has Microsoft Lync installed, you experience one or more of the following issues:

Microsoft Outlook does not display presence information.
The Microsoft SharePoint client does not display presence information.
Other Microsoft Office applications that support presence features do not display presence information

This behavior may occur if the value of the DefaultIMApp registry entry in the following registry key is incorrect:
HKEY_CURRENT_USER\Software\IM Providers

Note The DefaultIMApp registry entry specifies which IM application provides IM and presence information in Office applications. When you install the Lync 2010 client together with Microsoft Office, the value of the DefaultIMApp registry entry is updated to “Communicator.” Or, if you install the Lync 2013 client together with Microsoft Office, the value of the DefaultIMApp registry entry is updated to “Lync.”
To work around this issue, follow the steps that are appropriate for the version of Windows that you are running.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

Windows XP, Windows Vista, or Windows 7

Exit the Skype client and all Office applications.
Click Start, click Run, type regedit.exe, and then click OK.
Locate the following registry entry:
HKEY_CURRENT_USER\Software\IM Providers\DefaultIMApp registry value
Right-click DefaultIMApp, and then click Modify.
Type Skype in the Value data box, and then click OK.
Exit Registry Editor, and then restart the Skype client and the Office applications.

Windows 8

On the Start screen, click the Search tile.
Type regedit in the Search window and then double-click regedit.exe.
Locate the following registry entry:
HKEY_CURRENT_USER\Software\IM Providers\DefaultIMApp registry value
Right-click DefaultIMApp, and then click Modify.
Type Skype in the Value data box, and then click OK.
Exit Registry Editor, and then restart the Skype client and the Office applications

Want to record exactly what happens when you’re using the Exchange Management Shell? Use the Start-Transcript cmdlet. Anything that you do after you run this cmdlet will be recorded to a text file that you specify. To stop recording your session, use the Stop-Transcript cmdlet.

Notice that the Start-Transcript cmdlet overwrites the destination text file by default. If you want to append your session to an existing file, use the Append parameter:

Subscribe to my posts

Dont like Adverts

I know the adverts are annoying but I only use them to pay for hosting. If you find any of my posts useful then I’d really appreciate it if you could disable your ad-blocker and click a advert of two.
Or if not then you could buy me a coffee?
Thanks