Create a Hyper-V NAT Switch with PowerShell – the easy way

You can follow the original guide by Microsoft and manually edit all the details, or just use the variables from the script below and let PowerShell do the work for you.
# Variables
$InternalSwitchName = "Internal Virtual Switch"
$NATGatewayPrefixLength = "24"
$NATGatewayNetwork = "192.168.0.0/$NATGatewayPrefixLength"
$NATGatewayIP = "192.168.0.1"
$NATNetworkName = "NAT Network"

# Create the VM Switch and NAT Gateway
New-VMSwitch -SwitchName $InternalSwitchName -SwitchType Internal
New-NetIPAddress -IPAddress $NATGatewayIP -PrefixLength $NATGatewayPrefixLength -InterfaceIndex (Get-NetAdapter -Name $("vEthernet ($InternalSwitchName)")).InterfaceIndex
New-NetNat -Name $NATNetworkName -InternalIPInterfaceAddressPrefix $NATGatewayNetwork

Dell Precision 5510: Six Months Later

Six months ago I received an email from our IT Department. Good news, my old 3.5 KG Dell Latitiude E6540 (with a big battery) was out of warranty. The Surface Pro wasn’t announced yet but because of the rumors, I didn’t want to go with a soon-to-be-old Surface Pro 4. And I must say I wanted a notebook that I can place on my Bobby Notebook Stand.

Bobby Notebook Stand
Picture Source: Ergo2Go.nl

I also didn’t want the standard models like the E7270 or E7470 with i5 and Full-HD. Because I sometimes need to run Hyper-V Labs at customers, I wanted a High Performance machine. I took the Dell Precision 5510 with the following specs:

  • Intel i7-6820HQ CPU
  • 15.6 4K Touch Screen
  • 16 GB memory which is expandable to 32 GB
  • NVIDIA Quadro M1000M
  • 512 GB SSD

The 4K screen is absolutely gorgeous! Windows 10 scales much better in 4K than before and works great with Server 2016 in RDP. If you RDP a lot to older Operating Systems, I can recommend to scale back to Full HD. I also recommend not to sit in full sunlight because of the glare.

The device is absolutely silent in idle. Isn’t that always the case when a device is in idle?! Let me tell you that I’ve worked with several devices from different vendors and it’s not. Of course you will hear the fans when you spin up a Hyper-V Lab but it’s still not bad.

The case itself with the thin bezels, the aluminium design and the big touchpad is fantastic. The gestures from Windows 10 are working smooth and fast with the touchpad and the keyboard is solid.

So after six months I’m still happy with the Dell Precision 5510. Is there a device where I want to trade it for?! Yes, the Surface Book of course. 🙂

Dell-Precision-5510

Let me know what you think of the Precision 5510!

Cheers.

Unknown Devices when installing Hyper-V on Windows 10

The following unknown device IDs will pop-up when you run the script or when you open Device Manager:

ROOT\VMBUS\0000
ROOT\VID\0000
ROOT\VPCIVSP\0000
ROOT\STORVSP\0000
ROOT\SYNTH3DVSP\0000

If you want to find all Unknown Devices, open PowerShell as an Administrator and run:

Get-WmiObject Win32_PNPEntity | Where-Object{$_.ConfigManagerErrorCode -ne 0} | Select DeviceID

On my work notebook, all drivers were correctly populated so it had to be something with my test laptop. It’s a fresh Windows 10 machine deployed by a Task Sequence – enabled with Device Guard and Credential Guard.

Solution:
During the installation I’ve installed the Microsoft-Hyper-V-Hypervisor feature on Windows 10. You also need to install the Microsoft-Hyper-V-Services if you want to have those drivers installed as well.

Lock screen image not showing – Windows 10 1703

Recently I was trying to apply a lock screen image with a GPO. I distributed the image to the C:/Windows/Web/Wallpaper directory and configured the Windows 10 GPO to that location. After running the Windows 10 Task Sequence successfully, the default lock screen image came up. I was using a large image from the client so that it still looks good on bigger screens. I’ve found out that after resizing the image back to 1080P, the image was applied successfully after locking the machine. Looks like a strange bug if you would ask me.

Cheers!

Windows Autopilot – Configure OneDrive from OOBE?!

Windows AutoPilot OneDriveRecently Microsoft introduced Windows Autopilot. This is a feature where you can register your corporate devices and where users can use their internet connection to sign in with their Azure AD credentials. The device is automatically enrolled with MDM like Intune and will receive apps and policies from there. According to Microsoft’s recent blog post and instruction video, a user needs to insert their WiFi password as the device will get the configuration from MDM and is already enrolled, without having the option to change the MDM provider or enroll the device as a personal device. The device really becomes a corporate-owned device. This looks a bit like the Apple Device Enrollment Program. One of the interesting parts of that instruction video, is that it looks like OneDrive can be pre-configured from OOBE as well:

WindowsAutoPilotOneDrive.PNG

I hope that Microsoft will further expand the possibilities of this service. What I would like to see is that the device can cache/download applications and settings from Intune during the factory imaging process. This ensures that applications, policies and settings are pre-loaded on a device and don’t need to be downloaded anymore. This will dramatically decrease network bandwidth and deployment time.

Azure AD Domain Services now available from the Azure Portal!

Today I found out that Azure AD Domain Services is available from the new Azure Portal! The documentation is still based on using the old portal. Now you can finally use Azure Resource Manager for the VNET and deployment. Creating your first Azure AD Domain Services instance will take quite some time but is really easy to configure. Specify the DNS name of the domain, a resource group, a VNET with subnet and a subscription and you’re good to go. Enjoy this feature in the new Portal!