If you created a master image VM with GPU, you must log into the VM's Windows operating system and install the supported NVIDIA graphics drivers to get the GPU capabilities of that VM. You install the drivers after the VM is created and the Imported VMs page shows the agent-related status is active.

  • Obtain the NVIDIA GRID driver that is appropriate for the image's Windows operating system. See the Microsoft Azure documentation topic at Set up GPU drivers for N-series VMs running Windows.
    Note: In this release, when using a Microsoft Windows Server operating system, GPU is recommended for use only in Microsoft Windows Server 2016, due to an NVIDIA driver limit on the number of user sessions in Microsoft Windows Server 2012 R2. The master image VM must have been created with Microsoft Windows Server 2016.
  • Install the driver following the installation instructions in the Driver installation section of the Microsoft article Set up GPU drivers for N-series VMs running Windows.
Caution: Install the NVIDIA GRID drivers listed on that Microsoft page and not other drivers.

Prerequisites

Verify the Imported VMs page indicates the agent-related status is active for the VM. To get that status for a VM created in a pod at manifest 1600 and higher, use the Imported VMs page's Reset Agent Pairing action on the VM. That action is located in the More drop-down list.

Note: When using the Microsoft Remote Desktop Client as your RDP software to connect to the master VM, ensure it is the most up-to-date version. For example, the default RDP software in the Windows 7 operating system is not at a high enough version. The version must be version 8 or higher.
Verify you have at least one of the following credentials (user name and password) to log in to the VM's guest Windows operating system, according to how the master image VM was created.
When the VM was created How the VM was created Credentials to use to log in
Prior to the December 2019 service release going live in production

Import Virtual Machine wizard, from the Imported VMs page.

Prior to the December 2019 service release date, the Import Virtual Machine wizard created VMs that were always automatically joined to the Active Directory domain that was specified in the wizard. To log in to such a VM, you can use one of the following:

  • The credentials for the local administrator account that were specified in the wizard.
  • The credentials for a domain account in that Active Directory domain.
After the December 2019 service release went live in production

Import Virtual Machine wizard, from the Imported VMs page.

Starting with the December 2019 service release date, the Import Virtual Machine wizard provides the option of either having the wizard-created VM joined to a specified Active Directory domain or not having the VM joined to the domain at the end of the creation process.

  • If the VM was created with the wizard's Domain Join toggle enabled, you can use either the credentials for a domain account in the specified Active Directory domain or use the local administrator account that was specified in the wizard.
  • If the VM was created with the wizard's Domain Join toggle turned off, you must use the local administrator account that was specified in the wizard. In this case, because the VM is not joined to the domain, the local administrator account is the only account that has access to log in.
In any service release

Manual preparation steps in Manually Build the Master Virtual Machine in Microsoft Azure.

Typically you do not need to join the VM to your Active Directory domain when you manually build the VM. To log in to that VM, use one of the following:

  • The credentials for the local administrator account that was specified when the manually built VM was created in the Microsoft Azure portal.
  • If you manually joined that VM to an Active Directory domain, the credentials for a domain account in that domain.
Important: Starting with pod manifest 1230 and later, domain accounts can direct connect to domain-joined image VMs that have the agent software installed. Prior to pod manifest 1230, the agent software installed in a domain-joined VM prevented domain accounts from directly connecting to that VM. However, if you have not yet upgraded your pod to a manifest of 1230 and later, before a domain account can direct connect to a domain-joined image VM that has the agent software installed, you must first perform the steps in When Your Pod is Not Yet Upgraded to Manifest 1230 or Later, How to Configure the Ability for Domain Accounts to Remote Connect to the Imported Image.

Procedure

  1. Use the VM's IP address in your RDP software to connect to the VM's Windows operating system.
    • If the master image VM was created with a public IP address, you can use that IP address in your RDP software
    • If the master image VM has a private IP address, you must RDP into it by one of these two methods:
      • Using another VM in your Microsoft Azure subscription that does have a public IP address and doing an outbound RDP into the master image VM.
      • Use your VPN and RDP into the master image VM over your corporate network
    Note: To access a VM that is running the agent-related software components, the version of the Remote Desktop Client must be version 8 or later. Otherwise, the connection fails. Using the most up-to-date Remote Desktop Client is recommended.
  2. Log in to the Windows operating system using credentials (user name and password) as described in the prerequisites here.
    When using the local administrator account credentials that were specified in the Import Image wizard when the VM was created, enter the username as \username.
    Note: When the VM is a domain-joined VM, as described in the prerequisites here, and you want to use a domain account instead of the local administrator account, enter the user name as domain\username where domain is the name of the domain.
  3. Install the drivers as described in the Driver installation section of the Microsoft article Set up GPU drivers for N-series VMs running Windows.
  4. When the drivers are installed, restart the VM.
  5. Reconnect to the VM, log in, and verify that the NVIDIA driver is installed and working in the VM.
    In the VM, open the Device Manager, expand Display Adapters, and verify the proper installation of the NVIDIA driver.
  6. Sign out of the VM's Windows operating system.