Link to home
Start Free TrialLog in
Avatar of Geforce
GeforceFlag for Australia

asked on

Active Directory Rebuild

Hi,

We are facing very difficult situation at the moment. let me explain in detail.

Problem 1:
We are running Exchange 2016 server and  Domain controller AD on two separate VM's.
Last night, we faced disaster and our Hyper V HDD was crash. We trying everything but its totally crash.
We have Exchange 2016 VM backup but we don't have AD VM backup.
Please let me know how what will I do at this situation. If I created new AD with same domain name so I believe I need to rejoin exchange server with new AD.
What will happen with current mailboxes. They will work like same way that they were working previously.

Problem 2:
As i explain above our Hyper V HDD was crash so our three RDSH servers and their AD (Its not same AD as i explain above, different domain name) also down.
Again we have RDSH servers backup but we don't have AD backup so i guess I have to republish all the apps again.

Please let me know how to resolve these problems. Both are related to AD's. One for Exchange 2016 and other for RDSH server.

OS: Windows server 2016
Exchange: Exchange server is 2016

Shoaib Nawaz
Avatar of arnold
arnold
Flag of United States of America image

Did you have a single AD DC.or you have multiple, using ntdsutil you can seize the roles managed by the VM that crashed.

Setting up a new AD with the same name, would require the existence of the same users, main point the mailboxes are attached to the user SIds, you would need to reassign/attach the mailboxes to the "new" user accounts.


Before proceeding, please check
Caution as exchange may once the AD reflects a mailbox to a user that no love Niger exist, it might delete the mailbox.
Avatar of Geforce

ASKER

Hi Arnold,

Thanks for the reply. Unfortunately Yes, we have a single DC.

I will create all the users again but reassign/attach the mailboxes will show user old emails or not?
Avatar of Matt Fields
Matt Fields

It's technically impossible to rejoin an existing exchange server to a new forest. Exchange integrates very heavily with AD and the new forest wouldn't have record of the server you're trying to join and for this reason taking snapshots of exchange VMs is not supported and flat out doesn't work for recovery.

Honestly, If you can't bring the existing domain back online you won't be able to bring that exchange server back. You'll need to introduce a new forest and new exchange server, then grab the .edb from your exchange snapshot and restore it on that new exchange server.

Your remote desktop deployment will probably be easier and you should be able to just rejoin it to the new forest.

Going forward if you're going to virtualize you need to make sure you RAID the disks hosting the OS volume and make sure that you have at least two DCs and two Exchange servers on dedicated storage. If you can't afford to do that either use dedicated physical hardware to accomplish that or look to the cloud with office 365.

-Matt
First: Set up a new AD with a similar domain name. Do not use the old domain name as there are GUIDs in the background that will cause no end of grief.

To get going, set up a dial tone database after standing up a new Exchange.

Once ready, take the existing Exchange database and logs and set up a restore mailbox database. Restore to that.

Then, merge the dial tone and restored mailbox content.

Done.
Do not use the old domain name as there are GUIDs in the background that will cause no end of grief.
Please elaborate on this. There's always a GUID in the background and it will be different whether or not you use original domain name or a brand new name. The GUID is what is used in the background via system usually.

Exchange is different in that it is tied to the domain name, not only the GUID. For example, a domain rename is not supported in AD with Exchange, yet the GUID stays the same
Best, you can build, new AD and Exchange environment. Then use third party tool to extract data from .edb to PST and merge into new mailboxes.
@Shaun Group Policy Tattoos. There are certain policies that are tattooed to the machines that can cause grief if the rebuilt domain has exactly the same name. BTDT
Agree with Amit it is easy to build exchange and AD again and add all these users
But importing of emails may take time.
Avatar of Geforce

ASKER

Thank you guys for all your comments and suggestion.

I can access old exchange server but as you know that there is no AD so i am not able to see all users.

Is there any script or command where i can get all the users and distribution group list (Also who remember of this group)?

Please let me know how to restore the .edb into new exchange server. Size of .edb file is only 100GB.
@Shaun Group Policy Tattoos. There are certain policies that are tattooed to the machines that can cause grief if the rebuilt domain has exactly the same name. BTDT
Only if you setup it incorrectly
Without AD you don't have any option to bring back Exchange. As i advised above, your best bet is to build new environment and importing the data from old edb file.
Just a quick question, by any chance, do you have system state backup for your AD server.
Avatar of Geforce

ASKER

Hi Guys, Yes I am rebuilding new domain controller with new exchange but old exchange is still up. Obviously exchange services is not running because AD is not available.

Problem: I don't have list of users and groups.

Is there any script or command where i can get all the users and distribution group list (Also who remember of this group)?

Please let me know how to restore the .edb into new exchange server. Size of .edb file is only 100GB.
ASKER CERTIFIED SOLUTION
Avatar of Geforce
Geforce
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial