When launching a published application from a terminal Server, you may receive the following error;
“There are no available terminal servers to connect to at this time. Please report this message to your system administrator”
1. This can be caused when a Terminal Server was added to the farm by its FQDN rather than it’s NetBIOS name.
2. Corruption of the RDSH licensing in Windows 2008 / Windows 2008 R2, when checking the RD Session Host Configuration on the server you receive the error "Unable to complete operation".
Resolution for cause 1:
Use NETBIOS name when adding terminal servers to vWorkspace 7.2 MR1.
Resolution for cause 2:
1. Remove all the seamless apps from the server using the vWorkspace Management Console.
2. Remove the affected terminal server from Locations in vWorkspace Management Console
3. Uninstall vWorkspace from the affected terminal server
4. Uninstall the RDSH Role and features from the affected terminal server
5. Reinstall RDSH Role and features and test RDSH License by accessing the RD Session Host Configuration and Licensing Diagnosis
6. Reinstall the base install of vWorkspace (this may not connect to the database as it may be a new version). If it permits use the existing connection.
7. Test RDSH License by accessing the RD Session Host Configuration and Licensing Diagnosis
8. On the vWorkSpace management server add the terminal server to Locations and if using folders, to the relevant folder.
9. Assign a test app as a Published application an test that the app open from a client.
10. Apply the Microsoft security patches to the required level (optional)
