The HP and Microsoft partnership extends Windows Server 2012 features with the release of Windows Server 2012 R2. Combining the HP ProLiant Gen8 features with the advanced virtualization and scalability features of Windows Server 2012 R2 empowers IT users and provides flexible access to corporate resources while protecting corporate information. Windows Server 2012 R2 will continue to have the same licensing model as Windows Server 2012, with two editions available in volume licensing: Standard edition and Datacenter edition. Editions are differentiated by virtualization rights only (two OSEs for Standard, and unlimited OSEs for Datacenter). SQL Server (7) Filter by price. Server Operating Systems Microsoft Windows Server 2012 R2 Remote Desktop. Microsoft Windows Server 2012 Foundation $ 180. Windows Server 2012 R2 will continue to have the same licensing model as Windows Server 2012, with two editions available in volume licensing: Standard edition and Datacenter edition. Editions are differentiated by virtualization rights only (two OSEs for Standard, and unlimited OSEs for Datacenter). The Microsoft Evaluation Center brings you full-featured Microsoft product evaluation software available for download or trial on Microsoft Azure.
Windows Server 2012 is an operating system built by Microsoft and is the successor of Windows Server 2008 R2. Windows Server 2012 is the server-edition of Windows 8 and is available since September 2012. Its minor update (Windows Server 2012 R2) is available since Oktober 2013.
This article shows the differences between the individual Windows Server 2012 editions.
Windows Server 2012 pricing information about can be found at the Thomas-Krenn web shop in the area Microsoft software.
Windows Server 2012 is available in 4 editions:
The editions are suitable for the following application areas:
|Edition||Ideal for...||High level feature-comparision||Licensing model||Memory limits||Pricing|
|Foundation||Cost-efficient allround server||Essential server functionality without virtualization rights||Server (Limited to 15 users)||32 GB RAM||See Microsoft software in the Thomas-Krenn web shop.|
|Essentials||Environments in small companies||Essential server functionality without virtualization rights||Server (Limited to 25 users)||64 GB RAM|
|Standard||Non-virtualized or lightly virtualized environments||All features, with two virtual instances||Processor + CAL*||4 TB RAM|
|Datacenter||Highly-virtualized private cloud environments||All features, with unlimited virtual instances||Processor + CAL*||4 TB RAM|
- (*) CALs are required for each user or device, who directly or indirectly accesses a server. Find more information on this topic at the Client Access Licenses site at microsoft.com.
Minimal System Requirements for Windows Server 2012
The following are the minimal system requirements for Windows Server 2012 R2:
|CPU clock rate||1,4 GHz|
|Disc capacity||32 GB *|
- (*) Servers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.
Edition comparison by physical / virtual instances
Windows Server 2012 instances can either run in a physical operating system environment (POSE) or a virtual operating system environment (VOSE):
|Edition||Running instances in POSE||Running instances in VOSE|
- (*) When a customer is running all allowed virtual instances, the physical instance may only be used to manage and service the virtual instances.
- (**) Essentials can be run in either a physical or virtual operating system environment “1 or 1.”
Edition comparison by server roles
The Windows Server 2012 editions differ in the following server roles:
|AD Certificate Services||X||Automatically Installed/Configured (1)||Partial/Limited (1)|
|AD Domain Services||X||Automatically Installed/Configured (2)||X (3)|
|AD Federation Services||X||X||X|
|AD Lightweight Directory Services||X||X||X|
|AD Rights Management Services (4)||X (4)||X (4)||X (4)|
|DNS Server||X||Automatically Installed/Configured||X|
|File Services||X||Automatically Installed/Configured (5)||Partial/Limited (5)|
|Network Policy & Access Services||X||Automatically Installed/Configured||Partial/Limited|
|Print & Document Services||X||X||X|
|Remote Access||X||Automatically Installed/Configured (6)||limitiert (6)|
|Remote Desktop Services (7)||X (7)||- (7)(8)||Partial/Limited (7)(9)|
|Web Server (IIS)||X||Automatically Installed/Configured||X|
|Windows Deploy Services||X||X||X|
|Windows Server Update Services||X||-||-|
- (1) Limited to creating Certificate Authorities – there are no other Active Directory Certificate Services features (Network Device Enrollment Services, Online Responder Service). See ADCS role documentation on TechNet for more information.
- (2) Must be root of ADDS forest and domain and have all FSMO roles.
- (3) If ADDS role is installed, must be root of forest and domain and have all FSMO roles.
- (4) Requires an incremental AD RMS CAL for access.
- (5) The data de-duplication feature is not available.
- (6) Limited to 50 RRAS connections, 10 IAS connections; DirectAccess and VPN are supported.
- (7) Requires an incremental RDS CAL for access, with the exception of using the Remote Web Access feature of the Essentials edition.
- (8) Only the RD Gateway role service is installed and configured, other RDS role services including RD Session Host are not supported.
- (9) Limited to 50 Remote Desktop Services connections.
Edition comparison by feature
Windows Server 2012 R2 Purchase
|Feature||Datacenter / Standard||Essentials||Foundation|
|User Interfaces and Infrastructure (Server Core)||X||-||-|
|Windows Power Shell||X||X||X|
- ↑Windows Server 2012 Editionen - Die vier Editionen von Windows Server 2012 (www.microsoft.com)
- ↑Memory Limits for Windows and Windows Server Releases - Physical Memory Limits: Windows Server 2012 (msdn.microsoft.com)
- ↑System Requirements and Installation Information for Windows Server 2012 R2 (technet.microsoft.com, 24.06.2013)
- ↑ 4.04.1Windows Server 2012 Licensing Data Sheet (EN) (download.microsoft.com)
- Windows Server 2012 Products and Edition Comparison (download.microsoft.com)
- Windows Server 2012 Pricing Information (www.thomas-krenn.com)
I recently needed to reproduce a customer issue in my lab environment. My lab is a Windows 10 workstation with the Hyper-V role installed. Part of reproducing the issue involved building out a Windows Server 2012 R2 Foundation virtual machine. I figured this would not be a problem as 2012 R2 runs fine as a virtual machine. This was not the case though. I ran into a major hurdle with the integration tools. I will describe the process I went through to get a Windows Server 2012 R2 Foundation virtual machine running smoothly.
Windows Server 2012 R2 Price
Now before anyone goes out and tries the below procedure for a production system, please understand that running Foundation edition as a virtual machine is not supported by Microsoft. Also it will likely violate the EULA (End User License Agreement). Typically Foundation edition is only sold with an OEM license. That means it comes pre-installed on hardware and must remain on that hardware. So in order to do this, and not violate the EULA, a non-OEM license is required. I have a MSDN subscription and thus have a valid license. Additionally, I am not running the server for any type of production workload.
Windows Server 2012 R2 Foundation Price Philippines
I started the process by creating a generation 2 VM (virtual machine). Unfortunately I found out this will not work as the VM bugchecked during setup. I deleted that VM and created a generation 1 VM. I was then able to get the Windows loaded. This is when I discovered the major hurdle I mentioned above. The VM responded very slowly to mouse and keyboard input. I also noticed severely degraded performance. This was to the point of the VM almost being unusable. The VM behaved as if none of the integration services drivers were installed. Unfortunately Windows 10/2016 do not have the option to insert the integration disk. I was able to get the vmguest.iso from a 2012 R2 hyper-v host. However when I tried to run the setup I was informed that the latest integration services were already installed.
At this point I realized this was not going to be easy, but I enjoy a challenge. I browsed the vmguest.iso inside the Foundation VM. I extracted the following file: D:supportamd64Windows6.2-HyperVIntegrationServices-x64.cab. I then went into device manager. I noticed quite a few, a dozen or so, unknown devices.
Windows Server 2012 R2 Standard
I then tried to manually load the drivers from the extracted cab file. While the driver was found, it was not signed. I figured no sweat, just disable driver signing requirement in the BCD (Boot Configuration Data). Yet another roadblock. It is no longer possible to permanently disable driver signature enforcement. I was able to boot into driver signature enforcement disabled mode. I then manually loaded drivers for all the Unknown devices. This corrected the input and performance issues, at least for that boot. Booting into normal mode caused all the issues to return.
Getting the drivers to load each time Windows booted was the final step in getting the virtual machine to run properly. I looked into the bcdedit command line options and was not able to find an option to boot to driver signing disabled mode. What I ended up doing was to add a dummy entry to the boot list and set the timeout to 30 seconds with the following commands.
Presently, on each boot I press F8 to get the boot options. I then select Disable Driver Signature Enforcement. Now the VM runs with all guest integration services.
If you have been able to find a better way to do this I would like to hear about it in the comments below.