Hyper V Manager

Hi guys i wanted to ask whats the latest version of hyper v management for people running windows 7 because from the microsoft site the latest is v6.1 , but i know some one who is running v6.3 but his running windows 8.1?

Hi Vince-lee,
In addition , please refer to following article regarding hyper-v host and the corresponding "client" OS:
https://technet.microsoft.com/en-us/library/dn632582.aspx
Best Regards,
Elton Ji
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 Subscriber Support, contact [email protected] .

Similar Messages

Connect is not working on Hyper-V Manager on Windows 8.1 ( vmconnect does not work )

Hi all,
I have been running Windows 8.1 and in Hyper-V Manager, i can see 2 VM ( 1 Linux-Ubuntu , 1 Win 7 ) for couple of months.
Few days ago as usual i wanted to connect one of them while they were running but it did not work. I tried actions below already:
- Checked the event logs and they were saying vmconnect is crashing
Faulting application name: VmConnect.exe, version: 6.3.9600.16384, time stamp: 0x5215cae5
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0x6c0
Faulting application start time: 0x01d02e59f75297d7
Faulting application path: C:\WINDOWS\system32\VmConnect.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 351cf3fd-9a4d-11e4-beaf-7446a0bad879
Faulting package full name:
Faulting package-relative application ID:
=================================
Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
   at Microsoft.Virtualization.Client.Interop.IMsRdpClientNonScriptable3.set_NegotiateSecurityLayer(Boolean)
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.SetSecureModeOn()
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.CreateRdpClient(Boolean)
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)
   at Microsoft.Virtualization.Client.InteractiveSession.InteractiveSessionForm..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)
   at Microsoft.Virtualization.Client.InteractiveSession.VmisApplicationContext.TryParseCommandLine(System.String[])
   at Microsoft.Virtualization.Client.InteractiveSession.Program.Main(System.String[])
=================================
- Stop antivirus Avira, remove Hyper-V, restart add Hyper-V again, restart
- reboot, shutdown computer
- add new VM, delete existing one
-add/delete/modify virtual swtich and add/delete/modify virtual switch accordingly the connected VM
- restart Hyper-V Management services from services.msc
I dont know what is going on... When i open Hyper-V Manager i can start/stop VMs and i can see from preview that they are running.

Hi all,
A
After few months, problem occurred again and i could not install the windows from the scratch over and over again.
I started searching problem online and eventually i found the FIX.
Looks like Registry Entries are getting screwed up somehow.
My "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProvider" was looking exactly as below:
", schannel.dll"
And i made it as below:
"msapsspc.dll,
schannel.dll, digest.dll, msnsspc.dll, credssp.dll"
The solution for the other person in the link ( cannot share link since site does not allow me to ) as a source was only missing "credssp.dll" whereas i was missing everything except "schannel.dll". Strange...
============================
Adding credssp.dll to the list of SecurityProviders in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
fixed it for me.
My full registry entry now reads "msapsspc.dll,
schannel.dll, digest.dll, msnsspc.dll, credssp.dll"
============================

Default credentials not being saved in Hyper-V Manager for a single VM

Greetings,
I have a Server 2008 R2 SP1 Standard Hyper-V box running about 8 virtual machines on it. The machine is joined to a 2008 domain.
Recently, I moved the .VHD file for a single machine from one folder to another folder. After doing so, when I connect to ONLY that specific machine via Hyper-V manager, I receive the error: "Your credentials did not work. Your system administrator
does not allow the use of default credentials to log on to the remote computer XXXXXX because its identity is not fully verified. Please enter new credentials."
I have the "Use default credentials automatically (no prompt)" option checked in the Hyper-V settings, and I have tried checking and unchecking this box and saving multiple times. I have also deleted the saved credentials and the system reports no
saved credentials.
I have attempted to change settings in the group policy (gpedit.msc) regarding enabling the Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow Delegating Saved Credentials with
NTLM-only Server Authenticaton setting, something I found in older blog posts here in the Hyper-V forum and on other websites, and it has not made any difference.
At this point, I can only assume this must be some sort of bug because I cannot identify any other possible solution for getting rid of this annoying Windows Security pop-up box. There are no entries in the Windows event log that indicate anything
odd. When I enter the correct username/password, I can still access the VM, but the credentials are never remembered, and ONLY for this single VM.
Does anybody have any knowledge of how to fix this issue? I can't believe that just moving a VHD caused all these problems.
Thanks!

