beefy147
Enthusiast
Enthusiast

Guest Agent install via SCCM

Hello everyone

I am (desperately) trying to get the guest agent to install properly via SCCM (our build method for windows servers) using vRA 6.2.1 but having no luck and therefore my machines are deleting a few hours after they are created Smiley Sad

I have followed the instructions here to create the package http://pubs.vmware.com/vra-62/index.jsp#com.vmware.vra.iaas.physical.doc/GUID-B5BDDE7F-D59C-4D97-BF8...

however it doesn't seem to be installing at all. Any gotchas i should be looking for? We don't have UAC enabled in our environment (however it is disabled by group policy so would be "on" during build)

We are using SCCM 2012 R2 building a 2012 R2 server. The iaas server is also on 2012 R2 and I have also followed and confirmed it is patched against the following problem http://cloudrelevant.com/2014/08/19/vcac-6-0-x-with-windows-2012-guest-agent-looping/

If we were using templates I would move along and worry about the guest agent later but with SCCM as the deployment method this isn't a choice I can make

Any help or advice greatly appreciated!

0 Kudos
10 Replies
beefy147
Enthusiast
Enthusiast

p.s. the documentation lists that the final step must be the guest agent install. I tried this but actually think i got further having it a few steps before the end of the SCCM task sequence. how important is the order?

0 Kudos
beefy147
Enthusiast
Enthusiast

An update after going through the smsts.log on a machine which attempts to install the agent

the files get copied down and attempt to install but then it just waits with ""waiting for job status notification" and has been on that status for 2.5hrs so isnt working

any ideas?

screenshots of the logs attached for reference

guestagent2.PNGguestagent3.PNGguestagent4.PNG

0 Kudos
NuggetGTR
VMware Employee
VMware Employee

Ive only seen this when the vCAC agent can not talk back to vCAC on the correct ports.

________________________________________ Blog: http://virtualiseme.net.au VCDX #201 Author of Mastering vRealize Operations Manager
0 Kudos
beefy147
Enthusiast
Enthusiast

thanks. there are no firewalls between the servers

EDIT: just tried a manual install to confirm the service can register with the iaas server and got the following result so communication appears "ok"

guestagent5.PNG

Despite being patched I am thinking of disabling the TLS1.2 on the iaas server to see if that helps at all (clutching at straws a bit I know!)

How does the the package know what the vCAC server is called. I see the VBS file talks about replacing the hostname but its not obvious to me where it gets that information from?

Any other advice would be gratefully appreciated

Will

0 Kudos
beefy147
Enthusiast
Enthusiast

A further update. I just cant get the task sequence to work using the definition file. however if I get the VRMGuestAgent folder copied to the machine during build and run a script which does the winservice.exe -i -h IAASFQDN -p ssl command i get a "successful" message in the vRA requests console (yay!)

its not the best workaround but it will do. I wish I knew why the task sequence method doesnt work. I am still confused as to how the sms definition file knows what the hostname of the iaas server is in the first place. Obviously using my solution above I am using a push and providing the hostname which works

guestagent6.PNG

0 Kudos
pizzle85
Expert
Expert

are you using a load balancer in front of your IaaS servers?

0 Kudos
beefy147
Enthusiast
Enthusiast

hello

no load balancer. the most basic and simple of installs only! Smiley Happy

0 Kudos
pizzle85
Expert
Expert

your agent isn't talking to the IaaS web server. Check that the machine your deploying has access to the IaaS web IP. Windows firewall, network ACLs, etc. Also the SMS installer uses the SCCM computer variable Vrm.ProxyAgent.Uri. Make sure that is populated with the correct URL and protocol (http/https) for your IaaS. I also found that if your IaaS web server is not providing the full SSL certificate chain you will need to have the root and intermediate certs on the box, you can do this in the OSD TS.

beefy147
Enthusiast
Enthusiast

Are you saying the Vrm.ProxyAgent.Uri should be populated within the Build Profile as a property?

e.g. alongside SCCM.Collection.Name etc

I didn't see that documented anywhere (or maybe i missed it!?) that could be the answer!

0 Kudos
pizzle85
Expert
Expert

no its a system reserved property. vRA will always automatically put that variable on the CM machine object and you cant modify it. Take a look at one of your CM computer objects variables and see if its there and its value. You don't need to do anything with it other than verify its correct and what you expect it to be.

0 Kudos