Based on the pre-check validation you can change your input anytime in the previous steps and run the pre-validation check again.
How does Pre-Check Validation Work?
When you click the Run Pre-Check button, a report is generated indicating whether the pre-validation is in PASS or FAIL state. Therefore, based on the report you can modify your inputs given in the previous steps and click the RE - RUN PRE CHECK button. The report contains the following information:
Status of the Check
Component/Resource against which the current check is run.
Result description about the check execution
Recommendation, if there is FAILURE or WARNING
The report also generates color coded status:
GREEN SYMBOL - PASSED
RED SYMBOL - FAILED
YELLOW SYMBOL - WARNING
GREEN FIXED SYMBOL - REMEDIATED & FIXED
You cannot go further unless the pre-validation run is successfully complete. The pre-validation request progress can be tracked in the Request tab through a request that gets created with a name VALIDATE_CREATE_ENVIRONMENT. Once the pre-validation is run and the NEXT button is enabled, you can SUBMIT the request for deployment. When you are submitting, you can skip the pre-validation. By default, this flag is enabled. This verifies pre-validations are anyway run before deployment is triggered. If you want to skip this, then you can deselect the flag and then click submit. Pre-validations check does not run again before the deployment begins.
If you click Submit with the pre-validation flag enabled, a request by name VALIDATE_AND_CREATE_ENVIRONMENT is created. If you click SUBMIT only by deselecting the pre-validation flag, a request by name CREATE_ENVIRONMENT is created. You can track the progress of pre-validation requests in the Request tab that vRealize Suite Lifecycle Manager provides Out of the box. Before you run a pre-check on vRealize Automation, verify all the IaaS component VMs are communicating with Lifecycle Manager appliance. After you enable pre-check and submit the create environment, if the pre-check fails then user can resume the wizard from the Request page with a request state as PRE_VALIDATION_FAILED. From the report, if the failure is due to the wrong IaaS credential then rerunning pre-check on updating the windows password in the Product details page still results in the wrong IaaS credential. To fix this, update the Windows password in the product details page at each node level and rerun the Pre-Check.
If the VALIDATE_AND_CREATE_ENVIRONMENT request fails with a status PRE-VALIDATION-FAILED, then you can validate your inputs by clicking the icon under the action tab. This directs you to the wizard where you can modify your inputs and run PRE CHECK or click SUBMIT for deployment. Once the deployment is complete, you can see the last run pre-validation report. This option is available from the environment page in the Manage Environments page. You can also view the last run report under View Last Pre Check Result under Environment.
Pre-Check in LCM does not take extended storage into account. This means if the extended storage option is used to deploy vRealize Operations Manager nodes using vRSLCM, then the precheck might succeed but the actual deployment can still fail due to insufficient disk space. For more information, see KB article 56365.
Only Automate checks is automated to run a manual pre-requisite for vRealize Suite in vRealize Suite Lifecycle Manager 1.2. You can DOWNLOAD SCRIPT and run on all the windows machine. The zip contains a Readme file, which explains how to run the script. This step is mandatory if you have selected vRealize Automation as one of the products during an environment creation.