This is quite an interesting issue. And I only recently found out Wyse devices need to have write access to a terminal services key on Server 2008 R2. Here is a breakout of the issue and how to resolve in the event you bump into the same thing and need to quickly fix.
Step by step customer process:
- The very first screen after the device is switched on, is the “Network Authentication” screen. This has two input textboxes for User Name and Password.
- There would be a pop-up at the bottom right side of the screen saying “Network connection is up. Link speed is 100HX.”
- On entering the credentials we get a “Network Authentication Note” dialogue box displayed with a message: “Error: Unable to connect to network. Please check setting and try again. Again? “
- This appears with an auto-submit countdown of 60 seconds and a cancel button.
- This redirects to the initial Network Authentication screen.
- The second time entry of the credential shows the following text on the screen. “Looking up ip address from DHCP…”
- Then the text changes to “Connecting to WDM Server.” And to “Checking for software update”
- This redirects to WDM Login Window. Here we select our respective Group from its dropdown, User Name, Password, and Domain from its dropdown.
- When we give our credentials here, the text updates at the space below on the window, with its progress, in the below order.
- Loading profile…
- Connecting…
- Connecting to session…
- Preparing your desktop…
- Then we get the Windows Server 2008 R2 Enterprise Warning disclaimer with only an “OK” button.
- This displays the “CITRIX” screen.
- And then the Remote Desktop Connection Wizard which connects to our VDI.
How to correct issue on server:
- Logon to XenApp server hosting the users sessions via the thin/zero client
- open the registry and navigate to HKLM/Software/Citrix/MSLicensing
- Allow auticated users the rights to update the mslicensing key.