"/o=CUSTOMER-NAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=_shared_mailbox_name" "/o=customer-name/ou=old_administrative_group/cn=recipients/cn=_shared_mailbox_name " (this one oddly had an additional space at the end - don't ask - I don't know )). The new administrative group used by 2010 and higher doesn't contain links to the public folders.ĭon't know if it matters (it probably does) but the old group has no servers in it.Īnyways if we change the legacyExchangeDN from say: The group still exists in AD (can be seen through adsiedit.msc) and contains, amongst a few other things, links to the public folders (they still run an exchange 2010 server for this and a 2012 R2 DC because of this as the exchange 2010 is still on an old CU for SP3). On the shared mailboxes with issues these contain and old administrative group.
Compared AD attributes and found the issue to be the legacyExchangeDN. Probably an upgrade of Outlook (2013->2016) or office patches.Įrror Outlook throws: the set of folders cannot be opened the attempt to log on to microsoft exchange has failedĬreated some new shared mailboxes, they open just fine in Outlook. The root cause seems to have existed for quite some time. Guessing it might work just fine with Outlook 2013, but don't have one handy. Opening the same shared mailboxes in OWA works just fine.
They currently use Outlook 2016 from the 365 program. The issue is quite simple, there are a lot of shared mailboxes the customer can no longer open from Outlook. Also if people have stuff to add - that would be more than welcome. Think I've already found the issue, but I wanted to document it here anyways, as my searches on the internet weren't really fruitful in finding this.
0 kommentar(er)
