Hey guys,

I created two new VMs with domain controller role on a HyperV-Host. All Servers are installed with Windows Server 2016.

The domain controllers are working as expected, but I can't add clients from outside Hyper-V. VMs on the same HyperV-Host can join the domain as well.

I tested the connectivity with PortQuery and got an error on port 389 UDP. Same test on an non-domain-member VM on Hyper-V-Host is still successful.

PortQuery-Error (executed on my local PC):

UDP port 389 (unknown service): LISTENING or FILTERED

Using ephemeral source port
Sending LDAP query to UDP port 389...

LDAP query to port 389 failed
Server did not respond to LDAP query

The request has been executed with the domain controllers IPv4 address, not FQDN. Same result with disabled firewall on DC.

IPv6 is configured on HyperV and all VMs and working.

I spent a lot of time for Google-searching for a solution, but I only found some solutions with disabling IPv6, but I dont want to disable IPv6.

Maybe I do have to change some settings for HyperV-Switch? Or add static routes on HyperV? The configuration of the DC should be correct, because connections are successfull from other VMs, I think.

Thanks for your help!

It seems that I'd get rid of this error log if I uninstall and reinstall the Integration Services from the windows 8.1 that I am running on Hyper-V 2008 R2.

I was wondering though, whether there is a procedure to do it other way around; I mean instead of removing the version 3.3 that came bundled with 8.1 image and downgrading to 3.0 ; upgrade the Hyper-V 2008 R2 to accept 3.3 integration service.

---------------BEGIN LOG ENTRY-----------------------------

Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
Source:        Microsoft-Windows-Hyper-V-Worker
Date:          3/3/2014 10:48:53 AM
Event ID:      23014
Task Category: None
Level:         Warning
Keywords:     
User:          NETWORK SERVICE
Computer:      HypServer.QSCAudio.com
Description:
Device 'Microsoft Synthetic Display Controller' in 'Windows 8.1' is loaded but has a different version from the server.  Server version 3.0 Client version 3.3 (Virtual machine ID 105358BD-825A-40E6-ABC0-218517297DDC). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
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>23014</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T18:48:53.234733500Z" />
    <EventRecordID>6671</EventRecordID>
    <Correlation />
    <Execution ProcessID="3032" ThreadID="4304" />
    <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
    <Computer>HypServer.QSCAudio.com</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>Windows 8.1</VmName>
      <VmId>105358BD-825A-40E6-ABC0-218517297DDC</VmId>
      <Device>Microsoft Synthetic Display Controller</Device>
      <ServerVersion>3.0</ServerVersion>
      <ClientVersion>3.3</ClientVersion>
    </VmlEventLog>
  </UserData>
</Event>

---------------END LOG ENTRY-----------------------------

In a very simple windows 2012 r2 RDS server there are two setting which seem almost the same. If someone could explain the difference that would be helpful.

Both are accessible from the RDS Overview panel.

#1 is found in the Deployment Overview panel where there is a RD Licensing icon. If one adds a RD License Server via that icon, the server will appear in the adjacent Deployment Servers list.

#2 is exposed via Tasks list when you choose Edit Deployment Properties. The four deployment properties that are exposed there include an entry for RD Licensing, which allows you to again specify the FQDN for a RD License Server and to choose between licensing per device or per user.

Hi Experts,

My team did something wrong in the snapshot files of our VMs that eventually made them corrupted.  Now, booting the base disk, doesnt show up the files that we are looking for, they appear to be on the corrupted snaps and we need to recover them. Has anyone been in this situation?  What are the ways you guys did to recover the files in the corrupted snapshot files?  Is it still possible to recover them?  Please advise.

Thank You!

Noctis0791

Hello

novice here,so bare with me as I'm not fluent yet in all the technical therms and aspects.

i recently started learning for a mcsa certificate,

in class we use vmware; i make a windows10vm and a server2012 VM,

i assign the server an ip from the range i see in the subnet address(VMware-virtual network editor)

i set up ADDS,DHCP,DNS on the server and in "edit/virtual network editor"",i put both the sever and the win10  on a VMnet-nat and use local DHCP to distribute ip addresses.(i think it was nat,maybe local host?)

i try to do the same with hyper-v but having issues,i guess i didn't fully understand how those switches work.

i added an internal switch and put both the machines on it, but when using ipconfig, i see i get different range of ips for both the server and win10 and i wasn't able to have the server distribute an ip to the win10vm nor connect to its local domain with it.

i get these kind of ips:169.254...  saw it was apipa - not sure what that means.

I am having trouble starting the virtual machine using Hyper-V. It keeps prompting this error:

The application encountered an error while attempting to change the state of 'virtual machine'

'Virtual Machine' failed to start.

(Virtual machine ID D77B673-E1AB-4739-A539-7CF6BDE89ACE)

I have searched for solutions but none of those worked. I am running on Windows 10 Pro, I have configured all the necessary settings on Hyper-V such as the hard drives and private networks. Any ideas on how to solve this error?

