Windows 2003 vs. Enterprise

I have a Windows 2003 network mad up of one DC running
Windows 2003 Standard. I want to install a Terminal
Server on this network but they purchased Windows 2003
Enterprise edition software. Can I install Enterprise on
another server and install it on the network as a
Terminal Server? I have heard that Standard and
Enterprise do not get along together on the network but
if the Enterprise is only acting as a role server, is
that OK???

Hi Joe,

Windows 2003 Standard and Enterprise can run on same network without any
problem.

They can both be DC at the same time on same network, they can be Exchange
servers at the same time on the same network, and they can be plain domain
members or any combination of this and more...

You can even add Windows 2000 and NT servers into combination.

So no, this is not a problem at all...

What I wouldn't be comfortable is running only one DC on the network. It's
pretty hard to restore a domain if there is only one domain controller
running and it is time consuming.

I hope this helps,

Mike

"Joe" <(E-Mail Removed)> wrote in message
news:032e01c47a68$32631c00$(E-Mail Removed)...
>
> I have a Windows 2003 network mad up of one DC running
> Windows 2003 Standard. I want to install a Terminal
> Server on this network but they purchased Windows 2003
> Enterprise edition software. Can I install Enterprise on
> another server and install it on the network as a
> Terminal Server? I have heard that Standard and
> Enterprise do not get along together on the network but
> if the Enterprise is only acting as a role server, is
> that OK???

Your heard wrong. Enterprise and Standard don't even care about e/o. It will
run without issues. The real differences are mostly in hardware support and
expandability but they coexist without problems.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Joe" <(E-Mail Removed)> wrote in message
news:032e01c47a68$32631c00$(E-Mail Removed)...
>
> I have a Windows 2003 network mad up of one DC running
> Windows 2003 Standard. I want to install a Terminal
> Server on this network but they purchased Windows 2003
> Enterprise edition software. Can I install Enterprise on
> another server and install it on the network as a
> Terminal Server? I have heard that Standard and
> Enterprise do not get along together on the network but
> if the Enterprise is only acting as a role server, is
> that OK???

Is there a step by step out there that shows me the
way to set up a second DC on a domain??? I know it is
not hard but I would like a nice step by step.



>-----Original Message-----
>Hi Joe,
>
>Windows 2003 Standard and Enterprise can run on same
network without any
>problem.
>
>They can both be DC at the same time on same network,
they can be Exchange
>servers at the same time on the same network, and they
can be plain domain
>members or any combination of this and more...
>
>You can even add Windows 2000 and NT servers into
combination.
>
>So no, this is not a problem at all...
>
>What I wouldn't be comfortable is running only one DC on
the network. It's
>pretty hard to restore a domain if there is only one
domain controller
>running and it is time consuming.
>
>I hope this helps,
>
>Mike
>
>"Joe" <(E-Mail Removed)> wrote in
message
>news:032e01c47a68$32631c00$(E-Mail Removed)...
>>
>> I have a Windows 2003 network mad up of one DC
running
>> Windows 2003 Standard. I want to install a Terminal
>> Server on this network but they purchased Windows 2003
>> Enterprise edition software. Can I install Enterprise
on
>> another server and install it on the network as a
>> Terminal Server? I have heard that Standard and
>> Enterprise do not get along together on the network but
>> if the Enterprise is only acting as a role server, is
>> that OK???
>
>
>.
>

Hi Joe,

you are right it is simple.

Steps would be this:

1. Install Windows 2003 server
2. Patch it up with all the latest updates
3. Join this new server to domain
4. Run dcpromo (start -> run -> dcpromo -> click OK)

I hope this helps,

Mike

