This post is more than 5 years old
28 Posts
0
319347
March 28th, 2013 23:00
Agents not calling back to Hub
Team,
Good day to you! I have just deployed this tool for a customer via AD GPO MSI. We are deploying this using the local method as specified in the user guide. Currently, it seems that the agent is not calling back to the hub. I have a feeling that the ADM template which were imported into the GPO is not in effect. The VDI Assessment agent was deployed successfully however I don't see the computer record back at the administration console. Below are the client configuration and I have attached the report on the GPO that was linked to the OU (this is a lab setup based on the customer environment). Could you assist to advice on this? Thanks!
AD --> Windows Server 2008 R2
Client --> Windows 7
Regards,
Cyril
jasmine11
38 Posts
1
April 1st, 2013 07:00
Hi Cyril,
Glad to know that you've identified the cause of agent and hub not communicating.
The GPO is assisting to install agent software to target machines, they are machine based OUs.
The user has to have the minimum privilage of installing the agent software.
hope this helps
jasmine
jasmine11
38 Posts
1
March 29th, 2013 08:00
HI Cyril,
I need to understand a bit more of your deployment first.
Are the VDI Access Agents being deployed successfully to the end points? We are not sure what you are referring to as "no computer records back at the administration console". Is this the Hub administration console you are referring to?
Please logon to one of the machines that has the agent installed and check whether you have a control panel item named "Quest Workspace Accessment Agent". You can double click to open the control and check whether it has the valid Hub address assigned.
Have you also tried to download the installer directly to a machine and install it? does that work?
Jasmine
kcy43ccwc
28 Posts
0
April 1st, 2013 02:00
Jasmine,
Thanks for your reply. I have identified what's wrong with the agents not contacting back to the hub. It's due to the dns not able to resolve the hub fqdn. That being said, am curious if we can apply this to GPO to an OU with just users instead of linking it to an OU with computers? Reason being, customer did not manage the computer objects hence all their computer objects are in the default "computer group" and this includes their servers which they do not want to be part of the assessment.
Regards,
Cyril
kcy43ccwc
28 Posts
0
April 1st, 2013 04:00
Jasmine,
On another note, with regards to assigning agent to user configuration (GPO), are there any explicits rights that the user mush have in order for the application assigning to be successful? I'm trying this out in my lab and apparently, my normal users without any administrator privilege would have the gpo processed successfully however the agent is not installed where as if I login using a domain admin account, the agent would be able to install properly.
Regards,
Cyril
kcy43ccwc
28 Posts
0
April 1st, 2013 07:00
Jasmine,
Noted. Thanks for all the input! Cheers!
Regards,
Cyril
kcy43ccwc
28 Posts
0
April 2nd, 2013 02:00
Jasmine,
Would need your assistance once again on this case. I'm currently at customer site. It seems that Hub Address Properties are not propagating to the end point device even after the GPO is linked and gpupdate /force is executed. Attached is the gpresult which shows that the computer settings for the hub address properties are not taken into effect. Could assist to advice on this issue? Thanks!
Regards,
Cyril
Additional Attachments:
jasmine11
38 Posts
0
April 2nd, 2013 03:00
HI Cyril,
I can't tell the problem from the screenshot either. can you try:
1>download the agent and install to an end point, manual installation
2>go to the GPO deployed end points, check the control panel plugin's properties
3>if 1> works and 2> doesn't, i'd suggest remove/uninstall and start clean.
I assume you have read the GPO deployment guide in the administration guide, those are the steps that we've checked.
hope this helps.
jasmine
jasmine11
38 Posts
0
April 2nd, 2013 04:00
Hi Cyril,
My knowledge on GPO is also limited, i am not sure why the property is enabled yet coupled a "stop" sign.
To summerize, the agents are installed on the end points but the hub address is not set? what's shown on the control panel's plugin's hub address?
cheers
jasmine
kcy43ccwc
28 Posts
0
April 2nd, 2013 04:00
Jasmine,
Thanks for the reply. The standalone package (exe) works fine. The main problem here is getting GPO to push down the hub address information to the GPO deployed agent. I have read thru both getting started and administration guide that comes with the VDI assessment tool however, both of them are kind of dated as they are based off Windows Server 2003 AD which is slightly different compared to Windows Server 2008 AD. For instance, the group policy settings icon for the hub properties is showing with a "stop" symbol, hence I'm just wondering if that setting is applicable or not in Windows Server 2008 GP.
Regards,
Cyril
jasmine11
38 Posts
0
April 2nd, 2013 05:00
Thanks, Cyril.
Just a thought, the hub's IP address hasn't changed since configuration? is it a Static IP?
https://hubIP/vscenter/app/admin/im-config.html will let you check the config data again.
kcy43ccwc
28 Posts
0
April 2nd, 2013 05:00
Jasmine,
Thanks for the reply. It's shown as unassigned, hence not contacting back to the the hub. Am still troubleshooting on the GPO rights. Shall keep you posted if I found something.
Regards,
Cyril
kcy43ccwc
28 Posts
0
April 2nd, 2013 05:00
Jasmine,
Yeap, its configured with a static IP.
Regards,
Cyril