NT4 to Active Directory 2003 Qs

The fqdn you enter will be the domain name but the old netbios name will
stay the same. So you will have to ways to refer to the domain netbios and
fqdn. You won;t have to do anything to the existing clients.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"Mike" <nospam RemoveThis @test.com> wrote in message
news:OPj0begYJHA.5312@TK2MSFTNGP02.phx.gbl...
> Hi Paul,
>
> Thanks for your response. I didn't type my intentions clearly. I'm
> planning on doing an in-place upgrade, but thought it best I use a
> temporary machine to be the NT4 BDC that syncs SAM, then I remove it,
> promote to PDC, then do in-place upgrade. This machine would be a
> temporary machine and would sync AD to a permanet Win2003 domain
> controller with the same IP as the original PDC. This way doing
> everything off-line and separate from the production network making
> testing/troubleshooting easier. Also, my clients could have same WINS
> server and DNS server references.
>
> If I do an in-place upgrade,
>
> -The AD domain name will be the same correct? (in other words it will not
> be a FQDN such as domain.local)? I'm assuming this is the case if I won't
> have to change the workstation domain (by re-joining the new
> domain.local).
>
>
> Thanks for the answers I've never done a NT4 -> AD migration, just AD->AD,
> and my NT 4 memories are rusty (haven't used since 2001)
>
>
> Thanks,
> Mike
>
>
>
> "Paul Bergson" <pbbergs RemoveThis @nospammsn.com> wrote in message
> news:73742E4C-8B7F-4DB3-B432-75BF6F80FEEA@microsoft.com...
>> Why remove the PDC from the network? Just promote the new machine to a
>> PDC and do an in place upgrade. You can leave the NT4 machines in place
>> (member server or bdc's) on the network as long as you like you just
>> can't upgrade to DFL/FFL 2003 until you remove the BDC's, but you can
>> leave member servers as long as you like.
>>
>> If you change the domains you will need to join these XP machine to the
>> new domain. If you upgrade you shouldn;t have to.
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>> "Mike" <nospam RemoveThis @test.com> wrote in message
>> news:%233l9KEgYJHA.5108@TK2MSFTNGP04.phx.gbl...
>>> Hi,
>>>
>>> I have several migration questions for a NT 4 migration:
>>>
>>> I plan to migrate to AD 2003 in the following way:
>>> -Add BDC to NT 4 domain, remove from production network and promote as
>>> PDC.
>>> -Upgrade PDC to Win2003R2.
>>> -Build a permanent Domain controller on Win2003R2 sync with upgraded
>>> Win2003R2, then remove the upgraded machine.
>>>
>>>
>>> -If i Have the Win2003R2 on the same network as teh original NT4 system
>>> will this cause conflict?
>>> -Would I be best keeping the production and migration networks separate
>>> and have the new Win2003R2 system have the same IP as the NT4 PDC?
>>> -Will the XP PCs need to be re-joined to the domain or will their
>>> accounts carry to Active Directory?
>>> -Will the XP client domain name need to be chaned from domainname to
>>> domainname.local or will this migration not change the domain name to
>>> .local?
>>>
>>>
>>> Thanks for the answers in advance?
>>>
>>> Mike
>>
>