Hi, I'm hoping someone can help me with a really frustrating problem creating a VDI collection.

I have a 4 node Hyper-V cluster running Server 2019 DataCenter.

All VM servers are running ok as is RDS Remote Apps. The problem i have is specifically with VDI

I have installed the RD Virtualization host role on all 4 physical host servers and all show in the RDS section of server Manager as Virtualization hosts.

When I create a VDI collection it completes successfully if I use hosts 2, 3, and 4 in any combination, but if i include host 1 it fails with the error 'The collection was created successfully with the following warnings: Unable to retrieve the details of the virtual desktop collection'

In Server Manager then, under Collections I see the collection name with 'Not Valid' next to it.

The wizard has copied the template but not created any VDI machines.

Also, which may or may not be related. When I successfully create a collection by not including host 1 I can see the VDI machines in Hyper-V Manager, but not in Failover Cluster Manager.

This may be 2 separate issues but any help on either much appreciated.

Thanks

Kevin

I am trying to install Hyper-V server 2019 core onto a newly built sever ( ASUS Z10PE-D8 WS with dual Xeon 2620 v4, 64 GB DDR4). After installing the hypervisor from a USB stick I get into command shell and have several issues. Recall there is NO OTHER SOFTWARE on this rig.

After logging on as Administrator, and going to automatic sconfig the first problem is  "no active network adapters are found" so I went into the CMD prompt and installed these from the ASUS Utilities CD. that didn't do the trick so I figured, install the chipset drivers but when I try to do that there's a "class not recognized" response to my setup.exe command.  Also the remaining drivers and utilities on the CD have AsusSetup.exe commands which trigger an missing oledlg.dll response.

I know if I can just get the first domino to topple I can get this thing going.  Any insight would be appreciated.

When I am trying to initiate replication from HyperV Host 1 to Hyper-V Host 2 which in AD Domain. Replication gets failed with below Event :

Hyper-V could not replicate changes for virtual machine 'VM Name': The connection with the server was terminated abnormally (0x00002EFE)

Below steps are checked:

1.Able ping each other.

2.Test-netconnection is done for port 80 from both side.

3.Able to resolve domain name.

4.This issue is getting for few VMs. Existing replication is normal.

Request you to give us solution for this issue.

I was checking my Server 2012 DC (It’s a VM running on Hyper-V) while I noticed some Disk (event 153) and DFSR errors in the event viewer. Immediately I remoted into the Hyper-V host and checked the event viewer for similar errors but did not find any at all for “Disk”. I then ran some utilities on the host to check the drive status but everything is showing OK. There is another DC (server 2019) also running on the Hyper-V host so I popped in there to check and I do see some Disk errors (event 153) showing as well.

Perhaps there is an issue with the virtual disk? It looks like the errors first appeared about a month ago on 3/1. Most of them occur around the time that Veeam backups happen (8:00PM) but some occur outside of that window.

Hello,

I would like to understand, how the VHDX space allocation works, because when i created a VHDX Fixed inside a storage LUN, we couldnt see any space consumption on the storage side, but when we started to copy data to that VHDX, the space started to be consumed.

My question is, as we created a FIXED VHDX, is it suppose to allocate and consume that space even without data inside it?

Thanks!

Filipe Noronha Sisnema Informática LTDA

Hi Everyone,

 I've been working hard trying to replicate my Virtual Machines from one Hyper-v Cluster to other Hyper-v Cluster, both Cluster are Windows 2016, each one has 4 Nodes. I can replicate VMs by Failover Cluster GUI, but when I tried to do it by powershell, I cannot achieve this task (I have more than 200 VMs, so I need to do it by PS), I have the following errors:

PS C:\Windows\system32>Enable-VMReplication "MyVM" -ReplicaServerName broker-rep.domain.corp -ReplicaServerPort 80 -AuthenticationType Kerberos -ReplicationFrequencySec 30

Enable-VMReplication : Hyper-V encountered an error trying to access an object on computer 'broker-rep.domain.corp' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.
At line:1 char:43
+ ...  Enable-VMReplication MyVM -ReplicaServerName broker-rep.domain ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (:) [Enable-VMReplication], VirtualizationException
    + FullyQualifiedErrorId : ObjectNotFound,Microsoft.HyperV.PowerShell.Commands.EnableVMReplication

