Adding Windows Server 2K3 to SBS2K domain

I have found some resources showing that it is possible to add a W2K3
server to our SBS2K domain, but I also read that each of the servers you
add uses one of the SBS2K licenses. Is that correct?

If I remember correctly you can have a max of 50 SBS2K licenses. Is
that right?

Also, when I add a W2K3 Server, I would license it per-seat, using the
total number of seats purchased with the SBS2K server, right?

Thanks!

Dvord
Mon Jun 14 18:35:16 CDT 2004

Now a follow-up even though I haven't gotten a reply yet to my first
questions...

Understanding the License noted: "All of the Small Business Server
server applications must be installed on the Small Business Server
computer."

Does that mean I must run Exchange, ISA, and IIS on the SBS? I'd really
like to run E2K on a newly procured W2K3 server if at all possible, not
to mention moving ISA onto another procured server (I want to have 3
total).

Thanks!

Dvord Direwood wrote:

> I have found some resources showing that it is possible to add a W2K3
> server to our SBS2K domain, but I also read that each of the servers you
> add uses one of the SBS2K licenses. Is that correct?
>
> If I remember correctly you can have a max of 50 SBS2K licenses. Is
> that right?
>
> Also, when I add a W2K3 Server, I would license it per-seat, using the
> total number of seats purchased with the SBS2K server, right?
>
> Thanks!
>
>

Javier
Mon Jun 14 18:45:17 CDT 2004

If you want to do that, you need the migration pack (read $$$). SBS does not
allow you to split its components on different servers.

--
Javier [SBS MVP]

<< SBS ROCKS!!! >>

"Dvord Direwood" <dvord@Hotmail.com> wrote in message
news:OPbqRgmUEHA.2908@TK2MSFTNGP10.phx.gbl...
> Now a follow-up even though I haven't gotten a reply yet to my first
> questions...
>
> Understanding the License noted: "All of the Small Business Server
> server applications must be installed on the Small Business Server
> computer."
>
> Does that mean I must run Exchange, ISA, and IIS on the SBS? I'd really
> like to run E2K on a newly procured W2K3 server if at all possible, not
> to mention moving ISA onto another procured server (I want to have 3
> total).
>
> Thanks!
>
> Dvord Direwood wrote:
>
>> I have found some resources showing that it is possible to add a W2K3
>> server to our SBS2K domain, but I also read that each of the servers you
>> add uses one of the SBS2K licenses. Is that correct?
>>
>> If I remember correctly you can have a max of 50 SBS2K licenses. Is
>> that right?
>>
>> Also, when I add a W2K3 Server, I would license it per-seat, using the
>> total number of seats purchased with the SBS2K server, right?
>>
>> Thanks!
>>
>>
>

Javier
Mon Jun 14 18:49:47 CDT 2004

Inline

>I have found some resources showing that it is possible to add a W2K3
> server to our SBS2K domain, but I also read that each of the servers you
> add uses one of the SBS2K licenses. Is that correct?

Yes. But since you have SBS2k you also need Win2k3 CALs (read the last
question).

> If I remember correctly you can have a max of 50 SBS2K licenses. Is
> that right?

Yes. In SBS2k3 they raised the limit to 75 licenses.

> Also, when I add a W2K3 Server, I would license it per-seat, using the
> total number of seats purchased with the SBS2K server, right?

Not really. If you had SBS2k3... then the SBS CALs would cover access to the
Win2k3 member servers (and each member server will consume a cal by itself)
and what you said would be ok. However, since you have SBS2k... you need
Win2k3 CALs and install them accordingly. Upgrade to SBS2k3 and you might
save in CALs.

--
Javier [SBS MVP]

<< SBS ROCKS!!! >>

Stephen
Tue Jun 15 08:58:52 CDT 2004

Hello,
I believe that if you were to add a windows 2k server (rather than 2003) to
your sbs2k , you only have to purchase the basic windows 2000 server retail
pack.
You would not need to purchase additional cals for the 2k server.

This is not true if you opt for windows 2003 server - you would have to buy
additional 2003 server cals.

HTH
Stephen

Dvord
Tue Jun 15 10:54:55 CDT 2004

Well I thought about the migration pack and it seemed less than buying
it outright, Upgrade was $599, 3X20-pack VUP CALs (3X$776)= $2927, not
bad (from:
http://www.microsoft.com/windowsserver2003/sbs/howtobuy/pricing.mspx )

Hrm, well what is considered a component then? ISA, Exchange, IIS?
That wouldn't make much sense since it's good security policy to put IIS
and ISA on the DMZ and keep Exchange behind it, right? That's what
always bugged me about SBS, all your eggs are in one basket and if
something happens everything is gone.

Well I think I'll go over the SBS2K3 deployment guides and see what I
can see there...

Thanks

Javier Gomez [SBS MVP] wrote:

> If you want to do that, you need the migration pack (read $$$). SBS does not
> allow you to split its components on different servers.
>
>