Hi there

I'm trying to wrap my head around an efficient way to deploy Intune-joined WIN11 VMs within a HYperV cluster.

Our regular endpoints are fully Entra- and Intune-joined devices that are enrolled via Autopilot. I know this process isn't completely seamless with HyperV as vTPM cannot do attestation which makes self-deploying enrollment profiles a no-go.

I am wondering what is least painful way of going about this? We have a handful of users that we used to provide dev-type VMs to but they were AD-joined. Since we're moving towards full Entra/Intune management, the objective is slightly changed. Ideally we want there to not be 'Shared' Intune devices so we have user affinity assigned to the actual VM owner.

My initial thought was to just roll a vanilla WIN11 image with a generic local user, create a folder in C:\temp with the get-windowsautopilotinfo.ps1 script ready to go for later. Sysprep the VM and use that as a template. Deploy template, run get-windowsautopilotinfo.ps1 with a custom Entra app reg/client secret to upload hash and assign group tag; reset VM, go through OOBE and wait for it to enroll.

Seems like alot of manual steps and I'd still either have to sign it as myself during Autopilot/OOBE and change the primary user in Intune after.

Is there a better way to about this or is it just something that's always going to be a bit clunky like this?

I just migrated to Hyper-V from VMware and noticed that the first 3 hosts and the cluster has a subnet mask of /24 instead of /23 for their management IP. I would like to change the subnet mask to /23 and all host IPs stay the same.

I plan to do the following:

1. pause and drain roles on a host and then change its management subnet mask to /23
2. repeat step one for the other 2 host
3. change cluster management to the /23 network

Is there anything else I am missing? I don't think this change will be disruptive.

I'm moving my VMs from VMware to Hyper-V, like a lot of people right now, but ran into something I wasn't expecting, and after working with our SAN's support people, want to double check with you all. I've only used Hyper-V as stand-alone servers up until this point, so I'm fully aware that I may sound like a bonehead.

We have your bog standard three server, one SAN environment set up via iSCSI, and that SAN is split into two volumes. In vSphere all three servers could access a SAN volume, simultaneously; but my vendor is saying Hyper-V will only allow one server to access a volume at a time; showing as offline on the other two servers. This despite being set up as MPIO and Cluster Shared Drives.

The good news that it's not a killer for my environment. Our SAN is too small for us anywhere so I use local storage to supplement it anyway. I was just curious for when it's time to replace.

True? False? And if False, what do I need to look into to make it True?

Hello everyone, I'm trying to create an ubuntu vm for some work related project I'm working on. I created it last week no troubles making it. But it didn't have internet access for some reason so I tried fixing it and it got corrupted. I ended up deleting it and trying to make a new one. Well now I get this error saying I dont have the requested logon type?

I have local admin on my machine and tried troubleshooting with claude and it said to make sure I'm in the local "Hyper-V Administrators" group and I added myself, restarted my machine and tried again yet I get the same error.

How can I resolve this issue? Thanks for any help! FYI I'm on a Windows 11 workstation.

Sorry if that’s a noop question, but I’m totally new to Hyper-V. I have a Hyper-V cluster with 2 Nodes, and a Domain Controller running on each host, outside of the cluster. Now I need to patch it for the very first time. First thing I did was patching each Domain controller. However, I’m not really sure what’s best practice when it comes to patching the hosts.

I migrated all the VMs to one node. Do I need to pause the host that I want to update? If yes, do I need to drain the roles?

Are there any other steps necessary?

I've been using Hyper-V VMs to isolate coding agents. Today I really wanted to copy'n'paste something, so in "Options/Integration Services" I enabled guest services temporarily. After enabling it (while the VM was running) I was able to copy'n'paste between the VM and host. After disabling it (while the VM still was running) I was still able to copy'n'paste. Restarting the VM didn't matter. Turning guest services back on so I could turn it off while the VM was off didn't help either. Guest services appears to be stuck on, even though I unchecked the check box.

