Domain Migration

clivingIOS
clivingIOS used Ask the Experts™
on
I have a plan for a domain migration and would just like to know if you men and women would like to have a quick look over it and see if I've missed anything that may cause issues. I only have tonight to complete the migration.

1) Network 1 - domain company1.local - ip range 192.168.11.x - 15 users - sage accounts, 2 programs which use SQL databases. 2 servers, both DC's

2) Network 2 - domain parentcompany.local - ip range 192.168.1.x - 150 users - sage accounts, 2 programs which use SQL databases, various other packages - 12 servers.

both are currently linked together using a trust and are held together using a VPN tunnel through 2 draytek 2830N routers.

Both servers and networks can see each other with no issues.

My Intention:
Get rid of company1.local and merge all users and servers into parentcompany.local

My Plan:

1) Install ADMT
2) create local administrator accounts on all 15 machines at company 1
3) Make local admin accounts on all databases
4) run ADMt and migrate all users and SIDs from company1.local to parentcompany.local
5) join all 15 machines to parentcompany.local using profwiz (https://www.forensit.com/uk/downloads.html)
6) dcpromo both servers
7) join them both 2 new domain - 1 as a DC
8) Reshare shared folders/printers etc
9) setup programs to connect to SQL DB using new logons
10) remap sage drives

If there is anythign you think I have missed or should be doing please let me know.

Thanks for any advice.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
To be honest: 15 users? Instead of using ADMT I'd manually migrate the users and groups.
Ok, you have to re-set file permissions and database permissions but some scripting may help here.

Any Exchange involved?
8) is probably not required. Shares survive nearly everything. You may have to set share permisisons if not set to Everyone

Author

Commented:
No all of the emails are held on a pop server at our head office.

so you reccomend just creating the users on the new domain, them demote the current dc's and join them to the new domain?

I did think about that but wasn't sure whether it would be reccomended

Regards

James
Announcing the Winners!

The results are in for the 15th Annual Expert Awards! Congratulations to the winners, and thank you to everyone who participated in the nominations. We are so grateful for the valuable contributions experts make on a daily basis. Click to read more about this year’s recipients!

Its probably the most fail-safe way to do it.
Recommended would be a reinstall of the DC but usually demote and promote it to the other domain should be fine.
I'd first check wether  the database stuff survives or not. Is this MS SQL? I just don't like it on a DC...

Regards
GarveyJ, any update?

Author

Commented:
I Demoted the DC and them promoted it into the new domain, it was pretty pain free and other than updating mssql permissions and setting up share permissions again everything went very smooth.

I manually created the user accounts on the new server.

it's going to be itneresting next time as the next network to join into this domain has 35 users and they all have roaming profiles and use terminal server accounts!

Thanks for all your help.
Hope answers helped

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial