Hello,
Welcome to another blogpost about my friends from Nerdio.
Have you ever tried installing Nerdio Manager for Enterprise and have errors while doing it? You are probably not alone.
To install Nerdio Manager for Enterprise, you need Global Admin and Owner permissions. It might be that you have these permissions but that the deployment still fails. This can be for a variety of reasons ranging from lack of tags, specific config for the resources that are needed.
One of the things that can help you plan the deployment, is the Pre-Flight script from Nerdio. Look at it from a pilot perspective, you check all the plane systems to make sure everything is functioning correctly before take off.
Resource group
I choose to create the resource group in advance. For this example I take a random named resource group. It might be that in your environment you have a specific naming convention.
First thing to do is to open the Azure CloudShell and select PowerShell.
Now enter the below command to clone the GitHub repo where the script is located.
The next step is to navigate to the folder that contains the preflight script.
to run the script you need to add the following parameters.
- Subscription id
- Resource group that you created (optional)
If you don’t provide the resource group the script will ask to give a name so it can create the resource group.
During my test I got the blow error. The Microsoft.PowerShelle.consoleGuiTools module wasn’t installed.
Lets type y to start the process. The first option is to include the resource provider checks. When using a new subscription this is a good check to do. As you can see in below screenshot, the script discovered some providers that weren’t registered on my subscription.
Especially in larger, controlled environment, it’s possible that Azure policies will block resources to be deployed. Some of these can be:
- Default tags on resources
- No public resources allowed
- No local admin on SQL
You will see all the resources in the specified resource group that the script created.
After the testing, you have the option to delete all the created resources again. I advise to do this to avoid unwanted Azure costs.
Having the option to test the deployment is a very cool feature. It happens a lot that deployments fail and it can cause frustration for the people doing the deployment.
See you later for my following Nerdio and AVD blogpost.