I've been reading a lot of forums about it, but no one works for me. If I use the Module Version 1.1 of Hyper-V I can replicate by Powershell but I need to replicate Virtual Shared Disk, because I have 4 guest clusters in my Enviroment.

please anyone can help??

Hello together,

When I am working as a consultant, the project partners are providing me the computer to develop software. In which way could it be possible to run the projects partner's environment on my own computer? Let's say I have Hyper-V type 1 running on my computer. This VM would allow me to use the project partner's Windows 10 image with VPN credentials. In case my contribution is done, the project partner is switching off my windows 10 account in their organisation. Problem could be, that the windows 10 image is still present on my harddisk, but it could be encrypted.

This solution would have also the benefit, that the uncompiled source code never would go out of the "sphere" of the project partner. The cyber security policies for the hyper-v guest OS would still come from the project partner.  Further the project partner would safe the costs to provide hardware for the non-permanent employees.

Is such a solution makeable? Is such a solution available?

regards

I have a 2019 server (new clean install) and am trying to install wsus from the server manager gui.

All goes well until post installation tasks and I get: "Fatal Error: Failed to start and configure the WSUS service"

When I look at the log I see (amongst other things):

2019-08-16 09:47:33  CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.GetServerVersion()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
2019-08-16 09:47:33  StartServer encountered errors. Exception=The request failed with HTTP status 503: Service Unavailable.
2019-08-16 09:47:33  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service

Any ideas?

regards

roga

Hi all,

I have physical server Dell PE R330 (Intel Xeon E3-1220 / 32GB RAM /PERC H330 / RAID-1 on SSD / RAID 10 on SAS 15K).

Windows 2016 standard with Hyper-V / AD / DNS / DHCP installed on SSD RAID.

Hyper-V service has mostly standard settings. There are 2 virtual machines(KAV and WinFS-V) - both Win 2016 STD .

There's about 20-25% free space on all volumes at hypervisor right now.

All VM has 2 vhdx - first located on SSDfor OS and second on SAS for DATA.

All 3 OSes were patched last month.

One of VM has a problem. A year before the checkpoint was taken. So there were vhdx and avhdx disk files.

Today we have decided to take a new checkpoint, but the strange error raised. 

Then we tried to delete old checkpoint (it takes about 34Gb), but Windows also showed strange error (no specific error like 0x87979879). Just generic error and that's it.

powershell commands remove-vmsnapshot gives that generic error

• Get-VMSnapshot -VMName kav
  
  VMName Name                           SnapshotType CreationTime         ParentSnapshotName
  ------ ----                           ------------ ------------         ------------------
  kav    kav - (2/27/2019 - 1:52:21 PM) Standard     1/1/0001 12:00:00 AM

• Get-VMSnapshot -VMName kav | Remove-VMSnapshot

Remove-VMSnapshot : Deleting 'kav - (2/27/2019 - 1:52:21 PM)' failed.
At line:1 char:30
+ Get-VMSnapshot -VMName kav | Remove-VMSnapshot
+                              ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Remove-VMSnapshot], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.RemoveVMSnapshot

removing via GUI was failed, checkpoint and full tree too

and export VM as well.

After we followed some tips and merged vhdx and avhdx disk files for this VM.

Now it works with merged disk files, but shows that it has a checkpoint.

We cannot delete it, create new one or export VM and re-create KAV again.

If we create new VM (say KAV-2) and connect merged vhdx form old KAV, the configuration changes and services can't run.

EventViewer shows several errors, 

every time I tried to remove checkpoint, these 4 errors arise

1. The Hyper-V Virtual Machine Management service encountered an unexpected error: Unspecified error (0x80004005).
2. Virtual machine failed to generate VHD tree: 'The specified network resource or device is no longer available.'('0x80070037').
3. Failed to lock virtual machine's configuration 'V:\Snapshots\B7250DC8-04BE-4BDC-A481-2EC06CF6CD7B.vmcx': 'The specified network resource or device is no longer available.'('0x80070037').
4. Checkpoint operation for 'kav' failed. (Virtual machine ID 4C82B504-BE0C-41C0-9606-8DDD3F29E4B3)

