This was to the point of the VM almost being unusable. I also noticed severely degraded performance. The VM responded very slowly to mouse and keyboard input. This is when I discovered the major hurdle I mentioned above. I was then able to get the Windows loaded. I deleted that VM and created a generation 1 VM. Unfortunately I found out this will not work as the VM bugchecked during setup. I started the process by creating a generation 2 VM (virtual machine). Additionally, I am not running the server for any type of production workload. I have a MSDN subscription and thus have a valid license. So in order to do this, and not violate the EULA, a non-OEM license is required. That means it comes pre-installed on hardware and must remain on that hardware. Typically Foundation edition is only sold with an OEM license. Also it will likely violate the EULA (End User License Agreement). 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. I will describe the process I went through to get a Windows Server 2012 R2 Foundation virtual machine running smoothly. I ran into a major hurdle with the integration tools. I figured this would not be a problem as 2012 R2 runs fine as a virtual machine. Part of reproducing the issue involved building out a Windows Server 2012 R2 Foundation virtual machine. My lab is a Windows 10 workstation with the Hyper-V role installed. I recently needed to reproduce a customer issue in my lab environment.
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |