Some exciting news today...
Microsoft released Service Pack 1 for Exchange 2013. You can download it from here

But make sure you read the Release Notes for Exchange 2013 properly before you start installing/updating the server.

New feature and fixes includes the below:
















Cheers,

Microsoft Exchange Unified Messaging Service Failed to Start on one of Unified Messaging Server. When I tried to start the service it failed with error.

In the mix environment of Exchange Server 2007 and 2010, after doing cut over of Client Access Server and Hub Transport Server to Exchange Server 2010, everything was working fine, Mailflow, Outlook, OWA, FreeBusy, OOF, OAB, IMAP, POP (Internally) and Outlook, OWA, FreeBusy, OAB, IMAP, POP (Externally) except Out of Office.

I could access the FreeBusy and OAB information using Outlook Anywhere of the users on Exchange 2007 as well as 2010, but I couldn't access the OOF for any of the users when accessing it via Outlook Anywhere.
Now, to access the FreeBusy and OOF exchange uses EWS (Exchange Web Services), which was working fine, but when it comes to accessing or setting up OOF, it use to fail with the standard error. "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later"

We are using TMG Server 2010 to publish the exchange services like, OWA, Active Sync, Outlook Anywhere, POP and IMAP. TMG is running Active/Passive Cluster (I wouldn't do it like this). Cause you are not utilizing both the TMG server when running Active/Passive.

After spending sometime on TMG Server I found something which was kind of hard to believe. This is how you are going to fix this issue.
Open TMG Console, go to Firewall Policy, look for Outlook Anywhere Rule.









Double click on Outlook Anywhere Policy and click on Paths TAB.



























Make sure that you have Internal Path for EWS is set as /ews/*
Initially this path was missing from OA Rule, after making this entry, apply the changes. Now you can set your Out of Office and it will work like a charm from Outlook Anywhere.


This is my last article and also on the last day of year 2013. I hope everyone had great 2013 year. Wishing you all Happy and Prosperous New Year 2014.

Cheers,

There's some good news for all of (Exchange Server Guys) us. Microsoft will be releasing SP1 for Exchange Server 2013 in 2014. I am assuming it should be in first Q of 2014.

Some of the highlight of SP1.

Windows Server 2012 R2 Support First answering one the most common questions since the release of Windows Server 2012 R2. Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1. Let your planning begin.
S/MIME support for OWA Support for S/MIME in OWA will be brought back in SP1. With SP1 customers will have S/MIME support across Outlook, Exchange ActiveSync clients, and OWA.
Edge Transport Server Role The Edge Transport server role for Exchange Server 2013 will be available with SP1.
Fixes and Improvements Of course, SP1 will include fixes and improvements in areas you've helped us identity. SP1 is the first service pack issued in the new Exchange Server cumulative update release model - thus SP1 is essentially CU4. The installation of SP1 will follow the same process as the prior Exchange 2013 CU releases. SP1 will include all fixes included in previously released cumulative updates for Exchange 2013.

Yesterday (November 4th, 2013)  Microsoft released new version of DirSync which can be now installed on domain controller. Previously DirSync couldn't be installed on Domain Controller.