migrating from windows 2000 domain server to 2003 domain server

[Guest rich in need]

first off, configuration is

old windows 2000 domain server with 60 users in active directory

new windows 2003 domain server with the same 60 users active directory

both domain names are identical but not on the same network obviously

workstation are mixed windows 2000 and windows xp professional

 

i have installed windows 2003 server with all the latest SP's and updates

from microsoft and it works just fine if i JOIN a new/exsisting computer to

the domain.

i am having a problem when logging onto the new 2003 domain server with

workstations that were in the original 2000 domain.

i do not want to re-join these workstations to the new server as it greats a

new profile on each workstation and what a pain that would be

sometimes it might take 2 or 3 logins then it logs in

it seems as if the user login is (for lack of a better term) aware that this

is a different server (or vice versa)

 

i did some research and keep hitting on this SID situation

can anyone point me in the right direction so i can just use the exsisting

workstations and login to my new 2003 server.

 

thanks in advance

 

rich

[Guest kj [SBS MVP]]

Re: migrating from windows 2000 domain server to 2003 domain server

 

rich in need wrote:

> first off, configuration is

> old windows 2000 domain server with 60 users in active directory

> new windows 2003 domain server with the same 60 users active directory

> both domain names are identical but not on the same network obviously

> workstation are mixed windows 2000 and windows xp professional

>

> i have installed windows 2003 server with all the latest SP's and

> updates from microsoft and it works just fine if i JOIN a

> new/exsisting computer to the domain.

> i am having a problem when logging onto the new 2003 domain server

> with workstations that were in the original 2000 domain.

> i do not want to re-join these workstations to the new server as it

> greats a new profile on each workstation and what a pain that would be

> sometimes it might take 2 or 3 logins then it logs in

> it seems as if the user login is (for lack of a better term) aware

> that this is a different server (or vice versa)

>

> i did some research and keep hitting on this SID situation

> can anyone point me in the right direction so i can just use the

> exsisting workstations and login to my new 2003 server.

>

> thanks in advance

>

> rich

 

What you are describing is an interforest migration. If your domains have

different netbios names you can use ADMT to move objects from the old domain

to the new, security translations, sid history, the works.

 

If you made or have to keep the exact same domain names, I'm wondering why

you just didn't add 2003 servers and upgrade.

 

http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

 

 

--

/kj

[Guest rich in need]

Re: migrating from windows 2000 domain server to 2003 domain serve

 

Re: migrating from windows 2000 domain server to 2003 domain serve

 

hi kj

thanks for the quick response

have never done one of these before so bare with me please

 

"What you are describing is an interforest migration. If your domains have

different netbios names you can use ADMT to move objects ftrom he old domain

to the new, security translations, sid history, the works."

 

using ADMT

ok so if i change the netbios name (computer name, correct?) and of course

the ip addresses have to be different

would i have to remove Active Directory from the new server first or just

delete all user names i input manually ?

then move users, computers, etc to the new server from the current domain

controller with AD

 

"If you made or have to keep the exact same domain names, I'm wondering why

you just didn't add 2003 servers and upgrade."

if i add the 2003 server as just a file server how would i upgrade it

 

i found this article and i seems to fit what i am trying to do

can you confirm that

 

thanks again

 

rich

 

 

 

 

"kj [sBS MVP]" wrote:

> rich in need wrote:

> > first off, configuration is

> > old windows 2000 domain server with 60 users in active directory

> > new windows 2003 domain server with the same 60 users active directory

> > both domain names are identical but not on the same network obviously

> > workstation are mixed windows 2000 and windows xp professional

> >

> > i have installed windows 2003 server with all the latest SP's and

> > updates from microsoft and it works just fine if i JOIN a

> > new/exsisting computer to the domain.

> > i am having a problem when logging onto the new 2003 domain server

> > with workstations that were in the original 2000 domain.

> > i do not want to re-join these workstations to the new server as it

> > greats a new profile on each workstation and what a pain that would be

> > sometimes it might take 2 or 3 logins then it logs in

> > it seems as if the user login is (for lack of a better term) aware

> > that this is a different server (or vice versa)

> >

> > i did some research and keep hitting on this SID situation

