Wyte
10-16-2003, 11:32 AM
Does anyone here understand MS Windows licensing really well? Cuz I'm getting a headache.
Here's how I think it goes:
Win2k3 SBS Standard = Windows 2003 Server Standard Edition features
Win2k3 SBS Premium = Windows 2003 Server Enterprise Edition (with ISA server, SQL2000, yada yada)
CAL's
User CAL, Device CAL. Gotta choose. Simple enough.
But then, gotta license the individual components, requiring:
Windows CAL's
Exchange CAL's
MS TSC CAL's
SQL2000 CAL's
Okay, so if I were to buy a Win2k3 SBS Premium pack with 5 CAL's, is that 5 Windows CAL's only? IE: only licensed to log on to the domain and file/print share, but no terminal services, no exchange email etc... even though the runtimes for those are included in the package?
In other words, SBS Premium =
5 Windows CAL's
Exchange runtime (requires CAL's)
MS TSC runtime (requires CAL's)
SQL2000 runtime (requires CAL's)
Or maybe, I'd get 5 TS CAL's included? Or maybe (very very maybe) I'd get 5 Exchange + TS CAL's included?
I think it's prolly just the Windows CAL's. /sigh Gotta license every other "included" component seperately according to how many users will access it. Or, I could license per processor for many of those runtime components, which may come out on top for per user/device cost.
Okay, once I have my server licenses figured out, gotta look at client licenses.
In Win2k, if you had Win2k professional workstations, there was a clause allowing you to connect to the server without needing a Windows CAL for each station. It was 'included' in the Win2k pro O/S. Well, not really, I think the wording was that you can connect without needing a CAL if your workstation O/S is the same version or higher.
With Win2k3 server they've done away with this clause. However, from what I read, I can use WinXP pro the same way if I get the SA plan for the workstation? I'm confused. Or, even without the Software Assurance plan I can use WinXP Pro to connect without needing a CAL, but I'd be taking the risk of not having the CAL be 'upgradable' in any migration path. Ie: good for 1 O/S generation only.
aybe I should install RH Linux everywhere instead.
Any clarification from MS know-it-alls would be appreciated. ;)
Wyte
Here's how I think it goes:
Win2k3 SBS Standard = Windows 2003 Server Standard Edition features
Win2k3 SBS Premium = Windows 2003 Server Enterprise Edition (with ISA server, SQL2000, yada yada)
CAL's
User CAL, Device CAL. Gotta choose. Simple enough.
But then, gotta license the individual components, requiring:
Windows CAL's
Exchange CAL's
MS TSC CAL's
SQL2000 CAL's
Okay, so if I were to buy a Win2k3 SBS Premium pack with 5 CAL's, is that 5 Windows CAL's only? IE: only licensed to log on to the domain and file/print share, but no terminal services, no exchange email etc... even though the runtimes for those are included in the package?
In other words, SBS Premium =
5 Windows CAL's
Exchange runtime (requires CAL's)
MS TSC runtime (requires CAL's)
SQL2000 runtime (requires CAL's)
Or maybe, I'd get 5 TS CAL's included? Or maybe (very very maybe) I'd get 5 Exchange + TS CAL's included?
I think it's prolly just the Windows CAL's. /sigh Gotta license every other "included" component seperately according to how many users will access it. Or, I could license per processor for many of those runtime components, which may come out on top for per user/device cost.
Okay, once I have my server licenses figured out, gotta look at client licenses.
In Win2k, if you had Win2k professional workstations, there was a clause allowing you to connect to the server without needing a Windows CAL for each station. It was 'included' in the Win2k pro O/S. Well, not really, I think the wording was that you can connect without needing a CAL if your workstation O/S is the same version or higher.
With Win2k3 server they've done away with this clause. However, from what I read, I can use WinXP pro the same way if I get the SA plan for the workstation? I'm confused. Or, even without the Software Assurance plan I can use WinXP Pro to connect without needing a CAL, but I'd be taking the risk of not having the CAL be 'upgradable' in any migration path. Ie: good for 1 O/S generation only.
aybe I should install RH Linux everywhere instead.
Any clarification from MS know-it-alls would be appreciated. ;)
Wyte