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

Similar Messages

  • 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.

  • 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

    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
    Does simply recycling the ActiveSync app pool speed things up?
    Also, I would recommend installing CU6 instead of SP1.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • 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.

  • Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

    Hi
    I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
    not available. either there are network problems or the exchange server is down for maintenance."
    Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
    The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

    Hi northerly,
    I recommend you follow the steps below for troubleshooting:
    1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
    2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
    3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
    What's more, here is a helpful KB for your reference.
    Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
    http://support.microsoft.com/kb/2834139/en-us
    Hope my clarification is helpful.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • 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.

  • Exchange 2007 - User's mailbox disappeared in EMC but they can still send and receive email

    We have a user that was complaining about not being in the address book anymore.  After I did a little rooting around in management console I noticed that their mailbox was no longer listed under Recipient Configuration -> Mailbox, but what's weirder
    is I can do a search and find her listed in the results - at which point I can right-click her name and do everything I normally can with no problem. Listing all of the mailboxes with PS shows her still there too.  As far as I know, she is the only user
    having this problem.
    She can send and receive email just fine, but like I said, she is no longer in the global address list so other users have trouble sending her stuff.  At her computer, I tried repairing her email (under account settings) but the process would fail when
    searching for her settings.  I don't know if this is a stupid thing to add, but I did run Clean-MailboxDatabase on our first storage group to see if her mailbox had been deleted or disconnected or whatnot but nothing is currently showing up in Recipient
    Configuration -> Disconnected Mailbox.
    Some info on our setup:
    Exchange 2007 on Windows Server 2003r2
    AD is on Windows Server 2008r2
    Her computer is running Outlook 2010
    I did restart our Exchange server 2 days ago to update VMWare tools, but no Windows updates were installed.  She couldn't tell me exactly when this problem started, but it was more-than-likely in the last couple of days as she was recently married and
    I had to change her name in AD and Exchange - so everything was confirmed 100% functioning 2-3 weeks ago.
    I'm at a lost for what the issue could be, but then again Exchange isn't exactly my forte, so any help would be much appreciated.

    First things first - is her mailbox hidden from address lists?  Run
    Get-Mailbox <alias> | Fl HiddenFromAddressListsEnabled to find out.  It probably isn't, but we need to clear this, just in case.
    Now, assuming it is not hidden, have you searched for both her maiden and married names in your directory?  Often, when the name on a mailbox is changed, the display name is not - and vice versa.  Also, has her email address also changed? 
    If so, has a secondary proxy address been added to reflect her maiden name?  I'd do this, just to be sure things aren't lost that should be delivered to her.
    I can't think of anything else obvious right now.  After you've checked these things, get back to us with their results.

  • Exchange 2007 servers reports mailbox size full, but mailbox shows empty in OWA or Outlook.

    When the users log into their mailboxes in OWA or Outlook get this warning: "You have exceeded your limit quota and can not send or receive mail" but really they have the mailbox empty, there's nothing in calendar, folders or deleted items.
    I ran this command Get-MailboxStatistics and the mailbox reports for example 500 MB.
    I deleted the deleted items and I configured deleted items retention to 0 days to ensure that it wasn't the problem, but the servers still reporting the same mailbox size (500 MB). 
    This happen to some mailboxes, not all
    Please help, what can I do?

    1. How many Exchange 2007 servers do you have?
    2. What service pack and rollups are installed on the Exchange 2007 server(s)?
    3. If you have more than one server, are you using any form of replication: LCR, SCR, CCR... etc. ?
    4. What 3rd party software is installed on the Exchange 2007 server(s)? For example, antivirus, archiving, etc.
    5. Can you confirm that this happens in OWA as well? I see you mentioned OWA but I've just glanced at another problem with incorrect folder size being indicated in Outlook and it apparently had to do with the .OST file. Of course, if the problem occurs with
    OWA as well, then the OST file would not come into play. Sorry to insist on that but I'm trying to rule some things out, if possible (like 3rd party apps, maybe something with replication, maybe a problem that was corrected in a service pack or rollup).
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2007/2010 Console doesn't show up Exchange 2007 Databases after RBAC Implementation

    I have implemented a RBAC model after which Exchange 2010/2007 Console won't show up Exchange 2007 Mailbox Databases.
    Everything was working fine up until the Users were members of "Exchange Recipient Administrators" Group.
    I have created Custom Roles based on PArent Roles, Mail Recipients, Mail Recipient Creation, Distribution Groups & Public Folders and assigned that to a universal security group "Helpdesk operations". I removed membership for Helpdesk operations
    from "Exchange Recipient Administrators" Group and assigned the Custom Roles to "Helpdesk Operations" using the cmdlet below:
    New-ManagementRoleAssignment "Custom Role" -SecurityGroup "HelpDesk Operations"
    Exchange 2010 console shows Exchange 2010 Databases but not Exchange 2007 DAtabases. Exchange 2007 console doesn't show up any databases on New-Mailbox and simply displays a message "No Objects Found".
    Even Get-MailboxDatabase REturns blank output on Exchange 2007 SHell. Please help me with this and let me know in case if there is something that i need to be looking at!
    any help on this is much appreciated.
    M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
    Information is provided is "AS IS" and confers NO Rights!!

    Hi,
    I recommend you use the following cmdlet and check the result.
    Get-MailboxDatabase -Server "Exchange 2007 server name"
    In my environment, if I don't specify the Server parameter on Exchange 2010 Management Shell, Exchange 2007 mailbox database can't be displayed. If I specify the Server parameter, Exchange 2007 mailbox database will be displayed.
    What's more, please check if the account you use has been delegated the Exchange View-Only Administrator role.
    Here is a thread for your reference.
    Get-MailboxDatabase
    http://technet.microsoft.com/en-us/library/bb676367(v=exchg.80).aspx
    Hope it helps.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 07 to 13 OWA Error after mailbox move.

    I have an Exchange 2007 – Exchange 2013 Sp1 environment set up and coexistence is working properly. The issue I am seeing is sometimes when we do a migration from 07 to 2013 sporadic users cannot access OWA on 2013, they get an error..
    X-OWA-Error: ClientError;exMsg=_u is not defined;file=_y.$LE@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:155BootViewModelsComponent.prototype.$1XA/<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:305920_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309BootViewModelsComponent.prototype.$1XA/<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:306788_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309ApplicationAppComponent.prototype.$1XA/r<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:1141362_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309Program.main@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:663573invokeMain@https://XXXXX/owa/:549:17owastart/<@https://XXXXX/owa/:601:15:1
    X-OWA-Version: 15.0.847.32
    X-FEServer: SERVER1
    X-BEServer: null
    Date: 1/2/1601 3:14:04 PM
    It doesn’t happen for everyone just a few people, if we move them to different database in the same DAG on a different server they can access OWA.
    What logs can I look at to help find the root cause of this error? 
    Or has anyone seen this before?
    Thanks!
    Joe
    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Practice Manager Artemis Technology LLC

    Hi Winnie,
    Thank you for responding.  The mailbox and cas servers are separate, and I have rebooted and reset IIS multiple times.
      What I have come to find out is if I access the OWA from an older browser it doesn’t switch to OWA light, a newer browser will not have this problem and can get in with the problem mailbox. 
    If I specify the light directory
    owa/?layout=light I can get in to the problem mailbox with no issues.  
    It seems like the local client can’t process the script that will force the client to use OWA light.
    Thanks!
    Joe
    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP
    Hi Joe,
    According to youe further description, the issue seems to be related to browser. Please update your browser to the latest version or set the Internet Explore to Compatibility view to have a try.
    Regards,
    Winnie Liang
    TechNet Community Support

  • BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

    Hello,
    I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
    The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
    The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
    The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
    1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
    2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
    3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
    However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
    the migration to Exchange 2010?
    Thanks,
    HA

    Hello Ha20,
    Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • 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>

  • Free/Busy not working after mailbox migration to Exchange 2013

    I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
    It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated.  If we remove the Outlook profile and recreate it, all is good.  Problem is that this is happening to more and more people.  Everyone
    is on Outlook 2010
    Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
     Autodiscover: Outlook Provider Failure
     Exchange Web Services          Failure
     Availability Service           Skipped
     Offline Address Book           Failure
    The same if I run that command against the Exchange 2007 server.
    What am I doing wrong?

    I should have mentioned that.  Yes, OWA works perfectly for the affected users.  Just as deleting their Outlook profile and recreating a new one does.
    Results of Get-WebServicesVirtualDirectory:
    Identity    : Exch2007Srvr\EWS (Default Web Site)
    InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
    ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
    Identity    : Exch2013Srvr\EWS (Default Web Site)
    InternalUrl : https://mail.company.com/ews/exchange.asmx
    ExternalUrl : https://mail.company.com/ews/exchange.asmx
    The URL you reference above is actually the site I used to perform migration.
    What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
    get:
    Attempting URL
    https://mail.company.com/autodiscover/autodisconver.xml found through SCP
    Autodiscover to
    https://mail.company.com/autodiscover/autodisconver.xml starting
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    GetLastError=0;httpStatus=401
    Autodiscover to 
    https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
    Attempting URL 
    https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
    Autodiscover to
    https://autodiscover.company.com/autodiscover/autodisconver.xml starting
    GetLastError=0; httpStatus=200.
    Autodiscover to
    https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
    Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
    GetLastError=12029; httpStatus=0
    Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
    Autodiscover to
    https://autodiscover.company.local/autodiscover/autodisconver.xml starting
    GetLastError=0; httpStatus=0
    GetLastError=0; httpStatus=200
    Autodiscover to
    https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
    Local autodiscover for company.local starting
    Local autodiscover for company.local Failed (0x8004010F)
    Redirect check to
    https://autodiscover.company.local/autodiscover/autodisconver.xml starting
    Redirect check to
    https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
    Srv Record lookup for hydraforce.ads starting
    Srv Record lookup for hydraforce.ads Failed(0x8004010F)
    However, when I did this on a system that cannot see any calendars, it all works perfectly.
    Browsing to
    https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

  • Mailbox move from 2007 to 2010 causes performance problems on the 2007 box AFTER the move

    I'm having a problem where moving a mailbox from our 2007 Exchange server to our 2010 Exchange server is causing clients that are still on the 2007 server to lock up, sometimes for up to 20 minutes.  This all happens maybe 5 minutes *after* the mailbox
    move has completed - during the move we see no problems.
    I start seeing events 5015, 5016, and then 10025 on the 2007 box and that's when users start complaining of Outlook locking up and emails going to Outbox.
    If I do this off-hours like at night or on weekends I don't see the problem, which I'm sure is because there are far fewer clients connected.  We do not use cached exchange mode for a variety of reasons but mainly because our document management software
    doesn't play nicely with it.
    I am leaning toward the disk structure of our 2007 server.  They are fast (15k SAS) but arranged in a RAID-5 which isn't ideal, but which keeps up fine in all other cases.  What is happening post-move that makes for so much disk activity?  I
    thought maybe if I moved a good chunk of users off the 2007 box off-hours it might make daytime moves more possible, but I just tried again and it all locked up just the same.
    The details:
    Exchange 2007 SP3 (15k SAS disks, 2x quad core Xeon E5345, 16GB RAM)
    Exchange 2010 (VMware with 4 virtual cores, 16GB RAM, storage on EqualLogic SAN)
    Clients are almost exclusively Outlook 2010 on Win7, though a handful of 2007 users remain.
    We have about 240 users total, about 100 of which have moved to the 2010 system.
    Thanks for any suggestions.  I am stumped at this point.

    Hi,
    Based on my experience, the issue generally happens during the migration the old server didn’t get pulled from Active Directory correctly .
    http://www.squidworks.net/2013/02/solved-event-ids-5015-5016-microsoft-exchange-2010-cannot-find-a-route-to-the-source-transport-server-or-home-mta-server/
    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.
    Thus, please check if the issue still can be reproduced after the migration.
    If you have any question, please feel free to let me know.
    Best regards,
    Angela Shi
    TechNet Community Support

  • Concurrent mailbox moves from Exchange 2007 to 2013

    We are in the process of migrating from Exchange 2007 to Exchange 2013. We have about 200 mailboxes and we want to move them in groups of 40-50 at a time. I am trying to get more then 1 mailbox to actually sync to the new database at once.
    I start the batch with 49 mailboxes but only 1 mailbox is showing any progress when I go to details. They all have a status of "syncing" but only one has any "items synced".
    I have run multiple articles about increasing concurrent migrations from 2007 to 2010 and 2010 to 2013 and they all mention going to MsExchangeMailboxReplication.exe.config on the destination server and setting the “MaxActiveMovesPerTargetMDB" value
    to something larger. By default 2013 has it set to 20 would should be more than enough  for me. However despite this setting I still only see 1 mailbox syncing at a time.
    Is there someplace I should be making a similar change on the 2007 box? I can't find a file with that name so I am not sure if there is something to change or if it's even needed.
    Why is this not working? Any help is much appreciated. Thanks!

    Outlook will show the infamous login popup and users will not be able to access Exchange 2013 Public Folders.
    You can check the Outlook Clients version in Exchange Management Shell with Get-LoginStatistics (ex. Outlook 2010):
    Get-Logonstatistics | select-object username,clientversion | where {$_.clientversion -gt "14.0*" -AND $_.clientversion -lt "14.0.6117.5001"}
    Step by Step Screencasts and Video Tutorials

Maybe you are looking for