# License and Option Selection

## Purpose

Use the License and Option Selection form to modify licenses through the Applications Management Center (AMC). On MiVoice Business, licenses are required for options, features, and system capacity. For example, each IP Phone user that you connect to the system requires an IP User license.

Use this form when performing the following tasks:

- Select Licenses and Options

- Change Licenses and Options

## Conditions

CAUTION: Some changes to this form will affect service on an active MiVoice Business system. It is recommended that you make changes to the License and Option Selection form during off-peak hours. Keep in mind that some changes require a reboot. A reboot takes approximately 20 minutes during which time the MiVoice Business system will be out of service. Refer to the Select Licenses and Options or Change License Options procedure for more information on options that require a reboot and whether the reboot is manual or automatic and which options also require a database backup and restore.

- As of MiVoice Business Release 7.2, if no IP User (IPU) licenses are available (all are consumed or none are allocated), the system automatically consumes Multi-device User (MDU) licenses on behalf of the following IPU license users: Full Service IP Users, IP Console( MiVoice Business Console), External Twin Multi-device User Groups (MdUG). Once IPU licenses become available (for example, additional are allocated), the MDU licenses consumed instead of IPU licenses are automatically returned to the pool.

Changing the number of locally allocated IPU or MDU licenses can affect license consumption during various transactions. After each transaction, the system recalculates and updates the appropriate fields in this form. For details, see Multi-device User License Consumption for IP Users.

- Before you begin, perform a database backup. After you finish changing License and Option Selection parameters, you may need to perform a database restore (see Field Descriptions for details).

- Perform a database backup after changing the IP User or Multi-device User field to avoid possible licensing issues after the restore. For example, if you reduce the number of IPU licenses allocated to below the number consumed, then restore the database saved prior to the change, the restored database will have some MDU licenses consumed by Full Service IP users, causing some Multi-device User Groups (MdUG) to be thrown out due to lack of MDU licenses. Similarly, if you reduce the number of MDU licenses allocated, some Full Service IP users could be thrown out if they were consuming MDU licenses. For more information, see Multi-device User License Consumption for IP Users.

## Column Descriptions

Parameter | Description | Default Value
Locally Consumed | System-generated, protected field. The number of licenses that have been used on this system. This number cannot exceed the amount that is available for allocation. Licenses are used when: A user or device is configured. An ACD agent or MiVoice Business Console operator logs in. A Configuration Option (e.g., Extended Hunt Group) is enabled. |
Locally Allocated | The number of licenses that have been allocated for use on this system. To update this field, click Change, and then enter a numeric value or select an available option. Red colored text indicates that the feature has been over-allocated. |
Available for Allocation | System-generated, protected field. Specifies the total number of licenses that have been purchased, minus any licenses that have already been allocated. If license sharing is enabled, this is the total number available for all members of the application group. Otherwise, it is the number available for the local system only. NOTES This number can be exceeded if Over Allocation or Try Before You Buy is enabled in the System Core Package The minimum licensing required for every system that is sold and licensed through the Mitel Application Management Center. The Core Package tells the AMC what System Type to create on the Application Record and what licenses are included as part of the Core Package. It subsequently controls the type of licenses that can be added to the Application Record and what the license limitations (capabilities) of the Application Record are. Every Application Record on the AMC is essentially a Core Package with additional system licenses added on top of it. in the AMC. If this field contains a shopping cart icon() the administrator can allocate Try Before You Buy licenses. Once the trial period expires and the system passes into license violation mode, the shopping cart disappears and the "Available for Allocation" value is changed to 0. If this field contains "Unknown," there is no limit to the number of licenses available for allocation. |
Purchased | System-generated, protected field. Specifies the total number of licenses that have been purchased for the local system. NOTES If the system belongs to an application group, this field will contain N/A. To obtain licensing information for the group, access the Application Group License Distribution form. If this field contains a nil value (0), licenses may still be allocated on a Try Before You Buy basis. |
Local Limits (Core Package The minimum licensing required for every system that is sold and licensed through the Mitel Application Management Center. The Core Package tells the AMC what System Type to create on the Application Record and what licenses are included as part of the Core Package. It subsequently controls the type of licenses that can be added to the Application Record and what the license limitations (capabilities) of the Application Record are. Every Application Record on the AMC is essentially a Core Package with additional system licenses added on top of it.)
Licenses Allowed | System-generated, protected field. Specifies the maximum number of licenses that can be allocated to the local system, as defined by the System Core Package in the AMC. NOTES If this field contains "Unrestricted," there is no limit to the number of licenses available for allocation, provided that the system has sufficient resources. This is a "soft" limit that represents the absolute maximum number of licenses that can be allocated. Accordingly, this field may contain a value that exceeds the purchased number of licenses for the local system. |
Can be Over Allocated | System-generated, protected field. Specifies whether licenses can be allocated to the application in excess of the purchased limit, as defined by the System Core Package in the AMC. If no licenses have been purchased, the application cannot be over allocated. Note that over allocating causes a license violation error. |

