Windows client unlink or relink

[RoosterMDC]

We had a test Workspace environment up and my Windows client was connected to it.  We removed the test environment and installed a new production environment.  Since the test VAs were now gone I could not unlink from it to link to the new environment.  I uninstalled the client and connected to the new environment without issue.  Next, we had some issues with the new environment and made the decision to scrap it and start over.  Everything is working well except I cannot connect back to the new prod environment with my Windows client.  I uninstalled and reinstalled the client and I continue to get the error message that the service is unavailable, even though it is available and running with the same name as it was previously.  My questions:

1.  Is there any way to unlink from an orphaned VA and link to a different one without reinstalling the client?

2. How can I relink to a rebuilt VA with the same name?  I am assuming there is some unique identifier that needs to be cleared to allow me to relink - but it doesn't seem to get removed with an uninstall of the client.

I've searched but haven't found anything on these issues.  Thanks.

[HaiHuang]

This issue (cannot modify the server URL after it was set) was tracked in multiple bugs: HW-32777, HW-26758, HW-28559. Hopefully it will get fixed in near future.

Meanwhile, you can use install command-line option HORIZONURL to set the server url when you install / reinstall the Horizon Windows client, for example: VMware-Horizon-Workspace-1.x.x-nnnnnn.exe /s /v HORIZONURL=https://YourHorizonWorkspaceHost.com.

The server url registry is stored at HKCU > Software > VMware, Inc. > VMware Horizon Workspace > Configure > HorizonUrl if you the default installation, or at HKLM > Software > Wow6432Node > VMware, Inc. > VMware Horizon Workspace > Config > HorizonUrl, where the HKCU setting will overwrite the setting of HKLM if they both exist.

You can modify the HorizonUrl registry value (if you have the permission) without reinstall the Windows client, however directly modify the registry is not recommended and should always be done with caution.

[RoosterMDC]

Thanks for that info.  However it doesn't resolve the second issue.  I have uninstalled, rebooted, verified the reg keys were gone, reinstalled, and it still doesn't want to connect.  It works fine on new installs.

[HaiHuang]

When uninstall Windows client, not all registry entries are cleared and there is a reason for that (please refer to HW-30970).

For the Windows machine that has the problem, after uninstall, please check the registry for both HKCU > Software > VMware, Inc. and HKLM > Software > Wow6432Node > VMware, Inc. for any left over "Horizon" entries and manually clear them if exist and then try install again to see whether it helps.

[RoosterMDC]

All of the above mentioned registry locations are cleaned during the uninstall.  I had checked that previously when uninstalling the client.  How do I view HW-30970?

[HaiHuang]

Can you use [Collect diagnostic information] button to get related log info and upload it? It would be helpful to find out the issue on the machine.

[RoosterMDC]

Sure, where do you want it?

[HaiHuang]

Can you attach the log file in this thread? If security is a concern, you can email me at haihuang@vmware.com

We have tested this scenario before and I just performed another test and cannot reproduce the problem locally. What I did was following the steps you mentioned:

* Setup vApp and have gateway up and running (in my case is https://gw-hhuang.hs.trcint.com)

* Install Windows client on Windows 7 and register it using server url https://gw-hhuang.hs.trcint.com/

* Without unlink the client, reinstall vApp with same server url https://gw-hhuang.hs.trcint.com

* After vApp is up and running, check the Windows client, it is showing "The Horizon service is not available", which is as you reported, see attached screen-shot serviceNotAvailable.png.

* Click the "Exit" to quit Windows client, and then relaunch it, tray menu is shown with "Sign into Horizon Workspace ..." and I can successfully sign-in using a valid username / password.

[HaiHuang · Accepted solution]

Checking HoriznWorkspace.log it seems this could be an issue in IE browser, which is opened by HWS to perform the registration.

Would you check your system and provide the following info:

1) Can you ping mywork.mdch.com successfully? There are some connectivity errors in the log but it was not a consistent problem.

2) What is the version of Internet Explorer?

3) Please clear your IE cache and relaunch it.

4) Can you try to open https://mywork.mdch.com in internet explorer? Does this take too long?

5) Can you try to open device registration link in your Internet Explorer and see whether the login page shows up?

https://mywork.mdch.com/SAAS/API/1.0/GET/user/devices/register?user_device=%7b%22deviceId%22%3a%22LT...

6) Please login HWS admin page (https://mywork.mdch.com/SAAS/admin) and check Settings > Identity Providers > choose Edit for existing ones and check its "Allowed IP Addresses". Make sure that your IP adddress is within the range.

[RoosterMDC]

Answers to previous post:

1) Yes.

2) IE 10

3) Done

4) the web versions works as expected

5) I do get the login page and can login - but stays on "Signing In" after that (expected?)

6) All IP ranges are included

I am connected now.  I think either step 3 or 5 fixed the issues (the only ones that might have changed something).  Thanks for the help!  Good to know it uses IE in the registration process.

[HaiHuang]

Glad to know that you are connected. My guess is step 3 clearing the cache fix the problem. Step 5 was to register your Windows machine (directly) to HWS, so it stays on "Signing In" is expected.

Regards

[RoosterMDC]

So we had a maintenance outage this past weekend and had to restart our Workspace environment.  After the restart my client couldn't connect again.  I tried clearing all the IE cache, etc. to no avail, so that's not what fixed it previously after all.  I connected to the link in 5) above and as soon as I logged in there, the client connected.  My question is: how can we generate that link for other devices if we run into this issue again?

[HaiHuang]

Sorry for the late reply. The device registration link is in HorizonWorkspace.log, which is located at %localappdata%\VMware\Horizon Workspace directory in your Windows machine.