close

hyper‑v

Azure Copilot Migration Agent: AI-assisted migration planning for VMware, Hyper-V, and bare-metal servers

Azure copilot migration agent (image microsoft)

Azure Copilot Migration Agent is a new AI agent built into the Azure portal that assists with planning migrations from VMware, Hyper-V, and bare-metal servers to Azure. It works on top of Azure Migrate data and goes beyond answering questions: it can actively create business cases and assessments, apply tags to discovered servers, and generate deployable landing zone templates — all through natural language prompts. What it cannot do is execute the actual migration. Replication, test migrations, and cutover are performed in the Azure Migrate portal, not through the agent. The agent is currently in public preview.

Azure Copilot Migration Agent: AI-assisted migration planning for VMware, Hyper-V, and bare-metal servers Read Post »

Microsoft Teams VDI optimization: migrating from WebRTC to SlimCore (VDI 2.0)

SlimCore networking architecture (image Microsoft)

Microsoft is retiring the legacy WebRTC-based optimization for Teams in Virtual Desktop Infrastructure (VDI) and replacing it with a new architecture called SlimCore — also referred to as VDI 2.0 — introduced in Q4 2024. The change affects Windows endpoints connecting to Azure Virtual Desktop (AVD), Windows 365, and Citrix, with defined End of Support and End of Availability milestones. In parallel, Microsoft has announced a public tech preview of the new optimization for Omnissa Horizon. This article covers the architectural differences, supported platforms, new features, and the steps required to complete the migration.

Microsoft Teams VDI optimization: migrating from WebRTC to SlimCore (VDI 2.0) Read Post »

How to install Windows Admin Center vMode on Windows Server 2025

Windows Admin Center vMode (image Microsoft)

Windows Admin Center (WAC) vMode (Virtualization Mode) is a current in-preview management gateway for Hyper-V environments, deployable as a stateful appliance with an integrated PostgreSQL database. Unlike aMode (Administration Mode), vMode targets centralized virtualization management across multiple hosts and clusters, without requiring System Center Virtual Machine Manager (SCVMM). The only mandatory prerequisite is the Microsoft Visual C++ Redistributable. This article covers the system requirements, environment preparation, and installer walkthrough for vMode, and briefly explains how aMode installation differs.

How to install Windows Admin Center vMode on Windows Server 2025 Read Post »

S2D and SAN coexistence in Windows Server failover clustering for Hyper‑V, SQL Server, and file services

Failover Cluster Manager displaying healthy S2D virtual disks and storage pool details (image Microsoft)

Organizations running modern data centers increasingly need flexible storage architectures that balance performance, resiliency, and investment protection. With Windows Server 2022 and Windows Server 2025, Microsoft now enables true S2D and SAN coexistence—allowing Storage Spaces Direct (S2D) to operate alongside traditional SAN storage within the same failover clustering environment. This mixed-storage approach lets IT teams optimize workloads such as Hyper-V, SQL Server, and file services by combining high-performance local storage with existing enterprise SAN infrastructure, all while maintaining full cluster support and operational consistency.

S2D and SAN coexistence in Windows Server failover clustering for Hyper‑V, SQL Server, and file services Read Post »

New Windows Admin Center virtualization mode (vmode) vs VMware vCenter Server

Windows Admin Center Virtualization Mode architecture (image Microsoft)

Microsoft announced a new virtualization mode in Windows Admin Center, specifically designed for managing Hyper-V infrastructure. This mode allows centralized control of hosts, clusters, storage, and networking. Positioned as Microsoft’s alternative to VMware vCenter Server, this new mode complements the existing administration mode by focusing specifically on large-scale virtualization environments.

New Windows Admin Center virtualization mode (vmode) vs VMware vCenter Server Read Post »

Enable NIC Teaming (LBFO) and Switch Embedded Teaming (SET) in Windows Server 2025

Add a new NIC Team

In Windows Server 2025, LBFO NIC Teaming is blocked for Hyper-V virtual switches, and Switch Embedded Teaming (SET) is the only supported teaming method for Hyper-V. However, LBFO remains available for non-virtualization use cases. In this article, I’ll show you how to enable and configure both LBFO and SET in Windows Server 2025 using the GUI and PowerShell.

Enable NIC Teaming (LBFO) and Switch Embedded Teaming (SET) in Windows Server 2025 Read Post »

Migrate Hyper-V from Windows Server 2019 Core to Windows Server 2025

Exporting Virtual Switches

Migrating a Hyper-V host from Windows Server 2019 Core to Windows Server 2025 requires attention beyond just the virtual machines. The host’s configuration is equally essential and includes network cards, vSwitches, and default paths, all of which need to be transferred accurately. Using Windows PowerShell, you can export key settings and restore them on a new server.

Migrate Hyper-V from Windows Server 2019 Core to Windows Server 2025 Read Post »

Activate Windows authentication with a PIN

In A Remote Desktop Session, All Alternative Sign In Methods Are Unavailable

Entering a PIN is one of the authentication methods available through Microsoft’s Windows Hello. It offers a simplified sign-in experience, especially for devices that lack biometric capabilities. This option must be explicitly enabled in domain-joined environments or those using Entra ID. However, its functionality is significantly restricted on virtual machines hosted on Hyper-V.

Activate Windows authentication with a PIN Read Post »

WindowsUpdatePreventer
Scroll to Top