Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013

Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman

Similar Messages

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Multiple eventlog errors after mailbox-move to Exchange SP1

After a mailbox move completes on a Exchange 2013 SP1 server, multiple errors are logged in the eventlog. I opened a ticket with MS Support and they confirm this is a bug in SP1, but the moves itself aren't affected. They state the errors can be ignored.
About 10 error per move are being logged.
These are the errors occurring after completion of a mailbox move:
Event 1003:
An asynchronous Microsoft Exchange Server Information Store task has not handled an Exception gracefully. Exception text is (Microsoft.Exchange.Server.Storage.Common.StoreException: ErrorCode: NotSupported, LID: 43296 - Invalid counter range allocation at
this time.
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64& globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)).
Event 1050:
Global counter allocation in mailbox 3add23e8-7a32-4fb5-bc32-f5b1eae7f98c on database 0afbb5dc-b967-4ebd-acb0-15f85b8bad53 by source MailboxTask during operation 28 on call stack at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context
context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64&
globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, MailboxTaskQueue mailboxTaskQueue, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.Common.Task`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.SingleExecutionTask`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.Task`1.<Worker>b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch[T](TryDelegate tryDelegate, GenericFilterDelegate filterDelegate, GenericCatchDelegate catchDelegate, T state)
at Microsoft.Exchange.Server.Storage.Common.WatsonOnUnhandledException.Guard(IExecutionDiagnostics executionDiagnostics, TryDelegate body)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
is temporary not allowed.

Here's the technical descpription from MS support:
Description of problem: “During the mailbox move finalization stage the Store move is finalized followed by MRS move. In this state MRS executes MRS specific functionality. The state might take
a pretty long time in some cases. During this state the destination mailbox cannot be changed. The defensive code on the global counters depicts that the task with task ID 28: TaskTypeId.PropertyPromotionBootstrap is trying to allocate new global counter values
as seen in the event below.”
This is not a critical issue, and the production team also suggest safely ignore this warning, also they are now making progress to fix this issue, hoping to release the solution in the next CU or SP.
Frank.

Outlook cannot connect after mailbox move from Exchange 2007 to 2013

I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
AutoDiscoverInternalRpcClientServer
[email protected]
AutoDiscoverHomeMdbDn
/o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
I've checked and rechecked everything and can't seem to locate my error.
Any thoughts? Thanks.

Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Movemailbox issue: new empty calendar folder gets created after mailbox move

Hi,
when doing mailbox moves between Exchange 2010 and Exchange 2013 (CU3 and SP1) and also between two Exchange 2013 SP1 servers we experience the following issue:
sometimes a new empty default calendar folder is being created after the mailboxmove completes. Out of 230 moved mailboxes 6 mailboxes experienced this issue. For some reason the existing calendar folder is changed to a user created folder and a new
calendar folder gets being created. This causes some panic by the affected users, since they suddenly notice that their calendar is completely empty. The free/busy information other people see is also empty because they also see the empty calendar.
To correct the issue I have to manually move the items from the original calendar folder to the newly created calendar folder.
Any idea what might cause this? I don't have reproduction steps, it just happens at random during the mailbox move. The moverequest completes succesfully, no errors are reported and the movereport also doesn't contain any clues.
Frank.

But outlook wasn't running, so outlook couldn't have created the new calendar folder. I did the mailbox move out of office hours. Right after the mailbox move completed I ran the 'get-mailboxfolderstatistics' cmdlet. When looking at the output I search
for 'user created' calendar folders called 'Calendar'. The mailboxes that were affected also had another 'Calendar' folder of the type 'Calendar'. This is the newly created folder. So the mailbox contains two folders called 'Calendar' after the move. Although
I can't reproduce it, I'm able to detect when it happened by looking at the output of the above cmd-let.

Inter-Org Mailbox moves from Exchange 2007 to Exchange 2013

G'Day All,
Is it possible to move Exchange 2007 mailboxes to Exchange 2013 in a different forest? Both environment has all the required patches and service packs.
There is a two way trust, and I don't want to introduce Exchange 2010 CAS in the source forest if I don't need to.
I have read the following article http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ but it is not clear what is the required to setup in Exchange 2007. I have read many other articles to do with Exchange 2013 mailbox moves, endpoints,
etc, but non of them is clear of how does it work having Exchange 2007 source.
Thanks in advance.

Hi Atonal,
Could you please take a look at this technet blog that has been well elaborated about your concern :
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The blog provides step-wise assistance while you are planning to move from exchange 2007 to 2013.
Here is another library available from technet team that includes all the terms while preparing mailboxes for cross-forest move request : http://technet.microsoft.com/en-us/library/ee633491%28v=exchg.150%29.aspx
Alternatively, you can checkout this proficient application (http://www.exchangemigrationtool.com/) in order to avoid any interruption and proceed hassle-free migration from exchange 2007 to 2013.

Mailbox Move from Exchange 2007 to Exchange 2013

I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
Thanks

When you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange 2007 - 2010 Outlook doesn't autodiscover after mailbox move

We currently are in the process of migrating from Exchange 2007 to 2010. When I move a mailbox to 2010, Outlook (2010 in this case), fails to connect to the new environment. Restarting outlook does not help. I am forced to change the
servername in the mail applet. How can we make this happen automagically?

That URL points to the autodiscover.xml page on the 2010 CAS servers. Returns the typical
<?xml version="1.0" encoding="utf-8"
?>
- <Autodiscover
xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="01:46:57.9070185"
Id="814683946">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData
/>
</Error>
</Response>
</Autodiscover>

Exchange 2013 CAS IMAP Proxying to offline 2007 CAS Server

We're running in coexistence mode with 2013 and 2007. We had one of our 2007 CAS servers go down. We have IMAP users that keep getting a login prompt now. Looking at the IMAP logs it's failing when the 2013 CAS server tries
to proxy the IMAP session to the down 2007 CAS server. Is there any way to stop 2013 from attempting to proxy to the down 2007 CAS server? We have 3 other 2007 CAS servers that are available.

Hi,
I‘m following up this thread and if you have any question about the above information I provided, please feel free to let me know.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Autodiscover fails after mailbox move

Hello,
Environment: existing exchange 2010 org, with new Exchange 2013 introduced. Clients are Outlook 2013. Clients can connect to all mailbox on the 2010 Server, also can connect to new mailboxes on the 2013 Server. But if I move an existing mailbox from
the 2010 Server to the 2013 server Outlook cannot connect anymore, because autodiscover fails. Both servers use the same autodiscover settings, SCP contains the same URL.
TIA
Update: I've just installed an Outlook 2010 for testing purposes and it is working! From this point it may be rather a client side problem than a server side...

Hey there,
I actually installed 2013 using the CU5 install files. So you are right, CU5 does not matter from a first look, but it does matter overall for this issue. Keep reading.
Tangent: This appears to be unrelated but I will mention it anyways. I noticed, after the mailbox was migrated that when I am on the internal network, autodiscover fails the same way it does for you. However, when I bring the client off the corporate network
and have it connect via the public Internet, autodiscover suceeds. When testing with EXRCA autodiscover also succeeds. Please do note that external access to Exchange is handled by Microsoft's Web Application Proxy. This proxy performs "pass-through"
authentication of autodiscover so that may have something to do with it.
Back to the main issue of Outlook staying disconnected after the migration. I wasn't going anywhere with this so I opened a case with Microsoft. I was able to replicate the problem with the support tech and they were also able to replicate this in
their lab. This was the conclusion:
This is a known issue. It happens because when a mailbox is moved to 2013, the mailbox itself still has a cache entry that points the client back to the 2010 server. From what Microsoft said, this cache expires in an "undetermined" time interval
for Exchange 2013 SP1 up to CU4 and every "2 to 2.5 hours" in Exchange 2013 CU5. They could not reference a KB article with this info.
Microsoft mentioned that the cache is also cleared when recycling the IIS Application Pool that runs RPC on the 2013 CAS server which is also caused by an IISreset. However, I have not been able to verify the application pool recycle method in my tests.
From what I can see, IISreset is the only way to clear the cache. I have sent a follow-up to Microsoft asking which App Pools specifically need to be recycled to avoid having to perform a full IISreset. I will test and report back here.
In any case, here is my strategy moving forward which was blessed by the Microsoft team:
Create a migration batch for a number of users (in my case I will make it 5 to 10 users at a time)
Select to "Manually Complete the batch" in the "New Local Mailbox Move" window. This process will migrate 95% of the mailbox and then stop.
Once the migration has gone through 95% and it stops syncing, the batch shows as "synced" on the migration window. Until this point in the process, users are able to use Outlook without any interruption and the move is invisible to them.
When I am ready to finish the migration, I will select to "Complete This Migration Batch" on the ECP Migration screen. At this time, users that have Outlook open will receive a prompt to
restart it. When Outlook re-opens it will show as "Disconnected" until the next step is performed.
Once the batch shows as "completed" I will perform an IISreset on the 2013 CAS server (or recycle the appropriate app pools once Microsoft provides them to me.) At this time, Outlook will show as "Connected to Microsoft Exchange" and
users will receive a second prompt to restart Outlook. After the second restart you'll be good to go!
I will try to time my migration so they complete after hours, when most people are less likely to have Outlook open. Don't forget, that the cache entry that causes all these issues is cleared after about 2 to 2.5 hours if you are on 2013 CU5. In any
case, I think it's better if you have control over when the migration finishes by opting to complete it manually.
Hope this helps.
Fable
EDIT: Microsoft has confirmed that recycling the following Application Pools makes Outlook connect to Exchange 2013:
Exchange 2013 CAS Server:
MSExchangeAutodiscoverAppPool
MSExchangeRpcProxyFrontEndAppPool
Exchange 2013 Mailbox Server:
MSExchangeAutodiscoverAppPool
MSExchangeRpcProxyAppPool
If you decide to not do an iisreset and opt for recycling the App Pools instead, be advised that after the AppPools are recycled, Outlook connects to Exchange and asks to be restarted. If you close Outlook and immediately open it again, you will be prompted
with a username and password pop-up (At least I was in all my tests of this method.) This issue is resolved if, after you close Outlook, wait 5 to 10 minutes before you re-open it. You will not be prompted for a user/pass at this point.

Duplicate Items in Outlook After Mailbox Move to New Server

We are performing a server migration and after moving a group of pilot users from Exchange 2003 to Exchange 2007, they are reporting duplicate items (emails, calendar, contacts, etc.) in Outlook. What could be causing this to happen and how do we prevent
it? What's the best way to fix the existing duplicates? The duplicates have sync'd to the server as they show up in Outlook Webmail as well.
Thank you

Hi,
How do your move these mailboxes from Exchange 2003 to Exchange 2007? Using move request in Exchange 2007 or exporting/importing a PST file?
Since the duplicate items don't shown in Outlook Web App, please create a new Outlook profile in Outlook to have a try:
http://support.microsoft.com/kb/829918
Additionally, here is a reference about how to move mailboxes from Exchange 2003 to Exchange 2007:
http://exchangeserverpro.com/moving-mailboxes-from-exchange-2003-to-exchange-server-2007/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Thanks,
Winnie Liang
TechNet Community Support

New mailbox move request Exchange 2010 : queued

I have deployed new Exchange 2010 server in Exchange 2003 Organization. It is simple setup one Exchange 2003 and New Exchange 2010.
I was trying to move mailbox from Exchange 2003 to 2010 and it has status of QUEUE “indefinetly”.. I have tried several mailboxes and result is the same.
Then I decided to create new database on Exchange 2010 sever. I have crate new mailbox on Exchange 2010 sever, send and receive some emails. And then try to move mailbox to new database. Same results.
I run test MSR replication and is ok.
I have increase msr LOGGING TO Maximum, no errors. I have rebooted server several times, no differences…

Hi,
Based on the description, status of mailbox move request from Exchange 2003 to Exchange 2010 is "indefinitely".
Please make sure mailbox databases in Exchange 2010 and Exchange 2003 are mounted.
Have you moved mailbox using the New-MoveRequest with the BadItemLimit and the AcceptLargeDataLoss parameters? If not, it's worth to do it again. Before you create a new move request, please check if there is any previous move request. If there is, please
clear the previous move request and then move the mailbox.
If the issue persists, please try to move mailbox to another database in Exchange 2003 and then move to Exchange 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Mobile and remote Outlook access do not work after mailbox move

We recently moved our mailboxes to a different datastore. We are not unable to access our mailboxes using our cell phones or Outlook remotely. testconnectivity.microsoft.com gives me a http 500 error for both the Exchange virtual directory and the RPC.
Any ideas?

Was this a migration to another version of Exchange or simply mailbox move from the same version of Exchange?

2013 CAS working for 2010 users, certificate error on 2013 users

Yesterday we decided to pull the trigger on migrating to exchange 2013 from 2010. We changed the autodiscover URI's to mail.domain.com and we also changed the DNS records to as follows:
mail.domain.com -> 2013 cas
mailhub1.domain.com -> 2010 cas
mailhub2.domain.com -> 2013 cas
Ive pushed every single URL I can find through mail.domain.com. We had a few odd issues but were able to work through them. Now we are about 10 hours into troubleshooting without making any headway. Here is where we currently stand:
Exchange 2010 User - Works on everything - Web, Mac Mail, Outlook (inside and outside), mobile clients
Migrated and New Exchange 2013 User - Works on Web, Mac Mail, Mobile. Does not work on outlook inside or out.
For outlook we receive the following error:
Microsoft Outlook
There is a problem with the proxy server's security certificate.
The name on the security certificate is invalid or does not match the name of the target site mail.domain.com.
Outlook is unable to connect to the proxy server. (Error Code 0)
OK
---------------------------The certificate is perfectly fine from what I can tell. The main domain on it is "mail.domain.com" with "autodiscover.", "mailhub1.", "mailhub2.", and "domain.com" in the Subject Alternate Name.What on earth could I be missing here? It works on exchange 2010 but not on 2013 which is the exact opposite of what I was expecting.

Oooh, Im getting an error now in testconnectivity that wasnt there before so one of the approx. 6000 changes I made must have triggered it!
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
So I looked at the regirestry of both the old mailhub1 and the new mailhub2. The new one only had 2 entries where as the old one had tons. I copied it over, added mailhub2:6001-6004;mailhub2.domain.com:6001-6004 and did an iisreset and restarted the services.
The port still isnt open. Do I have to run a command or reboot? I would rather not have to reboot but I understand if I do. Also, am I doing this right?
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details

Exchange OWA Page Blank For Random Users After Mailbox Moves

We have three Exchange server. msexch1, msexch2, msexch3. msexch1 is currently offline. msexch1 and msexch have the CAS and MBX roles installed and are in a DAG. We moved all mailboxes from msexch1 to the other two servers. Since then we have users reporting
that when they logon to owa they get a blank page. The resulting url is owa/auth.owa. The domain we use is exchange.ourdomain.com. The fqdn of each exchange server is msexch2.ourdomain.com, etc. We use round robin dns for our exchange servers, therefore we
have two entries for exchange.ourdomain.com. For the purposes of this question lets say the ip of msexch2.ourdomain.com is 10.10.10.52 and msexch3.ourdomain.com is 10.10.10.53 and we have two entries in our dns for exchange.ourdomain.com, one for 10.10.10.52
and the other 10.10.10.53.
When a user experiences this issue I have found that when I ping exchange.ourdomain.com to determine which exchange server they are "connected" to; if I force them to use the other one they are then able to access owa just fine. For example, I
have a user whom is getting a blank page after they logon to owa. I ping exchange.ourdomain.com which returns 10.10.10.52 for an ip address, which tells me they are connected to msexch2.ourdomain.com. When I enter in the url https://msexch3.ourdomain.com/owa
to force them to logon using the other server, they are able to owa owa without any issues. When I use the url https://msexch2.ourdomain.com they receive a blank page after logon (as expected because this is the server they are trying to contact via dns exchange.ourdomain.com)
I have tried recreating both owa virtual directories which did nothing. I am at my wits end here and would greatly appreciate any assistance.

Hi,
According to your description, I understand that OWA get blank after move mailbox to another mailbox server, and you deploy DNS round robin in your environment.
If I misunderstand you concern, please do not hesitate to let me know.
It may be caused by OWA proxy cannot work correctly, please try below steps to double check:
1. Get a mailbox place in msexch3 and login OWA with
https://msexch3.ourdomain.com/owa.
2. Get other mailbox place in msexch2 and login OWA with
https://msexch3.ourdomain.com/owa.
If the steps 2 cannot proxy URL to https://msexch2.ourdomain.com/owa, it may be the key reason.
Please clarify the environment of your Exchange:
1. Which version are you used?
2. Check the authentication of OWA: Get-OwaVirtualDirectory | FL Identity,*URL*,*Auth*
OWA is configured to use integrated windows authentication on each virtual directory, and the external URL under is blank.
Also, please run below command to double check the health of Outlook Web App service:
Get-ServerHealth “msexch3” |?{$_.AlertValue –Eq “Unhealth”}
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013

Similar Messages

Maybe you are looking for