The question came up today about using Windows Server Essentials as a RADIUS server. Part of the consideration involves the arbitrary restrictions placed on the OS. Microsoft differentiates the server products with what are affectionately know as “Locks and Limits”.
Most folks in IT are aware of OS limits like the number of users in Windows Server or not being able to RDP into Windows 7 Home Edition. But there are other less-obvious limits like RAM or IAS, RRAS & SMB connection limits.
Fortunately there are two handy spreadsheets that detail the Limits, Roles & Features that are (or are not) available in Windows Server 2012 & R2 Editions.
Windows Server 2012 R2 Locks & Limits
File: Windows Server 2012 R2 Products and Editions Comparison.pdf (222 KB)
- Windows Server 2012 R2 Datacenter
- Windows Server 2012 R2 Standard
- Windows Server 2012 R2 Essentials
- Windows Server 2012 R2 Foundation
- Microsoft Hyper-V Server 2012 R2
- Windows Storage Server 2012 R2 Standard
- Windows Storage Server 2012 R2 Workgroup
Windows Server 2012 Locks & Limits
File: Windows Server 2012 Products and Editions Comparison.pdf (226 KB)
- Windows Server 2012 Datacenter
- Windows Server 2012 Standard
- Windows Server 2012 Essentials
- Windows Server 2012 Foundation
- Microsoft Hyper-V Server 2012
- Windows Storage Server 2012 Standard
- Windows Storage Server 2012 Workgroup
- Windows MultiPoint Server 2012 Premium
- Windows MultiPoint Server 2012 Standard
Currently, there is no word yet on Windows Server 2016 since it’s still in Technical Preview at this time. However, once the licensing folks figure out how to squeeze every penny out of Server 2016 (I’m very interested to see what they do with Nano Edition) there should be an updated spreadsheet released.
Title: Group Policy Settings Reference for Windows and Windows Server
Version: July 2015 (Updated for Server 2016 TP4)
- TP4 Policy Settings Spreadsheet.xlsx (654 KB)
- Windows 10 ADMX spreadsheet.xlsx (654 KB)
- Windows 8.1 Update and Windows Server 2012 R2 Update 1.xlsx (788 KB)
- WindowsServer2003SP2GroupPolicySettings.xls (3.9 MB)
- WindowsServer2008andWindowsVistaSP1GroupPolicySettings.xlsx (512 KB)
- WindowsServer2008R2andWindows7GroupPolicySettings.xlsx (612 KB)
- WindowsServer2012andWindows8GroupPolicySettings.xlsx (690 KB)
- WindowsServer2012R2andWindows8.1GroupPolicySettings.xlsx (628 KB)
- WindowsServer2012R2UpdateGroupPolicySettings.xlsx (634 KB)
- WindowsVistaGroupPolicySettings.xls (1.9 MB)
These spreadsheets list the policy settings for computer and user configurations that are included in the Administrative template files delivered with the Windows operating systems specified. You can configure these policy settings when you edit Group Policy Objects.
While kicking the tires on a Windows Server 2016 TP3 virtual machine in Microsoft Azure, I decided to try and install Skype. (Not recommended – I know).
The Skype 7.14 application installed just fine, but when I tried to login to Skype with my Windows Live ID I received the following error message:
“Your browser is currently set to block cookies. Your browser must allow cookies before you can use a Microsoft account.”
At first I thought the error message was related to Microsoft Edge, since you’re not allowed to run Edge with the default (500) Administrator account. Logging in with a different account didn’t resolve the error either.
Enabled Cookies in IE 11, still no joy.
I added http://skype.com and https://skype.com to trusted sites in IE 11, then I could login to Skype.
Internet Explorer | Internet Options | Security | Trusted Sites | Sites
It’s a pretty simple fix in hindsight, but one that isn’t blatantly obvious at first.