> > can anyone point me in the right direction so i can just use the

> > exsisting workstations and login to my new 2003 server.

> >

> > thanks in advance

> >

> > rich

>

> What you are describing is an interforest migration. If your domains have

> different netbios names you can use ADMT to move objects from the old domain

> to the new, security translations, sid history, the works.

>

> If you made or have to keep the exact same domain names, I'm wondering why

> you just didn't add 2003 servers and upgrade.

>

> http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

>

>

> --

> /kj

>

>

>

[Guest kj [SBS MVP]]

Re: migrating from windows 2000 domain server to 2003 domain serve

 

Re: migrating from windows 2000 domain server to 2003 domain serve

 

rich in need wrote:

> hi kj

> thanks for the quick response

> have never done one of these before so bare with me please

>

> "What you are describing is an interforest migration. If your domains

> have different netbios names you can use ADMT to move objects ftrom

> he old domain to the new, security translations, sid history, the

> works."

>

> using ADMT

> ok so if i change the netbios name (computer name, correct?) and of

> course the ip addresses have to be different

> would i have to remove Active Directory from the new server first or

> just delete all user names i input manually ?

> then move users, computers, etc to the new server from the current

> domain controller with AD

>

> "If you made or have to keep the exact same domain names, I'm

> wondering why you just didn't add 2003 servers and upgrade."

> if i add the 2003 server as just a file server how would i upgrade it

>

> i found this article and i seems to fit what i am trying to do

> can you confirm that

>

> thanks again

>

> rich

 

Well, it seems to fit what you are 'trying' to do. But the question is more

basic now, like "what are you wanting (end result) to do?"

 

If you are abandoning your current forest (&domains) for some reason, then

I'd wonder why you are keeping the same exact names and configurations. Most

often issues with current AD implementations can be fixed rather than just

tossing it out and starting over. Interforrest migrations are a lot of work.

 

>

>

>

>

> "kj [sBS MVP]" wrote:

>

>> rich in need wrote:

>>> first off, configuration is

>>> old windows 2000 domain server with 60 users in active directory

>>> new windows 2003 domain server with the same 60 users active

>>> directory both domain names are identical but not on the same

>>> network obviously workstation are mixed windows 2000 and windows xp

>>> professional

>>>

>>> i have installed windows 2003 server with all the latest SP's and

>>> updates from microsoft and it works just fine if i JOIN a

>>> new/exsisting computer to the domain.

>>> i am having a problem when logging onto the new 2003 domain server

>>> with workstations that were in the original 2000 domain.

>>> i do not want to re-join these workstations to the new server as it

>>> greats a new profile on each workstation and what a pain that would

>>> be sometimes it might take 2 or 3 logins then it logs in

>>> it seems as if the user login is (for lack of a better term) aware

>>> that this is a different server (or vice versa)

>>>

>>> i did some research and keep hitting on this SID situation

>>> can anyone point me in the right direction so i can just use the

>>> exsisting workstations and login to my new 2003 server.

>>>

>>> thanks in advance

>>>

>>> rich

>>

>> What you are describing is an interforest migration. If your domains

>> have different netbios names you can use ADMT to move objects from

>> the old domain to the new, security translations, sid history, the

>> works.

>>

>> If you made or have to keep the exact same domain names, I'm

>> wondering why you just didn't add 2003 servers and upgrade.

>>

>> http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

>>

>>

>> --

>> /kj

 

--

/kj

[Guest rich in need]

Re: migrating from windows 2000 domain server to 2003 domain serve

 

Re: migrating from windows 2000 domain server to 2003 domain serve

 

"kj [sBS MVP]" wrote:

"Well, it seems to fit what you are 'trying' to do. But the question is more

basic now, like "what are you wanting (end result) to do?"

 

i want to replace my exsisting 8 year old 2000 server/40 gb drives with a

new machine and 2003 server/160gb mirrored drives

 

"If you are abandoning your current forest (&domains) for some reason, then

I'd wonder why you are keeping the same exact names and configurations."

 

i am not abondoning my current domain, i want to keep it as it is so the

current 60 workstations can just log on as they usually do after the upgraded

server is in place

 

"Most often issues with current AD implementations can be fixed rather than

