Re: Move exsisting domain to a different forest?

OK. If you must have a child domain in the existing forest, then what
you're got looks fine.

1. Install a new Domain in the Target Forest
2. Install a seconed DC in the source Domain
3. Demote the current DC (FileServer) in the source domain
4. Use ADMT to transfer users, groups and computers from source domain to
new target domain
5. Promote the FileServer, now in the target domain, to a DC
6. Demote and remove the the machine (DC) installed in step 1


Note. There are considerable arguments to be had re. whether or not to use
a child domain. don't know your environment or your requirements so won't
be so bold to push the merits of one over the other. I will say have a look
at the deployment guide book "designing and deploying directory and security
services" so you can weigh the arguments up yourself.

You might also want to question whether you want your file server to be a DC
at all. As you've already created the new domain in the target forest, you
have a DC. Yes, you should have two, so if you don't have any other
servers, the file server is probably a good bet unless you can get a second
server for the second DC and leave the file server as a member server.


Are there any aditional steps I need to do with the FileServer since I
removed the first DC from the new Domain to make the FileServer the
Primary DC for the Domain?

Have a look at this article for some medium-high level guidance on this:
-- http://www.msresource.net/content/view/24/47/


Will the SQL server installation be of any problems or can that machine
move between domains withour any problems?

That should be OK. There's options available with ADMT to handle the
service account. Basically, you change the service account to the new
object in the target and then migrate the computer.


Where can I find documentation of ADMT? I can oly find the download
page...

There's quite a bit of help in the help when you install the tool. The rest
of the info. is in the book I mentioned earlier (designing and deploying
directory and security services) of which there's a downloadable version and
an online copy, both on MSFTs website.

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net




.

Relevant Pages

  • Re: Password migration error
    ... We had originally created the key on the server running ADMT. ... used on the target domian DC to install the password DLL. ... > Migration DLL and an encryption key for the target server. ... > Part II: Source Domain ...
    (microsoft.public.windows.server.migration)
  • Re: ADMT error when migrate password
    ... install on a member server in the Target domain, ... ADMTV3 needs to be installed on a 2003 Server. ... -On the primary domain controller in the Source domain, ...
    (microsoft.public.windows.server.active_directory)
  • Re: admt 3 error
    ... do I need to install ADMT 3 on my source server? ... "I installed the password migration on a dc in my source domain, ... Installed the Password Migration DLL on the Password Export Server ... on a dc in my source domain, ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADMT V3 migration errors.
    ... You didn't follow the KB 326480 to install PES server before you try to ... Source domain DC holds all the FSMO roles. ... I am not getting 'PES server should be dns client of the target domain'. ...
    (microsoft.public.windows.server.migration)
  • Password migration error
    ... After setting up the PES server in the source domain using a key generated ... on the target domain the following error occurs: ... The PES server is the PDC emulator and FSMO role holder. ...
    (microsoft.public.windows.server.migration)
Loading