Adobe - CMD /C START C:\TMP\AcroRdrDC1501020056_en_US.exe /sAll
IIS - Powershell
Import-Module ServerManager
Add-WindowsFeature Web-Server
import-module servermanager add-windowsfeature web-server -includeallsubfeatureFor Windows 2012, install-windowsfeature web-server instead.
MS SQL - C:\TMP\SQL2012\setup.exe /q /ACTION=Install /IAcceptSQLServerLicenseTerms /FEATURES=SQL /INSTANCENAME=MSSQLSERVER /UpdateEnabled=0
VI Client
CMD /C START C:\TMP\VMware-viclient-all-6.0.0-3249451.exe /S /v/qn
To install vRA-agent -
keeping the following URL for reference
http://www.virtualizationteam.com/cloud/vrealize-automation-7-bootstrap-installation.html
http://www.virtualizationteam.com/cloud/vcac-guest-agent-installation.html
Cert problem http://vmwarevcloudvirtualization.blogspot.co.id/2014/04/vcac-agent-ssl-issue.html. (Hopefully we don't need to do this!)
ManagerServiceHost = IaaS -> Windows, not the vRA.
Do not need to run winservice -i -h... under c:\VRMGuestAgent
After agent is installed, it should pull the cert.pem to c:\VRMGuestAgent folder as shown below.
SSLInfo text should have content with "CONNECTED". If you get empty log, it means not connected. This could be due to root certificate and trust issue. Refer to above link to address the root cert issue. Both root cert of IaaS and vRA must be imported to the template OS.
VCACGestAgentService looks the same if it fails to connect.
Once connected to IaaS, there will be logs folder under C:\VRMGuestAgent\axis2. If not, it will be empty.
agent_Bootstrap log will looks like this before script being deployed.
Once the VM is deployed via vRA, you can login (after customization) and look at the looks under c:\opt\vmware-appdirector\agent\logs. There are three logs file.
Goto vRA, you can see the process of building the VM.
ManagerServiceHost = IaaS -> Windows, not the vRA.
Do not need to run winservice -i -h... under c:\VRMGuestAgent
After agent is installed, it should pull the cert.pem to c:\VRMGuestAgent folder as shown below.
VCACGestAgentService looks the same if it fails to connect.
Once connected to IaaS, there will be logs folder under C:\VRMGuestAgent\axis2. If not, it will be empty.
agent_Bootstrap log will looks like this before script being deployed.
Once the VM is deployed via vRA, you can login (after customization) and look at the looks under c:\opt\vmware-appdirector\agent\logs. There are three logs file.
Goto vRA, you can see the process of building the VM.
To get this to work, did you add anything to the event broker for this? I'm simply trying to run a powershell script to install IIS and its failing. [computer name] not found, and possibly deleted before provisioning finished. Thoughts?
ReplyDeleteI am having the same problem with a linux VM ... any software component that i add it creashed the deployment
ReplyDelete