test1.com needs to become test2.com - on test1.com, the current servers (all
2003 standard) are: PDC, file server, file share server, FTP server, intranet
server, security server, terminal server, database server (plus clusters) and
a phone server. Already existing on test2.com (and actively operating) is a
print server, and an Exchange server. Also, on test2.com is a pdc and a bdc,
a server ready to mimic the intranet server. Test2 has been set up with AD,
but it is a lot cleaner, and is prepared with a whole new schema (including
user names.. switching from flast to first.last). Obviously, there are trusts
existing that allow all users to sign onto test1.com, and use the print
services and email services on test2.com. The migration is not overly
complex, except for trying to move the sequel databases and the file share
server. Database replication across the com forests is not an option as that
would require additional hardware. Interrupting productivity in the company
is limited at best - considering the company runs 24/7 and most changes will
have to take place at night so as to interrupt a smaller group of people. My
question is: Is there a way, a program, or a tool, that will monitor the
databases, their use of domain authentication for themselves and users, and
possibly help create an environment that would be able to replace every
instance of test1.com with test2.com, and re-establish the permissions, so as
to help make the migration easier? Additionally, a tool or method, that could
gather information from the file share server, in relationship to the users
and their current permission settings and file directory structures, to allow
us to reapply it like a 'template' onto the new domain would be fantastic. If
we had two weeks of downtime, we'd just rebuild everything and bring it all
back up on the new domain. Without that option, we are operating in the dark.
Any suggestions to make this easier? (More than the ADMT, as it too is
limited in its functionality, and can turn into a great big mess when
changing to a new AD schema with new GPOs applied). Thanks.