Migrate server 2003 to new machine in site

I am looking for a step-by-step publication for migrating server 2003 to a
new machine at a site. The machine is a DC running file services, DNS, DHCP,
print server, etc. It connects to other sites and replicates between them.
I've gone through the knowledge base trying to find a publication, but have
been unlucky in navigating through to find one. Can anyone help?

Hello Stu,

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU DATA/MACHINE!!!

One question first:
Is the old server also Exchange server and will it be taken out of the domain
forever, when the new server is running? ETC. is a unlucky description, please
post the details so we can provide maybe some additional help.

- 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, dcdiag and netdiag on the old machine to check for errors,
if you have some post the complete output from the command here or solve
them first

- run adprep /forestprep and adprep /domainprep from the 2003 installation
disk if you install a 2003R2 version, with an account that is member of the
Schema admins, to upgrade the schema to the new version

- 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 2003 server to an existing
domain

- if you are prompted for DNS configuration choose Yes (will not occur if
a DNS server is installed and configured in the domain), then install DNS
after the reboot

- 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 on both domain controllers

- if you have no errors, make the new server Global catalog server, open
Active directory Sites and Services and then double-click sitename, double-click
Servers, click your domain controller, right-click NTDS Settings, and then
click Properties, on the General tab, click to select the Global catalog
check box (http://support.microsoft.com/?id=313994)

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller, if needed
(http://support.microsoft.com/kb/324801)

- 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 2003 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)

- for the printers you can use Printmigrator (http://www.microsoft.com/windowsserv...grator3.1.mspx)



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 promotion

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


> I am looking for a step-by-step publication for migrating server 2003
> to a new machine at a site. The machine is a DC running file
> services, DNS, DHCP, print server, etc. It connects to other sites
> and replicates between them. I've gone through the knowledge base
> trying to find a publication, but have been unlucky in navigating
> through to find one. Can anyone help?
>

It is not an exchange server. It is running file services, dns, dhcp,
anti-virus, and backup.

"Meinolf Weber" wrote:

> Hello Stu,
>
> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU DATA/MACHINE!!!
>
> One question first:
> Is the old server also Exchange server and will it be taken out of the domain
> forever, when the new server is running? ETC. is a unlucky description, please
> post the details so we can provide maybe some additional help.
>
> - 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, dcdiag and netdiag on the old machine to check for errors,
> if you have some post the complete output from the command here or solve
> them first
>
> - run adprep /forestprep and adprep /domainprep from the 2003 installation
> disk if you install a 2003R2 version, with an account that is member of the
> Schema admins, to upgrade the schema to the new version
>
> - 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 2003 server to an existing
> domain
>
> - if you are prompted for DNS configuration choose Yes (will not occur if
> a DNS server is installed and configured in the domain), then install DNS
> after the reboot
>
> - 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 on both domain controllers
>
> - if you have no errors, make the new server Global catalog server, open
> Active directory Sites and Services and then double-click sitename, double-click
> Servers, click your domain controller, right-click NTDS Settings, and then
> click Properties, on the General tab, click to select the Global catalog
> check box (http://support.microsoft.com/?id=313994)
>
> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller, if needed
> (http://support.microsoft.com/kb/324801)
>
> - 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 2003 server, preferred
> DNS itself, secondary the old one
>
> - if you use DHCP do not forget to reconfigure the scope settings to point
> to the new installed DNS server
>
> - export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)
>
> - for the printers you can use Printmigrator (http://www.microsoft.com/windowsserv...grator3.1.mspx)
>
>
>
> 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 promotion
>
> 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
>
>
> > I am looking for a step-by-step publication for migrating server 2003
> > to a new machine at a site. The machine is a DC running file
> > services, DNS, DHCP, print server, etc. It connects to other sites
> > and replicates between them. I've gone through the knowledge base
> > trying to find a publication, but have been unlucky in navigating
> > through to find one. Can anyone help?
> >
>
>
>

It is also the dc at this site.

"Meinolf Weber" wrote:

> Hello Stu,
>
> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU DATA/MACHINE!!!
>
> One question first:
> Is the old server also Exchange server and will it be taken out of the domain
> forever, when the new server is running? ETC. is a unlucky description, please
> post the details so we can provide maybe some additional help.
>
> - 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, dcdiag and netdiag on the old machine to check for errors,
> if you have some post the complete output from the command here or solve
> them first
>
> - run adprep /forestprep and adprep /domainprep from the 2003 installation
> disk if you install a 2003R2 version, with an account that is member of the
> Schema admins, to upgrade the schema to the new version
>
> - 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 2003 server to an existing
> domain
>
> - if you are prompted for DNS configuration choose Yes (will not occur if
> a DNS server is installed and configured in the domain), then install DNS
> after the reboot
>
> - 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 on both domain controllers
>
> - if you have no errors, make the new server Global catalog server, open
> Active directory Sites and Services and then double-click sitename, double-click
> Servers, click your domain controller, right-click NTDS Settings, and then
> click Properties, on the General tab, click to select the Global catalog
> check box (http://support.microsoft.com/?id=313994)
>
> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller, if needed
> (http://support.microsoft.com/kb/324801)
>
> - 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 2003 server, preferred
> DNS itself, secondary the old one
>
> - if you use DHCP do not forget to reconfigure the scope settings to point
> to the new installed DNS server
>
> - export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)
>
> - for the printers you can use Printmigrator (http://www.microsoft.com/windowsserv...grator3.1.mspx)
>
>
>
> 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 promotion
>
> 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
>
>
> > I am looking for a step-by-step publication for migrating server 2003
> > to a new machine at a site. The machine is a DC running file
> > services, DNS, DHCP, print server, etc. It connects to other sites
> > and replicates between them. I've gone through the knowledge base
> > trying to find a publication, but have been unlucky in navigating
> > through to find one. Can anyone help?
> >
>
>
>

Hello Stu,

Then it should work that way. But again do NOT forget the backup at least
from the system state.

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


> It is not an exchange server. It is running file services, dns, dhcp,
> anti-virus, and backup.
>
> "Meinolf Weber" wrote:
>
>> Hello Stu,
>>
>> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU
>> DATA/MACHINE!!!
>>
>> One question first:
>> Is the old server also Exchange server and will it be taken out of
>> the domain
>> forever, when the new server is running? ETC. is a unlucky
>> description, please
>> post the details so we can provide maybe some additional help.
>> - 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, dcdiag and netdiag on the old machine to check for
>> errors, if you have some post the complete output from the command
>> here or solve them first
>>
>> - run adprep /forestprep and adprep /domainprep from the 2003
>> installation disk if you install a 2003R2 version, with an account
>> that is member of the Schema admins, to upgrade the schema to the new
>> version
>>
>> - 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 2003 server to an
>> existing domain
>>
>> - if you are prompted for DNS configuration choose Yes (will not
>> occur if a DNS server is installed and configured in the domain),
>> then install DNS after the reboot
>>
>> - 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 on both domain controllers
>>
>> - if you have no errors, make the new server Global catalog server,
>> open Active directory Sites and Services and then double-click
>> sitename, double-click Servers, click your domain controller,
>> right-click NTDS Settings, and then click Properties, on the General
>> tab, click to select the Global catalog check box
>> (http://support.microsoft.com/?id=313994)
>>
>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller,
>> if needed (http://support.microsoft.com/kb/324801)
>>
>> - 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 2003 server,
>> preferred DNS itself, secondary the old one
>>
>> - if you use DHCP do not forget to reconfigure the scope settings to
>> point to the new installed DNS server
>>
>> - export and import of DHCP database (if needed)
>> (http://support.microsoft.com/kb/325473)
>>
>> - for the printers you can use Printmigrator
>> (http://www.microsoft.com/windowsserv...erview/printmi
>> grator3.1.mspx)
>>
>> 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 promotion
>>
>> 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
>>> I am looking for a step-by-step publication for migrating server
>>> 2003 to a new machine at a site. The machine is a DC running file
>>> services, DNS, DHCP, print server, etc. It connects to other sites
>>> and replicates between them. I've gone through the knowledge base
>>> trying to find a publication, but have been unlucky in navigating
>>> through to find one. Can anyone help?
>>>

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:. com...
> Hello Stu,
>
> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU
> DATA/MACHINE!!!
>
> One question first:
> Is the old server also Exchange server and will it be taken out of the
> domain forever, when the new server is running? ETC. is a unlucky
> description, please post the details so we can provide maybe some
> additional help.

I do not know if it's usual to "interrupt your discussion" on news
servers...
I have the same situation here with the difference that there is an DC (GC)
with exchange on the same machine.
I will migrate the AD to w2k8 and the exchange to w2k8 server and exchange
2007.
Old server will be taken out of the domain.
What will change in the steps?
Many thanks for your clear descriptions.

Regards,

Adi

Hello Adi,

Even if you find a posting which comes near to you it will be better to create
your own. Then it will be recognized as a new one and i think read more often
then "running" postings.

Please give some more infos, you have one running DC 2003 with exchange 2003
or Exchange 2000?

Which service packs are you running for OS and Exchange, are they fully updated?

Hopefully for the new OS/Exchange you have two servers, one DC and one member
server. Exchange on a DC is not recommended for performance reasons, especially
2007. Be aware that you need to use 64bit version from 2008 to install Exchange
2007.

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

"Meinolf Weber" wrote in message
news:. com...
> Hello Adi,
>
> Even if you find a posting which comes near to you it will be better to
> create your own. Then it will be recognized as a new one and i think read
> more often then "running" postings.

Ok, I will remembre that. Thank you.

> Please give some more infos, you have one running DC 2003 with exchange
> 2003 or Exchange 2000?
> Which service packs are you running for OS and Exchange, are they fully
> updated?

I have DC running on w2k3 fully updated with latest service pack.
Exchange 2003 sp2.

> Hopefully for the new OS/Exchange you have two servers, one DC and one
> member server. Exchange on a DC is not recommended for performance
> reasons, especially 2007. Be aware that you need to use 64bit version from
> 2008 to install Exchange 2007.

Yes, I would like to separate roles to differents servers to avoid bad
response times in outlook, security reasons, backup flexibility etc...
I know also that exchange 2007 is available only in 64 bits architecture.

Hello Adi,

Forgot one question, is your domain name in the format DOMAIN.TLD or only
DOMAIN, which is single label and should be avoided?

Let's devide the upgrade/migration in 3 parts, 1. AD, 2. Exchange installation/removal
and 3. Demoting the old DC.
1. AD:
!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!

- no other roles/apps then DC, Exchange, DNS/DHCP are running on the 2003
server i assume. If there are more post them here.

- 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, dcdiag and netdiag 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 2003 installation disk.

- run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
the 2008 installation disk against the 2003 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 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

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- export and import of DHCP database for 2008 choose "netshell dhcp backup"
and "netshell dhcp restore" command

(http://technet.microsoft.com/en-us/l.../cc772372.aspx)


2. Exchange:
- for 2008 servers you need Exchange 2007 SP1

- single label domain name is supported with Exchange 2007 SP1 (http://msexchangeteam.com/archive/20...26/448511.aspx)

- first check this one (http://support.microsoft.com/kb/555854)

- this 3 part article includes a complete transition from 2003 to 2007 (http://www.msexchange.org/tutorials/...007-Part1.html)


3. Demoting
Demoting the old DC, FIRST you have to move exchange to the new one and THEN
uninstall Exchange then from the 2003 DC as stated in the artilces about
transitioning!!!

- 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 promotion





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


> "Meinolf Weber" wrote in message
> news:. com...
>
>> Hello Adi,
>>
>> Even if you find a posting which comes near to you it will be better
>> to create your own. Then it will be recognized as a new one and i
>> think read more often then "running" postings.
>>
> Ok, I will remembre that. Thank you.
>
>> Please give some more infos, you have one running DC 2003 with
>> exchange
>> 2003 or Exchange 2000?
>> Which service packs are you running for OS and Exchange, are they
>> fully
>> updated?
> I have DC running on w2k3 fully updated with latest service pack.
> Exchange 2003 sp2.
>
>> Hopefully for the new OS/Exchange you have two servers, one DC and
>> one member server. Exchange on a DC is not recommended for
>> performance reasons, especially 2007. Be aware that you need to use
>> 64bit version from 2008 to install Exchange 2007.
>>
> Yes, I would like to separate roles to differents servers to avoid bad
> response times in outlook, security reasons, backup flexibility etc...
> I know also that exchange 2007 is available only in 64 bits
> architecture.
>

I'm allready simulating the migration in my virtual environement.
I just have tested my latest backup -> recreate the same configuration on
virtual machines.

I really don't know how to thank you for this clear (mini) step by step
guide with all necessery ressources.

Thank you so much!

Regards,

Adi