Cannot connect to Windows Server 2012 Core using HYPER-V Manager

All replies

• 

  

  0

  Sign in to vote

  Windows 7 will not be able to manage Windows Server 2012 Hyper-V.  Management is very dependent upon like versions, and Windows 7 would manager Windows Server 2008.  There was also an issue with the early release of Windows 10.  Make sure you are running at least build 10586.

  Your first sentence says you have a 2012 system.  You say you are trying to move a VM to 'another ... 2012 R2 host'.  Are they both the same version or are they different?  How are you trying to move the VM?

  ---

  . : | : . : | : . tim

  Sunday, April 24, 2016 11:21 PM
• 

  

  0

  Sign in to vote

  Hi Dimitri,

  Which account are you using on Windows 10?

  Have you enabled remote management?

  Here is a guide which you could refer to:

  https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/remote_host_management

  >>I am trying to move a VM to another Windows Server 2012 R2 host.

  You could run export-vm to export the VM and import it on the 2012 R2 host.

  Here is the reference for the command:

  https://technet.microsoft.com/en-us/library/hh848491(v=wps.630).aspx

  Best Regards,

  Leo

  ---

  Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

  Monday, April 25, 2016 7:04 AM
• 

  

  0

  Sign in to vote

  Hi Tim, I'm running windows 10 10586.63. I was hoping to use the move wizard in HYPER-V manager.

  Monday, April 25, 2016 7:08 AM
• 

  

  0

  Sign in to vote

  Hi Leo,

  I am using my user acount that is also a domain admin. I have tried logging on to the HYPER-V Host using Domain\Administrator and also by logging in as Domain\Administrator on my local PC. When logging into HYPER-V Host either through console or prohvm, I login as Domain\Administrator.

  I have tried all the steps in the guide you sent.

  Also export-vm is an unrecognised cmdlet when run from powershell. This doesn't seem normal. 

  Monday, April 25, 2016 10:47 AM
• 

  

  0

  Sign in to vote

  Hi Dimitri,

  >>Also export-vm is an unrecognised cmdlet when run from powershell. This doesn't seem normal

  The command applies Server 2012 and R2, it also runs on my Hyper-V host.

  Have you imported Hyper-V module? If not, run Import-Module Hyper-V.

  Best Regards,

  Leo

  ---

  Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

  Tuesday, April 26, 2016 7:53 AM
• 

  

  0

  Sign in to vote

  Hi Leo,

  I have run 'Import-Module Hyper-V' and I get the following error (powershell v1.0):

  "The specified module 'Hyper-V' was not loaded because no valid module file was found"

   Get-Command –Module Hyper-V returns nothing. Get-WindowsFeature displays Hyper-V as enabled.

  I also check to see that RSAT-Hyper-V-Tools are enabled, to ensure that powershell modules are installed, but Get-WindowFeature doesn't list this as an option. Obviously Add-WindowsFeature RSAT-Hyper-V-Tools –IncludeAllSubFeature fails too.

  I'm guessing that the PowerShell modules are not enabled and I need to add the feature? 

  Tuesday, April 26, 2016 8:22 AM
• 

  

  0

  Sign in to vote

  From your explanation above, I am getting confused about which machine you are using for which function.  Get-WindowsFeature is a cmdlet available on Windows Server but not on Windows 10.  You are talking about RSAT Hyper-V tools, which would appear to be installed on your Windows 10 system.

  In your initial post, you state you have a VM on a Windows Server 2012 system. You also state that you want to move the VM to a Windows Server 2012 R2 host. Are these versions correct?

  Which system were you on when you tried to issue the Import-Module Hyper-V cmdlet?

  Have you tried using the GUI on the 2012 R2 installation to move the VM from the 2012 system?

  ---

  . : | : . : | : . tim

  Tuesday, April 26, 2016 1:14 PM
• 

  

  0

  Sign in to vote

  Hi Tim,
  
  To clarify. I am trying to connect from a windows 10 machine (client) to a windows server 2012 core hyper-v host (server), ideally using Hyper-V Manager.
  
  Having failed that with error "An error occured while trying to connect to <computername>. Check that the VM Management Service is running and that you are authorized to connect to the server". I wanted to try export-vm from the Windows Server 2012 Core powershell, which also didn't work.
  
  I was running Get-WindowsFeature on Windows Server 2012 Core, under the assumption that I could install the RSAT feature and associated powershell commands eg export-vm on the Hyper-V host. I was proven wrong.
  
  Yes, I am trying to move a VM from Windows Server 2012 Core to Windows Server 2012 R2 Core.
  
  When I run Get-VM from Windows Server 2012 R2 Core to my Windows Server 2012 Core computer I get message "hyper-v role is not installed on the destination host". Very odd seen as its hosting 3 VMs and Get-WindowsFeature shows it as installed.
  
  
  
  
  
  

  • Edited by Dimitri Shukuroglou Tuesday, April 26, 2016 2:00 PM

  Tuesday, April 26, 2016 1:52 PM
• 

  

  1

  Sign in to vote

  you have some work to do on the 2012 box before you can migrate to the 2012 R2 box

  https://technet.microsoft.com/en-us/library/dn486799.aspx?f=255&MSPPError=-2147217396

  - contains that guides for migrating virtual machines between 2012 and 2012 R2

  edit - I can't post links until my account is verified apparently....

  • Edited by Andy Nuttall Tuesday, April 26, 2016 2:45 PM
  • Proposed as answer by Andy Nuttall Wednesday, May 4, 2016 12:45 PM
  • Marked as answer by Dimitri Shukuroglou Wednesday, May 4, 2016 12:48 PM

  Tuesday, April 26, 2016 2:44 PM