Capability Profiles in SCVMM 2012

Encounter the follow issues after importing a Hyper-V image created to be used in my SCVMM / APP Center environment: Two Errors:

The virtual machine configuration cannot target a host due to placement errors. (StatusCode: 22039–PlacementErrorsPresentInVmConfig)

The virtual machine workload test01 specifies settings that are not allowed by any capability profile supported by the cloud. A list of validation errors specific to each matching capability profile can be accessed by validating the hardware profile or template before it is rated (StatusCode: 23751–NoSupportedCapabilityProfile)


While this issue does not directly point out what the problem. It’s directly related to “Capability Profile” of the Virtual Machine Guest being used. My guest was not configured at the time of this error.

To correct this I did the following:

  1. Opened SCVMM at administrator
  2. Under Library, selected VM Templates
  3. Selected the Template which had the above errors
  4. Entered the properties for the Template
  5. Entered the Hardware Configuration Tab
  6. Under Compatibility, selected Hyper-V (the built-in fabric capability profile…)
  7. Clicked OK

At this point I went back to my test user account and was able to deploy without error.


And thanks to the folks over at TechNet for this: http://social.technet.microsoft.com/wiki/contents/articles/4149.capability-profiles-in-scvmm-2012.aspx

Hyper-V VM Creation Fails – Product Key

Yes! Another error, and another thing to learn.

I ran in to an issue while importing a new template from an existing image. Error message was: Virtual Machine Manager was unable to find a value for the required Sysprep parameter Product Key.

It seems that the new machine is looking for a product key. The template I’m using has no product key as its activated from our internal KMS server. So after searching and not finding much on social.technet posts I decided to attempt to a KMS Client Setup Key; After all its looking for a key. These keys are useful for taking a system activated with a MAC or retail and moving them to be activated via a KMS.

I did this by doing the following:

1. Opening the SCVMM Console (as Administrator)
2. On the Library Tab, Select VM Templates and the Template you are working with
3. On the OS Configuration Tab, Select Product Key and enter in the Windows 8 Enterprise KMS Setup Key
4. I hope I do not have to tell you this, but click OK

Back at the App Center Page and I am now able to Create my new virtual machine from this template.

This posting is provided “AS IS ” with no warranties, and confers no rights.

Store virtual machine to library – Error

I attempted to store a Hyper-V image I was working with to the library for others to later use when I encountered the following error message.

Cannot store virtual machine <instance name> in cloud <cloud name> because this cloud does not have a stored VM path configured. (StatusCode: 22805–CannotStoreVmInCloudLibraryServerNotAvailable)

I then discovered that I needed to a path for the stored VMs. You can do this by:
1. Open the VMM Console as an administrator
2. Select the Cloud and open the Properties for the cloud
3. Go to the Library tab of the Properties page
4. Ensure there is a value for “Stored VM path”  listed at the top of the page

Retuning back and repeating my previous steps were not successful.


This posting is provided “AS IS ” with no warranties, and confers no rights.

Hyper-V Server 2012 hits Release to Manufacturing (RTM)

Hey there; you want to build some servers? You do? That’s good, real good.

Microsoft also pushed Hyper-V Server 2012 to Release to Manufacturing (RTM) status. It’s now yours for the download and installation pleasure. All you need to do is get it from here and you are on your way with virtualization using Microsoft latest technology.

And for the rest of you that might not know, let the filler begin:

What is Microsoft Hyper-V Server 2010

Microsoft Hyper-V Server 2012 is a hypervisor-based server virtualization product that enables you to consolidate workloads, helping organizations improve server utilization and reduce costs.

Hyper-V Server is a dedicated stand-alone product that contains the hypervisor, Windows Server driver model, virtualization capabilities, and supporting components such as failover clustering, but does not contain the robust set of features and roles as the Windows Server operating system. As a result Hyper-V Server produces a small footprint and and requires minimal overhead. Organizations consolidating servers where no new Windows Server licenses are required or where the servers being consolidated are running an alternative OS may want to consider Hyper-V Server.

In contrast, Windows Server 2012 is recommended for organizations that need flexible and cost effective virtualization rights. Virtualization rights in Windows Server 2012 are based on the specific edition purchased, with Windows Server 2012 Datacenter edition providing unlimited virtual instances.

One of the most common uses for Hyper-V Server is in Virtual Desktop Infrastructure (VDI) environments. VDI allows a Windows client operating system to run on server-based virtual machines in the datacenter, which the user can access from a PC, thin client, or other client device. A full client environment is virtualized within a server-based hypervisor, centralizing users’ desktops.

By deploying VDI with Microsoft Hyper-V Server 2012, users will have seamless access to a rich, full fidelity Windows environment running in the data center, from any device. Hyper-V Server also gives IT professionals a cost effective VDI solution with simplified administration, flexible storage options, and dynamic allocation of resources.

Key Features
Microsoft Hyper-V Server 2012 provides enhanced capabilities and features that help consolidate servers effectively while making maximum use of resources.

filler source: http://www.microsoft.com/en-us/server-cloud/hyper-v-server/

Installing the Failover Clustering Feature (FAIL)

I have been looking into using Hyper-V Server and its features.  One of those features are the Clustering feature for migrations and fail-over.    After many articles telling me to do this, try that, this may work , and here is a step by step filled with many links to other pages, and sites.  I now find out the following:

Applies To: Windows Server 2008 R2

Before you can create a failover cluster, you must install the Failover Clustering feature on all servers that you want to include in the cluster. This section provides instructions for installing this feature.

Note that the Failover Clustering feature is included in server products such as Windows Server 2008 R2 Enterprise and Windows Server 2008 R2 Datacenter. The Failover Clustering feature is not included in Windows Server 2008 R2 Standard or Windows Web Server 2008 R2.

Why doesn’t anyone ever put that in their steps.   Well reader, here it is and I hope you, unlike me find this out before setting up and starting your process.

Oy vey


Secured By miniOrange