Exchange Migration 2010 to 2013 different AD domains....

Here's my situation, I have migrated our users AD accounts to a new domain (newDomain.corp), but still use the exchange server in our old domain (oldDomain.corp) with linked mailboxes, which work fine.
I am now to the point where I want to decommission our old 2010 exchange server in the old domain, or at least have the users mailboxes on a new Exchange 2013 box belonging to the new domain.
I am looking for the best way to migrate the users mailboxes from the EXCH01oldDomain.corp (2010 Exchange server) to the new exchange 2013 server EXCH01.newDomain.corp, yet still have both servers online serving mailbox roles for users for a limited
time. So basically, can i have 2 exchange servers from different domains serving the same users in newdomain.corp?
Free busy and calendaring all have to work.
Thanks!
richard

Hi Richard,
Please make sure the two-way trust between the new domain and old domain has been set up.
Generally, when we run New-MoveRequest cmdlet to move a mailbox from an Exchange source forest (Old domain) to an Exchange target forest (New domain), the target forest must contain a valid Mail-Enabled user account with the set of AD attributes.
Since the mailboxes in old Exchange 2010 are all linked mailbox
which have Mail-enabled user accounts in new forest, we can directly move the mailbox from old Exchange 2010 to new Exchange 2013.
We can use the Prepare-MoveRequest.ps1 script with the -UseLocalObject to move mailbox with the existing AD account in new domain:
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Exchange 2013 / 2010 coexistence with different public domains

Currently in my organization
1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
1x Exchange 2010 Standard w/SP3 - Mailbox
In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
miles away. We have no IT staff in any of our field locations.
We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
domain.local - Our internal Active Directory domain.
We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
severely underutilized.
Goals for the Exchange migration
My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
final topology is:
2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
1x VM with Exchange 2013 Standard w/SP1 - Client Access
1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
until Exchange 2013 SP3 is released.
Deployment Plan
Install Exchange 2013 on new VMs.
Create CAS Array object.
Configure Exchange 2013 to publish under the new namespace.
Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
Unknowns
My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
since we'll be using the new domain for each mailbox we move.
My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

Hi,
From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013.
About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
Checklist: Upgrade from Exchange 2010
Install Exchange 2013 in an Existing Exchange 2010 Organization
Upgrade from Exchange 2010 to Exchange 2013
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

SSRS/SharePoint Migration 2010 to 2013 connection issues

We are currently attempting to move our SharePoint 2010 to 2013 and SSRS Information. The first attempt at this we were unable to get SSRS to show up in Central Admin. We decided to rebuild all servers and re-installed everything.
This time we have SSRS showing up in Central admin and we are able to run some reports from our sites now. In our 2010 environment we are using "Windows authentication (integrated) or Sharepoint user" option with SharePoint Lists. I am unable to
get this to work in our 2013 Environment, the stored credentials with windows authentication will work however.
I have read t through many different books, MS Guides, Blogs, Forums, etc but unable to solve this issue.
I have tried editing the rsreportserver.config to match our Production, did not help. (also tried different authentications)
I found an article saying to change the "Forms" Auth in some config files to "Windows" did not help
When I try to go to our \\localserver\reportserver (appserver) I get a blank page with this info:
HTTP/1.1 200 OK
Server: Microsoft-IIS/8.5
Date: Fri, 21 Nov 2014 22:30:03 GMT
Connection: close
I have tried going into Central Admin -> General Application Settings -> Report Server Integration. and fill out this information also but receive this error:
Failed to establish connection with report server. Verify the server URL is correct or review ULS logs for more information. Product area: SQL Server Reporting Services, Category: Configuration
Pages
I am not sure if I have missed some step along the way of migrating and setting up this information. Any help or other things to try would be very helpful.
Thanks!