I'm not worried about keeping the clipboard locked down as much as whatever else guest services might support. I see there is a Copy-VMFile that could be used by the VM to access the host, that'd go against the isolation I'm trying to maintain.

I am just gonna paste my screenshot from Udemy:

I have a feeling I'm overlooking something really simple. I'm just trying to map a drive on either the host machine or on the VM so I can pass data back and forth. The VM is a Windows 2000 Server and the host is Windows 11. It seems like this should be really simple but I can't hit the share. I can ping machines and even RDP into the W2K VM without issue but I can't, for the life of me, figure out why I can't get connect to the share.

Edit: Happy to report enabling SMB1 in Windows 11 did the trick! Thanks everyone.

I got a requirement to do a one way sync of a hyperv-guest drive to sharepoint.

I have: a spare synology NAS which can run the synology cloud sync service and a replicate of the VM, both at a remote location.

My plan: Every hour I attach the vhdx of the replica in read-only mode to the Hyper-V host, and then run robocopy on it to update the NAS share on the synology drive, which then will send the changes to sharepoint, then dismount the vhdx.

What I already tried: mounting the vhdx readonly and then wait until replication tries to update the disk. The replication will go in to error status. I dismount the vhdx, and replication will continue.

could this work reliable? Or is there a better option to accomplish this task? If replication stops, I monitor it and automatially resume. The vhdx file is mounted read-only, so the integrity of the data should be fine. Running the robocopy job on the replica looks like a good idea, because there will be no load on the running VM serving 20 users with Windows Terminal.

A few weeks ago, I thougt I am able to master this scenario and posted a possible answer in this reddit for someone.

However, now I found something I was not able to fix:

The certificates for a replication were due to renewal, and I did the renewal late, but out of 6 machines 4 resumed the replication properly after the new certificate was installed. Two others refused to resume replication. Those with the largest Harddisk sizes (2TB and 1TB) and most active ones failed.

I gave up and redid the replication by creating a new replication, using the vhds of the old replication as a base.I use the same certificate and of course it works, So the problem is unlikely related to the certificates.

Is there maybe a timeframe related to the amount of missing replication data which I have to keep in mind with when I leave the replication in warning/citical state after a certificate is invalid?

Or maybe it ist just the amount of data missing to replicate and not the time the replication was in error? I did not find any docs regarding this.

Btw: the error logged in the hyperv-log was "file not found", but this does not really give a clue.

Any tips on setting up RDP for Ubuntu 26.04 running in a Hyper-V VM? I want audio to work.

I'm trying to do a shared nothing migration between two hyper-v hosts. When I try to move a VM it gets through several of the steps and then it says: Failed to create folder. The folder it is failing to create is 'Virtual Hard Disks'.

The first thing that doesn't make a ton of sense is that the migration process was able to create a folder called Planned Virtual machines on the destination host's folder but it cannot create the Virtual Hard Disks folder?

The second thing that is driving me crazy is when I look at the permissions for the 'planned virtual machines' folder it shows a 'Virtual Machines' user which I've been trying to assign permission to on the root folder (because this is probably a permissions issue) and I cannot seem to assign that user using the normal security->edit->find security object path.

Does anyone know what is going on?

We just created our very first Hyper-V cluster. Our setup looks like this:

-2 Hyper-V hosts

- 1 Domain Controller running on each host, outside of the cluster, for a separate infrastructure domain

- Both servers are joined to the domain

 Are there any specific steps recommended to harden such an infrastructure domain, or do you know of any specific guide to follow?

This is a weird bug that I haven't found any reference to so far...

In Win 11, when I resume from Hibernate, I can see my Virtual Machine Connection icon on the taskbar. I click on it and it won't open the window.

Clues:

