Using a scope action, you can:
Report registry information.
Detect machines with a particular registry value.
Modify the registry contents.
This tutorial includes an example for each objective.
You need to generate a report which returns the contents of the HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications key.
Create a new scope action, define its name and click on Next.
Under Scope, select the Computers object type and define the list of machines to process (see: Defining the Scope). Click on Next.
Under Actions, double click on Add New to start the Action Module property window.
Before you can report the objects of a registry key, you need to configure it as accessible in Goverlan.
Under Execute the following Action(s), click on Add/Remove > Report Computer Property > Registry Value > Manage Accessible Key Paths...
In the Registry Key Paths Manager, click on the 
button.
In the Registry Key Paths dialog, click on Open Editor.
Browse to the HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications key, right-click on it and select: Copy Key Name. Then close the Registry editor.
Select the Key Path field and paste the registry path from the clipboard contents. Optionally, enter a display name for this key path. If you leave this field blank, Goverlan generates a display name for you.
If you wanted to report on the specified registry key and its children keys, you would need to check Include child keys. Here, we leave this check cleared. Click on OK.
Click on OK.
Under Execute the following Action(s), click on Add/Remove > Report Computer Property > Registry Value > RegisteredApplication (or the display name you configured) > All Registry Value Information
Note: You may not need to report the full set of attributes. It is always better to minimize the amount of attributes to be reported as it creates an easier to read report.
Instead of selecting All Registry Value Information, select the individual attributes you are interested in one per one.
If you want to exclude some registry information from your report, you can optionally add one or more conditions.
For instance, if you wanted to only report the Safari registry value in this key, you would add the following condition:
Add/Remove > Set Computer Condition > Registry Value > RegisteredApplication (or the display name you configured) > Name :: = ::Safari
Or, if you wanted to report the sub-keys of this key, you would add the following condition:
Add/Remove > Set Computer Condition > Registry Value > RegisteredApplication (or the display name you configured) > Object Type :: = ::Key
Complete your scope action and run it.
You need to detect which machines have ASP.NET version 2.x installed. To do so, you want to detect all machines which have the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.xxxxx registry key configured.
Create a new scope action, define its name and click on Next.
Under Scope, select the Computers object type and define the list of machines to process (see: Defining the Scope). Click on Next.
Under Actions, double click on Add New to start the Action Module property window.
Before you can report the objects of a registry key, you need to configure it as Accessible in Goverlan.
Under Execute the following Action(s), click on Add/Remove > Report Computer Property > Registry Value > Manage Accessible Key Paths...
In the Registry Key Paths Manager, click on the button.
In the Registry Key Paths dialog, click on Open Editor.
Browse to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET key, right-click on it and select: Copy Key Name. Then close the Registry editor.
Select the Key Path field and paste the registry path from the clipboard contents. Optionally, enter a display name for this key path. If you leave this field blank, Goverlan generates a display name for you.
Click on OK.
Under Execute the following Action(s), click on Add/Remove > Report Computer Property > Registry Value > ASP Net (or the display name you configured) > All Registry Value Information
UnderOnly if the following is true, click on Add/Remove > Set Computer Condition > Registry Value > ASP Net (or the display name you configured) > Name :: Begins With ::2.
Complete your scope action and run it. Finally, select the view HTML - Report Model. The results will look something like this:
The Scope Action feature provides you with many ways to modify the registry of your machines. You can create, set, modify or remove individual values and keys or upload entire registry key hives.
In this example, we need to transfer the entire set of configuration settings for a VPN client on a set of machines. The VPN Client settings are stored in the key: HKEY_LOCAL_MACHINE\SOFTWARE\VPNCPro. This registry key contains a lot of sub-keys and values, so it would be hard to configure a scope action to include an action for each individual registry object. Instead, we will be save the entire key into a registry file and ask Goverlan to transfer and register this file into the registry of the machines.
Open the registry editor and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\VPNCPro
Right-click on this key and selectExport. Save the VPNCPro.reg file onto your local system.
Create a new scope action, define its name and click on Next.
Under Scope, select the Computers object type and define the list of machines to process (see: Defining the Scope). Click on Next.
Under Actions, double click on Add New to start the Action Module property window.
Under Execute the following Action(s), click on Add/Remove > Execute Computer Action > Registry Actions > Import a Registry File
In the Set Arguments window, set the Registry Import File parameter to the full path and name of the VPNCPro.reg file on your local system. Click on OK.
Complete our scope action and run.
Once the scope action has been executed, you should check which machines were processed successfully and which machines failed.
Right-click on the scope action object and select View Last Run's Failed Nodes.
Review the Scope Action Log for failed computers and the reason why they couldn't be processed.
If one or more machine failed to be processed in this run because they were temporarily unavailable, you can select to re-run the scope action only for these failed computers at a later time. To do so, select the scope action, right-click on the mouse and select Re-Run on Failed Objects.
You can also schedule the scope action to re-run periodically using the execution mode: Failed Objects Only - Merge Output Data (see: Scheduling a Scope Action). This method of execution only processes the machines which failed during the previous run.