Forum Widgets
Latest Discussions
SCVMM/Hyper-V Manager/Powershell not able to apply Microsoft NDIS Capture virtual switch extension t
Hello all, As title implies, I cannot enable Microsoft NDIS Capture virtual switch extension on my new Server 2022 core Hyper-V hosts. We primarily manage VMs via SCVMM. Our server 2019 core hosts on the same hardware do NOT have this issue. I'm posting to: A) Understand what this extension really does, my understanding is it enables "packet capture" or "virtual port spanning" which my virtual environment DOES require, as we use DarkTrace v-sensors on all our hosts for IPS/IDS. We enable this by going into failover cluster manager and setting port mirroring to "source" for all our VMs and "destination" for all the v-sensors. I'm unsure if this will continue to work as intended if the NDIS capture extension isn't checked. B) See if anyone else has had this issue or resolved it. If I try to enable via Hyper-V manager, it simply states that "the selected extension isn't working correctly. Check the event logs for further information (There are no event logs to correlate). If this is a non-Microsoft extension, contact the vendor (it IS in fact, a microsoft extension. "Microsoft NDIS Packet Capture Filter Driver Company: Microsoft Version: 10.0.20348.1"). If I attempt to enable via powershell (enable-vmswitchextension -name "Microsoft NDIS Capture") it will start for a time, and then stop again. If I use SCVMM to apply the logical switch to the host, it will successfully apply the switch, but throw an error with the host being non-compliant. As follows: Warning(26846) Eithertheswitchextension'MicrosoftNDISCapture'withdriverID'ea24cd6c-d17a-4348-9190-09f0d5be83dd'wasnotinstalledonthehost,orVMMwasunabletoenumeratetheextension'sdriverversionanddriverID.Theswitchextensionisrequiredforthisvirtualswitch. Obviously, the logical switch has that driver selected to be enabled, but the hosts cannot enable it for some reason. What's interesting is that "driver ID" that SCVMM is reporting (ea24cd6c-d17a-4348-9190-09f0d5be83dd) is NOT the driver ID that is present on the Host. Running "get-vmsystemswitchextension" on the host reports the following: Id : 430BDADD-BAB0-41AB-A369-94B67FA5BE0A Name : Microsoft NDIS Capture Vendor : Microsoft Version : 10.0.20348.1 ExtensionType : Monitoring CimSession : CimSession: . ComputerName : HOST-Q-02 IsDeleted : False Im at a loss here. Ideally, I can just get this enabled in case it is needed. Alternatively, if I can determine that the extension is NOT needed... Im "ok" with not having it enabled.... but you never know when my org will add something that needs it.
ASCHI cluster different RAM amounts per node
is it a supported model for ASHCI to have 1 node in a cluster to have different amounts of RAM? i appreciate that you can specify preferred owners, and possible owners on VMs, to restrict/ allow VMs to go to specific hosts, and understand that under normal circumstances you probably wouldnt want to have hosts with different amounts of RAM to circumvent over provisioning and then getting into difficulties upon loosing hosts, but am looking at making one of my ASHCI hosts a SQL server, i dont want to remove it from the cluster due to impacting storage, but need to increase the RAM, and if i can do it to just a single host id prefer that.Creating a test environment similar to prod - how to license?
Hi, We want to create a test environment to avoid "system wide" settings deploy to production without testing them first (e.g. Kerberos Enforcement or Entra Sync Settings) We would use Windows Trial licenses and Entra Connect to connect to a Testtenant. How must we license this test environment to be compliant with MS licensing? Some say it's Trial and not production "you do not have to". Others say we need to license "like Prod". Can anyone (preferably a Microsoft employee) help with this question? BR StephanASHCI cluster with different RAM amounts
been looking through server requirements and things, and i cant see a definitive answer of whether i need to have the same amount of RAM per ASHCI host. i appreciate it may not be best practice due to failing over VMs within the cluster, and being in a position where you over provision RAM and could end up in a sticky situation, but given that you can not only set preferred owners, but also have the ability to set possible owners, you should be able to account for that. tldr: ASHCI cluster can i have have one node with 4TB of RAM and 5 nodes with 2TB of RAM
DNS record auto registered even the auto registration option was unchecked
Hello guys, I have an DC which have two NICs, A for Domain service and B for camera server. I don't want the IP address of NIC B registered in our DNS, so I uncheck the auto register option in the advance setting of NIC B. However, the IP address of it still keep registering t our DNS even I have manually deleted that option. I have checked the steps in the official article and it doesn't help. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/unwanted-nic-registered-dns-mulithomed-dc Any suggestion is much appreciated.
Windows Server 2025 | Kerberos Local Key Distribution Center (LocalKDC) service fails to start
I have found that this service was disabled before the December update, for some reason it has gone to automatic and cannot be started, maybe this behavior is normal if you are not using this feature. After the January security patch the service still does not start, I think microsoft should report this problem. This happens on a clean installation without any role installed, I know there are many users with this problem. The January patch has not fixed it.
Hyper-V NIC Configuration Question
I am about to build a new Windows 2025 Standard Edition server with 2 Ethernet ports and Hyper-V. Should I configure the 2 NICs as a teamed NIC that is shared with Hyper-V, or dedicate one NIC to Windows Server 2025 and the other NIC to Hyper-V? Or is there another recommended configuration? Thank you.
Hyper-V "Planned Virtual Machines" directory
Hi Folks, Search attempts failed me, apologies if this is covered elsewhere. Environment: I have a standalone Hyper-V host with partitions: C:\ [OS] 80GB D:\ [Data] ~900GB Hyper-V Default Folders have been updated: Set-VMHost -VirtualMachinePath 'd:\HyperV_VM' Set-VMHost -VirtualHardDiskPath 'd:\HyperV_VM' Issue: Using Windows Admin Center, I attempted to import a previously exported VM located on D:\archive\ During the attempt, my C: drive was nearly completely consumed. Trouble Shooting / Observations: The export includes: - vhdx >100GB - VMRS >16GB I attempted the import 3 times, during each attempt the verification stage was completed but the "import" button remained grayed out. The last attempt triggered a low disk space warning. During the importation process, the VM is staged under: C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines\ I now have 3 copies of the VMRS file in "Planned Virtual Machines" The files are locked, I will try to reboot (or use safe mode) to access and delete the staged VMRS files. Questions: During the importation process, is the VHDX transferred to "Planned Virtual Machines" directory? If so, this would explain the import failures; there is not enough space on the c:\ drive to temporarily host the vhdx. Is there a way to safely change (all) default "Planned" staging folders to the 😧 drive? I did not see a PowerShell setting, but it ma Any other advice to avoid this situation? I appreciate the help.WS2025 - LocalKDC Service Stopped
I have found that this service was disabled before the December update, for some reason it has gone to automatic and cannot be started, maybe this behavior is normal if you are not using this feature. After the January security patch the service still does not start, I think microsoft should report this problem. This problem occurs in a clean installation without any role installed or configured. If you try to start the service it shows the following error