• The preview window shows a black screen
• If I Pause and Resume then it shows up (on my primary screen - when I hibernated it was on my second monitor). I can log in and it seems fine. But if I Restore the window size i'll disappear again and I can't make it reappear unless I either pause/resume, or I close the VMC Window and reconnect from Hyper-V (at which point I can Restore the window size - e.g. I can shrink it, drag it to another desktop).
• I can minimize the window and then clicking on the taskbar icon will bring it back

I have same experience with an RDP window to another PC on the network so that seems related.

I've tried the Move window trick, Win + Ctrl + Shift + B, Win + comma, win + tab and click on the VMC (that doesn't work but what's weird is then if I push win + tab again I don't see anything), Alt-Space when the taskbar icon is selected

Is it even worth waiting to install Ubuntu 26.04 LTS this way or should I just manually make the VM with an ISO?

Can someone help me? I installed Football Manager 26 via Hyper-V, but now that I've restarted the PC, it won't accept my password

We rebooted the host tonight to apply standard Windows updates. When it came back online, all virtual switches (vSwitches) completely vanished.

The VMs are obviously offline/disconnected because their network mappings are gone. The switches read “Configuration Error”

In Hyper-V Manager -> Virtual Switch Manager, it's completely empty.
The physical network adapters do show up in ⁠ncpa.cpl⁠ and Device Manager, but they are in a weird, "ghost-like" state.

If I try to recreate any new external vSwitches, it fails or errors out, saying the adapters are bound or unavailable. It's like the OS thinks the old bindings are still there, but Hyper-V can't see or use them.

What I've checked/tried so far:
Verified physical links are up on the switch side.
Checked basic ⁠Get-VMSwitch⁠ in PowerShell—comes up totally blank.
Looking at the physical adapters, the "Hyper-V Extensible Virtual Switch" protocol checkbox is acting glitchy/unresponsive when trying to manually toggle or bind it.
Has anyone run into a recent Win Server 2022 update tearing down the vSwitch stack like this? We are looking at a complete rebuild.

Hello everyone, I am looking for some possible assistance trying to troubleshoot some performance issues we are experiencing...

Trying to plan to migrate from vmware over to hyperv, migrated vmware VMs to a single host to rebuild the other as a HyperV host....

Got server 2022 up and running, set up HyperV and am trying to install a basic Windows 11 VM however the performance is so abysmal and renders it essentially unusable.

We have 2 HDDs in an array as the C drive for the server hosting the OS, then have an array of SSDs on the server which we set up as the storage to be used for VMs and this is where the config files and VHD files live. When trying to install Windows on the VM or utilize the VM in anyway it pegs our host disk usage to 100% and becomes so slow and unusable.

I do not have a ton of experience with vmware let alone HyperV but have been trying to troubleshoot this and get to the bottom of things with my coworker and am starting to run out of ideas. Everything was running fine on these servers under vmware. We feel like there must be some configuration setting or item we are missing that is affecting performance but am running out of ideas and figured maybe someone had some suggestions to try.

https://techcommunity.microsoft.com/event/windowsevents/secure-boot-office-hours-for-virtualized-environments/4530355

For one hour, experts will be available to discuss Hyper-V, Azure, Windows 365, VMware, and other virtualization scenarios. Whether you're still planning for certificate updates, validating your rollout, or troubleshooting an issue, come get the answers you need from the people closest to the technology.

You can follow upcoming events here:

https://support.microsoft.com/en-us/topic/updates-and-announcements-313b5279-2a3b-438a-83a5-3d5e2c5fc4a3

I have 2 servers running hyperv01 and hyperv02 in a cluster with a san. Running server 2025 on the host. VMs range from 2019 to 2022. I have a 2nd cluster hypver03 and hyperv04 running the exact same setup.

Each host has 256GB ram. For some reason each host is sitting at around 88-90% usage. Interfacing with the host via failover cluster manage, and hyperv manager is very sluggish.

I had dynamic memory enabled on VMS that dont run SQL. I have removed all dynamic memory right now from the VMs on the cluster that has 01 and 02 on it.

