VDI Assessment - cannot change agent hub address

Hello Simon,

Thanks for the message. Sorry that we missed it: my team watches the VDI Assessment community and unfortunately missed this post as it's on the vWorkspace community.

We are looking at your issue now and will get back to you.

All the best,

Hugh

Hi Simon,

Can you please try the regkey under HMLM\Software\Wow6432Node\Quest Software\VDIAssessmentAgent\hubaddress and see whether the control panel applet can show the correct hub?

thanks

jasmine

Sorry, this is a 32 bit machine with no 32 bit subsystem.

There is not Wow6432Node subkey.

The only registry reference to the configured hub address is in the standard key:

HMLM\Software\Quest Software\VDIAssessmentAgent\hubaddress

The strange thing is : that the control panel applet does not report the registry entry under the above address, which lends me to believe it may be reading from disk/cache somewhere?

Sorry Simon, i mistakenly thought this is a 64 bit machine.

when you change the regkey to use the hub's assigned static IP (or are you using the FQDN?), and restart the agent, do you notice any file changes in

C:\Program Files\Quest Software\VDI Assessment Agent\ca\public?

Hi Jasmine,

I've tried using direct IP through the installation, direct registry and group policy.

I've also tried using FQDN addresses through the same measures with the same result.

As per your request

1. If I update the address (IP) and restart the agent - the rootcacert.pem certificate file is updated.

In the tntgrd_log.txt file (which i'm running in verbose mode), there is a corresponding entry to the following:

hub Discovery Hostname questvdi.lab.internal

I am starting to believe this might be someting internally related. There is another entry in this file stating :

tnt_assign_tuuid() can not make remote request, do't have realm and sid

There could be a time/domain related issue.

I'm building a fresh machine from a standard ISO build, and will test it as a domain member and as a stand-alone member.

Thanks,

Simon

Hi again - some testing outcomes.

Build environment:

* New workstation, build from XP SP3 CD

* No customisations

* Local workgroup member (not domain)

Download and install the standard executable agent:

* Same as before - configured hubaddress to domain controller address (but NO registry key of 'hubaddress')

Download and install vanilla executable for use with group policy

* Control panel reports 'no configured hub address' - as expected

* Add registry value 'hubaddress' as REG_SZ, add desired value (172.20.112.113)

     - Control panel then reports the FQDN

Solution / Problem

1. Looking under the public certificate folder (%programfiles\Quest Software\VDI Assessment Agent\ca\public), the file mgrcert.pem (presumably the VDI manager), has, at the top of the file a web services definition of SOAP_URI : http:// < FQDN of Domain controller

2. Stop services

3. Change this value to the correct one (http://172.20.112) .130

4. Restart services

5. All working !

Notes

1. It appears that something in the VDI server is causing the package to embed the DC FQDN, or upon first connect populate this value in the certificate

2. The registry key 'hubaddress' does not appear to do anything. I can delete this entry, or change it to another value and the value that is used is the one located in the mgrcert.pem file.

Verification

I repeated the above steps on the other non-working machines, with similar results.

Question

1. Any thoughts on why this may happen?

2. What is the likelihood of this behaviour if we perform an actual client assessment (which is scheduled?)

3. Work arounds? - I am happy to create a transform for the MSI that embeds this certificate in the correct folder, but would rather not.

Thanks,

Simon

Hi Simon,

I'm quite impressed how you modified the .pem file and get it to work. can you please check

https://youhubIP/vscenter/app/admin/im-config.htm has the intended values?

the DNS name should either be the static IP of the Hub, or the hub's resolvable domain name. This value is used in the SOAP_URL in the .pem file.

once you confirm above dialog has the correct values, can you please save it and then download the agent package and install again? you only need to download the standard exe. Please remember to uninstall the previous installed agent first then do a clean re-install.

if you do enable NTP, please use a local time server, such as the domain controller or a router, as the public ones may not be reachable if there are firewalls in between.  if the server is underload, saving the configuration might take a little longer as well, to be cautious, after the URL being redirected and downloading the agent, please check the configuration URL again.

thanks

Jasmine

Hi Jasmine,

This did indeed resolve the issue - thanks!

- Simon