When I try to export VM, these 2 errors arise

1. Failed to delete export directory ''. Please delete export directory manually.
2. Export failed for virtual machine 'kav' (4C82B504-BE0C-41C0-9606-8DDD3F29E4B3) with error 'Unspecified error' (0x80004005).

When we start KAV-2 with merged vhdx these errors arise

1. 'kav' Сетевой адаптер (4c82b504-be0c-41c0-9606-8ddd3f29e4b3--5113d8c0-f428-4e48-85bc-3068d552b266) failed to allocate a virtual function: The device does not recognize the command. (0x80070016): IOV networking might be incompatible with other configured networking features. (Virtual Machine ID 4C82B504-BE0C-41C0-9606-8DDD3F29E4B3)
   
2. Failed to allocate virtual function for NIC 4C82B504-BE0C-41C0-9606-8DDD3F29E4B3--5113D8C0-F428-4E48-85BC-3068D552B266 (Friendly Name: Сетевой адаптер), status = The device is not in a valid state to perform this request.
3. Failed to allocate virtual function for NIC 4C82B504-BE0C-41C0-9606-8DDD3F29E4B3--5113D8C0-F428-4E48-85BC-3068D552B266 (Friendly Name: Сетевой адаптер), status = {Drive Not Ready}
   The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed..
   

Please help

Hi,

i don't know if i have the right setup, so first what i have :

Hyper-V, server 2016 datacenter. On that hyper-V server i have : a AD-server, a FILE-Server, RDS-server and an SQL server. So 4 virtual machines.  All in production and working fine.

Now i wanted to add a 5th server, VDI-server. So made a new machine, installed 2016 datacenter and added the server tot the domain.  Then i installed Remote Desktop Services Role (for the VDI)

Hyper-V needed to be installed on that server to make the master image. So i made a new virtual machine and installed a "Windows 10 Pro".  The windows 10 Pro is starting and i"m ready to config and setup my master-image.  The only thing is i have no internetaccess, in other words i don't get a ip address. 

What could be wrong ? or am i settings this up in the wrong way ?

SCREENSHOTS

Can anybody share with me any easy sample about this topic?

I try it with PowerShell succesfully on a Server 2019 with VS2019 and C# but I need sample for native WMI version.

Or write me please any place where anybody can help me.

ManagementScope scope = new ManagementScope(@"root\virtualization\v2");
            using (ManagementObject vm = WmiUtilities.GetVirtualMachine("teszt1", scope))
            using (ManagementObject vssd = WmiUtilities.GetVirtualMachineSettings(vm))
            using (ManagementObject vmms = WmiUtilities.GetVirtualMachineManagementService(scope))
            {
...
            }

We've implemented a 4 server failover cluster with Windows 2016 datacenter. But 3 times now over the last 6 months or so we've had the same incident. The VMs on one host will get stuck in a stopping state when they're shutdown. We'll also be unable to migrate servers from or to that host. We're also unable to drain that host via the Failover Cluster.

In the Event Viewer under Hyper-V-VMMS Admin we'll see events 19060 for the VMs that are stuck:

'VM' failed to perform the 'Unregister Virtual Machine Configuration' operation. The virtual machine is currently performing the following operation: 'Turning Off'. (Virtual machine ID IDGUID)

In the Failover Cluster Manager cluster events, we'll see events 1205, 1254 and 1069 for the VMs.

To resolve we have to shutdown the host, which gets stuck as it tries to drain its roles to the hosts but can't, so we end up forcibly powering off the host.

While it is stuck I've tried to forcibly shutdown the Hyper-V Virtual Machine Management service, but it gets stuck completely. This is the same for trying to do it for the affected VM processes. We also see host status warnings in SCVMM, generally saying the host isn't responding.

