<code>Set-RDLicenseConfiguration -LicenseServer savdaldc01.savilltech.net -Mode PerUser</code>
However, if the host isn't part of a Virtual Desktop or Session Host collection, the cmdlet will display an error:
Set-RDLicenseConfiguration : A Remote Desktop Services deployment does not exist on savdalhv01.savilltech.net. This
operation can be performed after creating a deployment. For information about creating a deployment, run "Get-Help
Set-VDIDeployment" or "Get-Help Set-RDSHDeployment".
At line:1 char:1
+ Set-RDLicenseConfiguration -LicenseServer savdaldc01.savilltech.net -Mode PerUse ...
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Set-RDLicenseConfiguration
The solution is to add the host to a VDI collection, which means the Remote Desktop Services Connection Broker and Web Access role must be deployed to a server in the environment (not to the Hyper-V server). This deployment can be done by using the Server Manager interface or using the New-RDVirtualDesktopDeployment and New-RDVirtualDesktopCollection cmdlets.
Either option will install the RD Virtualization Host, Connection Broker, and Web Access roles on the configured server. After that's completed, the licensing mode will be able to be configured through the cmdlet.