High Performance at a Low Price for WVD

In this post and accompanying video, we go over the benefits and considerations of using ephemeral disks with Azure Windows Virtual Desktop Session Hosts.  We review the performance improvements as well as limitations that come with ephemeral disks, including the inability to deallocate Session Hosts.  Next, we examine Azure Reserved Instances and how they can be used to keep the cost of Session Hosts down without using an auto scale solution.

Continue reading “High Performance at a Low Price for WVD”

Starting Lab Computers with Stream Deck, a Webhook, and an Azure PowerShell Function

This video is a step-by-step introduction for using an Elgato Stream Deck to send a Webhook that starts or stops computers in Azure based on their tag settings.  We go over creating the Azure Function App, setting up system assigned identities and creating a custom RBAC role in Azure to grant the identity permissions to the subscription.  Then we configure the start stop function to use values passed in from the web hook to start or stop the computers.  Finally, we configure the Elgato Stream Deck with start and stop buttons that control the lab.

Continue reading “Starting Lab Computers with Stream Deck, a Webhook, and an Azure PowerShell Function”

Azure Automanage now in Public Preview

In this post and accompanying video, we go over Azure Automanage.  Automanage is an Azure solution to automate management of IaaS servers within the Cloud Adoption Frameworks best practices.  This post gives an overview of the services.  The video reviews the service and provides a demonstration of on-boarding a server.  After that, we go on to review settings on a server that is part of Azure Automanage.

Continue reading “Azure Automanage now in Public Preview”

Please Wait for the Windows Modules Installer

I do not like to wait; who does?  So, getting a ten-minute delay logging into VM’s with the message “Please Wait for the Windows Modules Installer” was frustrating.  There is a way to speed this up, and that is what this post is about.  In this post and accompanying video, I show you how to bypass this message when creating a custom image, including with Azure Image Builder.

Continue reading “Please Wait for the Windows Modules Installer”

The subscription is not registered to use namespace Microsoft.VirtualMachineImages

I am finally getting around to some hands-on with Azure Image Builder.  More to come on that shortly.  For now, I want to document my first issue for anyone who may experience the same problem.  When creating the image builder template with the New-AzImageBuilderTemplate command, I got the following error message:

Az.ImageBuilder.internal\New-AzImageBuilderTemplate @PSBo …
The subscription is not registered to use namespace ‘Microsoft.VirtualMachineImages’. See https://aka.ms/rps-not-found for how to register subscriptions.

The subscription is not registered to use namespace 'Microsoft.VirtualMachineImages'
Subscription not registered

The error indicates that a required resource provider, Microsfot.VirtualMachineImages in this instance, is not registered.  The provider can be registered with PowerShell or through the portal.  Below are the steps for each.

From the portal, go to your Subscription, then find Resource Providers under Settings.

Resource Provider in the Azure Portal
Resource Provider in the Azure Portal

Search for the resource provider Microsoft.VirtualMachineImages.  Notice the status is Not Registered.  Click the Register button in the portal to register the resource provider.

Resource Provider Not Registered
Resource Provider Not Registered

To register a provider from PowerShell, log into Azure with rights to register a resource provider, such as subscription admin.  Next, use the Register-AzResourceProvider command below to register the provider.

Register-AzResourceProvider -ProviderNamespace Microsoft.VirtualMachineImages

The provider will go to a state of registering.  It could take a few minutes for the service to register.

Resource Provider Registering
Resource Provider Registering

From PowerShell, use the command Get-AzResourceProvider to verify the status.

Get-AzResourceProvider -ProviderNamespace Microsoft.VirtualMachineImages

Once finished, the resource provider changes to the Registered status.

Resource Provider Registered
Resource Provider Registered

The New-AzImageBuilderTemplate should run now without an error.