Guntis S
asked on
Connect Exchange 2013 to new AD DC
Hello!
We have the environment with windows 2012 server which is AD DC and also we have Exchange 2013 server on windows 2012 machine and they are located in the forest called old.domain.com. Because of some issues with our AD DC server, we decided to install completely new AD DC server on windows 2012 in a new forest called domain.com and we migrated all users and computers from the old.domain.com AD to domain.com AD. Now we need to connect our Exchange 2013 which is located in old.domain.com to newly created AD DC in domain.com and connect user mailboxes to AD users which were imported from the old AD.
Thank you.
We have the environment with windows 2012 server which is AD DC and also we have Exchange 2013 server on windows 2012 machine and they are located in the forest called old.domain.com. Because of some issues with our AD DC server, we decided to install completely new AD DC server on windows 2012 in a new forest called domain.com and we migrated all users and computers from the old.domain.com AD to domain.com AD. Now we need to connect our Exchange 2013 which is located in old.domain.com to newly created AD DC in domain.com and connect user mailboxes to AD users which were imported from the old AD.
Thank you.
ASKER
maybe I can just backup all user mailboxes and then restore them on a new exchange server which will be in the new domain?
The problem is that your Exchange server relies on the Domain controller DNS and specifically in the domain that is already configured, even in the organization name, since those digital signatures won't match it won't be possible to do it as a recovery, for that, you need exact same domain name, same organization name and same OS versions
Since you changed your ADCS the process is a migration, not just a recovery.
Since you changed your ADCS the process is a migration, not just a recovery.
ASKER
And what if I perform Cross Forest Migration using PrepareMoveRequest.ps1 to migrate all mailboxes to a new Exchange server?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes it is true I am new to Exchange I will take your advice and will export mailboxes to PST files. Unfortunately, I am on my own here ...
Well, I'd suggest a gig.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Lee W MVP (https:#a42364175)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Lee W MVP (https:#a42364175)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I mean Exchange really depends on ADCS, since you already have it connected to the old.domain.com infrastructure (if there's no ADCS (old.domain.com) is orphan, so there's no way to disconnect from old.domain.com to connect it to the new.
The solution is to deploy it the new ADCS and do the migration, not just the connect-disconnect process
So the process is:
Export all PST of all users in old.domain.com
Deploy Exchange 2013 in the new infrastructure.
Load the PST on the server or just on the outlook to do the migration.