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 playlist below is a three-part video series that takes a user through the process of using Azure Image Builder to create a custom Windows 10 multi-user image. The first video starts with an overview and configuring a subscription for Azure Image Builder. The second video demonstrates creating and deploying a template and building an image based on that template. The third video walks through the steps to add software to the image in the build pipeline.Continue reading “Azure Image Builder Trilogy”
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 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.
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.
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.
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.
The New-AzImageBuilderTemplate should run now without an error.