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?
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
screenshots of the logs attached for reference
Ive only seen this when the vCAC agent can not talk back to vCAC on the correct ports.
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"
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
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
are you using a load balancer in front of your IaaS servers?
no load balancer. the most basic and simple of installs only!
1 person found this helpful
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.
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!
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.