Ah, finally found a solution! I cannot explain why this suddenly got changed other than to assume it must have had something to do with a recent Windows Update or me trying to install Remote Desktop Services and Network Policy and Access Services.
I roughly followed the directions from
KB954357 or this
older post on the Hyper-V forum.
FIX:
1) Run gpedit.msc on the Hyper-V host that exhibits the problem.
2) Enable the policy setting Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow Delegating Default Credentials with NTLM-only Server Authentication. Click the Show... button
next to "Add Servers to the list", and add the value "Microsoft Virtual Console Service/*" without the double quotes. Click OK. Click OK again to exit the dialog box.
3) Run a command prompt and execute gpupdate /force to refresh the group policy.
4) Now try to log into a machine in Hyper-V manager with default credentials enabled, and note that you are not prompted.
Again, I don't know why I had to do this, but it's working fine now.

No longer able to view virtual machine from Hyper-V Manager

From the Windows 2008 R2 host machine, I can run the Hyper-V Manager and 'connect' to the Virtual Machine. The window pops up with nothing but a gray background (clearly the same gray background of the log in screen), but no 'ctrl-alt-delete' prompt
and no ability to log in. This was previously working fine.
Note that I can still make a Remote Desktop connection to the Virtual Machine and it works fine.
Thanks.

Hi,
I never seen this issue before, base on my experience, it may cause by your AV soft block some critical components of Hyper-V host, please try the following exclude specific
directories or process with your AV soft.
•Default virtual machine configuration directory (C:\ProgramData\Microsoft\Windows\Hyper-V)
•Custom virtual machine configuration directories
•Default virtual hard disk drive directory (C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks)
•Custom virtual hard disk drive directories
•Custom replication data directories, if you are using Hyper-V Replica
•Snapshot directories
•Vmms.exe (Note: This file may have to be configured as a process exclusion within the antivirus software.)
•Vmwp.exe (Note: This file may have to be configured as a process exclusion within the antivirus software.)
The related KB:
Virtual machines are missing, or error 0x800704C8, 0x80070037, or 0x800703E3 occurs when you try to start or create a virtual machine
http://support.microsoft.com/kb/961804/en-us
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

MMC finds error with a snap-in when launching Hyper-V manager

From a clean install of Win 8.1 Pro 64-bit I had used the Hyper-V manager to test some virtualization. After tinkering around with a few virtual machines I put that aside for a while. Over the following weeks I continued applying updates as
Microsoft released them. Decided to play around with virtual machines again and when launching the manager I got the error "MMC has detected an error in a snap-in and will unload it." Options are to report the error to Microsoft and shut
down MMC, or unload the snap-in and continue running. If I report the error it goes into the problem reports but as of yet there is no solution available. If I unload the snap-in and continue running I get this additional output:
FX:{922180d7-b74e-45f6-8c74-4b560cc100a5}
Could not load file or assembly 'Microsoft.Virtualization.Client, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The module was expected to contain an assembly manifest.
Exception type:
System.BadImageFormatException
Exception stack trace:
at Microsoft.Virtualization.Client.VMBrowser.BrowserSnapIn.OnInitialize()
at Microsoft.ManagementConsole.SnapInBase.Initialized()
at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.ISnapInClient.Initialize(ISnapInPlatform snapInPlatform)
at Microsoft.ManagementConsole.Executive.SnapInInitializationOperation.OnStart()
at Microsoft.ManagementConsole.Executive.RunningOperationsTable.EnqueueOperation(Operation operation)
at Microsoft.ManagementConsole.Advanced.FrameworkSnapInFactory.Microsoft.ManagementConsole.Advanced.ISnapInFactory.CreateSnapIn(Int32 bookkeepingId, String snapInKey, Object& snapIn)
I tried restoring one of my earlier drive images and got Hyper-V manager working again. Unfortunately continuing to run with this image wasn't feasible as I've had too many changes in the install to apply all over again, my solution needs to be repairing
my image as it exists at the time I discovered Hyper-V was broken. The older image was useful though to use to see just what causes the break. From that restore I stepped through Windows Updates one by one, eventually finding that the fix for KB2898871,
"Security Update for Microsoft .NET Framework 4.5.1 for Windows 8.1 and Windows Server 2012 R2 for x64-based Systems" was what seemed to trigger it. Uninstalling this update on my current image does not resolve the issue. Somehow something
is hanging around that is the root cause of the problem. An additional odd thing with this is that this KB update is marked as February 2014, yet going back through my disk images I found that the problem had existed as early as December 2013, possibly
the month before. If .NET updates are cumulative then that would make sense as an earlier update that is now included in KB2898871 could have been applied before, but I don't know if the updates are designed that way. I have yet to find any information
online directly relating to this problem and those that are somewhat similar haven't produced any working fix. Looking for any thoughts on this while I hope that the problem report uploaded to Microsoft is being worked on.

