2003 Server in NT Domain?

Hi,

I have an NT Domain (One PDC, one BDC) with 5 W2000 application/member
servers. I need to buy a new application server. I'd like to install 2003
Server so I won't have to upgrade it when the Domain is finally upgraded.
Is this a viable proposition? What should I do so I don't have to make any
mods when the domain is upgraded?

Thanks,
SteveW

Hi Steve,

With information that you gave us, it's really hard to say anything useful.
If your new Windows 2003 server won't be a domain controller (DC) then you
shouldn't have any problems later on when you upgrade your domain...

Mike

"Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I have an NT Domain (One PDC, one BDC) with 5 W2000 application/member
> servers. I need to buy a new application server. I'd like to install 2003
> Server so I won't have to upgrade it when the Domain is finally upgraded.
> Is this a viable proposition? What should I do so I don't have to make any
> mods when the domain is upgraded?
>
> Thanks,
> SteveW
>
>

Hi,

When its installed, no, it won't be a domain controller. However, later on,
when I retire the PDC and BDC, I don't know what path to take.
I don't know if I should then make the new server a DC, or one of the W2000
servers. What would you advise?

Regards
Steve

"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi Steve,
>
> With information that you gave us, it's really hard to say anything
useful.
> If your new Windows 2003 server won't be a domain controller (DC) then you
> shouldn't have any problems later on when you upgrade your domain...
>
> Mike
>
> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > I have an NT Domain (One PDC, one BDC) with 5 W2000 application/member
> > servers. I need to buy a new application server. I'd like to install
2003
> > Server so I won't have to upgrade it when the Domain is finally
upgraded.
> > Is this a viable proposition? What should I do so I don't have to make
any
> > mods when the domain is upgraded?
> >
> > Thanks,
> > SteveW
> >
> >
>
>

Hi Steve,



for DC I would always recommend a separate server (actually two). My reasons
are:



* security (why would I allow users to run applications on my DC)

* performance (if applications that runs on DC cause a lot processor stress,
users could get slow logon and authentication responses)

* restore time (depending on applications that you run on your server it
could prolong disaster recover time)

* ...



Services that I usually allow to run on DC are DHCP service, DNS service
(obvious) and print service (print server)



I hope this helps you out,



Mike


"Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> When its installed, no, it won't be a domain controller. However, later
> on,
> when I retire the PDC and BDC, I don't know what path to take.
> I don't know if I should then make the new server a DC, or one of the
> W2000
> servers. What would you advise?
>
> Regards
> Steve
>
> "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hi Steve,
>>
>> With information that you gave us, it's really hard to say anything
> useful.
>> If your new Windows 2003 server won't be a domain controller (DC) then
>> you
>> shouldn't have any problems later on when you upgrade your domain...
>>
>> Mike
>>
>> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
>> news:(E-Mail Removed)...
>> > Hi,
>> >
>> > I have an NT Domain (One PDC, one BDC) with 5 W2000 application/member
>> > servers. I need to buy a new application server. I'd like to install
> 2003
>> > Server so I won't have to upgrade it when the Domain is finally
> upgraded.
>> > Is this a viable proposition? What should I do so I don't have to make
> any
>> > mods when the domain is upgraded?
>> >
>> > Thanks,
>> > SteveW
>> >
>> >
>>
>>
>
>

Thank you, Mike.

That is useful. Can you recommend a book or other resource so I could learn
more about What we've just been discussing?

Regards
SteveW

"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Steve,
>
>
>
> for DC I would always recommend a separate server (actually two). My
reasons
> are:
>
>
>
> * security (why would I allow users to run applications on my DC)
>
> * performance (if applications that runs on DC cause a lot processor
stress,
> users could get slow logon and authentication responses)
>
> * restore time (depending on applications that you run on your server it
> could prolong disaster recover time)
>
> * ...
>
>
>
> Services that I usually allow to run on DC are DHCP service, DNS service
> (obvious) and print service (print server)
>
>
>
> I hope this helps you out,
>
>
>
> Mike
>
>
> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > When its installed, no, it won't be a domain controller. However, later
> > on,
> > when I retire the PDC and BDC, I don't know what path to take.
> > I don't know if I should then make the new server a DC, or one of the
> > W2000
> > servers. What would you advise?
> >
> > Regards
> > Steve
> >
> > "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Hi Steve,
> >>
> >> With information that you gave us, it's really hard to say anything
> > useful.
> >> If your new Windows 2003 server won't be a domain controller (DC) then
> >> you
> >> shouldn't have any problems later on when you upgrade your domain...
> >>
> >> Mike
> >>
> >> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> >> news:(E-Mail Removed)...
> >> > Hi,
> >> >
> >> > I have an NT Domain (One PDC, one BDC) with 5 W2000
application/member
> >> > servers. I need to buy a new application server. I'd like to install
> > 2003
> >> > Server so I won't have to upgrade it when the Domain is finally
> > upgraded.
> >> > Is this a viable proposition? What should I do so I don't have to
make
> > any
> >> > mods when the domain is upgraded?
> >> >
> >> > Thanks,
> >> > SteveW
> >> >
> >> >
> >>
> >>
> >
> >
>
>