just

tossing it out and starting over. Interforrest migrations are a lot of work."

 

the issue is not with the AD it's the age of the machine ( i inherited) and

the need for more hard drive space for future projects

 

 

> rich in need wrote:

> > hi kj

> > thanks for the quick response

> > have never done one of these before so bare with me please

> >

> > "What you are describing is an interforest migration. If your domains

> > have different netbios names you can use ADMT to move objects ftrom

> > he old domain to the new, security translations, sid history, the

> > works."

> >

> > using ADMT

> > ok so if i change the netbios name (computer name, correct?) and of

> > course the ip addresses have to be different

> > would i have to remove Active Directory from the new server first or

> > just delete all user names i input manually ?

> > then move users, computers, etc to the new server from the current

> > domain controller with AD

> >

> > "If you made or have to keep the exact same domain names, I'm

> > wondering why you just didn't add 2003 servers and upgrade."

> > if i add the 2003 server as just a file server how would i upgrade it

> >

> > i found this article and i seems to fit what i am trying to do

> > can you confirm that

> >

> > thanks again

> >

> > rich

>

> Well, it seems to fit what you are 'trying' to do. But the question is more

> basic now, like "what are you wanting (end result) to do?"

>

> If you are abandoning your current forest (&domains) for some reason, then

> I'd wonder why you are keeping the same exact names and configurations. Most

> often issues with current AD implementations can be fixed rather than just

> tossing it out and starting over. Interforrest migrations are a lot of work.

>

>

> >

> >

> >

> >

> > "kj [sBS MVP]" wrote:

> >

> >> rich in need wrote:

> >>> first off, configuration is

> >>> old windows 2000 domain server with 60 users in active directory

> >>> new windows 2003 domain server with the same 60 users active

> >>> directory both domain names are identical but not on the same

> >>> network obviously workstation are mixed windows 2000 and windows xp

> >>> professional

> >>>

> >>> i have installed windows 2003 server with all the latest SP's and

> >>> updates from microsoft and it works just fine if i JOIN a

> >>> new/exsisting computer to the domain.

> >>> i am having a problem when logging onto the new 2003 domain server

> >>> with workstations that were in the original 2000 domain.

> >>> i do not want to re-join these workstations to the new server as it

> >>> greats a new profile on each workstation and what a pain that would

> >>> be sometimes it might take 2 or 3 logins then it logs in

> >>> it seems as if the user login is (for lack of a better term) aware

> >>> that this is a different server (or vice versa)

> >>>

> >>> i did some research and keep hitting on this SID situation

> >>> can anyone point me in the right direction so i can just use the

> >>> exsisting workstations and login to my new 2003 server.

> >>>

> >>> thanks in advance

> >>>

> >>> rich

> >>

> >> What you are describing is an interforest migration. If your domains

> >> have different netbios names you can use ADMT to move objects from

> >> the old domain to the new, security translations, sid history, the

> >> works.

> >>

> >> If you made or have to keep the exact same domain names, I'm

> >> wondering why you just didn't add 2003 servers and upgrade.

> >>

> >> http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

> >>

> >>

> >> --

> >> /kj

>

> --

> /kj

>

>

>

[Guest kj [SBS MVP]]

Re: migrating from windows 2000 domain server to 2003 domain serve

 

Re: migrating from windows 2000 domain server to 2003 domain serve

 

rich in need wrote:

> "kj [sBS MVP]" wrote:

> "Well, it seems to fit what you are 'trying' to do. But the question

> is more basic now, like "what are you wanting (end result) to do?"

>

> i want to replace my exsisting 8 year old 2000 server/40 gb drives

> with a new machine and 2003 server/160gb mirrored drives

>

> "If you are abandoning your current forest (&domains) for some

> reason, then I'd wonder why you are keeping the same exact names and

> configurations."

>

> i am not abondoning my current domain, i want to keep it as it is so

> the current 60 workstations can just log on as they usually do after

> the upgraded server is in place

>

> "Most often issues with current AD implementations can be fixed

> rather than just

> tossing it out and starting over. Interforrest migrations are a lot

> of work."

>

> the issue is not with the AD it's the age of the machine ( i