Hi young99,
According to your description, you get connection issue after migration from SharePoint 2010 to SharePoint 2013. Right?
In this scenario, we are not clear how you did the migration. Please follow these steps and check if you miss anything:
Restore Reporting Services encryption keys
Backup the SharePoint content databases and detach it.
Backup Reporting Services catalog database.
Copy Reporting Services configuration files.
Restore SharePoint Content databases to the new farm.
Restore the Reporting Servicesencryption keys.
Restore the SQL database that is the Reporting Services catalog database (ReportServer).
Restore Reporting Services configuration files.
Create a new Reporting Services service application.
For more information, please see:
Migrate a Reporting Services Installation (SharePoint Mode)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Public Folder Migration - 2010 to 2013 - Downtime incurred at "Lockdown" Stage

Looking for some information from those who have completed a successful Public Folder migration from 2010 to 2013.
1. Size of 2010 Public Folder Store
2. Downtime incurred upon the "Lock down 2010 Public Folder" stage once all mailboxes moved to 2013 and ready to cut-over to 2013

I would like to refer you at this well explained technet library and check whether you follow all the required prerequisites for a successful public folder migration from Exchange 2010 to 2013 : http://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx
Also, please check this another article resource : http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html
Apart from above resources, you may also consider at this comprehensive application(http://www.exchangemigrationtool.com/) that can be a better alternative approach while migrating public folder database
between two exchange server.

Business Contact Manager - migration 2010 to 2013

Hello,
I recently migrate my BCM 2010 database to 2013 following the link "Business Contact Manager for Microsoft Outlook 2013: Update for Upgrading from Business Contact Manager 2010".
At beginning everything went smoothly and I thought that everything has been migrated successfully.
Unfortunately, when I was checking my data more carefully, I found that some fields are now mixed up. This happened inside accounts and professional contacts forms.
The options and labels for fields email, address and phone are all mixed up.
Examples:
- Field email address, when selected "email 3", label changes to "work", this label belongs to address field.
- Field address, when selected "work", label changes to "email" that belongs to email field.
- Almost all labels are mixed up :(
Can somebody help my to find a solution for this issue....
Thank you
Regards
Abílio

Hello, we recently also migrated our BCM from 2010 to 2013 with the Business Contact Manager for Outlook 2013 Database Tool and all went also smoothly
except we now have the same problem as Abílio, meaning the fields are mixed up
Examples:
- Field email address, when selected "email 3", label changes to "work", this label belongs to address field.
- Field address, when selected "work", label changes to "email" that belongs to email field.
- Phone numbers: when selected "work", label changes to "Home"
- Almost all labels are mixed up :(
Can somebody please help us get this right again?

Error occurred in deployment step Recycle IIS Application Pool - migration 2010 to 2013

Hello
When I upgraded my solution from 2010 to 2013 and tried to deploy got the following error
Error occurred in deployment step 'Recycle IIS Application Pool'
Any idea ?
Thanks
Momo

Hi Momo,
Thank you very much for sharing your solution here. It would be helpful for others who encounter similar issue.
Thanks again,
Eric
Forum Support
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]
Eric Tao
TechNet Community Support

After Public Folder Migration 2010 to 2013

Last week I used technet page to migrate our exchange 2010 public folders over to exchange 2013. I'm still new to exchange management so I'm trying to understand what to do next.
The migration move showed 100% complete and successful and now show up as a mailbox in the 2013 admin center. I thought to myself Great! I did it. So I attempted to decommission my 2010 exchange server.
I attempted to remove my public folder database in the 2010 EMC and it tells me the database still contains folder replicas.
I found a couple options as possible fixes, either to remove it in ADSI edit or delete the files in the folder. I just want to make sure doing so won't effect the 2013 public folders.
Or should I do this a different way? Thanks in advance.

I had the server shut down for about 10 minutes and tested and was able to access PF's normally. Would you suggest longer?
Also I did attempt to remove the public folders via that article already and got the following error. I'm connected as an Admin with the correct rights.
[PS] C:\program files\microsoft\exchange server\v14\scripts>.\MoveAllReplicas.ps1 -Server mx2010 -NewServer mx2013
No existing 'PublicFolder' matches the following Identity: '\'. Make sure that you specified the correct'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.
+ CategoryInfo
: NotSpecified: (0:Int32) [Get-PublicFolder], MapiTransientException
+ FullyQualifiedErrorId : 2FF5D899,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
+ PSComputerName        : mx2010.company.local
No existing 'PublicFolder' matches the following Identity: '\NON_IPM_SUBTREE'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.
+ CategoryInfo
: NotSpecified: (0:Int32) [Get-PublicFolder], MapiTransientException
+ FullyQualifiedErrorId : 304E9272,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
+ PSComputerName        : mx2010.company.local

Can't complete public folder migration, 2010 to 2013

So I've been following both these:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part2.html
I've locked the 2010 PFs, nobody can access them. I've removed the preventcompletion flag in 2013, resumed the migration all according to the steps.
Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List
Shows no further activity any longer after some incremental stuff
Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics
Shows StatusDetail: InitialSeeding and PercentComplete: 95% and its not moving.
I've tried proceeding and removing the prevention from servering the hierarchy flag on my mailboxes. But it makes no impact on anything. The hold for migration flag remains true and the migration is not finishing.
What should I do?

Give it some more time. I don't know how much Public Folder data you have, but once the initial sync is done, it has to copy over the deltas to the mailboxes. I have seen this take some time. As long as it doesn't say failed, I think
you are in good shape :)

Public folder migration 2010 to 2013 insufficient access rights

Hi,
I'm having a frustrating time with trying to migrate public folders. I've migrated all the mailboxes with no problems but when trying to migrate public folders with the same account it fails with this message;
Active directory response: 00002098: SecErr: DSID-03150BB9, problem 4003
(INSUFF_ACCESS_RIGHTS), data 0
--> The user has insufficient access rights.
The account is in the organisation management and recipient management group.
I've tried ticking the inherit permission box in AD security.
I've tried creating a brand new account with the same permissions.
Nothing works. I'm tempted just to export to pst and import it to the public folder mailbox.
Any help would be much appreciated.
Thanks

Hi Nick,
ensure that the new admin account has the allow inheritance permission included
Also ensure that the account has full rights to all the public folders in Ex2010
Go to the application log and there would be an event triggered for the same with some description. YOu can find that it might be failing permission on a particular public folder if so grant them access.
And also check if the permission failed public folder is mail enabled. If so please disable the mail enable on that PF cancel the migration request and start a new migration request with the below cmd
New-publicfoldermigrationrequest -sourcedatabase (Get-publicfolderdatabase -server servername -csvdata (get-content c:\contents.csv -encoding byte) -BadItemLimit 5000 -AcceptLargeDataLoss
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.
Regards,
Sathish

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Exchange Server 2010: Convert Mailbox to MailUser

Dear All,
I plan to cutover migration exchange on-premises to exchange online with single-sign-on.
http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx
In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.
Could you guide what is the best solution to convert mailbox in exchange server 2010?
BR,
Khemarin
[email protected]

Hi Khemarin,
You can use the following cmdlet to convert a mailbox to a MailUser:
$DomainController = (Get-ADServerSettings).DefaultConfigurationDomainController.domain
$MailboxList= Get-Mailbox
foreach ($Mailbox in $MailboxList) {
    Disable-Mailbox -Id $mailbox.Identity -Confirm:$False -DomainController $DomainController
    Enable-MailUser -Id $mailbox.Identity -ExternalEmailAddress ($mailbox.alias +"@domain.com") -DomainController $DomainController
    Set-MailUser -Id $mailbox.Identity `
     -DomainController $DomainController `
     -CustomAttribute1 $Mailbox.CustomAttribute1
For more information, here is an article for your reference.
Converting a Mailbox to a MailUser
http://mikecrowley.wordpress.com/2010/12/09/converting-a-mailbox-to-a-mailuser-and-not-loosing-attributes/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
you completely understand the risk before retrieving any suggestions from the above link.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Migrate & coexist Exchange 2010 to 2010 in two different site under same domain

Hi all,
The initial plan was planning to coexist Exchange 2010 (old data center) & 2013 (new data center) .
Unfortunately there was a problem of upgrading the existing exchange 2010 sp2 to 2010 sp3 and Microsoft said they don't support this anymore.
So the only plan I can think of is build another exchange 2010 with SP3 (new data center) to coexist with existing exchange 2010 SP2 first then followed by exchange 2013.
I don't see any relevant info on the Internet for the coexistence of exchange 2010 SP2 and SP3. can you please share some detailed steps or info?
Thank you very much in advanced.

Hi all,
The initial plan was planning to coexist Exchange 2010 (old data center) & 2013 (new data center) .
Unfortunately there was a problem of upgrading the existing exchange 2010 sp2 to 2010 sp3 and Microsoft said they don't support this anymore.
So the only plan I can think of is build another exchange 2010 with SP3 (new data center) to coexist with existing exchange 2010 SP2 first then followed by exchange 2013.
I don't see any relevant info on the Internet for the coexistence of exchange 2010 SP2 and SP3. can you please share some detailed steps or info?
The last database upgrade exchange 2010 SP3 is unable to mount server with Exchange 2010 SP2 i.e., there is no database schema upgrade from SP1 or SP2 to SP3. Please check this link :
https://www.youtube.com/watch?v=M4hJfdqTe5s
You may download exchange Server 2010 Service Pack 3 from here :http://www.microsoft.com/en-us/download/details.aspx?id=36768
This Exchange Server 2010 SP3 software may be used to perform a new installation or to update an existing Exchange Server 2010 installation to Service Pack 2 (SP2) level.
Moreover, to migrate the mailbox database from exchange 2010 to 2013, you may consider on this exchange migration tool (http://www.exchangemigrationtool.com/) that can be a good approach for you.

Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 to 2013 users migration

Hi,
I am migrating users from Exchange 2010 to 2013 and facing a lot of migration issues. few of them are as follow.
1. It hung up at "syncing" and end up with a failure.
2. After a long migration i got the following errors
Error: MigrationPermanentExeception: Failed to reset the target mailbox after the move. Error Details:MaipExceptionADUnavailable: Unable to prepopulate the cache for user :: on domain controller xyz.domain.com (hr=0x80004005,ec=2414) Diagnosti Context: Lid:
65256 Lid:1494 ---- Remote Context Beg ---- Lid: 52664 StoreEc: 0x96E Lid: 35973 StoreEc: 0x96E Target Mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible.
Error details: Target mailbox connection was lost.
3. users migration is taking a lot of time although mailbox size is not big and both servers are in same datacenter.
Need urgent help pls....

Hi,
Here are the general steps for troubleshooting mailbox moves:
1. If the move request didn't complete, view the Move Request Statistics.
2. If the move request completed with errors, view the move report.
3. View the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
4. use the Exchange Management Console or the Exchange Management Shell to increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service.
For more detailed information about general steps for troubleshooting mailbox moves, you can refer to the article below:
http://technet.microsoft.com/en-us/library/dd638094(v=exchg.141).aspx
Additionally, in order to narrow down the cause, I’d like to confirm the following information:
1. Are the problematic target mailboxes in the same database?
2. Is there a time boundary? After that, you cannot move mailboxes:
http://social.technet.microsoft.com/Forums/en-US/90403f75-e530-478a-ab68-27823b730f68/exchange-2013-batch-to-migrate-users-from-2010-database-is-hung-at-syncing-after-a-disaster?forum=exchangesvrdeploy
Thanks,
Angela
Angela Shi
TechNet Community Support

Exchange Migration 2010 to 2013 different AD domains....

Similar Messages

Maybe you are looking for