Hi Steve,

I am sure there are quite a few very good books out there, but personally I
prefer using on-line resources from Microsoft site when possible...

Here is a pretty good start for you:
Upgrading Domains from Windows NT 4.0 to Windows Server 2003 Active
Directory
http://www.microsoft.com/resources/d..._upnt_sawk.asp

It will take you through the process of upgrade almost step-by-step.

If I was looking for a book I would go with this one:
Active DirectoryR for MicrosoftR WindowsR Server 2003 Technical Reference
http://www.microsoft.com/mspress/books/5867.asp

I hope this helps you out,

Mike

"Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
news:%(E-Mail Removed)...
> Thank you, Mike.
>
> That is useful. Can you recommend a book or other resource so I could
> learn
> more about What we've just been discussing?
>
> Regards
> SteveW
>
> "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Steve,
>>
>>
>>
>> for DC I would always recommend a separate server (actually two). My
> reasons
>> are:
>>
>>
>>
>> * security (why would I allow users to run applications on my DC)
>>
>> * performance (if applications that runs on DC cause a lot processor
> stress,
>> users could get slow logon and authentication responses)
>>
>> * restore time (depending on applications that you run on your server it
>> could prolong disaster recover time)
>>
>> * ...
>>
>>
>>
>> Services that I usually allow to run on DC are DHCP service, DNS service
>> (obvious) and print service (print server)
>>
>>
>>
>> I hope this helps you out,
>>
>>
>>
>> Mike
>>
>>
>> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
>> news:(E-Mail Removed)...
>> > Hi,
>> >
>> > When its installed, no, it won't be a domain controller. However, later
>> > on,
>> > when I retire the PDC and BDC, I don't know what path to take.
>> > I don't know if I should then make the new server a DC, or one of the
>> > W2000
>> > servers. What would you advise?
>> >
>> > Regards
>> > Steve
>> >
>> > "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
>> > news:%(E-Mail Removed)...
>> >> Hi Steve,
>> >>
>> >> With information that you gave us, it's really hard to say anything
>> > useful.
>> >> If your new Windows 2003 server won't be a domain controller (DC) then
>> >> you
>> >> shouldn't have any problems later on when you upgrade your domain...
>> >>
>> >> Mike
>> >>
>> >> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
>> >> news:(E-Mail Removed)...
>> >> > Hi,
>> >> >
>> >> > I have an NT Domain (One PDC, one BDC) with 5 W2000
> application/member
>> >> > servers. I need to buy a new application server. I'd like to install
>> > 2003
>> >> > Server so I won't have to upgrade it when the Domain is finally
>> > upgraded.
>> >> > Is this a viable proposition? What should I do so I don't have to
> make
>> > any
>> >> > mods when the domain is upgraded?
>> >> >
>> >> > Thanks,
>> >> > SteveW
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>

Thanks Mike.

