After implementing and migrating Exchange 2010 On-Premises to Office 365 I am getting this error/warning. And this is not just with editing email address of Exchange Object but there are several other error/warning I am getting while performing these kind of actions.

Here is the same error I am getting when editing the E-Mail Address:



























Now Microsoft says to to keep at least One On Premises Exchange Server to manage environment when you are doing Hybrid Deployment. Now the question is, what happens when I am doing Cut Over Migration with 2000 seats. Do I need to have On Premises Exchange to manage Office 365? What if a customer with 30K seat environment wants to migrate to Office 365 and keep all messaging related thing with Office 365 and Active Directory On Premises. And none of Exchange Server On Premises, what is the option in that case? These are the questions which needs to be answered.

As per this TechNet blog also, it ask you to keep One Exchange Server On Premises.
http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx

I wonder why do I get the above error? I have asked this question by my client and the only technical answer I could give them was, it's happening due to AD Sync between On Premises and Office 365. Another thing is, last time I checked DirSync is one way Sync, and this could be one of the reasons why it's happening. I looked at several places but didn't got the satisfactory answer.

Here is I am creating Room Mailbox using EAC or Office 365 Dashboard and I got the some error/warning.



























































































One thing is, after I click on OK and save and check for the Room Mailbox, it's present in there.
I am still looking for the answer of this behavior, that why I am getting the Sync error when editing the object.

Cheers,

I ran into an issue where as Outlook client experiencing slowness when accessing Public Folder on Exchange Server 2010. I was facing 2 different issues at 2 different geographical location, users at Europe were experiencing slowness when trying to access Public Folder via Outlook and Users in US where getting credential prompt when it failed to connect to default Public Folder Database.

I was able to fix Outlook slowness issue while accessing the Public Folder by making the registry changes on Public Folder Server, as Outlook client were trying to connect to Public Folder Server which were in US.

I followed this article and applied Method 2 to fix the issue.

But, the issue at US location was Outlook client were prompting for credential when trying to connect Public Folder Database which was not a Default Public Folder Database on Mailbox Database. So to fix this issue I had to apply the same registry fixes but I also had to install Hot Fix on Public Folder Server. Hot Fix is part of Method 1, but this article doesn't have a link to download the Hot Fix.

I had to call Microsoft get this Hot Fix which you can download from here. Writing this article, so that you don’t have to call Microsoft to get this Hot Fix.

I hope it helps.

Cheers,

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,