Microsoft Windows Server 2012 Essentials OEM by Microsoft. Platform: Windows 2012 Server 3.0 out of 5 stars 20 ratings. Currently unavailable. We don't know when or if this item will be back in stock. Full OEM Version of Windows Server 2012 Essentials Edition 25 User limit and 50 devices – No CALs ( Client Access Licenses) required. Windows Server 2012 Standard Core: VN93G-8PVT3-W2X3H-F3X87-FJMTW: Windows Server 2012 Datacenter Core: 2GMNX-8K7D2-X968C-7P62F-8B2QK: Windows Server 2012 R2 Essentials: KNC87-3J2TX-XB4WP-VCPJV-M4FWM: Windows Server 2012 R2 Foundation: 7JGXN-BW8X3-DTJCK-WG7XB-YWP26: Windows Server 2012 R2 Standard: D2N9P-3P6X9-2R39C-7RTCD-MDVJX: Windows Server. Upgrade information. Active Directory. Active Directory Domain Services (AD DS): Active Directory domains can be upgraded by upgrading the operating system of existing domain controllers or by replacing existing domain controllers with domain controllers that run Windows Server 2012. Full OEM Version of Windows Server 2012 Essentials Edition 25 User limit and 50 devices – No CALs ( Client Access Licenses) required Simplified user management and easy file sharing Includes PC backup and optional connection to Office 365. There is a link to a Server 2012 Standard download but this does not let me install Foundation and the key will not be accepted. Microsoft also scraped these versions from our MS Action Pack downloadcenter.
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.
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.
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.
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.
Sep 23rd, 2014
Never
Not a member of Pastebin yet?Sign Up, it unlocks many cool features!
- 2FND4-FCR66-RK9Q3-F82H3-4GB43 --- 00252-20000-00116-AAOEM --- Dell
- Windows Storage Server 2012 R2 Standard
- 2MNJB-4TKDY-M68W6-DQXTF-BY3YQ --- 00257-00000-00140-AAOEM --- HP
- Windows Server 2012 Foundation
- RTMNG-7K8HQ-3QVVW-W8QKF-Q9H7D --- 00185-00477-08754-AAOEM --- ???
- VXHGK-GRJQH-K7WVN-MTXP3-YBFHM --- 00185-65247-05792-ABOEM --- ??? (MUI locked to zh-CN)
- BDCBV-BQ27P-9PNJJ-BQJ96-KTJ3Y --- 00185-61015-53182-ABOEM --- ??? (MUI locked to zh-CN)
- 8MBNB-YB7W9-YV3VJ-7WMGG-MKH7D --- 00185-00000-00010-AAOEM --- ???
- 96764-R7KXM-CJKJB-BNGCW-CPKX3 --- 00185-06266-38201-AAOEM --- ???
- 2GDTN-RWTYX-TDK7V-4Q6K3-G8XX3 --- 00185-00000-00094-AAOEM --- ???
- Windows Server 2012 Essentials
- MXHGN-GRJQH-K7WVV-MTXP3-YBFHT --- 00186-00000-00000-AAOEM --- ???
- JXHGK-GRJQH-N7WVV-MTXP3-YBFHT --- 00186-08304-72192-ABOEM --- ???
- Windows Server 2012 Standard
- VDNYM-JBKJ7-DC4X9-BT3QR-JHRGY --- 00184-00070-00000-AAOEM --- ???
- BNHD9-KT7MY-4BX83-HTGM4-3C77J --- 00185-48475-45056-AAOEM --- ??? (MUI locked to zh-CN)
- 2G9DG-XKFR6-VG8D3-DN9T9-CDG98 --- 00185-48952-40532-AAOEM --- ??? (MUI locked to zh-CN)
- Windows Server 2012 Datacenter
- B7RRX-RVN4P-PCPBM-89D8Y-X4PQH --- 00184-50100-21572-AAOEM --- ???
- N67Y4-R7KXM-CJKJB-BHGCW-CPKXV --- 00184-50070-47113-AAOEM --- ???
- 2BVGY-TNRWK-6927W-866R9-66J3H --- 00184-50000-00130-AAOEM --- Dell
- Windows Storage Server 2012 Standard
- DXHGK-GRJQH-K7WVV-NTXP3-YBFGG --- 00182-85373-02912-ABOEM --- ???
- N67T9-R7KXM-CJKJB-BHGCW-CPKW6 --- 00182-80070-47113-AAOEM --- ???
- Windows Storage Server 2012 Workgroup
- CDNBD-9X68R-RRFYH-8G28W-82KXC --- 00183-30070-49169-AAOEM --- ???
- QNF7Y-QYYF3-FTQ76-WTWPV-JQG9C --- 00183-30000-05057-AAOEM --- Seagate
- Windows MultiPoint Server 2012 Standard
- KXHGK-GRJQN-K7WVV-MTXP3-YBFGB --- 00182-47717-51936-ABOEM --- ???
- NDQGD-9X68R-RRFYH-8GB8W-82KWG --- 00181-20069-74811-AAOEM --- ???
- Windows MultiPoint Server 2012 Premium
- RTDKG-7K8HQ-3QVVW-W8NKF-Q9H43 --- 00181-82704-22746-AAOEM --- ???
- VNKYM-JBKJ7-DC4X9-BT3QR-JHRF3 --- 00181-80070-00000-AAOEM --- ???
- QXHGN-GRJQH-K7WVV-MTXP3-YBFGD --- 00182-60000-00000-AAOEM --- ??? (MUI locked to zh-CN)