Hello Paul,
So you have an additional server which can run 2008? Then i suggest this way:
!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!
- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)
- run replmon from the run line or repadmin /showrepl(if more then one DC
exist), dcdiag and netdiag from the command prompt on the old machine to
check for errors, if you have some post the complete output from the command
here or solve them first. For this tools you have to install the support\tools\suptools.msi
from the 2000 installation disk.
- run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
the 2008 installation disk against the 2000 schema master, with an account
that is member of the Schema admins, to upgrade the schema to the new version
(44), you can check the version with "schupgr" in a command prompt.
- Install the new machine as a member server in your existing domain
- configure a fixed ip and set the preferred DNS server to the old DNS server
only
- run dcpromo and follow the wizard to add the 2008 server to an existing
domain, make it also Global catalog.
- if you are prompted for DNS configuration choose Yes. If not, install DNS
role after promotion.
- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear
- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag (copy the netdiag from the 2003 support tools to 2008,
will work) on both domain controllers
- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (
http://support.microsoft.com/kb/324801
applies also for 2008)
- you can see in the event viewer (Directory service) that the roles are
transferred, also give it some time
- reconfigure the DNS configuration on your NIC of the 2008 server, preferred
DNS itself, secondary the old one
Demoting the old DC (if needed)
- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC
- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok
- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again
- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever
- also you have to start AD sites and services and delete the old servername
under the site, this will not be done during demotion
For the data to copy use robocopy, included in server 2008, it also copy
the permissions.
ADMT is used when you have the need to change the domain name during migration.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Completely lost by this situation with migration of AD w2k to w2k8.
>
> Situation:
> I have:
> Physical server running Windows 2000 + AD + DNS - server.company.local
> Physical server(freshly installed) running Windows 2008 - server2k8
> Physical server empty - for testing or other purposes which are
> required for migration.
>
> I need:
>
> To migrate users+profiles+other settings from Windows 2000 to Windows
> 2008, but I cannot touch or disconnect currently running w2k server
> with AD, after migration I want to change "swap" servers without
> affecting anything in infrastructure. I don't know the best way to do
> this, I think there is more than one...
>
> I think about:
> To an empty server install w2k, somehow (if you know how, please write
> about it) replicate existing profiles+users+settings from main
> server.company.local to an empty w2k server, after that upgrade the
> system to w2k3 and later upgrade to w2k8 and at last somehow to
> replicate everything to the server2k8.
> I also think about: To an empty server install w2k3, use ADMT (which
> version?) to migrate everything from server.company.local to newly
> installed server and later to migrate to server2k8.
> The fact is that I just think about such variants, but don't know how
> to complete any of these, if you know, please provide me information.
>
> Maybe you have any other methods to offer, if so please provide my any
> required information, because I am completely lost in this situation
> and don't know how to do such a migration.
>