> inherited) and the need for more hard drive space for future projects

>

>

 

So what it sounds like you want to do is;

 

Add a new 2003 domain controller to the existing domain

Transfer the 5 FSMO roles to the new DC

Move any shared resources (File shares, printers, etc) to the new DC (or

better, elsewhere) that were on the old DC

 

Decommish and retire the old DC.

 

(done)

 

No need to migrate anything or mess with nasty workstation profile changes,

 

 

Sound better to you?

>

>> rich in need wrote:

>>> hi kj

>>> thanks for the quick response

>>> have never done one of these before so bare with me please

>>>

>>> "What you are describing is an interforest migration. If your

>>> domains have different netbios names you can use ADMT to move

>>> objects ftrom he old domain to the new, security translations, sid

>>> history, the works."

>>>

>>> using ADMT

>>> ok so if i change the netbios name (computer name, correct?) and of

>>> course the ip addresses have to be different

>>> would i have to remove Active Directory from the new server first or

>>> just delete all user names i input manually ?

>>> then move users, computers, etc to the new server from the current

>>> domain controller with AD

>>>

>>> "If you made or have to keep the exact same domain names, I'm

>>> wondering why you just didn't add 2003 servers and upgrade."

>>> if i add the 2003 server as just a file server how would i upgrade

>>> it

>>>

>>> i found this article and i seems to fit what i am trying to do

>>> can you confirm that

>>>

>>> thanks again

>>>

>>> rich

>>

>> Well, it seems to fit what you are 'trying' to do. But the question

>> is more basic now, like "what are you wanting (end result) to do?"

>>

>> If you are abandoning your current forest (&domains) for some

>> reason, then I'd wonder why you are keeping the same exact names and

>> configurations. Most often issues with current AD implementations

>> can be fixed rather than just tossing it out and starting over.

>> Interforrest migrations are a lot of work.

>>

>>

>>>

>>>

>>>

>>>

>>> "kj [sBS MVP]" wrote:

>>>

>>>> rich in need wrote:

>>>>> first off, configuration is

>>>>> old windows 2000 domain server with 60 users in active directory

>>>>> new windows 2003 domain server with the same 60 users active

>>>>> directory both domain names are identical but not on the same

>>>>> network obviously workstation are mixed windows 2000 and windows

>>>>> xp professional

>>>>>

>>>>> i have installed windows 2003 server with all the latest SP's and

>>>>> updates from microsoft and it works just fine if i JOIN a

>>>>> new/exsisting computer to the domain.

>>>>> i am having a problem when logging onto the new 2003 domain server

>>>>> with workstations that were in the original 2000 domain.

>>>>> i do not want to re-join these workstations to the new server as

>>>>> it greats a new profile on each workstation and what a pain that

>>>>> would be sometimes it might take 2 or 3 logins then it logs in

>>>>> it seems as if the user login is (for lack of a better term) aware

>>>>> that this is a different server (or vice versa)

>>>>>

>>>>> i did some research and keep hitting on this SID situation

>>>>> can anyone point me in the right direction so i can just use the

>>>>> exsisting workstations and login to my new 2003 server.

>>>>>

>>>>> thanks in advance

>>>>>

>>>>> rich

>>>>

>>>> What you are describing is an interforest migration. If your

>>>> domains have different netbios names you can use ADMT to move

>>>> objects from the old domain to the new, security translations, sid

>>>> history, the works.

>>>>

>>>> If you made or have to keep the exact same domain names, I'm

>>>> wondering why you just didn't add 2003 servers and upgrade.

>>>>

>>>> http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

>>>>

>>>>

>>>> --

>>>> /kj

>>

>> --

>> /kj

 

--

/kj

[Guest rich in need]

Re: migrating from windows 2000 domain server to 2003 domain serve

 

Re: migrating from windows 2000 domain server to 2003 domain serve

 

> So what it sounds like you want to do is;

>

> Add a new 2003 domain controller to the existing domain

> Transfer the 5 FSMO roles to the new DC

> Move any shared resources (File shares, printers, etc) to the new DC (or

> better, elsewhere) that were on the old DC

>

> Decommish and retire the old DC.

>

> (done)

>