"Joe" <(E-Mail Removed)> wrote in message
news:02ef01c47a70$e8193b30$(E-Mail Removed)...
>
> Is there a step by step out there that shows me the
> way to set up a second DC on a domain??? I know it is
> not hard but I would like a nice step by step.
>
>
>
> >-----Original Message-----
> >Hi Joe,
> >
> >Windows 2003 Standard and Enterprise can run on same
> network without any
> >problem.
> >
> >They can both be DC at the same time on same network,
> they can be Exchange
> >servers at the same time on the same network, and they
> can be plain domain
> >members or any combination of this and more...
> >
> >You can even add Windows 2000 and NT servers into
> combination.
> >
> >So no, this is not a problem at all...
> >
> >What I wouldn't be comfortable is running only one DC on
> the network. It's
> >pretty hard to restore a domain if there is only one
> domain controller
> >running and it is time consuming.
> >
> >I hope this helps,
> >
> >Mike
> >
> >"Joe" <(E-Mail Removed)> wrote in
> message
> >news:032e01c47a68$32631c00$(E-Mail Removed)...
> >>
> >> I have a Windows 2003 network mad up of one DC
> running
> >> Windows 2003 Standard. I want to install a Terminal
> >> Server on this network but they purchased Windows 2003
> >> Enterprise edition software. Can I install Enterprise
> on
> >> another server and install it on the network as a
> >> Terminal Server? I have heard that Standard and
> >> Enterprise do not get along together on the network but
> >> if the Enterprise is only acting as a role server, is
> >> that OK???
> >
> >
> >.
> >

On Thu, 5 Aug 2004 00:31:33 +0200, Miha Pihler <mihap-(E-Mail Removed)>
wrote:

> "Joe" <(E-Mail Removed)> wrote in message
> news:02ef01c47a70$e8193b30$(E-Mail Removed)...
>>
>> Is there a step by step out there that shows me the
>> way to set up a second DC on a domain??? I know it is
>> not hard but I would like a nice step by step.

> Steps would be this:
>
> 1. Install Windows 2003 server
> 2. Patch it up with all the latest updates
> 3. Join this new server to domain
> 4. Run dcpromo (start -> run -> dcpromo -> click OK)

Do you have to join the domain prior to running DC promo?
I though not. Reason for asking: Tests seems to ask for
least administrative effort, and joining the domain first
would add one more step.

--
Ole Kristian Bangås
http://www.bangaas.com/

Yes, you have to add this server to domain first... This is also a "test" of
you TCP configuration. If you are able to add server to domain then your DNS
configuration is very likely setup as it should be.

Mike

"Ole Kristian Bangås" <(E-Mail Removed)> wrote in message
newspsb8gb8dr2qlbo6@wks...
> On Thu, 5 Aug 2004 00:31:33 +0200, Miha Pihler <mihap-(E-Mail Removed)>
> wrote:
>
> > "Joe" <(E-Mail Removed)> wrote in message
> > news:02ef01c47a70$e8193b30$(E-Mail Removed)...
> >>
> >> Is there a step by step out there that shows me the
> >> way to set up a second DC on a domain??? I know it is
> >> not hard but I would like a nice step by step.
>
> > Steps would be this:
> >
> > 1. Install Windows 2003 server
> > 2. Patch it up with all the latest updates
> > 3. Join this new server to domain
> > 4. Run dcpromo (start -> run -> dcpromo -> click OK)
>
> Do you have to join the domain prior to running DC promo?
> I though not. Reason for asking: Tests seems to ask for
> least administrative effort, and joining the domain first
> would add one more step.
>
> --
> Ole Kristian Bangås
> http://www.bangaas.com/

In news:(E-Mail Removed),
Miha Pihler <mihap-(E-Mail Removed)> made a post then I commented below
> Yes, you have to add this server to domain first... This is also a
> "test" of you TCP configuration. If you are able to add server to
> domain then your DNS configuration is very likely setup as it should
> be.
>
> Mike
>

Actually, all you have to do is set the Primary DNS Suffix to the current
domain and set the DNS addresses to the current DNS that AD is using, then
run dcpromo. Not really necessary to join it. Dcpromo will do the rest. Of
course there are other 'best practice" tasks to be performed afterwards...

Here's more specific info about creating a n. This applies to W2k and W2k3:

Windows 2000 Step-by-Step Guides -Installing AD and Pro as a Client (look
for the link that says "Step-by-Step Guide to Setting up Additional Domain
Controllers ":
http://www.microsoft.com/windows2000...hs/default.asp

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================