[EDIT]

I have a 3 node HP cluster with each node directly attached to a JBOD device. Each node shows 4 CSV's that are all healthy.

I upgraded 2 of them from 2012R2 by draining node, reinstalling 2016 and then adding them back to the cluster and everything worked fine.

Started the same process off today and all the disks went offline along with all the machines in the cluster apart from 2 still on the original host that failed to migrate.

Got everything back by unpausing and fail back of the machines and restarting all the failed migrations.

Needless to say, that was not my favourite part of the day.

Event details for the drives show events such as 

===============

Cluster Shared Volume 'Volume1' ('Cluster Virtual Disk (Volume 1)') has entered a paused state because of '(c000020c)'. All I/O will temporarily be queued until a path to the volume is reestablished.

Cluster resource 'Cluster Virtual Disk (Volume 1)' of type 'Physical Disk' in clustered role '1912d37e-0360-434e-9212-3083db0d23fb' failed. The error code was '0x2' ('The system cannot find the file specified.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Cluster physical disk resource online failed.

Physical Disk resource name: Cluster Virtual Disk (Volume 1)
Device Number: 4294967295
Device Guid: {00000000-0000-0000-0000-000000000000}
Error Code: 3224895541
Additional reason: AttachSpaceFailure

Cluster resource 'Cluster Virtual Disk (Volume 1)' of type 'Physical Disk' in clustered role '1912d37e-0360-434e-9212-3083db0d23fb' failed. The error code was '0xc0380035' ('The pack does not have a quorum of healthy disks.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

=======================

The pools are owned by this last node.

After bringing the last node online, I saw that all the CSV's showed an operation status  of regenerating for a while before going back to healthy.

Anyone seen this behaviour before and have some pointers of anything that I might have missed in the process?

http://absoblogginlutely.net

Hi, we have recently created a Hyper-V server but after a few days of use we can no longer take backups. If we restart the VM the checkpoint still fail but if we restart the host they begin to work again. Is there a way of releasing whatever process is using the file so we can take checkpoints for backup again? I've attached a screenshot of the error.

Is there an easy way to find out what process is using the avhdx checkpoint file and can this be deleted to allow the checkpoint process to run. Also the VM does not show it has any checkpoints in the HyperV manager so assume these are created as part of a backup process.



1 Hyper-V host with a 4-port NIC running Windows Server 2019 Datacenter Core

Domain Controller VM and client VMs running on it, connected through an Internal vSwitch.  DC runs DHCP.  Client VMs connected to this Internal vSwitch get DHCP from DC fine.

Flat 192.168.0.x network, looking to keep it as simple as possible for now.

I would now like to connect wireless clients to this DHCP network.  

I have a wireless router that I turned into a bridge by disabling its DHCP and uPNP, and setting a static 192.168.0.x IP for it.

What should I do to enable clients connecting to this bridge to grab an IP from this DC?

(I've tried various things, but don't want to clutter this thread with my (likely faulty) actions, for now.

Thank you for all guidance.

Dear Microsoft!

On https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2019 you link the hyper v core server setup. However, it only leads to https://cloudblogs.microsoft.com/windowsserver/2018/11/13/update-on-windows-server-2019-availability/ and there is no download available.

When are you planning to make it available?

By the way: The download that was briefly online https://software-download.microsoft.com/download/pr/17763.1.180914-1434.rs5_release_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO is barely usable for 2 reasons:

A after installing it and activating Remote desktop, the server does not start to listen on port 3389. No RDP possible!

B Trying to do an in-place upgrade from Hyper-V Server 2016 leads to an error: "The installation failed in the SAFE_OS phase with an error during SET_Product_Key operation"

HyperV server 2016 Core

I changed the names of the networkcards  (4x onboard)

When i checked it with 

Get-NetAdapter ill see everything correct

Name: Port1
InterfaceDescription:AD-Server

Now i like to create a virtualswitch in HyperV manager 
Ill choose an ExternalSwitch , and theni have to choose the network adaptor
There ill see :
Intel Gigabit Network Controller
Intel Gigabit Network Controller #1
Intel Gigabit Network Controller #2

and not the names ill see on the server with powershell
In the windows admin center - devicemanagement - networkcard , ill see also the correct names, 
there is no place to find that "intel" name on the server... 

what do i have to change to see the correct names in the virtualswitch creator?

Henri

It's been a while I played around with Virtual PC/Server as it was called in the day. It's Hyper-V now and that's what I want to use to get two VM's running as a replacement for two SBS 2011 servers. So we bought a fairly 'fat' server - a Dell Poweredge R7415, sporting an AMD Epyc 7281, 64 GB RAM, BOSS-card (240 GB configured in RAID1), three 960 GB SSD's configured in RAID5, six 2 TB near-line SAS drives configured in RAID5 and four 1 Gbit network adapters.

What we need is a fileserver/domain controller and Exchange server. So we bought Windows Server 2016 and Exchange 2016. Windows Core is to be installed on the BOSS-card. The virtual domain controller / file server uses the near-line SAS drives to store it's virtual disk. The virtual Exchange server uses the SSD's to store it's virtual disk.

Installing Hyper-V is pretty much a no-brainer. As is creating a new VM. But both VM's and the host have to be configured for optimal performance. So I read the MS documentation for Hyper-V, but can't find anything about recommended configurations. I broadened the search to the internet, but that's no luck either. Tons of websites describing how to install Hyper-V and create VM's but there it stops.

Could be I searched the wrong way, so please point me in the right direction. Or maybe recommend how to configure both VM's like how many RAM I should allocate, what to do with the network settings - do I tie them all to the virtual switch or do bind them directly to the VM's etc.

Simon Weel

Ok I admit it. This one is driving me crazy ;)

1) I have two Server2016 (Standard) HyperV Clusters - Source01 and DR01. Both part of same forest/domain.

2) Both Source01 and DR01 clusters have a HyperV Replica Broker installed and replication settings configured for Kerberos, Port80 and allow from any server.