> No need to migrate anything or mess with nasty workstation profile changes,

>

>

> Sound better to you?

 

YEP

just replace the old with the new and make it look transparent

 

"kj [sBS MVP]" wrote:

> rich in need wrote:

> > "kj [sBS MVP]" wrote:

> > "Well, it seems to fit what you are 'trying' to do. But the question

> > is more basic now, like "what are you wanting (end result) to do?"

> >

> > i want to replace my exsisting 8 year old 2000 server/40 gb drives

> > with a new machine and 2003 server/160gb mirrored drives

> >

> > "If you are abandoning your current forest (&domains) for some

> > reason, then I'd wonder why you are keeping the same exact names and

> > configurations."

> >

> > i am not abondoning my current domain, i want to keep it as it is so

> > the current 60 workstations can just log on as they usually do after

> > the upgraded server is in place

> >

> > "Most often issues with current AD implementations can be fixed

> > rather than just

> > tossing it out and starting over. Interforrest migrations are a lot

> > of work."

> >

> > the issue is not with the AD it's the age of the machine ( i

> > inherited) and the need for more hard drive space for future projects

> >

> >

>

> So what it sounds like you want to do is;

>

> Add a new 2003 domain controller to the existing domain

> Transfer the 5 FSMO roles to the new DC

> Move any shared resources (File shares, printers, etc) to the new DC (or

> better, elsewhere) that were on the old DC

>

> Decommish and retire the old DC.

>

> (done)

>

> No need to migrate anything or mess with nasty workstation profile changes,

>

>

> Sound better to you?

>

> >

> >> rich in need wrote:

> >>> hi kj

> >>> thanks for the quick response

> >>> have never done one of these before so bare with me please

> >>>

> >>> "What you are describing is an interforest migration. If your

> >>> domains have different netbios names you can use ADMT to move

> >>> objects ftrom he old domain to the new, security translations, sid

> >>> history, the works."

> >>>

> >>> using ADMT

> >>> ok so if i change the netbios name (computer name, correct?) and of

> >>> course the ip addresses have to be different

> >>> would i have to remove Active Directory from the new server first or

> >>> just delete all user names i input manually ?

> >>> then move users, computers, etc to the new server from the current

> >>> domain controller with AD

> >>>

> >>> "If you made or have to keep the exact same domain names, I'm

> >>> wondering why you just didn't add 2003 servers and upgrade."

> >>> if i add the 2003 server as just a file server how would i upgrade

> >>> it

> >>>

> >>> i found this article and i seems to fit what i am trying to do

> >>> can you confirm that

> >>>

> >>> thanks again

> >>>

> >>> rich

> >>

> >> Well, it seems to fit what you are 'trying' to do. But the question

> >> is more basic now, like "what are you wanting (end result) to do?"

> >>

> >> If you are abandoning your current forest (&domains) for some

> >> reason, then I'd wonder why you are keeping the same exact names and

> >> configurations. Most often issues with current AD implementations

> >> can be fixed rather than just tossing it out and starting over.

> >> Interforrest migrations are a lot of work.

> >>

> >>

> >>>

> >>>

> >>>

> >>>

> >>> "kj [sBS MVP]" wrote:

> >>>

> >>>> rich in need wrote:

> >>>>> first off, configuration is

> >>>>> old windows 2000 domain server with 60 users in active directory

> >>>>> new windows 2003 domain server with the same 60 users active

> >>>>> directory both domain names are identical but not on the same

> >>>>> network obviously workstation are mixed windows 2000 and windows

> >>>>> xp professional

> >>>>>

> >>>>> i have installed windows 2003 server with all the latest SP's and

> >>>>> updates from microsoft and it works just fine if i JOIN a

> >>>>> new/exsisting computer to the domain.

> >>>>> i am having a problem when logging onto the new 2003 domain server

> >>>>> with workstations that were in the original 2000 domain.

> >>>>> i do not want to re-join these workstations to the new server as

> >>>>> it greats a new profile on each workstation and what a pain that

> >>>>> would be sometimes it might take 2 or 3 logins then it logs in

> >>>>> it seems as if the user login is (for lack of a better term) aware

> >>>>> that this is a different server (or vice versa)

> >>>>>

