win 2008 network

Hi,

Question:

I have a windows 2000 production network.. Just 2 servers. One is a PDC
one is a member server..

day the domain is: company.com

Then I have a Windows 2008 TEST network. That has 3 servers. One PDC, one
BDC and one member server.
It has the same domain name as the live production network.

Will there be a problem once everything is setup on the Win 2008 network
(users/files/printers, etc.) If one day we say okay WIndows 2008 network is
all set, tested, etc. Let's shut off the Win 2000 network.. Will the user
computers and things all be able to just hop on the Windows 2008 being the
domain name and all is the same?

Right now windows 2008 network is completely seperate from windows 2000
network..

No not at all.

You may have the names the same but the SAM is different. Just think if that
were possible a user could bring their own DC to work, make a domain with
the same name as the work domain and have all the user "hop" over to their
domain where they know all the admin passwords and take control of your
domain and lock you out.


Your best bet is to do some reading up on migrating to a new domain using
ADMT.

Your projected plan will cause you loads of trouble.

hth
DDS

"George" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> Question:
>
> I have a windows 2000 production network.. Just 2 servers. One is a PDC
> one is a member server..
>
> day the domain is: company.com
>
> Then I have a Windows 2008 TEST network. That has 3 servers. One PDC,
> one BDC and one member server.
> It has the same domain name as the live production network.
>
> Will there be a problem once everything is setup on the Win 2008 network
> (users/files/printers, etc.) If one day we say okay WIndows 2008 network
> is all set, tested, etc. Let's shut off the Win 2000 network.. Will the
> user computers and things all be able to just hop on the Windows 2008
> being the domain name and all is the same?
>
> Right now windows 2008 network is completely seperate from windows 2000
> network..
>

Hello George,

This will not work, just using the same names is not enough, the SID's of
the domain and everything belonging to that will be different. If you do
it that way you have to add the computers to the new domain and create all
user account, groups, policies etc. again.

What you can do is to create a new forest/domain with a different name, newdomain.loc,
and use ADMT v3.1 to migrate the old to the new one. In this case you are
able to take over everything to the new one. But this also should be tested
from you before using the production domain.

ADMTv3.1:
http://www.microsoft.com/downloads/d...displaylang=en

http://www.microsoft.com/downloads/d...displaylang=en

Small remark, since windows 2000 there is no longer the PDC/BDC concept.
The DC's are all the same and the differences are the 5 FSMO roles which
are located to some rules on the DC's.

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


> Hi,
>
> Question:
>
> I have a windows 2000 production network.. Just 2 servers. One is a
> PDC one is a member server..
>
> day the domain is: company.com
>
> Then I have a Windows 2008 TEST network. That has 3 servers. One
> PDC, one
> BDC and one member server.
> It has the same domain name as the live production network.
> Will there be a problem once everything is setup on the Win 2008
> network (users/files/printers, etc.) If one day we say okay WIndows
> 2008 network is all set, tested, etc. Let's shut off the Win 2000
> network.. Will the user computers and things all be able to just hop
> on the Windows 2008 being the domain name and all is the same?
>
> Right now windows 2008 network is completely seperate from windows
> 2000 network..
>

Thanks,

I haven't got to far along.. It is in a test environment.. So it's perfect
for learning. I've never done a migration before. It isn't a huge network
50 users..

In some ways I just wanted to do everything from scratch so it is all fresh.

I was curious about the same domain name.. Wondering if I should switch it
to something different just to keep that seperate..

Currently the Windows 2000 server PDC (in production) is running an
accounting database. I should be able to demote it and join the new domain
and keep that working in the new network..

Thanks for all the responses..
George


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:(E-Mail Removed) .com...
> Hello George,
>
> This will not work, just using the same names is not enough, the SID's of
> the domain and everything belonging to that will be different. If you do
> it that way you have to add the computers to the new domain and create all
> user account, groups, policies etc. again.
>
> What you can do is to create a new forest/domain with a different name,
> newdomain.loc, and use ADMT v3.1 to migrate the old to the new one. In
> this case you are able to take over everything to the new one. But this
> also should be tested from you before using the production domain.
>
> ADMTv3.1:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Small remark, since windows 2000 there is no longer the PDC/BDC concept.
> The DC's are all the same and the differences are the 5 FSMO roles which
> are located to some rules on the DC's.
>
> 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
>
>> Hi,
>>
>> Question:
>>
>> I have a windows 2000 production network.. Just 2 servers. One is a
>> PDC one is a member server..
>>
>> day the domain is: company.com
>>
>> Then I have a Windows 2008 TEST network. That has 3 servers. One
>> PDC, one
>> BDC and one member server.
>> It has the same domain name as the live production network.
>> Will there be a problem once everything is setup on the Win 2008
>> network (users/files/printers, etc.) If one day we say okay WIndows
>> 2008 network is all set, tested, etc. Let's shut off the Win 2000
>> network.. Will the user computers and things all be able to just hop
>> on the Windows 2008 being the domain name and all is the same?
>>
>> Right now windows 2008 network is completely seperate from windows
>> 2000 network..
>>
>
>

