finance_teacher
asked on
Microsoft -- multi-server CALs
I have 100 users with the below old
Microsoft servers that need upgrading
server #1 = MS File/Domain/Print
server #2 = MS SQL Database
server #3 = MS IIS external web frontend
server #4 = MS SharePoint external web frontend
server #5 = MS Exchange external web frontend
1. Can I get some type of "multi-server CAL" that does all of the above OR do I need to purchase CALS for each server ?
2. Can I just purchase the SERVER upgrade and NOT have to purchase CAL upgrades ?
If cost is TOO high I plan to put some items in the CLOUD.
I do not want a Microsoft EA agreement since we only upgrade once every six years.
Microsoft servers that need upgrading
server #1 = MS File/Domain/Print
server #2 = MS SQL Database
server #3 = MS IIS external web frontend
server #4 = MS SharePoint external web frontend
server #5 = MS Exchange external web frontend
1. Can I get some type of "multi-server CAL" that does all of the above OR do I need to purchase CALS for each server ?
2. Can I just purchase the SERVER upgrade and NOT have to purchase CAL upgrades ?
If cost is TOO high I plan to put some items in the CLOUD.
I do not want a Microsoft EA agreement since we only upgrade once every six years.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, and I tried in all of my sentences to clearly state license or CAL. My mistake for saying CAL in that sentence, thank you for point that out.
I was trying to point out that you said -
"Now, windows licensing is per user or per device. Not per server."
But this is not accurate.
The Windows Operating System needs a license, then the users need CALS- Client Access Licenses for accessing the server resources. Then they also need CALS for specific applications such as Exchange and SQL.
Since Microsoft has discontinued SBS (which wouldn't apply with 100 users anyway) I don't know of a CAL that groups all of those applications together.
I was trying to point out that you said -
"Now, windows licensing is per user or per device. Not per server."
But this is not accurate.
The Windows Operating System needs a license, then the users need CALS- Client Access Licenses for accessing the server resources. Then they also need CALS for specific applications such as Exchange and SQL.
Since Microsoft has discontinued SBS (which wouldn't apply with 100 users anyway) I don't know of a CAL that groups all of those applications together.
The core CAL suites do group some applications together.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looks like below is what everyone agrees on ?
If so, I will ask CDW.com to make sure
--------------------------
server #1 = MS File/Domain/Print
** 1 Windows OS server license
** 100 Windows OS CALs
ADD-ONS
** none
--------------------------
server #2 = MS SQL Database
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** 1 SQL server license, includes 2 processor-core licenses
** 2 SQL server processor-core licenses, since must do 4 TOTAL
processor-core licenses per Microsoft if doing "CORE" licensing
--------------------------
server #3 = MS IIS external web frontend
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** none
--------------------------
server #4 = MS SharePoint and external web frontend
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** 1 SharePoint server license, includes 2 processor-core licenses
** 2 SharePoint server processor-core licenses, since must do 4 TOTAL
processor-core licenses per Microsoft if doing "CORE" licensing
--------------------------
server #5 = MS Exchange and external web frontend
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** 1 Exchange server license
** 100 Exchange server CALs
If so, I will ask CDW.com to make sure
--------------------------
server #1 = MS File/Domain/Print
** 1 Windows OS server license
** 100 Windows OS CALs
ADD-ONS
** none
--------------------------
server #2 = MS SQL Database
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** 1 SQL server license, includes 2 processor-core licenses
** 2 SQL server processor-core licenses, since must do 4 TOTAL
processor-core licenses per Microsoft if doing "CORE" licensing
--------------------------
server #3 = MS IIS external web frontend
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** none
--------------------------
server #4 = MS SharePoint and external web frontend
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** 1 SharePoint server license, includes 2 processor-core licenses
** 2 SharePoint server processor-core licenses, since must do 4 TOTAL
processor-core licenses per Microsoft if doing "CORE" licensing
--------------------------
server #5 = MS Exchange and external web frontend
** 1 Windows OS server license
** 0 Windows OS CALs --> since already done on above "server #1"
ADD-ONS
** 1 Exchange server license
** 100 Exchange server CALs
A few corrections.
First, of you go the core route for SQL, you mist buy a license PER CORE. You listed two licenses and hinted that you thought that'd cover four cores total much like windows licenses cover two processors each. That is *incorrect.* one core license covers one core.
Also keep in mind that core licenses are definitely more expensive than server licenses. So server+CAL may make more sense depending on the workload.
SharePoint 2013 does not offer a core licensing model. You will be buying CALs for that.
First, of you go the core route for SQL, you mist buy a license PER CORE. You listed two licenses and hinted that you thought that'd cover four cores total much like windows licenses cover two processors each. That is *incorrect.* one core license covers one core.
Also keep in mind that core licenses are definitely more expensive than server licenses. So server+CAL may make more sense depending on the workload.
SharePoint 2013 does not offer a core licensing model. You will be buying CALs for that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Not trying to be pedantic, but when it comes to licensing, details matter. The operating system needs a server license. That *is not* a CAL. Historically (and for a few products, still true) there has been such a thing as a server CAL. So the distinction is important.