You should review all the following Nerdio Manager installation preparation steps before you start the installation.
Nerdio Manager uses specific App Service SKUs. Therefore, you must check your quotas before installation.
To check your quotas:
-
In the Azure portal, open the “App Service plan quota” for the subscription and region you are using.
-
Confirm there is quota for the following:
-
General App Service plan VMs (overall limit).
-
B3 SKU (used for the main Nerdio Manager application).
-
-
If you do not have enough quota, log a support ticket with Microsoft to increase it in the target subscription and region and notify Nerdio.
-
You need capacity for:
-
3 × B3 instances (main Nerdio Manager app, Intune Insights (optional), Realtime Insights (optional)).
-
1 × P0v3 instance (Cost Attribution (optional)).
-
Note
Ask for at least this much capacity when requesting quota.
Nerdio Manager’s deployment readiness script (Test-NmeDeploymentReadiness.ps1), also known as the pre-flight check, tests your Azure environment before you install.
Note
The deployment readiness script replaces the earlier pre-flight script and the Kusto query for finding policies with a Deny action. Both are no longer available.
The script accomplishes the following:
-
Confirms that the account you sign in with has the Entra ID and Azure roles that the installation requires. See Architecture and permissions.
-
Deploys temporary copies of the resources that the installer creates, using the installer's exact SKUs and configuration, to find any Azure Policy that would block the installation. If a policy blocks a resource, the script reports the name of the policy.
-
For private deployments, tests private endpoints, private DNS zones, App Service VNet integration, and outbound connectivity.
-
Removes everything it created when the test finishes.
-
Produces an HTML report that you can send to your Nerdio Solutions Engineer.
Important
The script requires the Owner role on the target subscription, so that it can create and remove the test resources. Nothing is deployed until you confirm a summary of what the script will do.
To run the deployment readiness test:
-
In the Azure portal, sign in with an account that has the roles described in Architecture and permissions, and then open Azure Cloud Shell in PowerShell mode.
-
Run the following command:
$s=New-Object Net.WebClient; & ([scriptblock]::Create($s.DownloadString('https://raw.githubusercontent.com/Get-Nerdio/NME-SE/main/preflight/Test-NmeDeploymentReadiness.ps1'))) -
When prompted, enter the subscription ID, the region, and whether to create a temporary resource group. For a private deployment, also enter the details of the existing VNet and its two subnets: one for private endpoints and one for App Service VNet integration.
-
Review the summary of what the script will do, and then confirm that you want to continue.
-
When the test completes, review the report that is displayed in the console. Cloud Shell downloads the HTML report (
NmeReadinessOutput.html) automatically. Send it to your Nerdio Solutions Engineer, and resolve any items that are marked as failures before you start the installation.
Note
To run the test from a local PowerShell 7 session instead, or to see all the parameters and requirements, see the Nerdio Manager preflight tools readme. If policy in your environment denies creating resources with public network access, run the script with the -PrivateEndpointOnly parameter.
This helps your team understand what Nerdio will deploy and which permissions are needed.
-
To perform the install, sign in to the Azure portal with:
-
Entra ID role: Global Administrator (or Privileged Role Administrator + Cloud Application Administrator).
-
Azure role: Owner on the subscription where you install Nerdio Manager.
-
The resources that are deployed in the Azure subscription are:
-
Automation account
-
SQL Server + SQL Database
-
Key Vault
-
App Service + App Service Plan
-
Application Insights
-
DPS storage account for encryption keys (Nerdio Manager v5.5 and later)
-
-
-
Hardened installs have an additional requirement to create a new VNet
-
Architecture diagrams and overview. See Nerdio Manager for Enterprise reference architecture for details.
-
Required permissions for install, configuration, and ongoing use. See Azure Permissions and Nerdio Manager for details.
Note
We recommend that the person who performs the installation has the roles described in the permissions article.
Nerdio Manager and your AVD session hosts must be able to reach certain Microsoft and Azure endpoints.
-
For AVD session hosts, confirm outbound internet access matches. See Required outbound internet access from AVD session host VMs for details.
-
For the Nerdio Manager App Service, confirm required external endpoints are reachable, and configured correctly if you use VNet integration or firewalls. See VNet integration firewall requirements for details.
Comments (0 comments)