If you have custom policies or rules, they must be restored to the driver after you overlay the new driver configuration file. If these policies have different names, they are still stored in the driver, but the links are broken and need to be reestablished.
You can add policies into the policy set in two different ways:
Perform these steps in a test environment before you move the upgraded driver to your production environment.
In the
view, select the upgraded driver to display the view.Right-click the policy set icon where you need to restore the customized policy to the driver, then select
.Browse to and select the customized policy, then click
.Specify the name of the customized policy, then click
.Click
in the file conflict message to save your project.After the Policy Builder opens the policy, verify that the information is correct in the copied policy.
Repeat Step 2 through Step 6 for each customized policy you need to restore to the driver.
Start the driver and test the driver.
For more information on starting the driver, see Section 13.13, Starting the Drivers. For more information on testing the driver, see Testing Policies with the Policy Simulator
in Policies in Designer 4.0.
After you verify that the policies work, move the driver to the production environment.
Perform these steps in a test environment before you move the upgraded driver to your production environment.
In the
view, select the upgraded driver, then click the icon .Right-click the policy set where you need to restore the customized policy to the driver, then select
.Browse to and select the customized policy, then click
.Specify the name of the customized policy, then click
.Click
in the file conflict message to save your project.After the Policy Builder opens the policy, verify that the information is correct in the copied policy.
Repeat Step 2 through Step 6 for each customized policy you need to restore to the driver.
Start the driver and test the driver.
For more information on starting the driver, see Section 13.13, Starting the Drivers. For more information on testing the driver, see Testing Policies with the Policy Simulator
in Policies in Designer 4.0.
After you verify that the policies work, move the driver to the production environment.
Perform these steps in a test environment before you move the upgraded driver to your production environment.
In iManager, select
.Browse to and select the location in the tree to search for Driver Set objects, then click the search icon .
Click the Driver Set object that contains the upgraded driver.
Click the driver icon, then select the policy set where you need to restore the customized policy.
Click
.Select
, then browse to and select the custom policy.Click
, then click .Repeat Step 3 through Step 7 for each custom policy you need to restore to the driver.
Start the driver and test the driver.
For information on starting the driver, see Section 13.13, Starting the Drivers. There is no policy simulator in iManager. To test the policies, cause events to happen that make the policies execute. For example, create a user, modify a user, or delete a user.
After you verify that the policies work, move the driver to the production environment.