elemist
asked on
Microsoft Licensing
Hi,
I'm attempting to get my head around the different Microsoft Licensing options.
I'm putting together a couple of possible scenarios for implementing a terminal server. However to keep things complex, there is an existing sbs 2003 server which will be due for retirement in approx 8 months, so we're considering replacing it at the same time.
To complicate things further, we are considering consolidating a number of site servers located in different offices (approx 3 - 6 additional servers) at some point in the future.
Scenario 1:
Additional Terminal Server - 15 Users
Existing SBS 2003 server with 10 CALS
Licensing Questions:
1) The idea is to rebuild the desktops as purely "thin clients". However they will still initially be full versions of Windows XP / 7. I would prefer to manage them via group policy, and have them as part of the domain. I assume this will require them to have a valid SBS CAL?
2) If we were to proceed down the path of keeping these off the domain, will they still need SBS CALS?
3) Assuming we proceed with some form of MS volume license agreement with SA we gain access to Windows 7 Think PC which we may use to replace the native OS. Again will these require SBS CALS?
4) If they don't require CALS, could we technically get away with using a single device CAL - that "device" being the terminal server?
5) We may have 2-3 computers we keep as fat clients due to the roles they do. These will obviously need SBS CALS.
6) See main Terminal Server licensing questions below :)
Scenario 2:
Additional Terminal Server - 15 Users
Replace SBS 2003 server with 2011 SBS - 15 CALS
1) Licensing wise - very similar to the above. Is there any licensing differences between 2003 and 2011?
Scenario 3:
Additional Terminal Server - 15 Users
Replace SBS 2003 server with 2008 R2 server - 15 CALS
1) I'm a bit hazy again when it comes to the CAL requirements. For "thin PC's" (EG Windows 7 Thin PC) do they require a SBS CAL?
2) For Fat Clients who are doing nothing apart from acting as "think PC's" do they require a SBS CAL?
General Licensing Questions:
1) Some form of MS Volume licensing for the Terminal Server licensing (OS, CALS, RDS CALS) would be the logical step forward right? There existing licensing (SBS, Windows, Office is all SBS)
2) How does Windows Server CAL licensing work in a terminal server environment? We will be having generic logins for each client - eg room1, room2. Do we need to have server CALS for the amount of logins, or the amount of concurrent logins? IE we might have Rooms 1 - 15, however generally there will only be 8-10 logged in at any one time.
3) If we were to go with Scenario 3 - i assume we would be better going for a per device CAL and licensing all the computers thus covering access to both 2008r2 servers?
4) Bearing in mind the possibility of scaling this into a virtual environment - any suggestions?
5) Do CALS count as product purchases for volume licensing. IE if there's a minimum of 5 products, do the CALS count towards a product ie is 15 CALS = 15 products or are "X amount of CALS" a single product?
I'm so confused.. dam Microsoft Licensing gives me a headache!
I'm attempting to get my head around the different Microsoft Licensing options.
I'm putting together a couple of possible scenarios for implementing a terminal server. However to keep things complex, there is an existing sbs 2003 server which will be due for retirement in approx 8 months, so we're considering replacing it at the same time.
To complicate things further, we are considering consolidating a number of site servers located in different offices (approx 3 - 6 additional servers) at some point in the future.
Scenario 1:
Additional Terminal Server - 15 Users
Existing SBS 2003 server with 10 CALS
Licensing Questions:
1) The idea is to rebuild the desktops as purely "thin clients". However they will still initially be full versions of Windows XP / 7. I would prefer to manage them via group policy, and have them as part of the domain. I assume this will require them to have a valid SBS CAL?
2) If we were to proceed down the path of keeping these off the domain, will they still need SBS CALS?
3) Assuming we proceed with some form of MS volume license agreement with SA we gain access to Windows 7 Think PC which we may use to replace the native OS. Again will these require SBS CALS?
4) If they don't require CALS, could we technically get away with using a single device CAL - that "device" being the terminal server?
5) We may have 2-3 computers we keep as fat clients due to the roles they do. These will obviously need SBS CALS.
6) See main Terminal Server licensing questions below :)
Scenario 2:
Additional Terminal Server - 15 Users
Replace SBS 2003 server with 2011 SBS - 15 CALS
1) Licensing wise - very similar to the above. Is there any licensing differences between 2003 and 2011?
Scenario 3:
Additional Terminal Server - 15 Users
Replace SBS 2003 server with 2008 R2 server - 15 CALS
1) I'm a bit hazy again when it comes to the CAL requirements. For "thin PC's" (EG Windows 7 Thin PC) do they require a SBS CAL?
2) For Fat Clients who are doing nothing apart from acting as "think PC's" do they require a SBS CAL?
General Licensing Questions:
1) Some form of MS Volume licensing for the Terminal Server licensing (OS, CALS, RDS CALS) would be the logical step forward right? There existing licensing (SBS, Windows, Office is all SBS)
2) How does Windows Server CAL licensing work in a terminal server environment? We will be having generic logins for each client - eg room1, room2. Do we need to have server CALS for the amount of logins, or the amount of concurrent logins? IE we might have Rooms 1 - 15, however generally there will only be 8-10 logged in at any one time.
3) If we were to go with Scenario 3 - i assume we would be better going for a per device CAL and licensing all the computers thus covering access to both 2008r2 servers?
4) Bearing in mind the possibility of scaling this into a virtual environment - any suggestions?
5) Do CALS count as product purchases for volume licensing. IE if there's a minimum of 5 products, do the CALS count towards a product ie is 15 CALS = 15 products or are "X amount of CALS" a single product?
I'm so confused.. dam Microsoft Licensing gives me a headache!
If you're not using SQL Server, getting the Premium Add-on is a waste of money - get a standard copy of Server, it's cheaper.
Otherwise, I agree with TechSoEasy.
Otherwise, I agree with TechSoEasy.
ASKER
Thanks for the replies. Yes your correct in that we currently have an additional 10 CALS to the 5 included. Honestly i have no idea whether they are device or user CALS as it was way before my time.
So i assume that the existing client machines will still require a device CAL given they will be a member of the domain.
I am considering moving away from an SBS environment due to the fact we don't really use the SBS features - IE we have a single email address which could easily be handled using pop mail hosted externally. No need to SQL or Sharepoint either.
The reason i'm looking towards Volume licensing is the fact there's a high probability that we will be consolidating the remote offices at some point in the next 12 months, so i need this solution to scale with us. Including the MS licensing.
So i'm thinking about doing the following.
Server 1: Win 2008R2 Std - AD/DNS/DHCP/File & Print
Server 2: Win 2008R2 Std - Terminal Server.
From my understanding of Server 2008R2 volume licensing allows for the use of a single license to run 1 physical and 1 virtual machine - on the proviso the the physical machine is only used to run the hyper-v role. *note* i'm suggesting buying two physical licenses, just need to confirm about the ability to have a physical & virtual machine per license.
This way when the consolidation occurs it will allow us to easily build up additional virtual machines by purchasing additional licenses.
So assuming the above i imagine the clients be it fat clients or thin clients will still require 1 2008 server device cal and 1 RDS device CAL each?
So i assume that the existing client machines will still require a device CAL given they will be a member of the domain.
I am considering moving away from an SBS environment due to the fact we don't really use the SBS features - IE we have a single email address which could easily be handled using pop mail hosted externally. No need to SQL or Sharepoint either.
The reason i'm looking towards Volume licensing is the fact there's a high probability that we will be consolidating the remote offices at some point in the next 12 months, so i need this solution to scale with us. Including the MS licensing.
So i'm thinking about doing the following.
Server 1: Win 2008R2 Std - AD/DNS/DHCP/File & Print
Server 2: Win 2008R2 Std - Terminal Server.
From my understanding of Server 2008R2 volume licensing allows for the use of a single license to run 1 physical and 1 virtual machine - on the proviso the the physical machine is only used to run the hyper-v role. *note* i'm suggesting buying two physical licenses, just need to confirm about the ability to have a physical & virtual machine per license.
This way when the consolidation occurs it will allow us to easily build up additional virtual machines by purchasing additional licenses.
So assuming the above i imagine the clients be it fat clients or thin clients will still require 1 2008 server device cal and 1 RDS device CAL each?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
It seems to me that your best option in this scenario would most likely be to upgrade to SBS 2011 with the Premium Add-on for licensing your Remote Desktop Services Server. (Formerly Terminal Server). Servers do NOT need a device CAL in an SBS environment.
You will then need an SBS "USER" CAL for each user account logging onto your network AND an RDS CAL for any user or device which accesses your RDS Server. If you have lots of people logging into the RDS Server from a single device (ie, Room1), you only need a single RDS CAL for this device and all of its users (and if they are sharing a domain user account, a single SBS USER CAL as well -- but remember SBS comes with 5 CALS so you would probably just need 10 additional).
With regards to Volume Licensing -- SBS alone, because it includes 5 CALS, is enough to get an agreement.
Don't think "concurrent" logins anymore... each user (a primary user which is not logging in on one of your shared devices) OR device that is used by multiple "other" users needs a CAL.
There is a decent overview video of SBS and RDS licensing here:
http://www.youtube.com/watch?v=IluFj9gcLZI
Jeff
TechSoEasy