Help me understand Windows Server Licensing
drasnor
Starship OperatorHawthorne, CA Icrontian
What a mess... Let me see if I have this straight:
Putting in a solution for a client that for simplicity's sake has no existing computer/server solution. The network infrastructure is already in place (multiple drops to each room, centralized wiring closet) so that isn't a problem.
Client wants 5 Windows XP PC's and one Windows Server 2003 server. Users have roaming profiles stored on the server but software will be stored locally on each machine. From what I understand, I'm going to need:
1x Windows Server 2003 license
5x Windows XP Professional licenses
5x Windows Server 2003 Client Access licenses (CALs)
...
all other software licensed on a per-machine basis.
Is this correct? What's the difference between a Terminal Server Client Access license and a normal CAL? What are TS-CALs used for and do I need any?
-drasnor
Putting in a solution for a client that for simplicity's sake has no existing computer/server solution. The network infrastructure is already in place (multiple drops to each room, centralized wiring closet) so that isn't a problem.
Client wants 5 Windows XP PC's and one Windows Server 2003 server. Users have roaming profiles stored on the server but software will be stored locally on each machine. From what I understand, I'm going to need:
1x Windows Server 2003 license
5x Windows XP Professional licenses
5x Windows Server 2003 Client Access licenses (CALs)
...
all other software licensed on a per-machine basis.
Is this correct? What's the difference between a Terminal Server Client Access license and a normal CAL? What are TS-CALs used for and do I need any?
-drasnor
0
Comments
TS licenses are if you are using dumb terminals on the client side and using the Win2k3 server as an application server (i.e, there is no "client" so there is no need for a CAL - winXP being the client software). You won't need any if you are using Windows XP (a client OS)
-drasnor