Manage VM Extensions with Nerdio Manager
Nerdio Manager leverages Azure VM extensions for various administrative and monitoring tasks. These extensions often require specific data files such as PowerShell scripts, zip archives, installers, and executables. A new App Service setting Artifacts:Mode has been added to control how these files are consumed during Nerdio Manager operations.
Deployment Mechanism (prior to v6.2)
In Nerdio Manager versions prior to v6.2, the necessary files used in image management and host deployment were uploaded to the Azure Storage account nmwextensions.blob.core.windows.net. VMs would directly request these files from the storage account. This remains the default approach for all deployments prior to v6.2, even after updating Nerdio Manager.
Deployment Mechanism (v6.2)
Starting with Nerdio Manager v6.2, the "Local" deployment mechanism was introduced. This is the default configuration for any new deployments from v6.2 onwards. This setting requires that only the Nerdio Manager WebApp has access to the nmwextensions.blob.core.windows.net public location. Access from desktop and image VNets is not required.
Scripts are now included in the Nerdio Manager package.
These scripts are uploaded to the private storage account as needed by Nerdio Manager.
-
Links and metadata for the uploaded files are stored in the ArtifactMetadata database table.
If Artifacts:Mode is set to "Local," the new mechanism is applied.
If Artifacts:Mode is not set to "Local," files are loaded from the location nmwextensions.blob.core.windows.net, as in the previous versions.
Private Storage Account
The private storage account is used as the source for scripts (v6.2) and binaries (v6.3+) required for the image management and host creation process if the App service setting is configured in either Local or Offline mode. The private storage account is identified with the following tag:
NMW_OBJECT_TYPE=CUSTOM_SCRIPTS_STORAGE_ACCOUNT
This account may be pre-created by the customer in the same resource group as Nerdio Manager is deployed to. If this storage account does not exist, it is created automatically. Files are uploaded at the time of first use or upon Nerdio Manager version updates. If a file has already been uploaded, the existing link is used.
Deployment Mechanism (v6.3 and later)
"Local" Mode Changes
Starting with v6.3, Nerdio Manager also uploads dynamically discovered FSLogix installation files to the private storage account if "Local" mode is selected. These files are copied to the defined private storage from a public source by the Nerdio Manager WebApp.
Note: The Winget package installer, which is required for UAM application deployment, is not included in the package due to size limitations. In "Local" mode, Nerdio Manager copies the package from the location below to the specified local storage account. AVD desktops dynamically download the Winget installer from Nerdio Manager. Ensure access to this location is available to the Nerdio Manager WebApp.
"Offline" Mode
In Nerdio Manager v6.3, "Offline" mode has been added to the product. If selected, Nerdio Manager consumes all required files for image management and host deployment locally from the defined private storage account. Only the scripts and binaries included in the Nerdio Manager deployment package are available for use in this scenario.
Note: The Winget package installer, which is required for UAM application deployment, is not included in the package due to size limitations. In "Offline" mode, Nerdio Manager copies the package from the location below to the specified local storage account. AVD desktops dynamically download the Winget installer from Nerdio Manager. Ensure access to this location is available to the Nerdio Manager WebApp.
Configuration Details
The new App Service Artifacts:Mode has the following possible values, as shown below.
Note: This setting has no effect on pre-v6.2 deployments.
Option |
Supported Version |
Description |
|---|---|---|
Default |
v6.2+ |
Extension scripts use resources from the publicly accessible nmwextensions.blob.core.windows.net storage account. This remains the default approach for all deployments prior to v6.2, even after updating Nerdio Manager. |
Local |
v6.2+ |
VM and image actions use the extension resources from the defined private storage account for each client. Nerdio Manager copies resources either from embedded resources, if available, or from public storage account (otherwise). Only Nerdio Manager requires access to nmwextensions.blob.core.windows.net. This is the default configuration for any new deployments from v6.2 and onwards |
Offline |
v6.3+ |
Extension scripts use resources from private storage account for each client. Nerdio Manager copies resources there from embedded resources only. No access is required to nmwextensions.blob.core.windows.net. |
Comments (0 comments)