I'm looking at logging a case for it now, but previously I've updated all of the hosts in the cluster to the latest updates (about a month ago). They also have ADDS roles on them (not setup) due to the Host Guardian role, but I've been removing it seeing as we've not used Host Guardian yet.

Has anyone out there experience similar issues and been able to resolve it?

Hi, I'm currently learning the ropes on how to configure a windows 2016 server in to a domain controller, i'm using hyper v to do all this in. I've got my windows 10 client as well as a server running 2016 on it.

I've set the server up with a static IP and have configured a reverse and forward lookup zone, I've created a DHCP scope as well but for some reason I can't get the windows 10 client to connect to the domain for some reason, are you able to assist? it may be something really simple. I've created a virtual switch and have assigned it to both the W10 VM and Server - when doing anipconfig on the W10 VM i get a 169.254 address 

Any help on this would be greatly appreciated. 

I have Azure Site recovery setup and it creates all these avhdx files which my VM ends up running on .. usually when i reboot the server it will merge them but that seems to have stopped working.. how do i get these all to merge or stop these from being created its taking up alot of space..

i want to avoid manually merging them as that will take forever to do 

thanks

We are running a Hyper-V-Failover-Cluster with two Nodes. Starting mid-May I see the following error pop up in my event log on both Nodes (Switch-ID is different though)exactly once after a restart:

Fehler    18.05.2016 04:13:12    Hyper-V-VmSwitch    15    (1010)

Protokollname: System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:         18.05.2016 04:13:12
Event-ID:   15
Aufgabenkategorie:(1010)
Ebene:         Error
Schlüsselwörter:
Benutzer:      SYSTEM
Computer:      HUGSNODE01.xxxxx.xxx
Beschreibung:
Failed to restore configuration for port Properties (Friendly Name: ) on switch 505595D4-6D1E-4533-BE0E-338B30360C8F (Friendly Name: ), status = Der Objektname wurde nicht gefunden..
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67DC0D66-3695-47C0-9642-33F76F7BD7AD}" />
    <EventID>15</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1010</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2016-05-18T02:13:12.084821000Z" />
    <EventRecordID>216769</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="240" />
    <Channel>System</Channel>
    <Computer>HUGSNODE01.xxxxxxxxx.xx</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="Status">3221225524</Data>
    <Data Name="PortNameLen">10</Data>
    <Data Name="PortName">Properties</Data>
    <Data Name="PortFNameLen">1</Data>
    <Data Name="PortFName">
    </Data>
    <Data Name="SwitchNameLen">36</Data>
    <Data Name="SwitchName">505595D4-6D1E-4533-BE0E-338B30360C8F</Data>
    <Data Name="SwitchFNameLen">1</Data>
    <Data Name="SwitchFName">
    </Data>
    <Data Name="UniqueEvent">9</Data>
  </EventData>
</Event>

There may be two incidents linked to the issue, although I am not sure about it.

Cluster-Aware-Updating was installing updates automatically. I remember that CAU was causing us major trouble once this year when an update one Node failed that also killed some Network settings. Major pain in the behind! I got it working again by reinstalling some network card drivers, but I honestly did not understand how. I followed some blog advice on the internet.

We also restructured the network connectivity at one point, deleting the NIC-Team and reconfiguring it. I don't think I made a mistake here, but just to be sure I'll say it.

I don't know what other Information you need, so I just copy-paste some I believe help

Once both Nodes are up and running, the cluster shows no errors and has full connectivity. But immediately after boot I see some weird errors regarding AD/DC/DNS/GPO issues and I believe this could be the underlying issue.

Please advise.

PS C:\Users\Administrator.AD> Get-VMSwitch | fl *

