Windows 2000 migration to 2003

[Guest Greg]

We have 4 DCs, each one at a different site. The main DC, with the global

catalog running windows 2000 in mixed mode resides in NY. The 4 DCs are on

machines that are 10 years old and need to be replaced. Ideally, I would like

to replace each site one at a time.I would like to keep the same domain name.

I would also like to transfer the machine name and IP address to the new

server. Below are my 3 options. Which one is best. TIA

 

1. Use ADMT. From what I read, this tool is only usefull if the domain is

different. Is this true?

2. Replace the DCs with the new 2000 machines, move roles over to the new

machine and perform an

upgrade to Win 2003 using ADPREP/FORRESTPREP AND ADPREP/DOMAINPREP

3. Install a new machine as a windows 2003 member server, promote to DC.

--

Greg

[Guest Herb Martin]

Re: Windows 2000 migration to 2003

 

 

"Greg" <Greg@discussions.microsoft.com> wrote in message

news:759A9ECC-B76C-4E35-A819-400192159312@microsoft.com...

> We have 4 DCs, each one at a different site. The main DC, with the global

> catalog running windows 2000 in mixed mode resides in NY. The 4 DCs are on

> machines that are 10 years old and need to be replaced. Ideally, I would

> like

> to replace each site one at a time.I would like to keep the same domain

> name.

 

Upgrade -- don't rebuild nor migrate.

> I would also like to transfer the machine name and IP address to the new

> server. Below are my 3 options. Which one is best. TIA

 

Backup and restore onto new hardware -- do repair installs -- keep this

whole part sepepate from the idea of upgrading the domain.

> 1. Use ADMT. From what I read, this tool is only usefull if the domain is

> different. Is this true?

 

Yes. It is for migrations.

> 2. Replace the DCs with the new 2000 machines, move roles over to the new

> machine and perform an

> upgrade to Win 2003 using ADPREP/FORRESTPREP AND ADPREP/DOMAINPREP

 

ADPrep (forest and domain) must be run before any Win2000 Forest/Domain

can accept the first Win2003+ DC.

> 3. Install a new machine as a windows 2003 member server, promote to DC.

 

Or upgrade one of the current ones to keep the name -- then migrate ONLY

the OS to new hardware.

 

"Repair install" or "ASR" is your friend.

[Guest Greg]

Re: Windows 2000 migration to 2003

 

Thanks for your response. The current DC machines are 11 years old and out of

warranty. What are the cons of adding a new 2003 machine as a member server

and promoting it?--

Greg

 

 

"Herb Martin" wrote:

>

> "Greg" <Greg@discussions.microsoft.com> wrote in message

> news:759A9ECC-B76C-4E35-A819-400192159312@microsoft.com...

> > We have 4 DCs, each one at a different site. The main DC, with the global

> > catalog running windows 2000 in mixed mode resides in NY. The 4 DCs are on

> > machines that are 10 years old and need to be replaced. Ideally, I would

> > like

> > to replace each site one at a time.I would like to keep the same domain

> > name.

>

> Upgrade -- don't rebuild nor migrate.

>

> > I would also like to transfer the machine name and IP address to the new

> > server. Below are my 3 options. Which one is best. TIA

>

> Backup and restore onto new hardware -- do repair installs -- keep this

> whole part sepepate from the idea of upgrading the domain.

>

> > 1. Use ADMT. From what I read, this tool is only usefull if the domain is

> > different. Is this true?

>

> Yes. It is for migrations.

>

> > 2. Replace the DCs with the new 2000 machines, move roles over to the new

> > machine and perform an

> > upgrade to Win 2003 using ADPREP/FORRESTPREP AND ADPREP/DOMAINPREP

>

> ADPrep (forest and domain) must be run before any Win2000 Forest/Domain

> can accept the first Win2003+ DC.

>

> > 3. Install a new machine as a windows 2003 member server, promote to DC.

>

> Or upgrade one of the current ones to keep the name -- then migrate ONLY

> the OS to new hardware.

>

> "Repair install" or "ASR" is your friend.

>

>

>

[Guest Herb Martin]

Re: Windows 2000 migration to 2003

 

 

"Greg" <Greg@discussions.microsoft.com> wrote in message

news:CC0E33E7-9B53-48CD-A28C-08452B0A5410@microsoft.com...

> Thanks for your response. The current DC machines are 11 years old and out

> of

> warranty. What are the cons of adding a new 2003 machine as a member

> server

> and promoting it?--

 

Nothing really at all -- but that doesn't directly answer your

interest in keeping the same server names and addresses....

 

OS's can be physically migrated to new hardware if you want

to meet that (extra) requirement.

 

Generally the Domain itself however should be UPGRADED.

(That is, add a new Win2003 Server and promote or upgrade

an existing DC to Win2003 as appropriate.)

 

> Greg

>

>

> "Herb Martin" wrote:

>

>>

>> "Greg" <Greg@discussions.microsoft.com> wrote in message

>> news:759A9ECC-B76C-4E35-A819-400192159312@microsoft.com...

>> > We have 4 DCs, each one at a different site. The main DC, with the

>> > global

>> > catalog running windows 2000 in mixed mode resides in NY. The 4 DCs are

>> > on

>> > machines that are 10 years old and need to be replaced. Ideally, I

>> > would

>> > like

>> > to replace each site one at a time.I would like to keep the same domain

>> > name.

>>

>> Upgrade -- don't rebuild nor migrate.

>>

>> > I would also like to transfer the machine name and IP address to the

>> > new

>> > server. Below are my 3 options. Which one is best. TIA

>>

>> Backup and restore onto new hardware -- do repair installs -- keep this

>> whole part sepepate from the idea of upgrading the domain.

>>

>> > 1. Use ADMT. From what I read, this tool is only usefull if the domain

>> > is

>> > different. Is this true?

>>

>> Yes. It is for migrations.

>>

>> > 2. Replace the DCs with the new 2000 machines, move roles over to the

>> > new

>> > machine and perform an

>> > upgrade to Win 2003 using ADPREP/FORRESTPREP AND ADPREP/DOMAINPREP

>>

>> ADPrep (forest and domain) must be run before any Win2000 Forest/Domain

>> can accept the first Win2003+ DC.

>>

>> > 3. Install a new machine as a windows 2003 member server, promote to

>> > DC.

>>

>> Or upgrade one of the current ones to keep the name -- then migrate ONLY

>> the OS to new hardware.

>>

>> "Repair install" or "ASR" is your friend.

>>

>>

>>