Avd
Was this helpful?
Was this helpful?
Create a new AVD Provider server to a site. The VDI agent will be installed on the server by default. You can optionally skip the agent installation by including the noInstall
parameter.
This is an Experimental feature which is subject to slight changes.
/api/Provider/avd
Specifies not to install the VDI agent on the server. If this parameter is omitted, the agent will be push installed on the server using your RAS admin credentials. To specify different credentials for push installation, specify the Username and Password parameters.
An administrator account for push installing the VDI agent on the server. If this parameter is omitted, your RAS admin username (and password) will be used.
The password of the account specified in the Username parameter.
Specifies not to restart the server after the RAS VDI Agent is installed when installing the VDI Agent. If this parameter is omitted, the server will be restarted if required.
Specifies not to add firewall rules to allow the RAS VDI Agent to communicate when installing the VDI Agent. If this parameter is omitted, the firewall rules will not be added.
AVD Version (Experimental)
0 = AVD,1441792 = AVD_Depr
The name of the Provider.
A Provider server FQDN or IP addresses.
The site ID to which to add the specified server. If the parameter is omitted, the Licensing Server site ID will be used.
A user account to log in to the hypervisor management tool (e.g. VMware vCenter). In case of Azure, it is an ID of the application which will be used by VDI agent to manage Azure resources.
The password of the account specified in the ProviderUsername parameter. In case of Azure, it is a secret key of the application which will be used by VDI agent to manage Azure resources.
The port to communicate with the Provider specified in Server parameter. In case of Azure, it is not required.
The preferred Connection Broker ID.
Use all guests.
Azure Subscription ID.
Azure Tenant ID.
Azure Authentication URL.
Azure Management URL.
Azure Resource URI.