Preparation and Prerequisites

Preparation and Prerequisites

Prior to deploying Nerdio Manager for Enterprise, ensure the following prerequisites are met:

  1. Nerdio Manager requires a pre-created VNet and subnet. For Active Directory-joined environments, this requires connectivity to Active Directory or Microsoft Entra Domain Services domains. DNS and any peerings or WAN connections should be established and functioning.

    The following should be prepared prior to Nerdio Manager deployment:

  2. Directory credentials to join session host virtual machines (VMs) to the domain are necessary. A service account with delegated privileges to join computers to the domain is needed (domain admin account may be suitable but is not necessarily required).

  3. The admin completing the Nerdio Manager deployment requires sufficient privileges for Microsoft Entra ID and the Azure subscription. For ease of deployment, we recommend subscription Owner privileges and one of the following roles:

    • Global Administrator

    • Privileged Role Administrator combined with Cloud Application Administrator

    Note:

    • Nerdio Manager is not assigned as Global Administrator, Privileged Role Administrator combined with Cloud Application Administrator, or Owner on the subscription. However, these permissions are required to complete the setup.

    • Global Administrator privilege is not required if there is access to another Global Administrator user that can grant consent to the required permissions for Nerdio Manager.

    • The subscription Owner privileges are required.

  4. A funded Azure subscription is required. This subscription requires the following resource providers:

    • Microsoft.DesktopVirtualization

    • Microsoft.Compute

    • Microsoft.Storage

    • Microsoft.Automation

    • Microsoft.RecoveryServices

    • Microsoft.SQL

    • Microsoft.Insights

    The deployment from Microsoft Azure Marketplace should enable most of these resource providers automatically, and Nerdio Manager should validate if any resource providers are missing during the initial configuration.

  5. A summary of permissions assigned to Nerdio Manager during provisioning. To learn more, see Azure Permissions and Nerdio Manager.

  6. Consideration for user profile storage accounts would also normally be required. For the early cases, profile storage may not be needed since users will be provided with individual and dedicated desktops.

Note: For additional installation instructions and references, see Nerdio Manager for Enterprise Implementation Guide.

Was this article helpful?

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

Comments (0 comments)

Article is closed for comments.