Guidance for Migrating

to License Policies

When upgrading to 2019.1 or above from an earlier version, you need to consider the impact of license policies and user groups. This topic includes guidance on how to preserve the previous default behavior with regard to checking out add-on functionality licenses.

Prior to 2019.1, licenses for add-on functionality were enabled using either the config/clientprops.xml file, or the Edit Capital Configuration dialog box from Capital Application Launcher.

From 2019.1, these mechanisms are no longer available, and the parameters are ignored if present in your clientprops.xml. You now enable the licenses for add-on functionality through the use of license policies in Capital Access Manager.

A license policy is a sub-set of enabled, add-on licenses. A license can be included in multiple policies. You assign license policies to user groups. The licenses included in the policy are made available to users in those user groups.

Caution

There are no default license policies, or user groups. If you do not create license policies and assign them to user groups, all users will be able to use all available add-on licenses.

A user group with no assigned license policies is allowed to use all licenses available in your installation.

Prior to 2019.1, the checking-out of the following licenses was deactivated by default: chstopology, lvlmgr_optimize, and lvlmgr_plan

In order to preserve this previous default behavior, a Capital administrator will have to do the following in the new Capital installation:

1. Create a user group with all Capital users. See Creating and Editing a User Group.

2. Create a license policy with those licenses deactivated. See Creating and Editing a License Policy. Figure 9: Default License Policy

3. Assign the license policy to that user group. See Assigning and Editing License Policies in a User Group.

If you previously used one clientprops.xml to activate and deactivate licenses, your administrator will need to create one license policy.

If you used multiple clientprops.xml files to activate and deactivate different combinations of licenses, your administrator will need to create multiple license policies and user groups, and assign users to appropriate groups.

See the License Policy Creation and License Policy Assignment figures that follow.

Figure 10: License Policy Creation

Figure 11: License Policy Assignment

Note

The strategy to assign license polices to a user group should be as follows:

When you create a user group, assign the most restrictive license policy to start. You can add additional, less-restrictive license policies as needed.

Parent Topic:

License Policy

Related Topics

• Manage License Policies Dialog Box

Capital Access Manager User Guide, 2512.2606

Unpublished work. © 2026 Siemens