Auto-Configuration of vWorkspace client for non-Domain members may not work as advertised.
This issue arises only when non-Domain joined computers try to connect to the built-in connections http://provision.<FQDN>, http://vworkspace.<FQDN>, https://provision.<FQDN>, https://vworkspace.<FQDN>.
The above mentioned issue is by design. When launching an unconfigured vWorkspace AppPortal client, it will, by default, try to connect to one of the above links calling for CONFIG.XML. If the file is not found, you are left with an unconfigured client. The above will try to append the %userdnsdomain% variable as the FQDN but if the computer is not joined to the domain there will be no variable for this.
When the string is built and the %uerdnsdomain% is empty the vWorkspace AppPortal will look for:
Notice the strings above are invalid requests as there is a pre-pended period at the end of the string.
As a work-around, make sure computers attempting to be auto-configured are joined to the domain or see https://support.quest.com/Search/SolutionDetail.aspx?id=SOL53711 for a supported way of auto-configuring the vWorkspace client via the Registry.