> >>>>> i did some research and keep hitting on this SID situation

> >>>>> can anyone point me in the right direction so i can just use the

> >>>>> exsisting workstations and login to my new 2003 server.

> >>>>>

> >>>>> thanks in advance

> >>>>>

> >>>>> rich

> >>>>

> >>>> What you are describing is an interforest migration. If your

> >>>> domains have different netbios names you can use ADMT to move

> >>>> objects from the old domain to the new, security translations, sid

> >>>> history, the works.

> >>>>

> >>>> If you made or have to keep the exact same domain names, I'm

> >>>> wondering why you just didn't add 2003 servers and upgrade.

> >>>>

> >>>> http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

> >>>>

> >>>>

> >>>> --

> >>>> /kj

> >>

> >> --

> >> /kj

>

> --

> /kj

>

>

>

[Guest kj [SBS MVP]]

Re: migrating from windows 2000 domain server to 2003 domain serve

 

Re: migrating from windows 2000 domain server to 2003 domain serve

 

rich in need wrote:

>> So what it sounds like you want to do is;

>>

>> Add a new 2003 domain controller to the existing domain

>> Transfer the 5 FSMO roles to the new DC

>> Move any shared resources (File shares, printers, etc) to the new DC

>> (or better, elsewhere) that were on the old DC

>>

>> Decommish and retire the old DC.

>>

>> (done)

>>

>> No need to migrate anything or mess with nasty workstation profile

>> changes,

>>

>>

>> Sound better to you?

>

> YEP

> just replace the old with the new and make it look transparent

 

So the bigest issue you have to face is changing references of

\\oldserver\share to \\newserver\share

 

If you are good with this using logon scripts or such, you are good to go.

 

You'll need to either wipe the new 2003 server or at least remove active

directory from it. Get it network connected to the existing domain. Join it

to the existing domain. Add the DNS roles to it (don't add any zones or

anything else) Add DHCP and WINS if you need them.

 

Install the server support tools (from the CD)

 

Make sure the servers dns client is using the existing 2000 DC for DNS.

DCpromo the 2003 server as adn additonal domain controller for the existing

domain. Let it finihs, reboot, and replicate.

 

If your current DNS is active directory integrated, your new 2003 DC will

become another DNS server for your domain.

 

Make your new 2003 DC a Global Catalog Server

 

wait until that completes - exam event logs

 

Transfer the FSMO roles to the new 2003 DC

 

Run DCDIAG / C /V and look for errors or post back here

 

Now start migrating your shared resources off the old DC.

 

When your done, you can test readiness for decommishing the 2000DC by

shutting it down for a couple of days (less than 60) . If you have no

issues, power up the 2000DC. Backup both DC's (including system states) and

verify.

Run dcpromo on the 2000dc this time removing AD from this server making it a

regular member server.

 

run dcdiag /c /v again

 

Finsih off any cleanup of the 2000 server and say bye bye.

 

No user or workstation changes needed at all (just any hard references to

the old server name)

>

> "kj [sBS MVP]" wrote:

>

>> rich in need wrote:

>>> "kj [sBS MVP]" wrote:

>>> "Well, it seems to fit what you are 'trying' to do. But the question

>>> is more basic now, like "what are you wanting (end result) to do?"

>>>

>>> i want to replace my exsisting 8 year old 2000 server/40 gb drives

>>> with a new machine and 2003 server/160gb mirrored drives

>>>

>>> "If you are abandoning your current forest (&domains) for some

>>> reason, then I'd wonder why you are keeping the same exact names and

>>> configurations."

>>>

>>> i am not abondoning my current domain, i want to keep it as it is so

>>> the current 60 workstations can just log on as they usually do after

>>> the upgraded server is in place

>>>

>>> "Most often issues with current AD implementations can be fixed

>>> rather than just

>>> tossing it out and starting over. Interforrest migrations are a lot

>>> of work."

>>>

>>> the issue is not with the AD it's the age of the machine ( i

>>> inherited) and the need for more hard drive space for future

>>> projects

>>>

>>>

>>

>> So what it sounds like you want to do is;

>>

>> Add a new 2003 domain controller to the existing domain

>> Transfer the 5 FSMO roles to the new DC

