Comments on: Moving mailboxes from Exchange 2010 organization to Exchange 2013 organization – Part 1 https://dizdarevic.ba/ddamirblog/?p=114 Blog about information technologies and learning Thu, 28 Jul 2016 08:58:35 +0000 hourly 1 https://wordpress.org/?v=6.4.3 By: Neth Wills https://dizdarevic.ba/ddamirblog/?p=114#comment-280157 Thu, 28 Jul 2016 08:58:35 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-280157 Mailbox migration can be easily done from (one domain to another) Exchange 2010 to 2013 using manual solution (https://blogs.technet.microsoft.com/meamcs/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i/), as well as if you prefer automated software (http://www.stellarservertools.com/exchange-edb-pst-converter.php)…it all up to you & your organization need!

]]>
By: Phillip pino https://dizdarevic.ba/ddamirblog/?p=114#comment-257640 Wed, 16 Mar 2016 12:55:46 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-257640 In reply to Daniel.

I ran into this too. The certificate on my test machines had a wildcard for the externally facing name. If I used the CAS server name or the internal load balanced name, I would get the same error stated. When I switched to the external name (I changed the DNS record fo the “external” name to point to the internal IP of one of my CAS servers) I was able to connect to the endpoint.

]]>
By: Phillip pino https://dizdarevic.ba/ddamirblog/?p=114#comment-257638 Wed, 16 Mar 2016 12:52:57 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-257638 Nice article. question.
Is there a way to link/MEU an exisiting User Object in the target domain if
1) the samaccountname is different from the source
2) the givenName and/or sn is different from the source domain
3) the displayName is different from the source domain

I see that if an existing contact exists prepare-moverequest will delete the contact and merge the addresses in the MEU. However, when I run the PS1 and one or more of the issues above are in place, the script creates a new user object instead of linking what is existing. I was able to get it to work my first time with a test account in the lab. Subsequent test in the same lab only create new accounts.

]]>
By: Philip Pino https://dizdarevic.ba/ddamirblog/?p=114#comment-253308 Tue, 23 Feb 2016 16:07:12 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-253308 I am looking to move my mailboxes from 2010 to 2013. I’m being brought in late to this migration and am looking to see what my options might be.

If I someone has already stood up User accounts (not disabled user not mail enabled) and contacts for the source mailboxes (for mail flow,) will I have to delete the contacts (exporting out the legacyexchangeDNs to apply to the target mailboxes) in order to run this prepare script? I am betting that I would need to remove the target orgs contacts since the SMTP addresses will conflict with the source mailboxes primary address.
Will the prepare script negatively modify the target user accounts or is it better to use ADMT? Will ADMT change the user accounts so that they can’t be used? (the new target forest AD accounts are in use now.) Does the new version of ADMT play nicer with Exchange migrations?

Any help would be appreciated.

]]>
By: Natesh https://dizdarevic.ba/ddamirblog/?p=114#comment-222995 Fri, 07 Aug 2015 05:43:10 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-222995 Hi,

I have question?

Can i move only the mailbox from one forest to a different exchange in the other forest? Like User A in (Domain A) need to be moved to exchange org in Domain B?

User A has his computer added to Domain A but mailbox to be in exchange org of Domain B?

Is this possible?

MTA

Regards
Natesh

]]>
By: Jenny Lembert https://dizdarevic.ba/ddamirblog/?p=114#comment-219155 Sun, 12 Jul 2015 05:06:29 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-219155 Thank you so much for sharing the excellent step by step guide. Migration from one forest to another is really very complicated and tedious job. There are many problems which are faced by the Exchange administrator when performing the migration job. Security, data loss, server downtime are major challenges which are encountered while moving from one organization to another in Exchange environment.

To overcome such problems, there are some third party tools available in the market which could be helpful. Here is one such application that helped us in migration from Exchange 2010 to Exchange 2013 production server:

Some key-features of the tool are here:

– Offer options to migrate data to Production Exchange Server and Office 365
– Fixes database related issues during migration so that users could not get any issue on new server
– Offer options to migrated all or selected items in databases
– Free trial version is also available to check its working functionality and efficiency

So, if anybody who wants quick migration in a rich graphical environment instead of command line, take a look at it.

Good Luck!
Jenny

]]>
By: Garo https://dizdarevic.ba/ddamirblog/?p=114#comment-190341 Mon, 09 Mar 2015 18:57:05 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-190341 In reply to Amir.

Were you able to accomplish this, I am looking to move only mailbox to new users in a new domain from 2010 to 2013?

]]>
By: Teddy https://dizdarevic.ba/ddamirblog/?p=114#comment-28508 Thu, 27 Mar 2014 17:41:15 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-28508 Hi thanks for your answer. I am not able to test now – sorry – my customer decided to take the on-premise exchange down and uninstall! Instead convert the slow ADSL to Fiber to get enough bandwidth to drive the 365 without a on-premise exchange.
Br. Teddy

]]>
By: Daniel https://dizdarevic.ba/ddamirblog/?p=114#comment-28475 Thu, 27 Mar 2014 13:17:15 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-28475 In reply to Teddy.

Hi Teddy!
Actually yes. If your issue is btw exc 2013 and 2010 the endpoint migration will work only if one of the exc 2010 name servers are in the certificate. Ex: exc01.mydomain.com With this name you can create the endpoint when a fqdn from it was requested. For my lucky my valid cert had one of them.

Now if you trying to migrate from exc2007 you don’t need it. Just use this command bellow after run the prepareMoveRequest.ps1:

New-Moverequest -Identity user@domain.com.br -RemoteGlobalCatalog dc01.ms.domain.local -RemoteCredential $Remote -RemoteLegacy -TargetDeliveryDomain domain.com.br

Of course you need trust in both ones.
It should help you. Let me know!

Regards,

]]>
By: Teddy https://dizdarevic.ba/ddamirblog/?p=114#comment-28118 Tue, 25 Mar 2014 07:27:50 +0000 http://dizdarevic.ba/ddamirblog/?p=114#comment-28118 In reply to Daniel.

Hi Daniel
Did you find a solution to your question? I am in the same situation..
Br. Teddy

]]>