Configure Custom Storage Account Names

Configure Custom Storage Account Names

Nerdio Manager allows you to configure custom storage account names in Azure for each of the storage account types. Storage accounts are detected for use based on the tags applied. New accounts must be pre-created to replace the default Nerdio Manager automated creation behavior.

The table below describes the use cases, required tags, and functional details. Please create separate storage accounts in each resource group and region that requires a custom storage account.

 

Use Case

Account Type

Tag

Notes

Boot Diagnostics

Standard

NMW_OBJECT_TYPE

Value: 

STORAGE_ACCOUNT

This is a standard storage account. There needs to be one of these accounts for each resource group, for each region.

Custom Scripts and Scripted Actions

Standard

NMW_OBJECT_TYPE

Value:

CUSTOM_SCRIPTS_STORAGE_ACCOUNT

This is a standard storage account. There needs to be one of these located in the same resource group where Nerdio Manager was deployed.

Desktop Image Imports

Premium

NMW_OBJECT_TYPE

Value: 

STORAGE_ACCOUNT

This is a premium storage account. There needs to be one of these accounts for each region.

This account is only required if you make use of the Add from Azure VM function in the Nerdio Manager console. This storage account can be skipped if this function is not required.

 

To configure storage accounts with custom names in Azure

The processes describe both the creation and tagging of the new resources.

For all newly created storage accounts, the following configuration options should be used:

  • Default access tier: Hot

  • Account kind: StorageV2

  • Minimum TLS version: Version 1.2

  • Require secure transfer for REST API operations: Enabled

  • Each storage account type should be LRS (locally-redundant storage)

Boot Diagnostics Storage Account

The following steps allow you to configure the Boot Diagnostics storage account in Azure.

  1. In the Azure portal, locate all Resource Groups to which VM objects have been deployed (both images and session hosts).

  2. Create a new, custom-named standard Storage Account in each Resource Group and region.

  3. Add a new tag with the following parameters:

    • Name: NMW_OBJECT_TYPE

    • Value: STORAGE_ACCOUNT

  4. Once you have added the tag, select Save.

Custom Scripts and Scripted Actions Storage Account

The following steps allow you to configure the Custom Scripts and Scripted Actions storage account in Azure.

  1. In the Azure portal, locate Resource Group where Nerdio Manager is deployed.

  2. Create a new, custom-named standard Storage Account.

  3. Add a new tag with the following parameters:

    • Name: NMW_OBJECT_TYPE

    • Value: CUSTOM_SCRIPTS_STORAGE_ACCOUNT

  4. Once you have added the tag, select Save.

    Note: For existing deployments, it is required that the contents of the certificate-store blob within the existing CSSA storage account are copied to the new certificate-store blob within the new storage account which has been tagged with CUSTOM_SCRIPTS_STORAGE_ACCOUNT.

Desktop Image Storage Account

Note: This account is only required if you make use of the Add from Azure VM function in the Nerdio Manager console. This storage account can be skipped if this function is not required.

The following steps allow you to configure the Desktop Image storage account in Azure.

  1. In the Azure portal, locate the Resource Groups to which images are targeted.

    Note: If you have a multi-region deployment, there is one per region.

  2. Create a new, custom-named Premium Page blob Storage Account in each Resource Group.

  3. Add a new tag with the following parameters:

    • Name: NMW_OBJECT_TYPE

    • Value: STORAGE_ACCOUNT

  4. Once you have added the tag, select Save.

Nerdio Manager can now identify the required storage accounts to use for Desktop Image Import, Boot Diagnostics, and Custom Scripts storage.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Please sign in to leave a comment.