Switching from Per Server to Per Seat Licensing

[owensdj]

This network has two Windows servers, both Active Directory DCs, one a 2003 and the other a Server 2008 machine. We're going to add new client machines to the domain that will require more CALs, and also replace the 2003 server with a new Server 2008 machine.

We've been in Per Server licensing mode, but it looks like we'd be better off switching to Per Seat mode because all of the users access both servers. Can we switch to Per Seat mode with a 2003-2008 mixed environment? If so, will the number of CALs we have for the 2008 machine be the number of Per Seat licenses we have available?

If we use User CALs rather than Device CALs, how does the licensing work if we have one user named "receptionist" logged into two computers at the same time? I assume that counts as 2 CALs? Also, do we count the number of users logged in at the same time or the total number of users in the domain user list?

 

[drebo]

Per Seat licensing is a bad idea. It is an administrative nightmare.

You only need one CAL per user performing authentication against your active directory, not one CAL per user per server.

Stick with Per Server and just make sure you have one CAL per user (not per username, per user).

Also, a tip: unless you're using Small Business Server, Windows licensing is unenforced. You should still be compliant, but things won't stop working if you're not compliant.

 

[owensdj]

drebo, thanks for the reply. Since we have two servers, wouldn't we be spending less on CALs if we're in Per Seat mode? All of the users access a file share on both servers. For example, if we stay in Per Server mode and buy a new Server 2008 machine, we're going to have to buy 20 CALs for it. If we switch to Per User mode we won't have to buy any CALs for the new server, just the base Server 2008 OS.

 

[theevilsharpie]

I can only think of a handful of scenarios where per server licensing makes sense.

 

[imagoon]

Per server tends to be the worst one. 1 Cal per connection = crap. Rarely is cheaper or worth it. One user with 53 files open = "53 cals" in per server mode. Per server as I recall is typically used in web servers only.

Per user or per device tends to be the best depending on if you have more users than devices or not. Per user = any number of connections for that user. Per device is useful when you run say 3 shifts and they share computers. Call centers are like this.

If it means anything... Per server is the only one that MS will let you convert to per user / per device.

Also to answer your question. In per user, if MS were to audit you, they look at how many users need access. If CALs > than that you are ok. Having 15 users logged in as BobUser = 15 user cals. Now if those 15 users always use the same reception computer you could use per device and only need one. However in many environments, per user is better unless you share a lot of devices.

 

[drebo]

You guys have your terminology backwards. Just FYI.

Per Server mode has the CALs applied per active directory domain. Per Seat mode has the CALs applied at the workstation level, requiring revocation and reassignment.

 

[imagoon]

Client Access Licensing Modes

After you have selected a license type—Windows Device CAL or Windows User CAL, you have the option to use the server software in two different modes: Per User/Per Device mode or Per Server mode. Both modes are available for either type of license.
Per User or Per Device Mode

Per User/Per Device mode is defined as follows:

*

A separate Windows CAL (of either type) is required for each user or device that accesses or uses the server software on any of your servers.
*

The number of Windows CALs required equals the number of users or devices accessing the server software.
*

If you choose this licensing mode, your choice is permanent. You can, however, reassign a Windows CAL from one device to another device or from one user to another user, provided the reassignment is made either (a) permanently away from the one device or user or (b) temporarily to accommodate the use of the Windows CAL either by a loaner device, while a permanent device is out of service, or by a temporary worker, while a regular employee is absent.

Per User/Per Device mode tends to be the most economical designation for Windows CALs in distributed computing environments where multiple servers within an organization provide services across most devices or users.

Note that Per User/Per Device mode replaces Per Seat mode, used in previous licensing models.



Per Server Mode

Per Server mode is defined as follows:

*

A separate Windows CAL (of either type) is required for each user or device that accesses or uses the server software on any of your servers. (This does not change the per server connection allowance of one CAL per one connection.)
*

The number of Windows CALs required equals the maximum number of users or devices that may simultaneously access or use the server software running on a particular server. The Windows CALs you acquire are designated for use exclusively with a particular server.
*

If you choose this licensing mode, you have a one-time right to switch to the other licensing mode—Per User/Per Device mode. Your Windows CALs (of either type) would then be used in Per User/Per Device mode instead.

Per Server mode tends to be the most economical designation for Windows CALs in computing environments where a small number of servers have limited access requirements.

------------

From the above.... Per seat is for the entire domain and all servers per device or user. Per server is the "web server" style where you need a CAL per connection. So a user with 15 open files = 15 active connections and thus 15 CALs.

http://www.microsoft.com/windowsserver2008/en/us/client-licensing.aspx

You never want per server in a SMB file serving environment.

 

[owensdj]

imagoon, will I be able to switch from Per Server to Per User mode if I have both a 2008 and a 2003 server? They're both AD DCs and both share files with all of the users.

 

[imagoon]

imagoon, will I be able to switch from Per Server to Per User mode if I have both a 2008 and a 2003 server? They're both AD DCs and both share files with all of the users.

2008 CALs cover all previous versions. So they will cover 2003.

 

[owensdj]

When you're in Per User licensing, does Microsoft count the total number of user accounts in the domain or the total number of users logged in at a time? For example, you have 25 users who use 15 computers. Some users work different days. There will be a max of 15 logged in. Does that require 25 or 15 User CALs?

 

[theevilsharpie]

25

 

[imagoon]

Per user: 25
Per device: 15

Personally for that ratio... 25:15 I would stick to user licenses unless you expect it to increase to about 2-3x the devices (ie shift workers). 45:15 I would use per device. Cals are dirt cheap though I mean 10 you are only looking at the $275 range or so.

EDIT:

Also ask hiring / your boss or what ever what your growth expectations are. I typically buy at least a few extra cals because the employee # tends to drift and I hate trying to buy 5 packs since the 10 and 25's are cheaper.

 

[owensdj]

One final question. How do I actually switch the Server 2003 and Server 2008 machines from Per Server to Per User licensing mode? The License Logging service is turned off(by default) in the Server 2003 machine, and I don't see anything about licensing in Server 2008. Do I just keep the User CAL documentation and say we're officially now in Per User licensing mode?

 

[imagoon]

Do I just keep the User CAL documentation and say we're officially now in Per User licensing mode?

Ding.

Cals are not enforced except on the SBS.