Windows Autopilot - Fixing Windows 11 VM 'No Internet' issue hosted in a Windows Server OS Hyper-V

-
In my line of work, I have to work with all kind of devices spread across multiple OS platforms. Now when it comes to building and testing a configuration on Windows endpoints, I would normally use a physical device or in absence of it, I will turn to a virtual setup involving a Windows 10\11 VM or most recently a Cloud PC. For sometime now, I have been hosting the Windows 10\11 VM in a Hyper-V installed on a Windows 10 Azure VM enabled & configured for nested virtualization. While this got the job done, it couldn't really match the performance of what Hyper-V running on Windows Server OS could deliver. I recently setup a new test tenant and used it as an opportunity to cleanup and introduce some new configurations. I decided to setup a Windows Server 2022 OS VM and installed Hyper-V on it then created the guest Windows 11 VM inside it. While I followed the usual steps of putting the configuration together like I did before, I did encounter some issues and learnt some new things along the way. It didn't seem as straight forward as one would have hoped for so I decided to capture the details and my overall experience in this blog post.

The Issue..

Let me dive straight into the issue. After creating the Azure Windows Server 2022 OS and installing Hyper-V followed by creating the Windows 11 23H2 VM, I immediately noticed the issue where Windows 11 VM didn't have any internet connectivity.


This is obviously not ideal especially if you are trying to provision the VM using Autopilot which relies solely on internet connectivity. So how did I reach to this point where the VM didn't have internet connectivity? A bit of research led me to the fact that unlike in Windows 10\11 Hyper-V where a Default Switch is created by default for the purpose of assigning IP addresses by allowing NAT through the internal switch and DHCP, the same is done through either an internal or external switch in Hyper-V session running on a Windows Server OS. In other words, the NAT configuration on a Windows Server OS running a Hyper-V needs to be created separately and this is done by the means of running some PowerShell commands.

Fix..

I ran the following commands to create NAT and configure a NAT switch for Hyper-V.

New-VMSwitch -SwitchName "NATSwitch" –SwitchType Internal


Get-NetAdapter (Run this to identify the Interface Index for assigning of IP Address)


New-NetIPAddress –IPAddress 192.168.0.1 -PrefixLength 24 -InterfaceIndex 108 (I am using 192.168.x.x as an example here.)


New-NetNat –Name MyNATnetwork –InternalIPInterfaceAddressPrefix 192.168.0.0/24


The NAT switch adapter should be visible in both Network adapters and Hyper-V switch manager. Make sure you assign the newly created NATSwitch to your Windows 11 VM.



That's it. Now you should be able to assign a static IP to the VM from the same subnet that was configured for NAT switch.

When in OOBE stage, press shift + f10 to bring the command prompt and type start ms-settings:


Navigate to Advanced network settings under Network & Internet.


Bring up the Internet Protocol Version 4 TCP/IPv4 settings under More adapter options.


Enter the IP from set NAT IP address range as shown below.



You should now have internet connectivity on the VM. You can run test-netconnection in PowerShell to check for internet connectivity.


Hope this post helps and saves you from a bit of trouble in setting up a similar configuration. Until next time..

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more