Resolving the error message: Virtual Machine cannot be transferred. Volume C: on server is unaivalable for placement

Share this:

If you are running System Center 2012 SP1 which is my case and you try to create your Virtual Machine you may have this issue when trying to do the process manually.

image

Solving the issue…

There are a couple of solution and it all boils down to your existent scenario. If you are using a Hyper-V cluster you just need to enable the option Make this virtual machine highly available and that will tell SCVMM to find a storage location in a CSV.

image

If you are not using a cluster you need to check on the server properties which drives you have available for placement, in the figure below the C: drive was not selected which means that is not being analyzed as part of the select host process.

image

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at ITPROCentral.com, MSExchange.org, Techgenix.com and Anderson Patricio.org (Portuguese).

Related Post

Managing Hyper-V Server remotely through PowerShel... Working with PowerShell can be very common for daily tasks and Hyper-V Server management. However, as there is more than one server to be managed, som...
Installing and running Hyper-V 2012 R2 from a USB ... Hyper-V 2012 R2 Server is the free version of Hyper-V and it offers all the components and features that are available in Windows Server 2012 R2 with ...
Integration between Hyper-V Network Virtualization... One of features on Windows Server 2012 R2 that was improved since the last version is network virtualization. Virtual networks are created by using Hy...
Hyper-V Best Practices Analyzer Sometimes when you deploy an Hyper-V Server you don’t know if you miss any configuration or if you are following the best practices regarding security...