3) I can initiate VM Replica successfully in both directions using the FailoverClusterManager UI. It creates the replica, transfers the initial data and everything appears to work.

However....

I need to create the replica using Powershell, but when I try to do it using the Enable-VMReplication powershell command it fails with:

I must be doing something wrong as the UI works. Perhaps some remote permissions not enabled? Remote WMI? something? hopefully some rookie mistake...

1) I've turned the firewall of DR01 off (just in case, just until figure out this issue)

2) The hyperV virtual machine management service is running correctly on both Source01 and DR01

3) the HyperV console on Source01 can correctly connect to DR01 and view/manage the VMs in the console - and vice versa.

Anyone got any ideas? Or seen this behaviour before?

thanks

Joe.

I part-time manage a branch office IT infrastructure. (More formally, I am developer who has unofficially assumed the IT role.) There are other sites within the company running a common domain. Originally we were not connected  via site-to-site VPN to other sites, so we created our own separate domain. After a number of years things have changed and we are now connected and are moving our IT infrastructure to the common domain. This has been progressing for a few months, generally fairly smoothly.

We also have two Hyper-V hosts, one running Windows Server 2008 R2 Datacenter. I set it up a number of years back and until now have not had any problems. Recently I noticed one of our VMs that I had moved from the old domain to the new domain a few weeks back had failed to register its IP in the DNS. Checking the event log indicated KMS failures. I naively tried to re-activate it: slmgr /ipk 74YFP-3QFB3-KQT8W-PMXWJ-7M648. The screen turned black and indicated that Windows is not genuine.

I have checked several of the other VMs, but there does not seem to be any significant issues so far. Please note that the VM host is still in the original domain. Googling around I found this, I found this indicating to check the SRV record for _vlmcs._tcp. The domain had changed, so this was pointing to the old domain. (Still available if necessary.) I updated it in the new domain DNS. I have also verified that the VM host server is available over port 1688 via telnet.

I then ran the above slmgr /ipk again. It indicates that the key was successfully applied, but Windows still indicates that the environment is not genuine. I'd appreciate some help in resolving this.

Here is the output for slmgr /dlv on the Hyper-V VM host.

(Please let me know if this contains any keys that I should not post here and I will gladly edit it.)

---------------------------

And here is the same output for the problematic VM client.

====================

I am stumped here.

We have a Windows Server 2016 Datacenter Host, Hyper-V role, 8 Virtual Machines (all same OS as host).

One of these Virtual Machines is a Terminal Server for a number of users inside and outside the LAN. I'll call it TS-SERVER. TS-SERVER randomly reboots a number of times a week. It always logs Event 41, Kernel-Power, but I cannot find the underlying reason. Obviously this is a critical issue for us since 5-10 users can be logged into this VM at any given time, all of them losing any unsaved work every time it happens. 

I've browsed the event logs surrounding the times of the reboots, but I can't seem to pinpoint any related events.  No Bugcheck logged either. 

Any suggestions are appreciated. Thank you

In a very simple windows 2012 r2 RDS server there are two setting which seem almost the same. If someone could explain the difference that would be helpful.

Both are accessible from the RDS Overview panel.

#1 is found in the Deployment Overview panel where there is a RD Licensing icon. If one adds a RD License Server via that icon, the server will appear in the adjacent Deployment Servers list.

#2 is exposed via Tasks list when you choose Edit Deployment Properties. The four deployment properties that are exposed there include an entry for RD Licensing, which allows you to again specify the FQDN for a RD License Server and to choose between licensing per device or per user.

Original Issue: Was the VMMS services stops and starts every minute

Issue now: VMMS services is missing by running the vmms /regserver

On a Windows Server 2012 R2 host server how can we get the vmms service back into windows services? Can we do this without uninstalling the Windows Role Hyper-V.

What has happened is the  /regserver has deleted the service and we need to put it back any suggestions will be welcome.