ComputerName                        : HUGSNODE01
Name                                : ClusterSwitch
Id                                  : 505595d4-6d1e-4533-be0e-338b30360c8f
Notes                               :
SwitchType                          : External
AllowManagementOS                   : True
NetAdapterInterfaceDescription      : Microsoft Network Adapter Multiplexor Driver
AvailableVMQueues                   : 0
NumberVmqAllocated                  : 0
IovEnabled                          : False
IovVirtualFunctionCount             : 0
IovVirtualFunctionsInUse            : 0
IovQueuePairCount                   : 0
IovQueuePairsInUse                  : 0
AvailableIPSecSA                    : 0
NumberIPSecSAAllocated              : 0
BandwidthPercentage                 : 1
BandwidthReservationMode            : Weight
DefaultFlowMinimumBandwidthAbsolute : 0
DefaultFlowMinimumBandwidthWeight   : 1
Extensions                          : {Microsoft NDIS-Aufzeichnung, Microsoft Windows Filtering Platform}
IovSupport                          : False
IovSupportReasons                   : {SR-IOV wird von diesem Netzwerkadapter nicht unterstützt.}
IsDeleted                           : False
Key                                 :
PS C:\Users\Administrator.AD> Get-VMNetworkAdapter -ManagementOS

Name                  IsManagementOs VMName SwitchName    MacAddress   Status IPAddresses
----                  -------------- ------ ----------    ----------   ------ -----------
LiveMigration         True                  ClusterSwitch 00155D0A0142 {Ok}
Cluster               True                  ClusterSwitch 00155D0A0141 {Ok}
Management and Client True                  ClusterSwitch 00155D0A0140 {Ok}

I requested certificate from Enterprise CA using .inf file as described in https://docs.microsoft.com/en-us/virtualization/community/team-blog/2012/20120702-requesting-hyper-v-replica-certificates-from-a-ca

I also added "1.3.6.1.4.1.311.62.1.1.1" = "{hex} 02 01 04" to [Extensions] section and added issued certificate to AuthCertificateHash key underHKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization

I deleted self-signed certificate fromHyper-V management local machine service certificate store.

However Hyper-V does not accept Enterprise CA and keeps generating self-signing certificate. If I disable self-certificate generation (by setting DisableSelfSignedCertificateGeneration reg key) when HV service will unable to start because it can not find suitable certificate.

Saludos  tengo una  maquina  hyper-v en windows server 2016 standar,  fallò  al proceso   de  exportacion,  y  al tratar de iniciarla  comenzo a mostrarme  el  error 3050 y 3326 de memoria  y capacidad d e  disco;  asi  que  elimine  el estado  guardado  que tenia  la maquina. trate  de iniciar nuevamente  y  me  muestra  otro error :'MV-NAME' no pudo inicializar la memoria: Espacio en disco insuficiente. (0x80070070). (Identificador de la máquina virtual: ID-MAQUINA-VIRTUAL) , este  error esta  marcado como  3050 y este  otro como  3326 : La máquina virtual 'MV-NAME' no se pudo iniciar porque no hay suficiente espacio en disco. El sistema no pudo crear el archivo de contenido de la memoria en 'F:\MV-NAME\MV-NAME\Virtual Machines\ID-MAQUINA-VIRTUAL' con el tamaño de 17141 MB. Establezca la ruta de acceso en un disco con más espacio de almacenamiento o elimine los archivos innecesarios del disco e inténtelo de nuevo. (Identificador de máquina virtual  ID-MAQUINA-VIRTUAL.

Borre el estadoo  guardado de  la maquina  y ya  no me salen estos  mensajes  de  error  sino  este  otro: 'MV-NAME' Synthetic SCSI Controller (Identificador de instancia INSTANCIA-ID no se pudo conectar. Error: 'Error general de acceso denegado' (0x80070005). (Identificador de la máquina virtual: ID-MAQUINA-VIRTUAL).

encontre  el siguiente  comando para  corregirlo, pero  genera error : 

icacls <Ruta del archivo .vhd o .avhd> / grant "NT VIRTUAL MACHINE \ <ID de máquina virtual del paso 1>": (F) 

gracias  por  la ayuda, bendiciones !!!

Hi

I have Hyper V 2012 R2 Failover Cluster

I need one tool to evaluate my cluster and propose the recommendation and the best practice otherwise show if there are any gaps.

Thanks

We have a 6 host cluster and we are finding that only 1 host is merging the avhdx files from our Azure site recovery none of the other hosts are doing this.. we had to migrate the VM to the working server in order for the avhdx files to merge

anything i can look into to resolve his