Ok, now I'm stumped. I restored the first image I captured of my 8.1 install (11/14/2013, looks like with all available updates at that time) and started applying updates. After this I could still launch Hyper-V without error. Now, this
image was before I had created any virtual machines and at this point I still haven't added any to my test image, but Hyper-V does launch.
So my suspicion is now moving to something about maybe the information of the VMs I had previously created in Hyper-V aren't playing well with the later .net update. Haven't gone digging for this yet but with this new finding does anyone have any areas
they think I should examine? The first place I'm going to look is the registry and see what I can find for differences there.

How to up Windows Server 2008 R2 SP1 created VM with Windows 8.1 hyper-v manager

Hi
I have VM that created with Windows Server
2008 R2 SP1. This was up without a problem with the windows 8 hyper-v manager. I have recently upgraded my OS with 8.1. Now I have tried to import this VM but it
throwme following message.
This is a real pain when there is no way of doing this. Any help greatly appreciated.
Regards
Radika

Hi,
Brian is right, for mange the Server 2008r2 sp1 we recommend use the Windows 7 or 7.1 platform.
More information:
Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=7887
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Can't connect to the Hyper-V manager after upgrading to Windows Hyper-V 2012 R2

I have some Hyper-V server based on the free version (Windows Hyper-V 2012). I want to upgrade to the new version (Windows Hyper-V 2012 R2). So I begin to test it with
an already working server (aka I was able to totally manager the server remotely without problem) and so upgrade it to the R2.
After the upgrade, remote management and Hyper-V manager does not work anymore. So I redo my usual configuration steps (enable remote management, open firewall, uses
latest hvremote.wsf, etc.). I was able to regain access to Computer Manager but not the Hyper-V manager which still can't connect at all. I can't access the Task Scheduler too without having a lot of XML error like "The task XML contains a value which
is incorrectly formatted or out of range" (see below for screenshot).
Is there a new step to do to be able to manage Hyper-V 2012 R2 from a Windows 7 computer?
It's not a network problem as I can access RDP and MMC Computer Manager.
To be sure the problem is coming from the R2, I have taken an old computer, install Windows Hyper-V 2012, do my usual configuration step, and
tada: it works perfectly. I can access the Hyper-V manager from my client.
Technical details:
- Client is a Windows 7 SP1 x64 English member of a domain with latest RSAT (Windows6.1-KB958830-x64-RefreshPkg.msu).
- Servers are in a workgroup (not a domain's member). And no, I can't add them to the same domain as the client.

HI,
Can we upgrade HyperV 2012 to hyper v 2012 R2.
Thanks
Atul

Hyper-v manager in windows 8.1 cannot connect to hyper-v server. RPC server unavailable

I am setting up a new server. I installed Hyper-V 2012 R2 on it and want to manage it remotely with Hyper-V manager from a Windows 8.1 computer. I am unable to communicate with the computer with the server. Hyper-V manager gives me the following error: RPC
Server Unavailable. Unable to establish communication between "the hypervserver" and "the W8.1station". Both computer are located in the same subnet and both are on the same domain.
I configured the server with a fixed IP, DNS, to accept pings, connected it to the domain and set it up to allow remote access and management. Although I do not think it is necessary, I added my domain account to the administrators group in the hyper-V server.
I can perfectly ping the server and remote into the server from the W8.1 station. From he server I can also ping the W8.1 station as well as exterior websites (DNS functionality is ok).
I have play with the firewall in both, the Hyper-V server and the management station and have not being able to get them to communicate. Blaming the Hyper-V server for all this and the great time that I have already spent on this problem, I borrowed a Windos
7 Pro computer, installed RSAT and enabled the Hyper-V manager in that computer. Launched the manager AND CONNECTED TO THE HYPER-V SERVER WITH NO PROBLEMS AT ALL !!!!!!!
I have read a lot already about this but most people having this issue are setting up servers in a workgroup environment, and almost nobody is using Windows 8.1 as the management station. Can someone PLEASE give me a hand with this problem??
Thanks to you all !!!

Hi reirem,
Please use the script " hvremote " to Verify configuration for errors via command "hvremote /show /target:othercomputername
Here is HvRemote script link :
http://code.msdn.microsoft.com/Hyper-V-Remote-Management-26d127c6
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-v manager ver 6.1 not allowing to add VM's on 2012R2

Hi
I am using Hyper-V manager ver 6.1 to manage all VM's on 2008, 2008 R2 and 2012 but i cannot manage VM's on 2012 R2, is there something i can do about.
Pragnesh

The version of Hyper-V Manager RSAT tool must match the version of the Server being managed in order to support all features that the Hyper-V Server offers.
This dictates an OS version match.
Client 8.1 manages Server 2012 R2
The v1 virtualization namespace was removed with the 2012 R2 release (as in gone) and versions of the Hyper-V Manager prior to the 2012 release only knew about the v1 virtualization namespace.
2012 was the only release that knew of both the v1 and v2 namespaces.
But the other statement still stands. If the version of the Hyper-V Manager is older than the version of Hyper-V being managed, not all features will be available.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

Hyper-v manager no new option - unable to create new/a vm

Hello,
I have a leptop HP 450 , with Windows 8.1 pro . I am trying to create a virtual machine but I can not do it.
In Hyper-v manager I don't have the "new" option. I have Only "connect to a server" .
My leptop is for home use.
Thanks,

You should connect to local server for see Virtual machine and Management tools on local system.
Do this Steps:
1-Right clik on hyper-v Manager and select "Connect To Server...."
2-On page Select Computer click on "Local Computer" and then click OK.
3-You see Virtual machine (if you haven't virtual machine it was empty) and management tools.
4-Have fun!
Whenever you see a helpful reply, click on Vote As Helpful & click on
Mark As Answer if a post answers your question.
LinkedIn:
Facebook:

Linux VM KVP IP can't be shown on Hyper-V Manager after querying its KVP/IP information on Hyper-V host several times

Hello
[Sorry for asking the same question in the wrong place/forum of "Hyper-V"]
I am using a CentOS 6.5 VM (Linux kernel 2.6.32-431) and (generation 2) CentOS 7 VM (Linux
kernel 3.10.0-123) with Hyper-V KVP daemon installed,
and I periodically query its IP (via using WMI or Powershell to query its KVP information) to manage it.
However, after querying its IP (KVP) for several times, its IP can’t
be queried or shown on Hyper-V Manager anymore (Windows VM is ok without this problem).
And here is the vmIntegrationService status of my CentOS 7 VM for the references.
PS C:\Users\Administrator> (Get-VM -name G2_CentOS7).vmIntegrationService
VMName Name Enabled PrimaryStatusDescription SecondaryStatusDescription
G2_CentOS7 Time Synchronization True OK
G2_CentOS7 Heartbeat True OK
G2_CentOS7 Key-Value Pair Exchange True OK The protocol version of the component installed ...
G2_CentOS7 Shutdown True OK
G2_CentOS7 VSS True No Contact
G2_CentOS7 Guest Service Interface False OK
I attached a simple KVP query Powershell script as
the follows, and this problem can be reproduced in couple minutes if you run two instances with this script at the same time.
$VMName = $args[0]
write-host "$VMName"
filter Import-CimXml
$CimXml = [Xml]$_
$CimObj = New-Object -TypeName System.Object
foreach ($CimProperty in $CimXml.SelectNodes("/INSTANCE/PROPERTY"))
if ($CimProperty.Name -eq "Name" -or $CimProperty.Name -eq "Data")
$CimObj | Add-Member -MemberType NoteProperty -Name $CimProperty.NAME -Value $CimProperty.VALUE
$CimObj
$CimObj = $null
for ($i=1 ; $i -le 10000 ; $i++) {
$a = Get-Date
write-host "$i - Time: " $a.ToLocalTime()
$vm = Get-WmiObject -Namespace root\virtualization\v2 -Query "Select * From Msvm_ComputerSystem Where ElementName='$VMName'"
$vm.ElementName
$vmkvp = Get-WmiObject -Namespace root\virtualization\v2 -Query "Associators of {$vm} Where AssocClass=Msvm_SystemDevice ResultClass=Msvm_KvpExchangeComponent"
$vmkvp.GuestIntrinsicExchangeItems | Import-CimXml
Actually, if your CentOS VM (has LIS) installed with KVP daemon running well,
my test script will show more than 4 keys (include NetworkAddressIPv4 or NetworkAddressIPv6 keys).
However, while the KVP daemon becomes problematic, it will only show a few keys
(ex. 4~6 keys) and at this moment, Hyper-V Manager also can't show IP address of it anymore and you may need to reboot the CentOS VM to recover it.
For example (KVP in 252 time is good, but KVP in 253 and 254 times become problematic)
252 - Time: 8/26/2014 7:19:42 PM
G2_CentOS7
localhost FullyQualifiedDomainName
3.1 IntegrationServicesVersion
10.1.145.190;192.168.122.1 NetworkAddressIPv4
fe80::215:5dff:fe91:b902 NetworkAddressIPv6
3.10.0-123.el7.x86_64 OSBuildNumber
0 OSDistributionData
0 OSDistributionName
199168 OSKernelVersion
7 OSMajorVersion
OSMinorVersion
CentOS Linux OSName
129 OSPlatformId
3.10.0 OSVersion
x86_64 ProcessorArchitecture
253 - Time: 8/26/2014 7:19:42 PM
G2_CentOS7
localhost FullyQualifiedDomainName
3.1 IntegrationServicesVersion
10.1.145.190;192.168.122.1 NetworkAddressIPv4
0 OSDistributionData
0 OSDistributionName
199168 OSKernelVersion
129 OSPlatformId
254 - Time: 8/26/2014 7:19:44 PM
G2_CentOS7
0 OSDistributionData
0 OSDistributionName
199168 OSKernelVersion
129 OSPlatformId
I
found the following patches and gave them a try, but the
problem still remains after applying these patches and the (generation 2) Ubuntu 14.04 with Linux kernel 3.13 also has this problem.
- Patch "Drivers:
hv: util: Fix a bug in the KVP code" has been added to the 3.14-stable tree
- Drivers: hv: vmbus: Fix a bug in the channel callback dispatch code
But (generation 1) Ubuntu 14.04 VM with Linux kernel 3.17 doesn't encounter this problem after querying its KVP/IP information on Hyper-V host several times.
Does anyone know what changes between Linux kernel 3.13 and 3.17 fix this issue?
Thanks,
Paul

Hi Dexuan and Mike,
Thanks for your help!
I did the patch with rpmbuild on CentOS 6.5 (with kernel 2.6.32-431).
However, the second patch cannot patch on CentOS6.5 since there is no target_cpu in such version.
So we are patching that with the following similar patch but this issue still occurs. (also replace ko in initrd)
https://lists.ubuntu.com/archives/kernel-team/2014-August/047725.html
Can you tell me if any patch I could miss or any suggestion?
Thanks for your time.

Virtual Machines disappear from Hyper-V Manager on reboot

I have a Windows 2012 RC server that has fail-over clustering installed (single server at the moment), and it has an iSCSI disk that is configured as a CSV volume. When I create a new VM in Hyper-V Manager, I am storing the .vhdx and machine definition
on that CSV. Everything is good until I reboot the server. Once I do that, the VM disappears from the Hyper-V console even though the symbolic link to the server still exists in C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines.
I have tried to add the VM to the cluster manager (Configure Role...High Availability Wizard), but it fails with no error message that indicates why it is failing. I get the following two errors in the report:
An error occurred while configuring the virtual machine configuration resource 'Virtual Machine Configuration MYVM' with information about the virtual machine.
and
There was a failure configuring the virtual machine role for 'MYVM'.
Please, override 'Header' property The object has been deleted from the cluster.
The first error occurs after "Notifying virtual machine configuration resource 'Virtual Machine Configuration BUF-FS-SQL' that its configuration has changed..."
I sense it might be related to permissions on the CSV, but not sure what permissions may need to be set?
Thanks,
Bob

That did not work. VM still does not show up after restart. I have tried to import the VM from the original location on the CSV, but I get:
"Hyper-V encountered an error while loading the virtual machine configuration from C:\ClusterStorage\Host\Hyper-V\Virtual Machines\Test\Virtual....\GUID....
Hyper-V encountered an error trying to access an object on computer 'localhost' because the object was not found. The object might have been deleted, or you might not have permission to perform the task.".....
BW

Could not intialitize a virtual machine on Hyper-V Manager on a Windows 8.1 laptop

Hello,
I am receiving the following error when I try to start any virtual machine on Hyper-V Manager on a Windows 8.1 lap"color:black;">An error occurred while attempting to start the selected virtual machine(s):
Morillo-DC could not initialize (Virtual Machine ID …)
On the Event Viewer, I can see:
Event ID 3040
Log Name: Microsoft-Windows-Hyper-V-Worker/Admin
Morillo-DC could not initialize (Virtual Machine ID …)
Thank you in advance for any help.
Regards,
Alberto Morillo

Hello,
Hyper-V was working fine with Windows 8 before installing Windows 8.1 update.
On the Applications and Services Logs (Event Viewer), I found the following event:
Log Name:
Microsoft-Windows-Hyper-V-Worker-Admin
Source:
Microsoft-Windows-Hyper-V-Worker
Date:
12/16/2013 3:59:13 PM
Event ID:
3040
Task Category: None
Level:
Error
Keywords:
User:
NT VIRTUAL MACHINE\E304221F-2B11-4E29-B235-85A3F505EC48
Computer:
MorilloPC
Description:
'borrar' could not initialize. (Virtual machine ID E304221F-2B11-4E29-B235-85A3F505EC48)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
<EventID>3040</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-16T19:59:13.665065300Z" />
<EventRecordID>114</EventRecordID>
<Correlation />
<Execution ProcessID="6364" ThreadID="3340" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>MorilloPC</Computer>
<Security UserID="S-1-5-83-1-3808698911-1311320849-2743416242-1223427573" />
</System>
<UserData>
<VmInitialize xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>borrar</VmName>
<VmId>E304221F-2B11-4E29-B235-85A3F505EC48</VmId>
</VmInitialize>
</UserData>
</Event>
Thank you for your help.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to Connect to WS2012R2 Hyper-V manager with Windows 7 version of Hyper V manager.

Just brought up a new WS2012R2 host server and created a gen 2 VM on it . I already have a WS2008R2 Host server with several VMs running. I manage the WS2008r2 WM from my Win7pro laptop using Hyper-V remote management tool. But when I try to connect to the
new WS2012R2 host server the operation fails with the message 'The operation on computer 'HOSTSERVERNAME' failed'
I've checked for downloads to update the remote HyperV management tool and cant find any. Am I correct in assuming that I can only connect to the Hyper-v Management tool for WS2012R2, from Win8 or higher? or is it something I've over looked. remote
management is enabled on the host server and the vm.
thanks
Marty
MAR

I am having the same problem however I can access a WS2012 with my Win 7 client but cannot access my WS2012R2.
My thread
http://social.technet.microsoft.com/Forums/windowsserver/en-US/720e98a2-6a97-4cd6-bab7-aeacb861e71e/allow-domain-users-rd-access-to-hyper-v-manager-located-on-a-dc?forum=winserverhyperv&prof=required
Any ideas?
Phil

Hyper-V Manager missing from tools menu

I've just installed a new domain. It has one domain controller (Windows Server 2012 R2), SVR0 and one Hyper-V Server (not the Hyper-V role...Hyper-V Server), SVR1. I joined SVR1 to the domain and now I wan to manage it from a Windows 8.1 client. I've installed
RSAT on the client and I can open Server Manager no problem. The problem that I am having is that there is no sign of Hyper-V manager anywhere. Server Manager knows that SVR1 is a Hyper-V server but still there are no Hyper-V Manager links anywhere. I was
expecting it to show up in the tools menu on Server Manager but it did not. I made sure that Hyper-V management feature is installed on SVR1, but still nothing.
What am I doing wrong?

Hi,
After you setup the Hyper-V server did you create the external and all that external virtual switch has configured as “Allow management operating system to share this network
adapter” ?
If you want the Hyper-V can be managed by Server Manager that is running on a remote server, you need to enable your local server to run the Windows PowerShell cmdlet
Configure-SMRemoting.exe –Enable.
If you want to use RSAT Please reconfirm you firewall configure correctly and disable your Hyper-V server firewall and use the domain administrator account to try the management,
thanks.
The related KB:
Manage Hyper-V Server Remotely
http://technet.microsoft.com/en-us/library/jj647785.aspx
More information:
Manage Windows Server 2012 Remotely with RSAT tools for Windows 8 RTM
http://blogs.technet.com/b/keithmayer/archive/2012/09/13/manage-windows-server-2012-remotely-with-updated-rsat-tools.aspx
Description of Remote Server Administration Tools for Windows 8.1 and Remote Server Administration Tools for Windows 8
http://support.microsoft.com/kb/2693643
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Manager remote connection

This is originally posted to the following forum and they suggested I post here.
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_perf/hyper-v-manager-remote-connection/708e46c4-8e84-4fd6-8cdd-590d10a008a9
In Windows 10 Technical Preview (Build 10041) I am trying to connect to my remote Hyper-V Server 10 Preview (Build 9841) to manage it. I enabled all the firewall ports (even disabled it at one point) but I can't get the Hyper-V manager to list the VMs on
the server. I am able to make a remote PowerShell connection to manually do some stuff but the interface is much easier obviously.
Anyone have information on what we can check or what we need to do in order to get the new Hyper-V manager talking to a remote server properly? It is actually connected just not listing VMs on that machine. I can modify Virtual Switches just fine, but the
listing never shows a VM.
There are no 3rd party anti-virus programs installed. So that is not the issue. I wanted to see if someone else had ideas or if this was a known bug.

just a confirm, have you checked if the hyper-v manager works OK in the server machine, I mean not remotely.
Another point, you can check if you have permissions to create new VMs, it might be related to permissions issue I guess, add your user account to Administrator\domain admin\hyper-v administrators...
Other user shows that it could be related to symlinks in the directory
%SYSTEMDRIVE%\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\
http://blog.brainmassage.co.uk/2011/02/no-virtual-mahines-were-found-on-this-server/
https://social.technet.microsoft.com/Forums/windowsserver/en-US/38f7bf66-0a39-4905-90f8-c6900a4fdfd6/hyperv-guest-vms-disappeared-after-orderly-reboot-not-virus-scanning-issue?forum=winserverhyperv

Hyper V Manager

Similar Messages

Maybe you are looking for