Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Server Migration > Migration from W2K DC to W3K DC ( new hardware )

Reply
Thread Tools Display Modes

Migration from W2K DC to W3K DC ( new hardware )

 
 
pilo
Guest
Posts: n/a

 
      08-10-2009
Does anyone know the steps to migrate Window Server 2000 DC standard
to Window Server 2003 R2 standard?
The hardware for W3K is new and the old W2K server will shutdown.
Thanks
 
Reply With Quote
 
 
 
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      08-10-2009
Hello pilo,

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR 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?

- 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 (only 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 or 2003 installation disk.

- run adprep /forestprep and adprep /domainprep from the 2003 installation
disk against the 2000 server, 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 (also possible that
no DNS preparation occur), 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 (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)

- backup WINS (http://technet.microsoft.com/en-us/l.../cc727901.aspx)

- restore WINS (http://technet.microsoft.com/en-us/l.../cc727960.aspx)


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

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


> Does anyone know the steps to migrate Window Server 2000 DC standard
> to Window Server 2003 R2 standard?
> The hardware for W3K is new and the old W2K server will shutdown.
> Thanks



 
Reply With Quote
 
pilo
Guest
Posts: n/a

 
      08-10-2009


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> ha scritto nel messaggio
news: .com...
> Hello pilo,
>


Hi, Meinolf, Thank you of response..

> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR
> 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?
>


No, is only DC, with DNS server...

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


How I check if running Active Directory integrated zone?
Yes, I have another DNS server in LAN, That server is Windows 2003.




 
Reply With Quote
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      08-10-2009
Hello pilo,

Open DNS management console on the DNS server and highlight the forward/reverse
lookup zone. In the right pane you see the kind of zones.

If not AD integrated, doubleclick the zone and open the zone properties,
choose change button.

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 [MVP-DS]" <meiweb(nospam)@gmx.de> ha scritto nel
> messaggio news: .com...
>
>> Hello pilo,
>>

> Hi, Meinolf, Thank you of response..
>
>> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR
>> 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?

> No, is only DC, with DNS server...
>
>> - 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)
>>

> How I check if running Active Directory integrated zone? Yes, I have
> another DNS server in LAN, That server is Windows 2003.
>



 
Reply With Quote
 
pilo
Guest
Posts: n/a

 
      08-10-2009


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> ha scritto nel messaggio
news: .com...
> Hello pilo,
>
> Open DNS management console on the DNS server and highlight the
> forward/reverse lookup zone. In the right pane you see the kind of zones.
>
> If not AD integrated, doubleclick the zone and open the zone properties,
> choose change button.
>


Ok, the type is Active Directory-integrated ...

> - run replmon from the run line or repadmin /showrepl (only 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 or 2003 installation
> disk.
>


replmon open the windows with title: Active Directory Replication Monitor,
but there is no server...
-----
The command repadmin /showrepl :

Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]

Supported <cmd>s & args:
/sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force] [/async]
[/full] [/addref] [/allsources]
/syncall <Dest DSA> [<Naming Context>] [<flags>]
/kcc [DSA] [/async]
/bind [DSA]
/propcheck <Naming Context> <Originating DSA Invocation ID>
<Originating USN> [DSA from which to enumerate host DSAs]
/getchanges NamingContext [SourceDSA] [/cookie:<file>]
/getchanges NamingContext [DestDSA] SourceDSAObjectGuid
[/verbose] [/statistics]

/showreps [Naming Context] [DSA [Source DSA objectGuid]] [/verbose]
[/unreplicated] [/nocache]
/showvector <Naming Context> [DSA] [/nocache]
/showmeta <Object DN> [DSA] [/nocache]
/showtime <DS time value>
/showmsg <Win32 error>
/showism [<Transport DN>] [/verbose] (must be executed locally)
/showsig [DSA]
/showconn [DSA] [Container DN | <DSA guid>] (default is local site)
/showcert [DSA]

/queue [DSA]
/failcache [DSA]
/showctx [DSA] [/nocache]

Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate servers
<Naming Context> is the Distinguished Name of the root of the NC
Example: DC=My-Domain,DC=Microsoft,DC=Com

.......
>
> - run adprep /forestprep and adprep /domainprep from the 2003 installation
> disk against the 2000 server, 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 (also possible that
> no DNS preparation occur), 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
> (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)
>
> - backup WINS (http://technet.microsoft.com/en-us/l.../cc727901.aspx)
>
> - restore WINS (http://technet.microsoft.com/en-us/l.../cc727960.aspx)
>
>
> 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
>
> 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
>
>> Does anyone know the steps to migrate Window Server 2000 DC standard
>> to Window Server 2003 R2 standard?
>> The hardware for W3K is new and the old W2K server will shutdown.
>> Thanks

>
>

 
Reply With Quote
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      08-11-2009
Hello pilo,

The older version from repadmin uses /showreps. Replmon is the GUI version
to check replication. If you rightclick at "Monitored server" you have to
choose Add server and follow the wizard.

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 [MVP-DS]" <meiweb(nospam)@gmx.de> ha scritto nel
> messaggio news: .com...
>
>> Hello pilo,
>>
>> Open DNS management console on the DNS server and highlight the
>> forward/reverse lookup zone. In the right pane you see the kind of
>> zones.
>>
>> If not AD integrated, doubleclick the zone and open the zone
>> properties, choose change button.
>>

> Ok, the type is Active Directory-integrated ...
>
>> - run replmon from the run line or repadmin /showrepl (only 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 or 2003
>> installation disk.
>>

> replmon open the windows with title: Active Directory Replication
> Monitor,
> but there is no server...
> -----
> The command repadmin /showrepl :
> Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]
>
> Supported <cmd>s & args:
> /sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force]
> [/async]
> [/full] [/addref] [/allsources]
> /syncall <Dest DSA> [<Naming Context>] [<flags>]
> /kcc [DSA] [/async]
> /bind [DSA]
> /propcheck <Naming Context> <Originating DSA Invocation ID>
> <Originating USN> [DSA from which to enumerate host DSAs]
> /getchanges NamingContext [SourceDSA] [/cookie:<file>]
> /getchanges NamingContext [DestDSA] SourceDSAObjectGuid
> [/verbose] [/statistics]
> /showreps [Naming Context] [DSA [Source DSA objectGuid]]
> [/verbose]
> [/unreplicated] [/nocache]
> /showvector <Naming Context> [DSA] [/nocache]
> /showmeta <Object DN> [DSA] [/nocache]
> /showtime <DS time value>
> /showmsg <Win32 error>
> /showism [<Transport DN>] [/verbose] (must be executed locally)
> /showsig [DSA]
> /showconn [DSA] [Container DN | <DSA guid>] (default is local
> site)
> /showcert [DSA]
> /queue [DSA]
> /failcache [DSA]
> /showctx [DSA] [/nocache]
> Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate
> servers
> <Naming Context> is the Distinguished Name of the root of the
> NC
> Example: DC=My-Domain,DC=Microsoft,DC=Com
> ......
>
>> - run adprep /forestprep and adprep /domainprep from the 2003
>> installation disk against the 2000 server, 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 (also possible
>> that no DNS preparation occur), 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
>> (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)
>>
>> - backup WINS
>> (http://technet.microsoft.com/en-us/l.../cc727901.aspx)
>>
>> - restore WINS
>> (http://technet.microsoft.com/en-us/l.../cc727960.aspx)
>>
>> 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
>>
>> 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
>>> Does anyone know the steps to migrate Window Server 2000 DC standard
>>> to Window Server 2003 R2 standard?
>>> The hardware for W3K is new and the old W2K server will shutdown.
>>> Thanks



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
RE: migration to new hardware Manfred Zhuang [MSFT] Windows Small Business Server 0 03-17-2008 02:36 AM
SBS Migration to new hardware RGA Windows Small Business Server 1 08-03-2007 02:44 PM
DNS Migration New Hardware hsmlives DNS Server 1 10-11-2006 11:16 AM
Migration from one hardware to another hardware - Windows 2000 Microsoft Lover Server Migration 3 07-27-2006 06:21 AM
SBS Migration to new Hardware Mike D Windows Small Business Server 4 10-03-2004 02:05 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59