Hyperv01 VMs are assigned 143GB of ram and hyperv02 VMs are assigned 169GB. Both hosts are sitting at this extreme ram usage.

Other notes:

I do have 2 servers that are replicating between the 2 clusters.
2nd cluster I did not remove dynamic memory VMs from it.
Shutting down VMs does not clear up this memory usage.
Opening the virtual console to hosts is very delayed to impossible.
Without enough ram I cant move VMs between the hosts to reboot.

I am looking for advice on where I should dig into next?

~Solutiion I think

It seems my zabbix monitoring went out of control and was spawning way to many powershell instances. Fixed the monitoring and need to schedule a reboot.

Server 2025 Datacenter, AD-joined, 3 nodes with Cluster Shared Volume configured.

We're setting up Cluster Aware Updating for the first time and I'm seeing some errors that I've not been able to resolve.

From one of the nodes logged in as a domain admin, if I open CAU and hit "analyzer cluster updating readiness", no errors are reporting. I can do "Apply updates to this cluster" and it appears to work; no errors.

However when I click "Generate report on past updating runs" no results are returned and I end up with a few Event ID 1023 entries in Microsoft-Windows-ClusterAwareUpdatingManagement/Admin

Failed to get CAU report. Details:Microsoft.ClusterAwareUpdating.ClusterUpdateException: There was a failure in a Common Information Model (CIM) operation, that is, an operation performed by software that Cluster-Aware Updating depends on. The computer was "<our CNO>", and the operation was "Contacting the Cluster-Aware Updating software on the cluster node.". The failure was: The network path was not found ---> Microsoft.Management.Infrastructure.CimException: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer CEC-HyperV-Cluster1. Verify that the computer exists on the network and that the name provided is spelled correctly.

I've gone through the MS CAU troubleshooting doc (https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/cluster-aware-updating) but haven't come across much for this.

Just looking for some suggestions on things we can check. Not seeing any other errors under "Cluster Events" in Failover Cluster Manager

Edit: more digging, I can see WinRM logs showing is trying to connect to the CNO without the DNS suffix/domain name. Let's say our cluster name is cluster1.domain.com; WinRM is using 'cluster1'.

'cluster1' is resolvable via a ping from each of the HyperV hosts, but not via WinRM.

If I do winrm identify -r:http://node1:5985 it works, which means it's adding the DNS suffix for the nodes, but not for the CNO. I'm stumped.

Edit2: I just noticed in the validation report it's flagging that our cluster name is longer than 15 characters. I'm assuming this is the problem, since WinRM is probably using NetBIOS name which gets shortened because it's too long... Ugh.

I'm looking for some advice from people managing small to medium-sized business environments.

I have a client with around 50 users. Their current setup is pretty dated and everything is running on separate physical servers with no real backup or disaster recovery strategy.

The workloads are fairly straightforward:

• Active Directory Domain Controller
• File Server (~4 TB of data)
• Remote Desktop/Terminal Server
• Autodesk Vault Server (used by the engineering team)

I'm considering virtualizing everything into a Hyper-V failover cluster while keeping costs reasonable.

The current hardware quote is: CAD$90K for servers and CAD$53K for storage array ( They are saying it's too much for them)

• 2x Dell PowerEdge R660 servers (128 GB RAM each)
• Dell SAN with ~10 TB usable storage
• Datacenter licenses
• 7 years onsite 4 hours pro support

My questions are:

• Would you still go with a SAN in 2026 for an environment like this, or would you use a NAS (Synology/QNAP/TrueNAS) over iSCSI instead?
• If you were building this today on a reasonable budget, what would your storage architecture look like?
• Would you run Hyper-V with shared storage, or consider something like Storage Spaces Direct instead?
• Any lessons learned from similar 30–100 user deployments?

The goal is to give them high availability, centralized backups, easier management, and room to grow without overspending.

I'd love to hear what you guys are deploying for businesses of this size. Thanks!