Creating Custom Registry Value Exists Checks


Within VMware vCenter Protect - Configuration Management, you can define a custom check that looks to see if a specific registry value exists on a scanned machine. For example, this type of check could be useful for determining if an application has placed an expected registry key needed for its configuration.


Note: Custom Registry Value Exists checks are not enforceable. Enforcement may be available in a future release of VMware vCenter Protect - Configuration Management. See Enforcement Overview for more information on enforcement.

  1. To create a new custom Registry Value Exists check from scratch, from the Custom Check Wizard click Create New Custom Check.

The following dialog is displayed:


  1. Select the desired operating system levels and then click Next.

The General Properties dialog is displayed.


  1. Type a unique name for the custom check and description.

  2. In the Type box select Registry Value Exists and then click Next.

The Specific Properties dialog is displayed.

  1. Use the available boxes to define the exact registry key for which you want to create a policy check.

You must provide the root and path information (the registry value data type and its data are not relevant to this check). For example:


Hint: For tips on using the Windows Registry Editor program (regedit) to locate these values and easily populate the fields on this dialog, see Using Regedit.

  1. After defining the specific properties of the check, click Test Check.

This will show whether the registry key value defined here currently exists on the local machine.

  1. Click Next.

The Operator and Value dialog is displayed.


  1. Select an operator and an expected value, and then click Next.

  1. Click Next.

The following dialog is displayed.



  1. (Optional) If you want to export this custom check to an XML file to use it as the starting point for other custom checks, click Export to File.

For more information, see Exporting Custom Checks.

  1. Click Finish.

The custom check is displayed within the policy. For example: