A customer uses an Exchange 2013 server as the mail hosting server, and the specific version is Exchange SP1.
Now the customer has a demand, they want their mailbox as a room mailbox to create, and must have ordinary mailbox all the features, so that all the room mailbox must be the same as normal users can send and receive e-mail.
After we created the room mailbox through the PowerShell command, we needed to enable the ad account that was hooked up with that mailbox.
However, it is very strange that after we enable the account, the room mailbox has been unable to log in, the login page has been logged in the process, the process is not error and will not appear unable to display the page. I found a strange phenomenon when I diagnosed with Chrome's diagnostic mode, and the browser traced the following error:
Something went wrong
Sorry, we can ' t get that information right now. Please try again later. If the problem persists, contact your helpdesk.
X-owa-error:microsoft.exchange.security.authentication.tokenmungingexception
x-owa-version:15.0.847.32
X-feserver:mail2013-1
X-beserver:mail2013-2
date:28/04/2014 11:35:42 AM
Found the problem, then the solution is very convenient, this is because the room mailbox using the Linkedmasteraccount "property is set up" NT authority\self ", so it will not stop automatically re-landing, resulting in no landing, then the solution is very simple , perform the following PowerShell command to resolve the issue:
Set-user-identity meeting Room Mailbox-linkedmasteraccount $null
??
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
The room mailbox user for Exchange 2013 has been unable to log on properly.