Solved

2012 R2 vmware support

Posted on 2014-01-24
3
1,076 Views
Last Modified: 2014-01-24
Hello,

I upgraded one of my vsphere environments to 5.0 U3 today to get support for MS windows server 2012 R2. But I can't see the OS in dropdown menu when creating the VM. I do see 2012, but no sign of 2012 R2.  Is this OK?

Thank you
0
Comment
Question by:synackrst
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 39806529
Even with 5.5, and vCenter 5.5 you do not see a Windows Server 2012 R2, it only shows Windows Server 2012 (64 -bit).

Windows Server 2012 R2 is supported as a Guest OS on 5.0 U3, see

HCL here - http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16

Just use the Windows Server 2012 (64 -bit) (template in the wizard)
0
 

Author Comment

by:synackrst
ID: 39806537
Alright. Thanks for clearing that up. I just wanted to be totally sure.
0
 
LVL 120
ID: 39806541
Thanks

It does not even appear yet, in the vSphere Client 5.5 or Web Client 5.5!
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
ESXi 5.5.0, 1623387 - HP Proliant DL380P G8 server 6 63
Cloud Lab Environment for Company 5 103
optimizeing VM 24 93
Restore DC not visible on network 13 23
In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question