Unsolved
This post is more than 5 years old
9 Posts
0
8455
February 3rd, 2011 00:00
Agent is not talking to the server
ok, i've installed the server and given it a hostname & fqdn which is resolveable.
I have installed the agent (intreractive) from the server onto my machine
Whilst the agent is installed, it didn't create any entries under HKLM\SOFTWARE\Quest Software\VDIAssessmentAgent stating the hubaddress or group (these have been set as default in the admin console)
I have also tried with these populated.
I have no firewall on the client device
I have nofirewall between the client & hub. They are stored on the same subnet.
I have restarted both the client & the server but the client is not showing up.
the agent service is running (tntgrd, tntuidsvc & tntupdsvc
What am I missing?
Client is Win7, not a member of any domain
I have also tried the network install agent. The documentation says to run a command
vdiassessmentagent start < vdiassessmentagent-folder-path > [-ha hub-ip-or-dns-name] [-mg machine-group-name] [-ug user-group-name]
Don't know about anyone else, but my network install agent doesn't include any file called vdiassessmentagent. Tried it using tntgrd.exe instead but that didn't work
I can connect over port tcp5501 from the client to hub, no reason to belive i can't on udp.
thanks
Mark
jasmine11
38 Posts
1
February 3rd, 2011 14:00
Hi Mark
Thanks for using Quest VDI Assessment solutions. for a default install there is no registry key created.
from the agent, when you go to Control Panel | Quest VDI Assessment Agent Configuration, on the about tab, does it show the correct assigned hub IP/fqdn? what's the content on the status tab?
from the Hub administration tab, Inventory subtab, can you see the machine?
hope this helps
jasmine
fredbloggs1
9 Posts
0
February 6th, 2011 23:00
Hi,
didn't realise there was a control panel applet, don't think this is in the guide, helped quite a bit to troubleshoot. Appears as though there was a typo in the original server name, added a host entry for the typo and now it works
Have now corrected the hostname on the hub, redeployed and all good. Would have saved quite a bit of time if there was some mention of how to test the agent on the client.
Thanks
jasmine11
38 Posts
0
February 7th, 2011 10:00
HI Mark
Glad that you've got it working! We would update the documentation to include this information in a later update, thanks for your suggestion.
Cheers
Jasmine