Company Details Instructions

Please provide the customer company name and (if applicable) the partner company name.

Customer Company Name

The customer company is the consumer of the virtual desktop service. The employees of this company are the end users who work in the virtual desktop service. The environment will be created in the customer company’s Microsoft 365 (aka Azure AD) tenant.

Partner Company Name

NetApp VDMS may be purchased through authorized NetApp partners. These service providers resell the service, provide implementation services and ongoing technical support. If this implementation is being sold and supported by a NetApp partner, enter the partner company name.

Technical Contact Instructions

Please provide the name and contact information of the contact person NetApp can work with on the technical aspects of this onboarding project. If this is a partner project, the technical contact should be from the partner company.

Time zone

We'll use this to assign NetApp resources to match the technical contact's availability. This data is also used to define the time zone settings for servers and logs in the environment. End user desktops will operate in their local time, regardless of this setting.

Purchased SKUs Instructions

Please provide a summary of the purchased SKUs to assist with the early design planning steps.

Shared Users

A shared user's session runs on Windows 10 EVD session hosts (virtual machines) that are simultaneously hosting other shared users' sessions. Up to 10 total user sessions can run on a single session host. Each time a shared user connects they are assigned to a session host with the fewest concurrent sessions running to optimize resource allocation across active users.

Shared user session hosts are based on Azure virtual machine family with at least 8 CPU cores and 64GiB RAM allocated for every 10 users, typically an E-Series VM.

VDI Users

A VDI user's session runs on a Windows 10 EVD session host (virtual machine) that is dedicated to that user's session. Only one user session at a time will run on a VDI session host. Each time a VDI user connects they are assigned to an empty VDI session host.

VDI user session hosts are based on the Azure virtual machine family with at least 2 CPU cores and 8GiB RAM allocated for every user, typically a D-Series VM.

GPU Users

A GPU user's session runs on a Windows 10 EVD session host (virtual machine) that is dedicated to that user's session. Only one user session at a time will run on a GPU session host. Each time a GPU user connects they are assigned to an empty GPU session host.

GPU user session hosts are based on the NV-Series virtual machine family with at least 8GiB of GPU memory allocated for every user. Currently supported options are the Nvidia-based NV12s v3 and the AMD-based NV16as v4 VMs. Availability varies by Azure region.

Business Servers

A business server supports workloads other than hosting user sessions. This virtual machine runs Windows Server and is allocated 8 CPU cores and 64GiB RAM along with a 128GiB OS disk. As much as possible, application data (including databases) should be stored on the data storage layer (e.g. Azure NetApp Files) and not the business server OS disk.

Additional TiB(s) Storage

Additional storage can be purchased in 1 TiB increments, increasing the total size of the data storage layer. This additional storage capacity will be allocated to the storage type and tier as determined by the user count, adding storage will not change the type or tier of storage service used.

Azure Reseller Relationship Instructions

A prerequisite of VDMS is that NetApp create a subscription within the customer company’s Azure AD tenant and that NetApp be granted delegated admin rights to deploy & manage VDMS. Establishing this relationship does not impact any existing reseller relationships or subscriptions. NetApp cannot see any other resellers/subscriptions you may already use. More information on multi-partner setups can be found here.

New Azure Subscription

The reseller relationship will be used to create a new subscription within the Azure AD tenant. This subscription will contain Azure resources for VDMS. NetApp will retain financial responsibility for the costs incurred in this subscription.

Delegated Admin

The delegated admin permissions will be used to deploy Azure Enterprise App(s) for VDMS, which in turn are used to automate the deployment and management of VDMS services and infrastructure.

Azure Domain Name

Please enter the domain name of this Azure AD tenant. Instructions to locate this can be found here found here.

Active Directory Domain Controller Instructions

Azure AD Connect

AVD authentication requires that a domain controller and Azure AD be setup and synced with Azure AD Connect. If this is already setup it is strongly recommended that VDMS be integrated with the AD DC already synced to Azure AD. A new AD DC can only be deployed if it can be synced to Azure AD and only one Azure AD Connect sync is supported.

Find AD Connect Status:

1. Sign in to the Microsoft 365 admin center and choose DirSync Status on the home page.
2. Alternately, you can go to Users > Active users, in the Azure Portal and on the Active users page, choose More > Directory synchronization. On the Directory Synchronization pane, choose Go to DirSync management.

Integrate with Existing AD DC

VDMS can be configured to integrate with your existing Active Directory Domain Controller (AD DC) or to deploy a new AD DC inside the VDMS subscription.

Existing AD DC Details Instructions

Domain Controller VM Running in Azure

If the existing AD DC is on a VM running in Azure, we'll setup vNet peering between VDMS and the vNet of the AD DC so that VDMS machines can join the domain.

Domain Controller VM Running Outside of Azure

If the AD DC is running outside of Azure, we'll either establish vNet peering to an Azure network that has network connectivity to AD DC or we'll setup a dedicated Site-to-Site VPN.

Azure AD Domain Services

If the existing AD DC is the "domain controller as a service" Azure AD Domain Services, we'll setup vNet peering between VDMS and the vNet of AADDS so that VDMS machines can join the domain.

AD DC Network Connectivity Instructions

Network Connectivity to AD DC

In order to integrate with an AD DC that is outside of Azure we'll need to establish network connectivity between the network of the AD DC.

If the AD DC is already connected to a vNet in Azure (e.g. VPN or Express Route), the best way to add network connectivity to VDMS is to establish vNet Peering between the VDMS network and the Azure network that is connected to the AD DC.

If the AD DC is not already connected to a vNet in Azure, the best way to add network connectivity to VDMS is to establish a SIte-to-Site VPN between the VDMS network and the gateway device on the AD DC network.

Detailed Network Connectivity Instructions

Azure Region for AD DC Network Connectivity

Select the Azure region of the Azure vNet that has connectivity to the existing AD DC.

Azure vNet Resource ID

Finding the vNet Resource ID in the Azure Portal:

1. Target: The Resource ID of the vNet that has network connectivity to the AD DC.
2. Login to the Azure Portal with an admin account that has access to the subscription containing the target vNet
3. Navigate to and select the target vNet
4. Select Properties from the vertical list
5. Copy the RESOURCE ID

Detailed Network Connectivity Instructions

Gateway Device

In order to correctly configure the Azure Site-to-site virtual gateway service, we'll need to know the brand, model and version. Please provide any other details that may be relevant

Gateway Device Public IP

When setting up the Site-to-Site VPN, we'll need to know the public IP address of the gateway device.

Validated Gateway Device

See the Azure validated device list to verify if the gateway device is listed as validated by Azure. Devices that are not validated may still work and additional investigation may be required to successfully configure the Site-to-Site VPN.

Network Scope Instructions

Virtual Network Scope

A /20 network scope for the VDMS virtual network and subnets is required.

It is important that you check with your current network design and select a scope that does not overlap with any other networks in your environment. If two overlapping networks are joined via VPN and/or vNet peering VDMS services will likely be impacted and significant labor required to resolve the problem.

As an illustration, the "10.75.96.0 /20" scope will use the IP range of 10.75.96.1 - 10.75.111.254