do you actually think it is best to take the new server join it to the old
domain as a member server or backup domain controller? Then demote the
primary and make this new server the primary?


"Danny Sanders" <(E-Mail Removed)> wrote in message
news:30638243-0143-49EF-88D6-(E-Mail Removed)...
> No not at all.
>
> You may have the names the same but the SAM is different. Just think if
> that were possible a user could bring their own DC to work, make a domain
> with the same name as the work domain and have all the user "hop" over to
> their domain where they know all the admin passwords and take control of
> your domain and lock you out.
>
>
> Your best bet is to do some reading up on migrating to a new domain using
> ADMT.
>
> Your projected plan will cause you loads of trouble.
>
> hth
> DDS
>
> "George" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi,
>>
>> Question:
>>
>> I have a windows 2000 production network.. Just 2 servers. One is a PDC
>> one is a member server..
>>
>> day the domain is: company.com
>>
>> Then I have a Windows 2008 TEST network. That has 3 servers. One PDC,
>> one BDC and one member server.
>> It has the same domain name as the live production network.
>>
>> Will there be a problem once everything is setup on the Win 2008 network
>> (users/files/printers, etc.) If one day we say okay WIndows 2008 network
>> is all set, tested, etc. Let's shut off the Win 2000 network.. Will
>> the user computers and things all be able to just hop on the Windows 2008
>> being the domain name and all is the same?
>>
>> Right now windows 2008 network is completely seperate from windows 2000
>> network..
>>
>

Hello George,

Check with the database vendor if any problems are known when you move it
to another domain. Service accounts for example created for the use of the
database or hardcoded servernames(if badly written).

Also keep in mind that you have to start from scratch when you demote the
existing DC from the production domain, so your users must save there data
on a network share or burn it to disk or whatever storage media.

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


> Thanks,
>
> I haven't got to far along.. It is in a test environment.. So it's
> perfect for learning. I've never done a migration before. It isn't a
> huge network 50 users..
>
> In some ways I just wanted to do everything from scratch so it is all
> fresh.
>
> I was curious about the same domain name.. Wondering if I should
> switch it to something different just to keep that seperate..
>
> Currently the Windows 2000 server PDC (in production) is running an
> accounting database. I should be able to demote it and join the new
> domain and keep that working in the new network..
>
> Thanks for all the responses..
> George
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news:(E-Mail Removed) .com...
>
>> Hello George,
>>
>> This will not work, just using the same names is not enough, the
>> SID's of the domain and everything belonging to that will be
>> different. If you do it that way you have to add the computers to the
>> new domain and create all user account, groups, policies etc. again.
>>
>> What you can do is to create a new forest/domain with a different
>> name, newdomain.loc, and use ADMT v3.1 to migrate the old to the new
>> one. In this case you are able to take over everything to the new
>> one. But this also should be tested from you before using the
>> production domain.
>>
>> ADMTv3.1:
>> http://www.microsoft.com/downloads/d...d=6D710919-1BA
>> 5-41CA-B2F3-C11BCB4857AF&displaylang=en
>> http://www.microsoft.com/downloads/d...d=AE279D01-7DC
>> A-413C-A9D2-B42DFB746059&displaylang=en
>>
>> Small remark, since windows 2000 there is no longer the PDC/BDC
>> concept. The DC's are all the same and the differences are the 5 FSMO
>> roles which are located to some rules on the DC's.
>>
>> 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
>>> Hi,
>>>
>>> Question:
>>>
>>> I have a windows 2000 production network.. Just 2 servers. One is
>>> a PDC one is a member server..
>>>
>>> day the domain is: company.com
>>>
>>> Then I have a Windows 2008 TEST network. That has 3 servers. One
>>> PDC, one
>>> BDC and one member server.
>>> It has the same domain name as the live production network.
>>> Will there be a problem once everything is setup on the Win 2008
>>> network (users/files/printers, etc.) If one day we say okay WIndows
>>> 2008 network is all set, tested, etc. Let's shut off the Win 2000
>>> network.. Will the user computers and things all be able to just
>>> hop
>>> on the Windows 2008 being the domain name and all is the same?
>>> Right now windows 2008 network is completely seperate from windows
>>> 2000 network..
>>>