OEM Windows Server 2012 Standard Retail , 32 64 Bit Windows 2012 R2 Standard Retail

Microsoft Windows OEM Software Windows Server 2012 standard R2 32 Bit / 64 Bit

Requirement:

Minimum system requirements for Windows Server 2012

Windows Server 2012 runs only on x64 processors. Unlike its predecessor, Windows Server 2012 does not support Itanium.
Upgrades from Windows Server 2008 and Windows Server 2008 R2 are supported, although upgrades from prior releases are not.

Windows Server 2012 R2

Windows Server 2012 R2 was released on October 18, 2013.It was unveiled on June 3, 2013 at TechEd North America. According to Windows Server 2012 R2 datasheet published on May 31, 2013, there are four editions of this operating system: Foundation, Essentials, Standard and Datacenter. As with Windows Server 2012, the Datacenter and Standard editions are feature identical, varying only based on licensing (particularly licensing of virtual instances). The Essentials edition has the same features as the Datacenter and Standard products, with some restrictions.
A further update, formally designated Windows Server 2012 R2 Update, was released in April 2014, a cumulative set of security updates, critical updates and updates.
Windows Server 2012 R2 is succeeded by Windows Server 2016.

Changes from Windows Server 2012

Microsoft has confirmed the following changes introduced by Windows Server 2012 R2:
Automated Tiering: Storage Spaces stores most frequently accessed files on fastest physical media
Deduplication for VHD: Reduces the storage space for VHD files with largely similar contents by storing the similar contents only once
Windows PowerShell v4, which now includes a Desired State Configuration (DSC) feature
Integrated Office 365 support (Essentials edition)
User interface changes from Windows 8.1, including visible Start button.
UEFI-based virtual machines
Upgrades from driver emulators to synthetic hardware drivers to minimize legacy support
Faster VM deployment (approximately half the time)
Internet Information Services 8.5: Support for logging to Event Tracing for Windows and the ability to log any request/response headers. To improve scalability, if IIS is configured with 100 or more web sites, by default it will not automatically start any of them. Alongside this, a new "Idle Worker Process Page-Out" configuration option has been added to application pools to instruct Windows to page-out the process if it has been idle for the idle time-out period (by default, 20 minutes).
Server Message Block: Performance and event logging quality improvements, support for Hyper-V Live Migration over SMB, bandwidth prioritization management, and the ability to remove SMB 1.0 support.
Windows Deployment Services: Support for managing WDS via PowerShell.
Windows Defender is available in a Server Core installation, and is installed and enabled by default.
IP Address Management (IPAM): Extended to support role-based access control, allowing for fine-grained control over which users can view or change configurations for DHCP reservations, scopes, IP address blocks, DNS resource records, etc. Additionally, IPAM can integrate with System Center Virtual Machine Manager 2012 R2 to have coordinated IP policy across both physical and virtual environments. The IPAM database can be stored in a SQL Server instance instead of Windows Internal Database.
Group Policy has a new "Policy Cache" setting which allows domain-joined machines to store a copy of the group policy settings on the client machine and, depending on the speed of access to the domain controller, use those at startup time instead of waiting for the policy settings to download. This can improve startup times on machines that are disconnected from the company network. New Group Policy settings have been added to cover new features in Windows 8.1 and Internet Explorer 11, such as enabling/disabling SPDY/3 support, configuring start screen layouts, and detecting phone numbers in web pages.
TLS support is extended to support RFC 5077, "Transport Layer Security (TLS) Session Resumption without Server-Side State", which improves performance of long-running TLS-secured connections that need to reconnect due to session expiration.
Hyper-V role and Hyper-V management console are added to the Essentials edition.

Product compare:

Notes:
Applies to Windows Server 2008 R2 and 2012 Datacenter and Windows Server 2012 Standard only. Other editions support less.
Each virtualized partition, including the host itself, can use up to 64 processors.
Each license of Windows Server 2012 Standard or Datacenter allows up to two processor chips. Each license of Windows Server 2012 Standard allows up to two virtual instances of Windows Server 2012 Standard on that physical server. If more virtual instances of Windows Server 2012 Standard are needed, each additional license of Windows Server 2012 allows up to two more virtual instances of Windows Server 2012 Standard, even though the physical server itself may have sufficient licenses for its processor chip count. Because Windows Server 2012 Datacenter has no limit on the number of virtual instances per licensed server, only enough licenses for the physical server are needed for any number of virtual instances of Windows Server 2012 Datacenter. If the number of processor chips or virtual instances is an odd number, the number of licenses required is the same as the next even number. For example, a single-processor-chip server would still require 1 license, the same as if the server were two-processor-chip and a five-processor-chip server would require 3 licenses, the same as if the server were six-processor-chip, and if 15 virtual instances of Windows Server 2012 Standard are needed on one server, 8 licenses of Windows Server 2012, which can cover up to 16 virtual instances, are needed (assuming, in this example, that the processor chip count does not exceed 16).
For the Standard and Datacenter editions, each user or device accessing the software must have a client access license (CAL) assigned (either per-user or per-device), so there may be no more simultaneous users than the number of client-access licenses, except up to 2 simultaneous users purely to administer the server software, or for running virtualization or web workloads. Remote Desktop Services requires an additional CAL separate from the aforementioned CAL.
If the number of physical processors in a particular server is under 64, the limit is determined by the quantity of licenses assigned to that server. In that case, the number of physical processors cannot exceed twice the number of licenses assigned to the server.