Good afternoon community!
I'm reaching out in hopes that I can get help with an issue we are having. Now, before we go too deep, I would like to simply mention that I'm not a vRA/VMWare SME in my enterprise. I'm working with my colleague who wears that hat. 
For my part, I would be the SCCM SME. So, safe to say that we are working very very closely to get this whole thing working.
Now, before we implemented vRA, we would basically install our servers from scratch using SCCM's built in OSD feature.
We are trying to eliminate all the manual effort we need to do before and after that with vRA.
So... We are able to provision a virtual machine and the network boot is successfully picked up by SCCM. Reading all the documentation we could find on the matter, we:
- Downloaded the 64 bit "Guest Agent Installers" from our https://hostnameFQDN/software/index.html
- Extracted the EXE locally on the SCCM
- In SCCM, imported the package from definition file, pointed to the "SCCMPackageDefinitionFile.sms" we created the package
- We distributed the package to the appropriate DP
- Added the program that was created with the package in step 3 as the last step in our Server task sequence
From there, we provision a VM from the appropriate Catalog. The VM gets created. The Task sequence starts and actually, even finishes without any errors. Validation in the SMSTS.log file does indeed indicate that the action completed with a success code 0.
But.... the vRealize Automation console seems to stay "In progress..." and eventually times out and deletes the Virtual Machine.
Where do I start looking? I can't seem to find any logs spefically to the vCAC Guest agent vbs. Should I be passing any variables in my Task Sequence? One piece of pertinent information I would say is that when the computer object is created in SCCM, there is 2 variables that are created "Vrm.ProxyAgent.Uri" and "VrmProxyAgentUri" both with the same URL.
Anyway! Any help you can toss my way would be greatly appreciated!!!
Thanks!!!
Steph
Good morning!
Ok so... Progress!!!
Based on your post Darrenoid...
1. Make sure there are also files in the subdirectories to verify the copy command worked recursively
2. Open the properties of some of the files in the VRMGuestAgent directory to make sure they were not blocked when they were extracted StorageGumbo: vCAC Windows Deployment Stuck at CustomizeOS State
3. Try changing to the C:\VRMGuestAgent directory before running the winservice command
4. Try running the commands manually on a fresh VM. This will help show you if the issue is with the way the command is being passed through SCCM.
1. :smileycheck:
2. :smileycheck:
4. :smileycheck:
Now... Step number 3 intrigued me.... I was wondering if for some reason, the application would be "stupid" enough not to work the way I had initially invoked it, ie: "C:\VRMGuestAgent\WinService.exe". So instead.... I tried the following:
- Fill in the "Start In" folder (1)
- Not put the full path in the command line, but just straight up the exe file (2)
Now...
The vCACGuestAgentService notes:
And sure enough... I see the service in the Services List. Automatic. But not started.
Is this normal? Should I add another command line after this one my Task Sequence to simply start it? Will that "break" anything since the VCAC Service wouldn't technically be the "last" step anymore...