When you add a rule to the vSphere Auto Deploy rule set or make changes to one or more rules, hosts are not updated automatically. vSphere Auto Deploy applies the new rules only when you test their rule compliance and perform remediation.
Verify that your infrastructure includes one or more ESXi hosts provisioned with vSphere Auto Deploy, and that the host on which you installed PowerCLI can access those ESXi hosts.
- In a PowerCLI session, run the Connect-VIServer cmdlet to connect to the vCenter Server system that vSphere Auto Deploy is registered with.
The cmdlet might return a server certificate warning. In a production environment, make sure no server certificate warnings result. In a development environment, you can ignore the warning.
- Use PowerCLI to check which vSphere Auto Deploy rules are currently available.
The system returns the rules and the associated items and patterns.
- Make a change to one of the available rules.
For example, you can change the image profile and the name of the rule.
Copy-DeployRule -DeployRule testrule -ReplaceItem MyNewProfile
You cannot edit a rule already added to the active rule set. Instead, you can copy the rule and replace the item or pattern you want to change.
- Verify that you can access the host for which you want to test rule set compliance.
Get-VMHost -Name MyEsxi42
- Run the cmdlet that tests rule set compliance for the host, and bind the return value to a variable for later use.
$tr = Test-DeployRuleSetCompliance MyEsxi42
- Examine the differences between the contents of the rule set and configuration of the host.
The system returns a table of current and expected items if the host for which you want to test the new rule set compliance is compliant with the active rule set.
CurrentItem ExpectedItem ----------- ------------ My Profile 25 MyNewProfile
- Remediate the host to use the revised rule set the next time you boot the host.
What to do next
If the rule you changed specified the inventory location, the change takes effect when you repair compliance. For all other changes, reboot your host to have vSphere Auto Deploy apply the new rule and to achieve compliance between the rule set and the host.