>> Move any shared resources (File shares, printers, etc) to the new DC

>> (or better, elsewhere) that were on the old DC

>>

>> Decommish and retire the old DC.

>>

>> (done)

>>

>> No need to migrate anything or mess with nasty workstation profile

>> changes,

>>

>>

>> Sound better to you?

>>

>>>

>>>> rich in need wrote:

>>>>> hi kj

>>>>> thanks for the quick response

>>>>> have never done one of these before so bare with me please

>>>>>

>>>>> "What you are describing is an interforest migration. If your

>>>>> domains have different netbios names you can use ADMT to move

>>>>> objects ftrom he old domain to the new, security translations, sid

>>>>> history, the works."

>>>>>

>>>>> using ADMT

>>>>> ok so if i change the netbios name (computer name, correct?) and

>>>>> of course the ip addresses have to be different

>>>>> would i have to remove Active Directory from the new server first

>>>>> or just delete all user names i input manually ?

>>>>> then move users, computers, etc to the new server from the

>>>>> current domain controller with AD

>>>>>

>>>>> "If you made or have to keep the exact same domain names, I'm

>>>>> wondering why you just didn't add 2003 servers and upgrade."

>>>>> if i add the 2003 server as just a file server how would i upgrade

>>>>> it

>>>>>

>>>>> i found this article and i seems to fit what i am trying to do

>>>>> can you confirm that

>>>>>

>>>>> thanks again

>>>>>

>>>>> rich

>>>>

>>>> Well, it seems to fit what you are 'trying' to do. But the question

>>>> is more basic now, like "what are you wanting (end result) to do?"

>>>>

>>>> If you are abandoning your current forest (&domains) for some

>>>> reason, then I'd wonder why you are keeping the same exact names

>>>> and configurations. Most often issues with current AD

>>>> implementations can be fixed rather than just tossing it out and

>>>> starting over. Interforrest migrations are a lot of work.

>>>>

>>>>

>>>>>

>>>>>

>>>>>

>>>>>

>>>>> "kj [sBS MVP]" wrote:

>>>>>

>>>>>> rich in need wrote:

>>>>>>> first off, configuration is

>>>>>>> old windows 2000 domain server with 60 users in active directory

>>>>>>> new windows 2003 domain server with the same 60 users active

>>>>>>> directory both domain names are identical but not on the same

>>>>>>> network obviously workstation are mixed windows 2000 and windows

>>>>>>> xp professional

>>>>>>>

>>>>>>> i have installed windows 2003 server with all the latest SP's

>>>>>>> and updates from microsoft and it works just fine if i JOIN a

>>>>>>> new/exsisting computer to the domain.

>>>>>>> i am having a problem when logging onto the new 2003 domain

>>>>>>> server with workstations that were in the original 2000 domain.

>>>>>>> i do not want to re-join these workstations to the new server as

>>>>>>> it greats a new profile on each workstation and what a pain that

>>>>>>> would be sometimes it might take 2 or 3 logins then it logs in

>>>>>>> it seems as if the user login is (for lack of a better term)

>>>>>>> aware that this is a different server (or vice versa)

>>>>>>>

>>>>>>> i did some research and keep hitting on this SID situation

>>>>>>> can anyone point me in the right direction so i can just use the

>>>>>>> exsisting workstations and login to my new 2003 server.

>>>>>>>

>>>>>>> thanks in advance

>>>>>>>

>>>>>>> rich

>>>>>>

>>>>>> What you are describing is an interforest migration. If your

>>>>>> domains have different netbios names you can use ADMT to move

>>>>>> objects from the old domain to the new, security translations,

>>>>>> sid history, the works.

>>>>>>

>>>>>> If you made or have to keep the exact same domain names, I'm

>>>>>> wondering why you just didn't add 2003 servers and upgrade.

>>>>>>

>>>>>> http://www.microsoft.com/downloads/details.aspx?familyid=6F86937B-533A-466D-A8E8-AFF85AD3D212&displaylang=en

>>>>>>

>>>>>>

>>>>>> --

>>>>>> /kj

>>>>

>>>> --

>>>> /kj

>>

>> --

>> /kj

 

--

/kj