"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Steve,
>
> I am sure there are quite a few very good books out there, but personally
I
> prefer using on-line resources from Microsoft site when possible...
>
> Here is a pretty good start for you:
> Upgrading Domains from Windows NT 4.0 to Windows Server 2003 Active
> Directory
>
http://www.microsoft.com/resources/d..._upnt_sawk.asp
>
> It will take you through the process of upgrade almost step-by-step.
>
> If I was looking for a book I would go with this one:
> Active DirectoryR for MicrosoftR WindowsR Server 2003 Technical Reference
> http://www.microsoft.com/mspress/books/5867.asp
>
> I hope this helps you out,
>
> Mike
>
> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> news:%(E-Mail Removed)...
> > Thank you, Mike.
> >
> > That is useful. Can you recommend a book or other resource so I could
> > learn
> > more about What we've just been discussing?
> >
> > Regards
> > SteveW
> >
> > "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Hi Steve,
> >>
> >>
> >>
> >> for DC I would always recommend a separate server (actually two). My
> > reasons
> >> are:
> >>
> >>
> >>
> >> * security (why would I allow users to run applications on my DC)
> >>
> >> * performance (if applications that runs on DC cause a lot processor
> > stress,
> >> users could get slow logon and authentication responses)
> >>
> >> * restore time (depending on applications that you run on your server
it
> >> could prolong disaster recover time)
> >>
> >> * ...
> >>
> >>
> >>
> >> Services that I usually allow to run on DC are DHCP service, DNS
service
> >> (obvious) and print service (print server)
> >>
> >>
> >>
> >> I hope this helps you out,
> >>
> >>
> >>
> >> Mike
> >>
> >>
> >> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> >> news:(E-Mail Removed)...
> >> > Hi,
> >> >
> >> > When its installed, no, it won't be a domain controller. However,
later
> >> > on,
> >> > when I retire the PDC and BDC, I don't know what path to take.
> >> > I don't know if I should then make the new server a DC, or one of the
> >> > W2000
> >> > servers. What would you advise?
> >> >
> >> > Regards
> >> > Steve
> >> >
> >> > "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
> >> > news:%(E-Mail Removed)...
> >> >> Hi Steve,
> >> >>
> >> >> With information that you gave us, it's really hard to say anything
> >> > useful.
> >> >> If your new Windows 2003 server won't be a domain controller (DC)
then
> >> >> you
> >> >> shouldn't have any problems later on when you upgrade your domain...
> >> >>
> >> >> Mike
> >> >>
> >> >> "Steve W" <antispamsteveW@=No-Spam=.org> wrote in message
> >> >> news:(E-Mail Removed)...
> >> >> > Hi,
> >> >> >
> >> >> > I have an NT Domain (One PDC, one BDC) with 5 W2000
> > application/member
> >> >> > servers. I need to buy a new application server. I'd like to
install
> >> > 2003
> >> >> > Server so I won't have to upgrade it when the Domain is finally
> >> > upgraded.
> >> >> > Is this a viable proposition? What should I do so I don't have to
> > make
> >> > any
> >> >> > mods when the domain is upgraded?
> >> >> >
> >> >> > Thanks,
> >> >> > SteveW
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>

On Sun, 20 Jun 2004 07:52:56 +0100, "Steve W"
<antispamsteveW@=No-Spam=.org> wrote:

>I have an NT Domain (One PDC, one BDC) with 5 W2000 application/member
>servers. I need to buy a new application server. I'd like to install 2003
>Server so I won't have to upgrade it when the Domain is finally upgraded.
>Is this a viable proposition? What should I do so I don't have to make any
>mods when the domain is upgraded?

Works fine. Make it a member server. At some future time, either
upgrade a PDC or BDC to Server 2003 to migrate your domain or install
a new Server 2003 system to become the DC and migrate over.

Jeff

As a follow-up to Steve's question, If I install A W2K3
member server on an NT domain, can I run Exchange 2003 on
it? E2K3 requires Active Directory which requires DNS,
but the W2K3 server won't be a domain controller.


>-----Original Message-----
>On Sun, 20 Jun 2004 07:52:56 +0100, "Steve W"
><antispamsteveW@=No-Spam=.org> wrote:
>
>>I have an NT Domain (One PDC, one BDC) with 5 W2000
application/member
>>servers. I need to buy a new application server. I'd
like to install 2003
>>Server so I won't have to upgrade it when the Domain is
finally upgraded.
>>Is this a viable proposition? What should I do so I
don't have to make any
>>mods when the domain is upgraded?
>
>Works fine. Make it a member server. At some future
time, either
>upgrade a PDC or BDC to Server 2003 to migrate your
domain or install
>a new Server 2003 system to become the DC and migrate
over.
>
>Jeff
>.
>

Hi,

if you would like to have Exchange 2003 you will need Active Directory -
Windows 2003 (or Windows 2000) will have to be a domain controller.

In NT domain you can have Exchange 5.5, but it will not run on Windows 2003
(it will run on Windows 2000).

Hope this helps,

Mike

"PaulW" <(E-Mail Removed)> wrote in message
news:2cc1301c46911$2f7a6f10$(E-Mail Removed)...
> As a follow-up to Steve's question, If I install A W2K3
> member server on an NT domain, can I run Exchange 2003 on
> it? E2K3 requires Active Directory which requires DNS,
> but the W2K3 server won't be a domain controller.
>
>
> >-----Original Message-----
> >On Sun, 20 Jun 2004 07:52:56 +0100, "Steve W"
> ><antispamsteveW@=No-Spam=.org> wrote:
> >
> >>I have an NT Domain (One PDC, one BDC) with 5 W2000
> application/member
> >>servers. I need to buy a new application server. I'd
> like to install 2003
> >>Server so I won't have to upgrade it when the Domain is
> finally upgraded.
> >>Is this a viable proposition? What should I do so I
> don't have to make any
> >>mods when the domain is upgraded?
> >
> >Works fine. Make it a member server. At some future
> time, either
> >upgrade a PDC or BDC to Server 2003 to migrate your
> domain or install
> >a new Server 2003 system to become the DC and migrate
> over.
> >
> >Jeff
> >.
> >