Exchange 2007 - Exchange 2013 Mailbox Migration Issues
Exchange 2013 - Mail Flow is working. OWA Access is great. We have issues connecting Outlook 2010 Clients. If I create a new user and mailbox Outlook 2010 works fine. However, if we migrate a user's mailbox to the new Exchange
2013 server. Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server" There is something different about a newly created account and a migrated account. Any help would be great. I did check
inheritance in AD and it was on for these accounts. This occurs with any account migrated to the new server.
1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
generates and provides the correct information.
2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
Step by Step Screencasts and Video Tutorials
Similar Messages
-
2007 to 2013 Mailbox migrations hang at 95%
We are in the process of migrating from 2007 to 2013. 2013 is installed with CU2, new mailboxes created on 2013 work fine, mail is routing between both servers, etc. The only issue we seem to be having is we can't migrate mailboxes from 2007 to 2013. We
are testing migration with test email accounts with just a couple emails in them. We have several databases on the 2007 server and we've created several new ones on 2013, regardless of what database we try and migrate from and what database we try and migrate
to we have the same problem. The status just sits at "Syncing" and when I use Exchange PS with the Get-MoveRequestStatistics on the mailbox it shows StatusDetail-Finalization and PercentComplete-95%. The Mailbox size is only 6k.After almost 3 hours it finally completed. Here is the output using the above command.
RunspaceId : 0230342b-1960-4ff5-8ecd-93778501fd4c
MailboxIdentity : XXXXX/Users/Exchange2007 TestMigration02
DistinguishedName : CN=Exchange2007 TestMigration02,CN=Users,DC=XXXXX,DC=XX,DC=XX,DC=XX
DisplayName : Exchange2007 TestMigration02
Alias : testmigration02
ExchangeGuid : f435a52f-ad07-4b23-b25d-a27247f0af62
ArchiveGuid :
Status : Completed
StatusDetail : Completed
SyncStage : SyncFinished
Flags : IntraOrg, Pull
RequestStyle : IntraOrg
Direction : Pull
IsOffline : False
Protect : False
DoNotPreserveMailboxSignature : True
Priority : Normal
WorkloadType : LoXXl
Suspend : False
SuspendWhenReadyToComplete : False
IgnoreRuleLimitErrors : False
RecipientTypeDetails : UserMailbox
SourceVersion : Version 8.3 (Build 298.0)
SourceDatabase : EMAIL-SRV\First Storage Group\Mailbox Database
SourceServer : email-srv.XXXXX
TargetVersion : Version 15.0 (Build 712.0)
TargetDatabase : DB04 DO
TargetServer : NOC-EXCH-01.XXXXX
SourceArchiveDatabase :
SourceArchiveVersion :
SourceArchiveServer :
TargetArchiveDatabase :
TargetArchiveVersion :
TargetArchiveServer :
RemoteHostName :
RemoteGlobalXXtalog :
BatchName : MigrationService:Test04
StartAfter :
CompleteAfter :
RemoteCredentialUsername :
RemoteDatabaseName :
RemoteDatabaseGuid :
RemoteArchiveDatabaseName :
RemoteArchiveDatabaseGuid :
TargetDeliveryDomain :
ArchiveDomain :
BadItemLimit : 0
BadItemsEncountered : 0
LargeItemLimit : 0
LargeItemsEncountered : 0
AllowLargeItems : True
QueuedTimestamp : 9/5/2013 2:35:14 PM
StartTimestamp : 9/5/2013 2:35:24 PM
LastUpdateTimestamp : 9/5/2013 5:24:32 PM
InitialSeedingCompletedTimestamp : 9/5/2013 2:35:46 PM
FinalSyncTimestamp : 9/5/2013 2:35:47 PM
CompletionTimestamp : 9/5/2013 5:24:32 PM
SuspendedTimestamp :
OverallDuration : 02:49:17
TotalFinalizationDuration : 02:48:41
TotalDataRepliXXtionWaitDuration :
TotalSuspendedDuration :
TotalFailedDuration :
TotalQueuedDuration : 00:00:07
TotalInProgressDuration : 02:49:10
TotalStalledDueToCIDuration :
TotalStalledDueToHADuration :
TotalStalledDueToMailboxLockedDuration :
TotalStalledDueToReadThrottle :
TotalStalledDueToWriteThrottle :
TotalStalledDueToReadCpu :
TotalStalledDueToWriteCpu :
TotalStalledDueToReadUnknown :
TotalStalledDueToWriteUnknown :
TotalTransientFailureDuration :
TotalProxyBackoffDuration :
TotalIdleDuration : 00:00:01
MRSServerName : NOC-EXCH-01.XXXXX
TotalMailboxSize : 6.055 KB (6,200 bytes)
TotalMailboxItemCount : 7
TotalArchiveSize :
TotalArchiveItemCount :
BytesTransferred : 76.73 KB (78,568 bytes)
BytesTransferredPerMinute :
ItemsTransferred : 7
PercentComplete : 100
CompletedRequestAgeLimit : 7.00:00:00
PositionInQueue :
InternalFlags : SkipFolderPromotedProperties, WordBreak
FailureCode :
FailureType :
FailureSide :
Message :
PoisonCount : 0
FailureTimestamp :
IsValid : True
ValidationMessage :
RequestGuid : 65084222-de5e-49b8-bae4-6c9bb9a6a961
RequestQueue : DB04 DO
Identity : XXXXX/Users/Exchange2007 TestMigration02
DiagnosticInfo :
Report : 9/5/2013 2:35:14 PM [NOC-EXCH-01] '' created move request.
9/5/2013 2:35:22 PM [NOC-EXCH-01] The Microsoft Exchange Mailbox RepliXXtion
service 'NOC-EXCH-01.XXXXX' (15.0.712.11 XXps:3F) is examining
the request.
9/5/2013 2:35:22 PM [NOC-EXCH-01] Connected to target mailbox 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)', database 'DB04 DO', Mailbox server
'NOC-EXCH-01.XXXXX' Version 15.0 (Build 712.0).
9/5/2013 2:35:23 PM [NOC-EXCH-01] Connected to source mailbox 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)', database 'EMAIL-SRV\First Storage
Group\Mailbox Database', Mailbox server 'email-srv.XXXXX'
Version 8.3 (Build 298.0).
9/5/2013 2:35:23 PM [NOC-EXCH-01] Request processing started.
9/5/2013 2:35:23 PM [NOC-EXCH-01] Source mailbox information:
Regular Items: 2, 6.055 KB (6,200 bytes)
Regular Deleted Items: 0, 0 B (0 bytes)
FAI Items: 5, 0 B (0 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
9/5/2013 2:35:23 PM [NOC-EXCH-01] Mailbox signature will not be preserved for
mailbox 'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)'. Outlook clients
will need to restart to access the moved mailbox.
9/5/2013 2:35:24 PM [NOC-EXCH-01] Stage: CreatingFolderHierarchy. Percent
complete: 10.
9/5/2013 2:35:25 PM [NOC-EXCH-01] Initializing folder hierarchy from mailbox
'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)': 38 folders total.
9/5/2013 2:35:25 PM [NOC-EXCH-01] Folder creation progress: 0 folders created
in mailbox 'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)'.
9/5/2013 2:35:27 PM [NOC-EXCH-01] Folder hierarchy initialized for mailbox
'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)': 37 folders created.
9/5/2013 2:35:27 PM [NOC-EXCH-01] Stage: CreatingInitialSyncCheckpoint.
Percent complete: 15.
9/5/2013 2:35:28 PM [NOC-EXCH-01] Initial sync checkpoint progress: 0/38
folders processed. Currently processing mailbox 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)'.
9/5/2013 2:35:30 PM [NOC-EXCH-01] Initial sync checkpoint completed: 35
folders processed.
9/5/2013 2:35:30 PM [NOC-EXCH-01] Stage: LoadingMessages. Percent complete:
20.
9/5/2013 2:35:32 PM [NOC-EXCH-01] Messages have been enumerated successfully.
7 items loaded. Total size: 6.055 KB (6,200 bytes).
9/5/2013 2:35:32 PM [NOC-EXCH-01] Stage: CopyingMessages. Percent complete:
25.
9/5/2013 2:35:32 PM [NOC-EXCH-01] Copy progress: 0/7 messages, 0 B (0
bytes)/6.055 KB (6,200 bytes), 32/38 folders completed.
9/5/2013 2:35:41 PM [NOC-EXCH-01] Copying messages is finished. Copying rules
and security descriptors.
9/5/2013 2:35:46 PM [NOC-EXCH-01] Initial seeding completed, 7 items copied,
total size 6.055 KB (6,200 bytes).
9/5/2013 2:35:46 PM [NOC-EXCH-01] Stage: IncrementalSync. Percent complete:
95.
9/5/2013 2:35:47 PM [NOC-EXCH-01] Folder hierarchy changes reported in source
'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)': 0 changed folders, 0
deleted folders.
9/5/2013 2:35:47 PM [NOC-EXCH-01] Content changes reported for mailbox
'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)': 0 changed messages.
9/5/2013 2:35:47 PM [NOC-EXCH-01] Incremental Sync 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)' completed: 0 changed folders, 0
changed messages.
9/5/2013 2:35:47 PM [NOC-EXCH-01] Stage: IncrementalSync. Percent complete:
95.
9/5/2013 2:35:47 PM [NOC-EXCH-01] Final sync has started.
9/5/2013 5:24:20 PM [NOC-EXCH-01] Folder hierarchy changes reported in source
'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)': 0 changed folders, 1
deleted folders.
9/5/2013 5:24:20 PM [NOC-EXCH-01] Content changes reported for mailbox
'Primary (f435a52f-ad07-4b23-b25d-a27247f0af62)': 0 changed messages.
9/5/2013 5:24:21 PM [NOC-EXCH-01] Incremental Sync 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)' completed: 1 changed folders, 0
changed messages.
9/5/2013 5:24:21 PM [NOC-EXCH-01] Source mailbox information:
Regular Items: 2, 6.055 KB (6,200 bytes)
Regular Deleted Items: 0, 0 B (0 bytes)
FAI Items: 5, 0 B (0 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
9/5/2013 5:24:21 PM [NOC-EXCH-01] Stage: FinalIncrementalSync. Percent
complete: 95.
9/5/2013 5:24:21 PM [NOC-EXCH-01] Mailbox Store finalization is complete.
9/5/2013 5:24:21 PM [NOC-EXCH-01] SessionStatistics updated.
9/5/2013 5:24:21 PM [NOC-EXCH-01] Verifying mailbox contents...
9/5/2013 5:24:26 PM [NOC-EXCH-01] Mailbox contents verifiXXtion complete: 35
folders, 7 items, 6.055 KB (6,200 bytes).
9/5/2013 5:24:26 PM [NOC-EXCH-01] Mailbox 'Exchange2007 TestMigration02' was
loaded from domain controller 'email-srv.XXXXX'.
9/5/2013 5:24:29 PM [NOC-EXCH-01] Mailbox was updated using domain controller
'NOC-XX-ROOT.XXXXX'.
9/5/2013 5:24:29 PM [NOC-EXCH-01] Mailbox 'Exchange2007 TestMigration02' was
updated on domain controller 'NOC-XX-ROOT.XXXXX'.
9/5/2013 5:24:29 PM [NOC-EXCH-01] Move has completed and final clean up has
started.
9/5/2013 5:24:31 PM [NOC-EXCH-01] Source mailbox 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)' was successfully cleaned up after the
move.
9/5/2013 5:24:31 PM [NOC-EXCH-01] Target mailbox information:
Regular Items: 2, 17.93 KB (18,363 bytes)
Regular Deleted Items: 0, 0 B (0 bytes)
FAI Items: 5, 6.247 KB (6,397 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
9/5/2013 5:24:31 PM [NOC-EXCH-01] Target mailbox 'Primary
(f435a52f-ad07-4b23-b25d-a27247f0af62)' was successfully reset after the move.
9/5/2013 5:24:32 PM [NOC-EXCH-01] Request is complete.
ObjectState : New
I ran another testmigration user move and it went through in 30 seconds. -
Exchange 2013 mailbox migration issues
or I could just restart the 2013 mail server.... *sigh*
So Exchage 2013 is set up, sending and receiving emails is working, OWA access is working and redirecting to our old 2010 if the mailbox resides there.However after moving a mailbox from 2010 to 2013 there have been a few issues.The mailbox connects ok with Outlook 2013, but will not open the onprem Archive."cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available.."This works ok in OWA.I then deleted the outlook profile, but now Outlook cannot connect to create a profile at all!It detects my name and email ok, then when it gets to "logging on to the mail server" I get the error"Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this...
This topic first appeared in the Spiceworks Community -
Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'
I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227) Diagnostic
context: ...... Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN> Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 45169 StoreEc: 0x824
Lid: 50544 ClientVersion: 15.0.847.32 Lid: 52080 StoreEc: 0x824 Lid: 44273 Lid: 49064 dwParam: 0x1 Lid: 37288
StoreEc: 0x6AB Lid: 49064 dwParam: 0x2 Lid: 59431 EMSMDB.EcDoConnectEx called [length=203] Lid: 51239 EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 3460 Lid: 12696 dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1753 Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4 Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN> Lid: 12952 dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 59505 StoreEc: 0x824 Lid: 50544 ClientVersion:
15.0.847.32 Lid: 52080 StoreEc: 0x824 Lid: 36081 Lid: 51152 Lid: 52465 StoreEc: 0x80040115
Lid: 60065 Lid: 33777 StoreEc: 0x80040115 Lid: 59805 Lid: 52487 StoreEc: 0x80040115 Lid: 19778 Lid: 27970
StoreEc: 0x80040115 Lid: 17730 Lid: 25922 StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
JonAny update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required -
Can only access emails through OWA after migration from exchange 2007 to 2013
can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support -
Issue moving remote user from exchange 2007 to 2013
have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.
outlook was working connecting to both servers, and OWA was working on both servers.
couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
could this have caused my outlook connectivity issue?
I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
any suggestions?I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
Hi,
Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
Please try to logon OWA to check whether this user works.
If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
Please try to run Outlook under safe mode to avoid AVs and add-ins.
Thanks
Mavis Huang
TechNet Community Support -
How to migrate from exchange 2007 to 2013 step by step tutorials please
Hi
I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
We have 800 mailbox in total
Our domain controllers are
Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
I currently only have 1 exchange server 2007, with all the roles on the one server. I would like to keep that same as
well with exchange 2013.
ThanksExchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
migration task in more secure way. -
Exchange 2013 mailbox migration stalled duration
I am in the process of migrating mailboxes from Exchange 2007 to 2013. The moves seem to take an awfully long time. I am migrating a batch of 10 users and the total mailbox size is 32GB. It has been running for 12 hours and is not complete. I have notice
that there is a "Stalled Duration Time" what does that represent? Also, what should I expect in terms of migration time?Also, seeing this in the logs. It's been about 18 hours now.
Relinquishing job because of large delays due to unfavorable server health or budget limitations.
12/15/2014 9:06:11 PM [Server01] Copy progress: 7546/44948 messages, 167.4 MB (175,539,357 bytes)/2.441 GB (2,620,927,938 bytes), 9/300 folders completed.
12/15/2014 9:06:11 PM [Server01] Relinquishing job because of large delays due to unfavorable server health or budget limitations.
12/15/2014 9:22:30 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:24:35 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:27:10 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:31:53 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:36:51 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:39:47 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:41:21 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:54:43 PM [Server01] Connected to target mailbox 'f491b26b-4a91-4b23-a9aa-d256e8acb8c4 (Primary)', database 'Server0101', Mailbox server 'Server01.domain.com' Version 15.0 (Build 995.0).
12/15/2014 9:54:44 PM [Server01] Connected to source mailbox 'f491b26b-4a91-4b23-a9aa-d256e8acb8c4 (Primary)', database 'mailbox01\Database\DatabaseDB', Mailbox server 'MAILBOX01.domain.com' Version 8.3 (Build 379.0).
12/15/2014 9:58:16 PM [Server01] Request processing continued, stage LoadingMessages. -
Free/Busy not working Exchange 2007 and 2013 co-existence
Hi,
I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
works correctly, but between Exchange 2007 and 2013 it's not working.
I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
The internal and the external URLs are set to https://legacy.mydomain.com/....
What am I missing?
Thanks & Kind Regards,
JürgenHi,
According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
1. Does the issue happen to all users or specific users?
2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
create a new Outlook profile
to have a try.
4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
Virtual directories settings in Exchange 2007:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Certificate and Virtual directories settings in Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
Regards,
Winnie Liang
TechNet Community Support -
Legacy Namespace for Exchange 2007 to 2013 co-existence
We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
Thanks in advance for your help.In coexistence with exchange 2013 and legacy version the request happens in 2 types.
For Exchange 2010 –
Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
For Exchange 2007 –
Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
Certificates:
All the required SAN entries for UM,webservices and activesync should be created.
Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
Exchange 2013 only then owa redirection will work.
You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
Existence.
Following change needs to be done in Firewall
External OWA URL should be directed to exchange 2013 Internet Facing CAS.
External EWS URL should be directed to exchange 2013 Internet Facing CAS.
External Autodiscover URL should should be directed to Exchange 2013 CAS.
External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
External UMvirtualDirectory should be directed to Exchange 2013 CAS.
Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
a mailbox on Exchange 2007.
External and Internal DNS settings
Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN
Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
address
The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server
Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
Authentication Settings:
This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
Set the owa virtual directory authentication only to Basic in exchange 2007.
In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
Things to check:
If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
Virtual Directories doesn’t have it configured.
If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
For further references you can refer my article below
http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
Remember to 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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP) -
Exchange 2007 and 2013 coexistance Problem
We are in the process to migrate our current Exchange 2007 to Exchange 2013.
Our environment is as follows:
HT01= Hub CAS Server (Exchange 2007)
MB1, MB2 = Mailbox CCR Cluster (Exchange 2007)
CAS1= CAS Server (Exchange 2013)
MBNew1, MBNew2 = Mailbox Servers (Exchange 2013)
Emails for users that are on Exchange 2007 can send and receive external emails. But they cannot send emails to users that are on Exchange 2013.
Users on Exchange 2013 can send/receive externally, send to Exchange 2007 users, but cannot receive emails from Exchange 2007 Users.Are you getting any NDR? Post it.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
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. -
ActiveSync in Exchange 2007 and 2013 Coexistence
Hi,
I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
autodiscover works well for users on both 2007 and 2013
I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
I have A records configured for both names on my public DNS and internal DNS
THE ISSUES
testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
Existing users on exch2007 can no longer receive mails on their mobile devices
URLs
Exchange 2007
Exchange 2013
Internal owa
mydomain.com/owa
mail.mydomain/owa
External owa
legacy.mydomain.com/owa
mail.mydomain.com/owa
AutoDiscover
mail.mydomain.com
mail.mydomain.com
EWS
legacy.mydomain.com
mail.mydomain.com
ECP
mail.mydomain.com
Internal ActiveSync
legacy.mydomain.com
mail.mydomain.com
External ActiveSync
$null
mail.mydomain.com
OutlookAnywhere
legacy.mydomain.com
mail.mydomain.com
I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
Any help on this would be much appreciated ..
Richard ..
..forever is just a minute away*You don't need to use a legacy URL for ActiveSync in Exchange 2013. It will proxy ActiveSync for Exchange 2007 just fine. In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition. I recommend
you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
Exchange 2007 and 2013 coexistence
Hi,
we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server) i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
ThanksHello,
Please check your DNS configuration and ISA/TMG rules.
We recommend you use TMG or UAG.
You can refer to the "TMG rules" section in the following article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Cara Chen
TechNet Community Support -
Autodiscover service overlap between Exchnage 2007 and 2013 mailboxes
Hi,<o:p></o:p>
I have Exchange 2007 Legacy environment and owa/rpc/activesync/autodiscover configured with DNS name owa.domain.com.<o:p></o:p>
I have installed Exchange 2013 and owa/rpc/activesync/autodiscover configured with DNS name mobile.domain.com.<o:p></o:p>
Its a requirement to retain different URL for Exchange 2007 and 2013.<o:p></o:p>
Now...Exchange 2007 users RPC over http is broken because their outlook rpc setting is automatically getting configured to mobile.domain.com which belongs to Exchange 2013.<o:p></o:p>
I know I have thought about updating the hostfile for Exchange 2007 clients to achieve this.Without changing the URL and
retaining the existing DNS names, can we prevent RPC over https outlook setting changes for Exchange 2007 users alone?Hi,
You can deploy localxml for Exchange 2007 user:
http://support.microsoft.com/kb/2212902/en-gb
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 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName : EXCHANGE2007SVR
SSLOffloading : False
ExternalHostname : legacy.domain.com
InternalHostname :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods : {Basic}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : False
MetabasePath : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 8.3 (Build 83.6)
Server :
EXCHANGE2007SVR
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 12/31/2013 4:08:04 PM
WhenCreated : 7/18/2008 10:56:46 AM
WhenChangedUTC : 12/31/2013 9:08:04 PM
WhenCreatedUTC : 7/18/2008 2:56:46 PM
OrganizationId :
OriginatingServer : DC1.domain.local
IsValid : True
ObjectState : Changed
ServerName :
EXCHANGE2013SVR
SSLOffloading : True
ExternalHostname : webmail.domain.com
InternalHostname : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : EXCHANGE2013SVR
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 1/7/2014 11:29:05 AM
WhenCreated : 12/31/2013 1:17:42 PM
WhenChangedUTC : 1/7/2014 4:29:05 PM
WhenCreatedUTC : 12/31/2013 6:17:42 PM
OrganizationId :
OriginatingServer : DC1.domain.local
IsValid : True
ObjectState : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support
Maybe you are looking for
-
Passing Parameters via Post Method from Webdynpro Java to a web application
Hello Experts, I want to pass few parameters from a web dynpro application to an external web application. In order to achieve this, I am referring to the below thread: HTTP Post As mentioned in the thread, I am trying to create an additional Suspend
-
Dec 24, 2012 9:47 AM I made a article in Pages, so I exported to the desk top by PDF now I can not move it to the tash, it keeps saying can not remove. There must be a way. Please help. When I click on Desktop it does not show in a finder window b
-
I have a Macbook running SnowLeopard. I recently purchased a Canon Powershot SX30. I can remove the card and use a card reader but can not get the Macbook to recognize the camera when I plug the USB cord from the camera to the computer. Any suggestio
-
Thinkpad yoga ultrabook screen flickers
I just got a thinkpad yoga and I have noticed since I started using it that the screen randomly flickers. I can't narrow it down to a time where I'm doing a specific task. Any help in tracking down the problem would be greatly appreciated. Solved!
-
Calls from Lumia 610 doesn't transfer to MW600
Hi, I'm using a Nokia Lumia 610 running Windows Phone 7.5 Mango, using the MW600 with the phone's music works fine. But when a call comes up or I made an outgoing call, no audio from earphones and microphones of MW600. Call audio remains on the hands