Install the NSX Agent on your Windows VM. This is the first of two steps required to enable NSX to manage your VMs. Currently, only Windows 2012 Server R2 is supported.


If you have the Quarantine Policy enabled for your compute VPC, before installing the NSX agent, assign the vm-override-sg security group to the VM to ensure that NSX Cloud does not quarantine this VM by auto-assigning the default security group to the VM. See Manage Quarantine Policy for more information.


  1. Find the VM’s public or private IP address so you can connect to it using RDP (or any other method you prefer):
    1. From the CSM dashboard, select Cross-Cloud > AWS > <AWS_account_name>
    2. From the VPC section, select <Compute-VPC-Name> Instances
    3. Select a Windows Server 2012 R2 VM.
    4. Locate either the public or private IP address of the VM.

      If using a jump host, you do not need the public IP address, you can use the private IP address. This is the preferred method of accessing your workload VMs.

  2. Download the installation script:
    1. Remote log in to the VM using RDP.
    2. Download the installation script from http://nsx-gw.vmware.local:8080/factory_default/win63_x64/nsx_install.ps1

      The default DNS name of PCG is nsx-gw.vmware.local. AWS Route 53 maps this name with the primary PCG IP address. The secondary CGW’s IP address, if you have one for HA, is also mapped to the same DNS name.

  3. Run the installation script: \nsx_install.ps1 -downloadPath <path> -operation install

    The script uses the interface with the lowest index as the default interface. For a list of all script options and uninstallation instructions, see NSX Agent Install Script Options for Windows VMs.

  4. Verify that the required NSX Cloud and Open vSwitch services are running:
    • nsx-agent

    • nsx-vm-command-relay-agent

    • logical-exporter

    • ovs-vswitchd

    • ovsdb-server

    • ovs-l3d

    Alternatively, run sc.exe in the Windows command prompt to verify that the required services are running:

    c:\> sc query nsx-agent

What to do next

Apply the nsx:network tag to VMs in AWS