Re: NT4 to Win 03

> But if I do not need to use NT 4.0 BDCs, but do need to continue to
> provide
> users access to NT 4.0 file/application servers (member servers), could I
> accomplish this with the upgrade method? In other words, if I upgrade my
> PDC
> to Svr 03 AD, will NT 4.0 member servers still work right on the network?


Yes.
When you upgrade you automatically go into mixed mode. To migrate you have
to change the domain to native mode. It should be noted that this switch has
no affect what - so - ever on member servers or clients. It ONLY affects
replication between NT 4.0 BDCs and AD DCs in the same domain.

hth
DDS Win 2k MVP MCSE

"Savvytron" <Savvytron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3B2E77BA-900C-4533-BC86-FF31C9C49A58@xxxxxxxxxxxxxxxx
> I'm also interested in this topic. In regards to this part:
>
> "To move from NT to AD you either migrate, by setting up the NT domain and
> AD
> domain "side by side" on the same wire and use ADMT to migrate users from
> the NT domain to the AD domain, or upgrade, by upgrading the NT PDC first.
>
>> bearing in mind i would like to keep our existing NT 4 servers on the
> <snip>
>> I am not looking to change the existing domain name, if this makes it"
>
> But if I do not need to use NT 4.0 BDCs, but do need to continue to
> provide
> users access to NT 4.0 file/application servers (member servers), could I
> accomplish this with the upgrade method? In other words, if I upgrade my
> PDC
> to Svr 03 AD, will NT 4.0 member servers still work right on the network?
>
> "Danny Sanders" wrote:
>
>> To move from NT to AD you either migrate, by setting up the NT domain and
>> AD
>> domain "side by side" on the same wire and use ADMT to migrate users from
>> the NT domain to the AD domain, or upgrade, by upgrading the NT PDC
>> first.
>>
>> > bearing in mind i would like to keep our existing NT 4 servers on the
>> <snip>
>> > I am not looking to change the existing domain name, if this makes it
>>
>>
>> These two requirements rule out migrating.
>> To use ADMT the AD domain must be in Win2k or later native mode. In
>> native
>> mode your AD DCs will not replicate with NT BDCs.
>>
>> Migrating also requires a trust be set up between the two domains which
>> you
>> can't do if they have the same name.
>>
>>
>> Will your existing PDC support AD? If so upgrade it to Win 2k3, add the
>> "new" servers to the new as member servers then run dcpromo to make them
>> DCs.
>>
>> If not consider promoting one of the other BDCs that can support AD to
>> PDC,
>> then upgrade to Win 2k3.
>>
>> If none of your servers will support AD, remove Win 2k3 from one of the
>> "new" servers and install NT 4.0 on it as a BDC while connected to your
>> existing network, promote to PDC, then upgrade to Win 2k3.
>>
>>
>> hth
>> DDS W 2k MVP MCSE
>>
>>
>> "Moahmad" <Moahmad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:F727375B-B5D9-496F-B24A-2E535544B987@xxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > Our currnet network consists of two sites, site one has the PDC, and a
>> > File
>> > and Print Server. Site two has a BDC and the two sites are connected
>> > via
>> > a
>> > VPN.
>> >
>> > I have purcased two new servers with Windows 2003 and one with Exchange
>> > 03.
>> >
>> > What i would like to know is what is the best way of migrating to Win
>> > 03,
>> > bearing in mind i would like to keep our existing NT 4 servers on the
>> > network. Site one will host Exchange and the mail accounts for site
>> > two.
>> > The VPN is currently run over an ADSL line, will this cause any issues
>> > with
>> > regards to site two users accessing their mail accounts.
>> >
>> > I am not looking to change the existing domain name, if this makes it
>> > easier. We currently dont have Exchange, i am assuming i will neet to
>> > import
>> > the pst files into everyones mailbox, or is there a quicker way of
>> > moving
>> > the
>> > pst files into Exchange 03.
>> >
>> > Thanks for all your help
>> >
>> > Mohammad
>>
>>
>>


.

Relevant Pages

  • Re: NT4 to Win 03
    ... Easies is to upgrade your existing PDC. ... you have to set the AD domain in Native mode. ... If you upgrade you do not have to set your AD domain in native mode. ... > assume i will install the new 2003 servers one at a time. ...
    (microsoft.public.windows.server.migration)
  • Re: Please Confirm my design
    ... > One NT 4 PDC two BDCs, one BDC at headquarters with PDC and one BDC in a ... > Mixed clients, mostly XP Pro, few Windows 2000, and half dozen Win 98. ... > I have purchased 2 new IBM Computer and built them as new NT 4 BDCs, ... > I purchased three new Dell PowerEdge Servers with Windows 2003 Standard ...
    (microsoft.public.windows.server.migration)
  • Re: NT Server 4.0 to Server 2003 deployment
    ... > Of these seven servers one is my PDC and the other is my BDC. ... > have done research and one of the common methods is to install ... To upgrade your domain see the post I posted somewhere else. ...
    (microsoft.public.win2000.setup_deployment)
  • Re: NT Server 4.0 SP6a to Server 2003
    ... > Of these seven servers one is my PDC and the other is my BDC. ... > have done research and one of the common methods is to install ... To upgrade your domain see the post I posted somewhere else. ...
    (microsoft.public.win2000.setup_upgrade)
  • Re: Moving NT4 based PDC and BDC to Win2k
    ... The "easiest" way to move to AD is to just upgrade your pdc. ... > We are totally Win2k with the exception of our PDC and BDC ... We are planning on retiring these servers ...
    (microsoft.public.win2000.active_directory)