Checks to ensure that the proposed name for a hosting unit is unused.
Test-HypHostingUnitNameAvailable -HostingUnitName <String> [-BearerToken <String>] [-AdminAddress <String>] [<CommonParameters>]
Use this command to check that the proposed name for a hosting unit is unused. This check is done without regard for scoping of the existing hosting unit, so the names of inaccessible hosting units are also checked.
|Name||Description||Required?||Pipeline Input||Default Value|
|HostingUnitName||The name or names of the hosting units(s) to be tested.||true||true (ByValue, ByPropertyName)|
|BearerToken||Specifies the bearer token assigned to the calling user||false||false|
|AdminAddress||Specifies the address of a XenDesktop controller the PowerShell snap-in will connect to. You can provide this as a host name or an IP address.||false||false||Localhost. Once a value is provided by any cmdlet, this value becomes the default.|
An array of PSObjects which pair the name and availability of the name## Notes
In the case of failure, the following errors can result.
An error occurred in the service while attempting a database operation.
The operation could not be completed because the database for the service is not configured.
An error occurred in the service while attempting a database operation - communication with the database failed for
An error occurred while communicating with the service.
The user does not have administrative rights to perform this operation.
An unexpected error occurred. To locate more details, see the Windows event logs on the controller being used or examine the XenDesktop logs.
Test-HypHostingUnitNameAvailable -HostingUnitName $NewHostingUnitName
This tests whether the value of $NewHostingUnitName is unique or not, and can be used to create a new hosting unit or rename an existing one without failing. True is returned if the name is unique.