## Field Descriptions

Parameter | Description | Default Value
System Licenses and Option Selection Online Licensing with the Application Management Center
Application Record ID | System-generated, protected field. Displays the ARID entered in the Service account ID field under ServiceLink > Status in the Server Manager (for all platforms except Container-based MiVoice Business (cMiVB). For Container-based MiVoice Business (cMiVB), the ARID is auto-generated and configured during the deployment. NOTE: After the account is activated, the AMC is contacted and the System Core Package license values are retrieved and automatically appear within the form (they do not need to be typed in manually). | Blank
System Type | System-generated, protected field. Specifies the system type programmed in the AMC. Options include: Unknown - The system is not yet activated on the AMC. Standalone - The system does not support clustering, IP trunks or resiliency. All other MiVoice Business features, including XNET trunks, are supported. Enterprise - The system supports the full range of MiVoice Business features, including clustering, IP trunks and resiliency. NOTE: When a system is changed from Standalone to Enterprise, its database is erased. To retain data, perform a backup prior to programming the System Type in the AMC. Then perform a restore. | Unknown
License Sharing | System-generated, protected field. Specifies whether the system is a member of an application group on the AMC. Options include: No - The system is not a member of an application group. Therefore, it cannot share licenses with other elements. Yes - The system is a member of an application group. Therefore, it can share licenses with other elements in the same group. Use the Application Group License Distribution form to track the number of licenses that have been purchased, allocated, and used. | No
Hardware Identifier | System-generated, protected field. When the installation of the MiVoice Business software is complete, it generates a unique Hardware ID that includes the MAC address of the controller. The system uses the Hardware ID and the Application Record ID to identify itself to the AMC. Upon synchronization with the AMC, purchased software and options become available. | Blank
Licensed Options - Users |
IP Users | Allocate the number of licenses (0-5600) for MiNet and SIP users/devices. An IP User License is consumed by each of the following: Standard user & device IP console Hot Desking user ACD enabled set ACD Hot Desking agent ACD Express agent If no IP User (IPU) License is available (all are consumed or none are allocated), the system automatically consumes a Multi-device Users (MDU) License instead. If at least one MDU License is being consumed instead of an IPU License and you increase the value of this field, some MDU Licenses automatically return to the pool and the corresponding number of the newly allocated IPU Licenses are automatically consumed. You can also decrease the value of this field to below the number of currently consumed licenses, if there is enough MDU Licenses available to compensate for the decrease. After each transaction, the system displays the following warning, then recalculates and updates the affected fields: The number of locally allocated IPU licenses has changed, therefore the IP and Multi-device Users consumed fields have been recalculated. If there is not enough MDU licenses to compensate for the decrease in this field, the transaction fails and the following error message is displayed: Insufficient Multi-device Users to handle the removal of IP Users. NOTE: It is recommended that you perform a database backup after changing this field to avoid possible licensing issues after the restore. For more information, see Multi-device User License Consumption for IP Users. The maximum number of licenses available varies by controller type as follows: AX: 700 CX II or CXi II: 700 MXe III: 5600 After saving the change, a reboot is required if: you are installing a new system that does not yet have IP User Licenses you have reduced the number of IP User Licenses. NOTES Hot desk users and SIP phones require an IP User license. For additional information on licenses, refer to About IP User and Device Licenses. | 0
External Hot Desk Users | Allocate the number of licenses for External Hot Desk Users (EHDUs) and External Hot Desk Agents (EHDAs) (0 to 5600 of IP User Licenses allocated). | 0
ACD Active Agents | Allocate the number of licenses (0-2100 for server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms ; 0-350 for all other controllers) for ACD Active Agents. Changes are updated immediately without a reboot. Although these are the maximum possible configuration values, please see the MiVoice Business Engineering Guidelines for the recommended maximums. When 0 is selected, ACD options (ACD, ACD Extended Agent Skill Groups, ACD Skills-based Routing, ACD Real Time Events, Networked ACD, ACD Max Agent ID Appearances) are disabled. ACD Active Agent Licenses cannot be over-allocated. | 0
HTML Applications | Allocate the number of licenses (0-5600) for HTML Apps Infrastructure. Each license allows you to assign HTML applications to a device using any of the following: the User and Services Configuration form, the Multiline Set Keys form, the Settings key on the phone or the Desktop Tool. One license is required per DN. Use the Multiline IP Sets form to assign the DN(s) a license. Licenses are only required for applications developed using the Release 2 HTML Toolkit. Release 1 applications do not need to be licensed and will continue to work Changes are updated immediately without a reboot. | 0
Single Line Users | Allocate the number of licenses (0-5000) for Single Line Users. The licenses can be used to enable an ONS or OPS line card circuit on an AX controller, or an ASU II; and to configure a Generic SIP Phone as a Single Line Phone. Changes from a non-zero value to any other value are updated immediately without a reboot. Changes from zero to any value require a reboot. NOTES: The AX controller and ASU II support ONS line cards Analog devices programmed as a Remote Group Pilot Number in the Analog Sets form do not consume a Single Line Users license. | 0
MiVoice Business Console Active Operators | Allocate the number of licenses (0-20) for MiVoice Business Console operators. Changes are updated immediately without a reboot. This type of license is consumed while the console is in "Operator Present" state. When console changes to "Operator Absent"state the license is returned to the pool for use by other MiVoice Business Consoles. Use the LOCATE OPERATORS maintenance command to identify the consoles currently consuming licenses. Actions that cause the console to go absent (thereby relinquishing consumption of an Active Operators license): Putting the MiVoice Business system into Night Service via the last console. Expiration of the Attendant Busy-out COS timer. Setting DND on a MiVoice Business Console remotely using the DND remote feature access code or from the console interface using the Program Sets menu. Failover of a present MiVoice Business Console from the primary to secondary controller. Deleting a present MiVoice Business Console from the primary controller in ESM, or through an SDS sync action (sync from a secondary that does not have a console configured to a primary that does have a console configured. Loss of LAN connection between a Present MiVoice Business Console and the MiVoice Business system. Closing the MiVoice Business Console application. NOTES The 5540 IP Console does not require an Active Operators license. A MiVoice Business Console requires both an IP User license and an Active Operator license to operate. Other IP console types require an IP User license only. Resilient consoles require licences while connected to their primary controller only. If a MiVoice Business Console is unable to obtain an Active Operator license because they are all in use, the user is presented with the option of forcing another console Absent to free up its license. | 0
Multi-device Users | Allocate the number of licenses for Multi-device User Groups (MdUG). Changes are updated immediately without a reboot. The limit on MdUG licenses is equal to half the maximum number of prime lines on the system. See MdUG Limits for more information. Standard group: A single MdUG license is consumed when a PRG is programmed on the Multi-device User Groups form. The license is shared between all members of the group, provided that they are programmed as Multi-Device This Service Level indicates that the directory number (DN) is assigned to a user that has only basic telephony functionality (e.g., emergency or attendant calls) until programmed as a member of a Multi-Device user group or suite. The DN does not use an IP User License. However, the group or suite has a Multi-device Users or Multi-device Suites license which one person can use at a time in order to receive full telephony service. users. The prime member of the group has access to full telephone functionality and can be programmed on the same forms as Full Service This Service Level indicates that the directory number (DN) is assigned to a standard user and device with full telephony functionality. users. External Twinning group: An MdUG license is not required for External Twinning but an IP User (IPU) license must be available and is consumed on the primary node. However, if an IPU license is not available, a Multi-device Users (MDU) license will be consumed instead. If the user is an External Hot Desk User (EHDU), an EHDU license must be available and is consumed on the primary node. MDU licenses are automatically consumed on behalf of the IPU license users when no IPU license is available: Full Service IP User, IP Console, or External Twin MdUG. When an IPU license becomes available, an MDU license automatically returns to the pool. For more information, see Multi-device User License Consumption for IP Users. If you attempt to decrease the value of this field to below the number of MDU licenses currently consumed, the system displays the following message: Unable to change "Multi-device Users". Delete <x> Multi-device Users currently using these licenses and try again. Since IP users can also consume MDU licenses, the above message means that you need to delete x number of Multi-device Users or Full Service IP Users. NOTE: It is recommended that you perform a database backup after changing this field to avoid possible licensing issues after the restore. See Multi-device User License Consumption for IP Users for details. | 0
Multi-device Suites | Allocate the number of licenses (0-350) for Multi-device Suites. Changes are updated immediately without a reboot. A single Multi-device Suites license is consumed when a suite is programmed on the Multi-device Suites form. The license is shared between all members of the group, provided that they are programmed as Multi-Device This Service Level indicates that the directory number (DN) is assigned to a user that has only basic telephony functionality (e.g., emergency or attendant calls) until programmed as a member of a Multi-Device user group or suite. The DN does not use an IP User License. However, the group or suite has a Multi-device Users or Multi-device Suites license which one person can use at a time in order to receive full telephony service. users. | 0
Purchased Options - Messaging
Embedded Voice Mail | Allocate the number of Mailbox licenses (0-750 for PowerPC (PPC) platforms Variants of MiVoice Business that use PowerPC processors--MX, MXe, CX, CXi, and AX. See also x86 platforms.; 0-5000 for x86 platforms (server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms). Refer to the MiVoice Business Engineering Guidelines for provisioning rules. Changes from a non-zero value to any other value are updated immediately without a reboot. Changes from zero to any value require a reboot. | 0
Embedded Voice Mail PMS | Select "Yes" if a Hospitality/Property Management System (PMS) license is available for allocation in order to use embedded voice mail for guest services. Changes are updated immediately without a reboot. You must configure PMS features before the functionality will be available. NOTE: This license is required when using embedded voice mail for guest services. It is not required for clustered hospitality or PMS. | No
Purchased Options - Trunking/Networking
Digital Links | Allocate the number of licenses (0-16) for Digital Links. Changes are updated immediately without a reboot. | 0
Compression | Allocate the number of licenses (0-256). The limits are 256 server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms ; 128 on AX; 64 on CXi II and MXe III, and 24 on EX. Changes are updated by the next reboot. Licensed 1 per bidirectional channel of compression. Ensure that you have enough DSPs to support the compression licenses allocated. Compression licenses are purchased in groups of eight. | 0
FAX Over IP (T.38) | Allocate the number of licenses for fax over IP. Licenses are purchased in groups of four. You can purchase a maximum of 64 licenses. Each license supports a single FAX Relay (T.38) channel. A reboot is required to enable new FAX Relay (T.38) licenses. NOTES The maximum number of supported T.38 licenses depends on your system configuration. Refer to the MiVoice Business Engineering Guidelines for details. FAX over IP support requires the DSP II card. You can allocate and configure licenses on the system before you install the required DSP II cards in the system. However, an alarm will be raised after you reboot the system if required DSP II cards are not installed. Refer to the Engineering Guidelines to determine the DSP resource requirements for the system. This field is disabled and not applicable to EX controllers. | 0
SIP Trunks | Allocate the number of licenses (0 to 2000) for SIP Trunks. Changes are updated immediately without a reboot. These licenses are distributed to the SIP peers through the SIP Peer Profile form. Each SIP Peer has access to the whole pool of licenses, but you can also reserve some or all of the assigned licenses for a particular peer. NOTE: An increase in licenses takes place immediately. To decrease licenses, you may be required to remove some licenses from the SIP Peer Profile form first. This ensures that the number of licenses do not decrease below the actual licenses programmed for use. | 0
Purchased Options - Others
IDS Connection | Select "Yes" if an Integrated Directory Services (IDS) license is available for allocation. Enabling the IDS license adds new forms to the interface. Changes are implemented immediately without a reboot. |
MLPP | MLPP is not supported by the MiVoice Business system. | No
Configuration Options |
Country | Select the country variant of the system. This parameter is used to set the default language, dialing plan, tone plan, and loss and level plan. Language refers to the text on the Mitel phone displays. AUX1 and AUX2 are the alternate languages that can be selected from the set or from the System Administration Tool using the LANGUAGE SELECT maintenance command. (The language of the embedded voice mail prompts are independent of the set language and selected by the administrator only in the VM Prompt Languages form.) Supported countries and associated languages are as follows:
Region | Language
| Default | Aux1 | Aux2
UK | English | French | Italian
North America1 | English | French | LA4 Spanish
New Zealand | English | German | Italian
Italy | Italian | EU2 Spanish | English
Germany | German | English | Dutch
China | SIMP3 Chinese | English | French
Latin America | LA4 Spanish | English | PT5 Portuguese
Spain | EU2 Spanish | English | PT5 Portuguese
Portugal | PT5 Portuguese | EU2 Spanish | English
Holland | Dutch | English | German
Australia | English | German | Italian
Brazil | BR6 Portuguese | LA4 Spanish | English
France | French | English | EU2 Spanish
1 North America = United States, Canada 2 EU = Europe 3 SIMP = Simplified 4 LA = Latin America (Argentina, Chile, Mexico) 5 PT = European (Portuguese) 6 BR = Brazil
A change to this option requires a DBMS Save, Reboot, and Restore. The Italy option also suppresses internal inter-digit timers, and uses the inter-digit timeouts provided by the network or the PRI card. includes a supplementary information string that identifies the calling party as an analog device (for analog devices that originate calls to ISDN trunks, in the DPNSS call setup message). | North America
Extended Agent Skill Group | For non-x86 platforms, select "Yes" to enable Extended Agent Skill Groups and allow up to 128 Agent Skill Groups with a maximum of 500 agents per group. For x86 platforms (server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms), select "Yes" to allow up to 999 Agent Skill Groups with a maximum of 700 agents per group. For all systems, Select "No" to disable Extended Agent Skill Groups and allow up to 64 Agent Skill Groups with a maximum of 150 agents per group. IMPORTANT: Changing this option results in a system dimension change. It also erases the system database. To preserve the database, make a backup before changing the option. Following the change, reboot the system, and restore the database. Make sure to select “Use current (select if Dimensions were modified)" when prompted to avoid restoring the original database. NOTE: The total number of Agent Skill Groups includes ACD groups for which the system is the primary element, ACD groups for which the system is the secondary element, and ACD Express groups. This effectively reduces the maximum number of ACD groups. | No
Maximum Elements per Cluster | Select the maximum number of elements permitted in a network cluster (30, 60, 250, 999). When 30 or 60 elements are enabled, Mitel Feature Resource Dimension (MFRD) 17 is applied to the system. If 250 or 999 elements are enabled, MFRD 19 is applied. The MFRD level for the system is displayed in the Dimension Selection form. IMPORTANT: Changing this option results in a system dimension change. It also erases the system database. To preserve the database, make a backup before changing the option. Following the change, reboot the system, and restore the database. Make sure to select “Use current (select if Dimensions were modified)" when prompted to avoid restoring the original database. NOTES The same Maximum Elements per Cluster must be configured for all elements within the cluster; the selected value should be relative to the actual size of the cluster. All elements in the cluster must have 999 Maximum Elements Per Cluster programmed to support more than 28500 Remote Directory Numbers. For PowerPC (PPC) platforms Variants of MiVoice Business that use PowerPC processors--MX, MXe, CX, CXi, and AX. See also x86 platforms., the combination of 250 or 999 Maximum Elements per Cluster and 5600 Configurable Users and IP Devices will cause unnecessarily high resource usage, and for that reason it is not recommended. If you attempt to save such combination, the following warning will be displayed: "The currently selected license and options combination of 5600 IP users and 250/999 cluster elements is not recommended for this hardware platform. The Max elements per cluster should be set to 30 or 60 when selecting 5600 IP users. Press OK to proceed or cancel to correct." To optimize resource usage, set this field to 30 or 60 if you need to configure 5600 IP users and devices. | 30
Maximum Configurable IP Users and Devices | This field may be system-generated and protected, depending on the MiVoice Business controller type and amount of system memory. AX: 700 CX II or CXi II: 700 MXe III: 5600 IMPORTANT: Changing this option results in a system dimension change. It also erases the system database. To preserve the database, make a backup before changing the option. Following the change, reboot the system, and restore the database. Make sure to select “Use current (select if Dimensions were modified)" when prompted to avoid restoring the original database. NOTES This field limits the IP Users Licenses field. For example, if you enter 5600 here, you cannot enter more in the IP User Licenses field. The actual number of physical connections supported by the controller may be less than the value selected in this field. For example, although it is possible to program a maximum of 700 IP user and devices for an AX Controller, the system will only support 100 IP Phones in a normal-traffic environment or 288 IP Phones in a low-traffic environment. This is a node-specific value and it should reflect the actual number of users and devices to be supported by the node. For PowerPC (PPC) platforms Variants of MiVoice Business that use PowerPC processors--MX, MXe, CX, CXi, and AX. See also x86 platforms., the combination of 5600 IP Users and Devices and 250 or 999 Maximum Elements per Cluster will cause unnecessarily high resource usage, and for that reason it is not recommended. If you attempt to save such combination, the following warning will be displayed: "The currently selected license and options combination of 5600 IP users and 250/999 cluster elements is not recommended for this hardware platform. The Max elements per cluster should be set to 30 or 60 when selecting 5600 IP users. Press OK to proceed or cancel to correct." To optimize resource usage, set this field to 700 if you need to configure 250 or 999 Maximum Elements per Cluster. | Varies
Extended Hunt Group | For non-server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual platforms, selecting "Yes" allows up to 16 Hunt Groups with a maximum of 250 members per group. Only one 250-member voice mail hunt group should be programmed on a switch; a 250-member recorder hunt group can also be programmed. Do not program any additional large (more than 64 members) groups. Selecting "Yes" also allows for more than 64 ports in an Embedded Voice Mail (EMEM) Hunt Group setup. IMPORTANT: Changing this option results in a system dimension change. It also erases the system database. To preserve the database, make a backup before changing the option. Following the change, reboot the system, and restore the database. Make sure to select “Use current (select if Dimensions were modified)" when prompted to avoid restoring the original database. When this option is set to "No" (default) the system uses the existing Hunt Group capacity: up to 2000 Hunt Groups with a maximum of 64 members per group for server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual platforms; up to 176 Hunt Groups with a maximum of 64 members per group for all other platforms. NOTES Extended Hunt Group functionality is intended to support hunt groups of type "VoiceMail" and "Recorder" only for NuPoint Messenger IP Release 10.0 voice mail. Extended Hunt Groups are also required when more than 65 MiCollab Audio, Web, and Video Conferencing User Licenses are purchased. It should not be used for other purposes. Hunt Groups will be lost if the option is selected when more than 16 hunt groups are programmed on the switch. Only one extended hunt group of type VoiceMail is supported on a controller. Only one extended hunt group of type Recorder (for Record-A-Call) is supported on a controller. Refer to the Hunt Groups for the maximum number of members supported in an extended hunt group. | No
5560 IPT Device Extended Key Lines | Select "Yes" to enable provisioning of an additional 96 line keys (for a total of 192) on the 5560 IPT. Support for 192 keys is available to 700-user systems only; 5600-user systems are limited to 96. IMPORTANT: Changing this option results in a system dimension change. It also erases the system database. To preserve the database, make a backup before changing the option. Following the change, reboot the system, and restore the database. Make sure to select “Use current (select if Dimensions were modified)" when prompted to avoid restoring the original database. NOTE: Enabling this option consumes a "virtual" (non-physical) PKM Programmable Key Module for each “5560 IPT device configured. The maximum number of PKMs (virtual and physical) supported per system is normally 75 (as reported in the System Capacity and Dimension Selection forms). Selecting this option increases the maximum to 700. | No
Extended PRG/MDUG | Select "Yes" to allow up to 16 Personal Ring Group (PRG) or Multi-device User Group (MdUG) members per group. If you modify the setting to "No", the system reverts to the default setting that allows up to 8 PRG/MdUG members in a group and increases the number of combined PRG/MdUG groups back to the default. IMPORTANT: Changing this option results in a system dimension change. It also erases the system database. To preserve the database, make a backup before changing the option. Following the change, reboot the system, and restore the database. Make sure to select “Use current (select if Dimensions were modified)" when prompted to avoid restoring the original database. | No

Purchased:System-generated, protected field. Specifies the number of licenses purchased for the system, as defined by the System Core Package in the AMC. If this field contains a nil value (0), licenses may still be allocated on a "Try Before You Buy" basis.