Public folders permissions exchange 2010

I then tried to reproduce this in my own environment but could not.

Clearing the value & restarting the Information Store Service also resolved their issue.ДЄfter hearing this I went online to see if any others were encountering this issue. That environment also had Mailbox Databases that were pointed to a deleted object for their default Public Folder Database. After an improperly performed Exchange 2007 migration, the Exchange 2013 mailboxes were getting prompted to restart Outlook. Not long after this issue, I was contacted by a Consultant I know who encountered the exact same issue. Afterwards, a restart of the Information Store Service resolved the issue. The resolution in this case was to drill down to the properties of the Mailbox Database in ADSIEDIT & set the value of вЂњmsExchHomePublicMDBвЂќ to be blank. So the result was that the Outlook clients were trying to access Public Folder information but were reacting in a way that resulted in the frequent prompt to restart Outlook. The Public Folder Database was showing up as a deleted object in AD. In this case, the decommissioning of Exchange 2007 & its Legacy Public Folders was not done correctly (same issue probably would have occurred if it were 2010). In this customerвЂ™s scenario, I determined that the вЂњPublicFolderDatabaseвЂќ attribute on every Exchange 2013 Mailbox Database was set to a value resembling the screenshot below: One such thing relates to the Public Folder Hierarchy. While it did eliminate the prompts when the RPC Endpoint (Server Name field in Outlook) changed, there are still other scenarios that could result in this prompt (please see reference links at bottom of post for a detailed history). This seemed odd because Exchange 2013 was supposed to all but eliminate those prompts. After decommissioning the 2007 servers, all the Exchange 2013 mailboxes started getting the infamous вЂњThe Microsoft Exchange Administrator has made a change that requires you quit and restart OutlookвЂќ prompt. I was working with a customer who migrated from Exchange 2007 to Exchange 2013. IвЂ™ve seen this issue happen in two different environments & then found out via the forums that several other people have run into it as well. I usually refrain from writing posts on issues where I havenвЂ™t been able to fully reproduce them in my lab but enough people seem to be having this issue that it would be good to spread the word should another person find themselves afflicted by it. After installing the hotfix & rebooting the issue was resolved & their users no longer received the prompts.

This is actually an IIS issue with Server 2008 R2 (the operating system Exchange 2010 was installed on) thatвЂ™s resolved by a hotfix. Turns out this issue was recently addressed via вЂњOutlook Anywhere users prompted for credentials when they try to connect to Exchange Server 2013вЂќ. After a search through my OneNote I realized I previously had a discussion with some people I know from Microsoft Support regarding this issue. When I was approached with this issue/symptom it sounded familiar.

Sometimes the prompts would be when connecting to Public Folders while other times mail or directory connections from Outlook to Exchange. While this was somewhat working, they also immediately noticed users were randomly being prompted for credentials, resulting in a negative user experience. At this point all of their Outlook Anywhere clients should have been connecting to Exchange 2013 & then been proxied to Exchange 2010. As part of their migration process they pointed their Exchange 2010 Outlook Anywhere namespace (letвЂ™s call it ) to Exchange 2013 in DNS. I was working with a customer who had Exchange 2010 & were in the process of migrating to Exchange 2013.

Public folders permissions exchange 2010