akkadian Provisioning Manager Express

Transcription

1 akkadian Provisioning Manager Express Version Release Notes January 31 st, 2017 Copyright and Trademarks: I. Copyright: This website and its content is copyright 2017 Akkadian Labs, LLC. All rights reserved. Except with the prior written permission of Akkadian Labs, LLC, any redistribution or reproduction of part or all of the contents of this website, including the redistribution or reproduction of any documentation or other materials downloaded from this website, in any form and in any media, is prohibited. II. Trademarks: Akkadian Labs, the Akkadian Labs logo and other trademark or service marks used on this website, whether registered or not, are the property of Akkadian Labs, LLC and may not be used or reproduced without the prior written permission of Akkadian Labs, LLC. apme RN 1/15/

2 Table of Contents Upgrade Notes New and Changed Features... 5 Visual Phone Editor Enhancement Resolved Caveats New and Changed Features... 8 Visual Phone Editor... 8 Additional Swap Support... 9 Device Swap Feature... 9 User Swap Feature DN Synchronization to Microsoft Active Directory Device Overwrite Enhancement Personal Audit Report Cisco VG300 Series Gateway Support Global Variable List Enhancement Unity Application Server Synchronization Application Server Synchronization Scheduling Enhancement DN Pool Reporting Job Templates Device Groups Resolved Caveats New and Changed Features Resolved Caveats Upgrade Notes New and Changed Features CUCM End User Database - LDAP Status Monitoring Client Matter & Forced Authorization Code Support Provisioning Enhancements akkadian Provisioning Manager Express Version Release Notes 1/31/2016 2

3 Bulk Phone Swap Automatically Generate Dummy MAC address View and Provision Results Overwrite Device Option Extension Mobility Auto-logout feature on Delete Site Template Enhancements New Provisioning Options Site Template Bulk Import Provisioning User Interface Enhancements Job Template Export and Import Resolved Caveats akkadian Provisioning Manager Express Version Release Notes 1/31/2016 3

4 Upgrade Notes Make sure you have a backup of apme before running the upgrade. The apme upgrade process preserves all data and does not require a server reboot. Please note that apme is no longer supported on Windows. apme for Windows can easily be migrated to Linux using the backup and restore process. All clusters, including Unity Connection must be synchronized after performing the upgrade or provisioning will not function properly Support for Upgrading from Previous Versions of apme apme supports direct upgrades from the following version of apme: apme and above apme supports upgrades from the following version of apme with the addition of a pre-upgrade patch: apme apme apme , , & Prior to upgrading from any release requiring the pre-upgrade patch, please download the respective patch here: apme for Windows - Download Patch here apme for Linux- Download Patch here akkadian Provisioning Manager Express Version Release Notes 1/31/2016 4

5 New and Changed Features Visual Phone Editor Enhancement Visual Phone Editor has been updated to support editing Speed Dials. Visual Phone Editor Features: Changing the phone button template for device Associating existing lines to the device Editing Speed Dial and BLF Speed Dials Editing the Line on Device settings Modifying line positions using drag and drop Modifying speed dial positions using drag and drop Using Visual Phone Editor: 1. Select Visual Phone Editor from the Actions menu 2. Select the appropriate Service Group 3. Search for and select the device to edit 4. Perform the desired edit actions using Visual Phone Editor 5. When finished, click to apply the changes akkadian Provisioning Manager Express Version Release Notes 1/31/2016 5

6 Resolved Caveats Tracking Number PME-3500 PME-3535 PME-3537 PME-3316 Description Display and log error when unable to find Importable Unity User. Global Variable - Input Validation is currently not saving Self-provisioning service is not functioning Cannot log into apme after deleting default LDAP agreement akkadian Provisioning Manager Express Version Release Notes 1/31/2016 6

7 akkadian Provisioning Manager Express Version Release Notes 1/31/2016 7

8 New and Changed Features Visual Phone Editor Visual Phone Editor provides the ability to visually edit a device. This tool can be very useful when editing phones with add-on modules containing bridged line appearances. Visual Phone Editor supports the following functions: Changing the phone button template for device Associating existing lines to the device Editing the Line on Device settings Modifying line positions using drag and drop Modifying speed dial positions using drag and drop Using Visual Phone Editor: 6. Select Visual Phone Editor from the Actions menu 7. Select the appropriate Service Group 8. Search for and select the device to edit 9. Perform the desired edit actions using Visual Phone Editor 10. When finished, click to apply the changes Figure akkadian Provisioning Manager Express Version Release Notes 1/31/2016 8

9 Additional Swap Support The Phone Swap feature has been renamed to Swap and expanded to support, phones, device profiles and end users. The Swap feature migrates configurations between: Devices swap phones or device profiles of the same or different model Users migrate device associations and ownership to a new user Device Swap Feature The Device Swap tool provides the ability swap configurations between most phone and device profile models. This tool is very useful when you need to replace a user s phone or profile with the same or different model. Device swap will provision the new device, copy all applicable settings, apply device ownership and associated the new device with the user. The tool also provides the option to delete the old device upon successful completion of the swap. This feature can be equally as useful when adding a new device to a user as it will copy over pertinent settings and perform all proper associations. Swapping some newer phone models to older phone models may result in errors due to model incompatibility between the Max Call & Busy Trigger. Phone Swap supports Intercom lines, but the Intercom Line will always be removed from the source phone prior to the swap due to CUCM inability to support shared Intercom Lines. If the target device does not support the same number of lines or speed dials, they will show up as unassociated. Performing a Device Swap: 1. Select Swap from the Actions menu. 2. Select the appropriate Service Group. akkadian Provisioning Manager Express Version Release Notes 1/31/2016 9

10 3. Select the Source Device Type: Phone or Device Profile 4. Locate the Source Device. This is the device you want to copy. 5. If you wish to delete the source device upon successful completion of the swap, select the Delete source device after swap checkbox 6. Select the Target Device Type. This is the model of the target device. 7. Select the Target Device Protocol. This may vary depending on the model. 8. Select the Target Device Template. The Template is used to configure required settings which are not available to be copied from the source device. For example, if you are going from a SCCP phone to SIP phone, the SIP profile will be configured using the Template. 9. Click Perform to complete the swap. Templates used for Swap should not contain GVs. If the device is the same model and protocol, a template is not required. 10. Enter the device name or MAC address. 11. Click to complete the process. Figure Phone Swap User Swap Feature The End User Swap tool provides the ability to migrate all line and device associations from one user to another. akkadian Provisioning Manager Express Version Release Notes 1/31/

11 Performing a User Swap: 1. Select Swap from the Actions menu. 2. Select the End-User Swap Form Tab. 3. Select the appropriate Service Group. 4. Select the Source End User. 5. If you wish to delete the source user upon successful completion of the swap, select the Delete source end-user after swap checkbox. 6. Select New User Account to create and new user during the process or selecting and existing user as the target. Note - all existing associations will be removed from target user. 7. Click Perform to complete the swap. Figure Device Profile Swap akkadian Provisioning Manager Express Version Release Notes 1/31/

12 DN Synchronization to Microsoft Active Directory apme now supports the ability to push a telephone number to Active Directory. apme uses LDAP to update the Active Directory attribute of the provisioned users directory number. To configure apme to use this feature: Step 1 Configure an LDAP agreement with write access to an LDAP Base URL containing the users that will be updated. If there is already an LDAP agreement that meets these requirements, proceed to Step Log into apme as PMEAdmin 2. Select LDAP from the System menu 3. Click Add to add a new LDAP agreement 4. Configure the LDAP settings for your environment and click Save LDAP Configuration Field LDAP Config Name Base Server Port Username Password Username Bind Attribute Description Enter a name to identify this specific LDAP configuration Enter the LDAP search base. Ensure search base contains users that will be updated. The LDAP server IP address or DNS name Enter the LDAP server port number Enter the LDAP Username used to authenticate to the LDAP server Enter the LDAP Password used to authenticate to the LDAP server Enter LDAP Attribute to bind to Username during authentication Step 2 Enable the DN Synchronization to Active Directory feature on the Service Group. 1. Select Service Group from the System menu 2. Select the appropriate Service Group 3. Scroll down to the DN Synchronization to Active Directory section 4. Complete the fields as shown in the table below akkadian Provisioning Manager Express Version Release Notes 1/31/

13 DN Synchronization to Active Directory Enable DN synchronization to Active Directory LDAP server Username Bind Attribute LDAP Update Attribute Check this box to enable the feature Select the LDAP agreement to use for the sync. The user in the LDAP agreement must have write privileges. Specify the LDAP attribute used to bind or locate the user. This must match the username being provisioned by apme to function. This is the attribute in LDAP that will updated. This is typically telephonenumber or ipphone in Active Directory. Example configuration Step 3 The final step is to configure DN Synchronization to Active Directory on a Site Template. This feature can be enabled on as many Site Templates as necessary. When the feature is enabled on a Site Template, whenever the Site Template is used to provision it will attempt to update the matching user in Active Director. If the apme username cannot be matched to the LDAP bind username in Active Directory, the action will be ignored and the job will continue to process. To configure the Site Template: 1. Select Site Template from the Templates menu 2. Select the appropriate Site Template 3. Scroll down to the DN Synchronization to Active Directory section 4. Complete the fields as shown in the table below akkadian Provisioning Manager Express Version Release Notes 1/31/

14 DN synchronization to Active Directory Enable DN synchronization to Active Directory Enable Synchronization Rules DN Begins With Discard Digits Prefix Select this option to enable pushing the Directory Number to Active Directory Select this option to enable synchronization rules, which allow manipulation of the Directory Number before it is pushed to Active Directory Used to match the DN in order to apply the rule The number of digits to discard from left to right Digits to prefix. Applied after the digits are discarded. Device Overwrite Enhancement The device overwrite feature has been enhanced to overwrite the following fields: Phone Description Phone Load Name Packet Capture Duration Information Directory Messages Services Authentication Server Proxy Server Idle Idle Timer(seconds) Secure Authentication URL Secure Directory URL Secure Idle URL Secure Information URL Secure Messages URL Secure Services URL Secure Shell User Secure Shell password akkadian Provisioning Manager Express Version Release Notes 1/31/

15 Personal Audit Report Users are now presented with a personal audit trail upon login to apme. The audit trail contains all provisioning actions for the logged in user. The audit trail can be accessed anytime by click on the akkadian Provisioning Manager Express in the upper left-hand corner of the screen. akkadian Provisioning Manager Express Version Release Notes 1/31/

16 Cisco VG300 Series Gateway Support apme 4.9 adds support for provisioning VG300 series analog gateways. As with support for other analog gateways, the gateway must be fully configured in CUCM before apme can manage the ports. Support has been added for the following VG3XX models: VG310 VG320 VG350 Global Variable List Enhancement The Global Variable List feature has been enhanced to include a Display Name and Value field. The Display Name value will appear in the Global Variable drop-down page, but the Value will be applied to the provision. akkadian Provisioning Manager Express Version Release Notes 1/31/

17 Unity Application Server Synchronization Prior to apme 4.9, Unity Connection did not synchronize any data to the apme database. Starting with version 4.9, Unity Connection now synchronizes certain data to apme to support template import and export. Unity Connection end user data is not synchronized as part of this process. Application Server Synchronization Scheduling Enhancement The apme 4.9 application server synchronization scheduling feature has been enhanced to include the ability to set the time and day(s) to perform application server synchronization. An notification can now be sent upon a successful and or failed application server sync. akkadian Provisioning Manager Express Version Release Notes 1/31/

18 DN Pool Reporting apme 4.9 now includes DN Pool usage reporting. This feature provides the percentage of available directory numbers within a DN Pool. In addition to providing usage data, apme 4.9 provides the ability to send DN Usage Reports via and the ability to customize threshold color indicators. DN Usage reporting configuration settings must be configured at the Service Group level. To Configure DN Reporting Configuration options: 1. Select Service Groups from the System menu 2. Click on the Service Group 3. Scroll down to the DN Reporting Configuration section 4. Configure the options as shown in the table below DN Pool Reporting Configuration Specify what time the DN Pool usage Set Time information should be updated from CUCM. Select which days the DN Pool usage Set Days information from be updated from CUCM. Send Specify an address to which the system Notification will send usage warning. Set the respective thresholds for DN pool Usage Levels warning levels. akkadian Provisioning Manager Express Version Release Notes 1/31/

19 Job Templates Device Groups apme 4.9 adds support for Device Groups in Job Templates. Device Groups provide the ability to select one or more devices during the provisioning process. The Device Group alleviates the need to create one Job for each device type, instead allowing the provisioner to select the device(s) at provision time. Using Device Group: Jobs may only contain one Phone Device Group Jobs may only contain one Device Profile Device Group Device Profile and Phone Device Groups may be used simultaneously within a Job Device Groups may be used in conjunction with standard Device and Device Profile Groups. Configuring Device Groups: 1. Select Job Builder from the Templates menu 2. Create or select an existing job akkadian Provisioning Manager Express Version Release Notes 1/31/

20 3. If you selected an existing job, click the checkbox to enable the feature 4. If creating a new job, add at least one phone template and then click on the checkbox to active the feature 5. Drag additional phone templates into the group 6. When finished configuring the job, click Save akkadian Provisioning Manager Express Version Release Notes 1/31/

21 Resolved Caveats Tracking Number PME-3446 PME-3454 PME-3476 PME-3478 PME-3482 PME-3483 PME-3486 PME-3498 PME-3505 PME-3510 Description Search is throwing error if all service groups are selected and one of the CUCMs is not available. Removed add-on module option from device that do not support add-on modules Not validating SMTP Username and Password Bulk Delete for End-user is not working Intercom templates line templates should only show Intercom CSS types Remove Auto Answer Off as an option in Intercom Template WebEx - Call-in-teleconferencing Section - Add support for selecting Toll & Toll Free option License Pool - Should assign license user when no userid is selected Phone Template not saving Service URL under Configure Phone Buttons Bulk add for Device Profile is not working akkadian Provisioning Manager Express Version Release Notes 1/31/

22 New and Changed Features Provisioning Manager Express contains no new or changed features. akkadian Provisioning Manager Express Version Release Notes 1/31/

23 Resolved Caveats Tracking Number PME-3463 Description Cross-Server Transfer Extension(URI) field replaced with zero after 4.8 update akkadian Provisioning Manager Express Version Release Notes 1/31/

24 Upgrade Notes Make sure you have a backup of apme before running the upgrade. The apme upgrade process preserves all data and does not require a server reboot. All clusters must be synchronized after performing the upgrade Support for Upgrading from Previous Versions of apme apme supports direct upgrades from the following version of apme: apme and above apme supports upgrades from the following version of apme with the addition of a pre-upgrade patch: apme apme apme , , & Prior to upgrading from any release requiring the pre-upgrade patch, please download the respective patch here: apme for Windows - Download Patch here apme for Linux- Download Patch here akkadian Provisioning Manager Express Version Release Notes 1/31/

25 New and Changed Features CUCM End User Database - LDAP Status Monitoring Provisioning Manager Express now includes the ability to monitor the CUCM end user database for Disabled LDAP Synchronized Users and take one or both of the following actions: 1. Send an notification 2. Deprovision the user This feature is not active by default and is only applicable when apme is integrated to a CUCM cluster using LDAP synchronization. To activate the LDAP Status Monitoring feature: 7. Select Service Groups from the System menu 8. Navigate to the CUCM End User Database - LDAP Status Monitoring section 9. Click the Enable LDAP Status Monitor checkbox to enable the feature 10. Set the polling Frequency. This is the frequency in hours that apme will query the CUCM end user database to check for disabled LDAP synchronized users. 11. Check the Send Notification Checkbox and provide a valid address for apme to send a notification when disabled LDAP users are located. 12. Check the Deprovision User box to activate automatic deprovisioning when a user becomes inactive. Any combination of the following items can be automatically deprovisioned: Lines Hard Phones (Devices) Soft Phones (Devices) Mobility (RDP & RD) Device Profiles akkadian Provisioning Manager Express Version Release Notes 1/31/

26 Webex accounts Voice Mail (Unity) Deprovisioned item details will be included in the notification Client Matter & Forced Authorization Code Support Provisioning Manager Express now includes the ability to create, edit and delete Client Matter Codes (CMC) and Forced Authorization Codes (FAC). Client Matter & Forced Authorization Code Rules In CUCM, CMC and FACs have no logical association to end users, but apme has the ability to create a logical association using CMC and FAC Rules. The rules are used to create a link by using a common apme Global Variable between the user and the code. For example, if a CUCM end user s ID is bsmith, you might want to create a rule that configures the Client Matter Code description as CMC_bsmith. Let s say the Global Variable in the End User Template is {{LDAP User}}. The rule would be CMC_{{LDAP User}}. To configure Client Matter Code Rule: 1. Select Service Groups from the System menu 2. Navigate to the Client Matter Code Rule section 3. Check the Enable Client Matter Code Rules checkbox 4. Enter the Rule. In the case of CMCs, the rule will be used to populate the CMC description field. In most cases, the rule should have a prefix followed by same Global Variable (GV) used in the User Template Username Field. Example CMC_{{LDAP User}} To configure Forced Authorization Code Rule: 1. Select Service Groups from the System menu akkadian Provisioning Manager Express Version Release Notes 1/31/

27 2. Navigate to the Forced Authorization Code Rule section 3. Check the Enable Client Matter Code Rules checkbox 4. Enter the Rule. In the case of FACs, the rule will be used to populate the FAC name field. In most cases, the rule should have a prefix followed by same Global Variable (GV) used in the User Template Username Field. Example FAC_{{LDAP User}} In order for Client Matter or Forced Authorization Code rules to have any effect, they need to be configured on one or more apme End User Template. To configure Client Matter Codes on End User Template: 1. Select End User from the Templates menu 2. Navigate to the Client Matter Code section 3. Check the Enable Client Matter Code Creation checkbox 4. Enter a code or Global Variable in the Code field. In most cases you should use a Global Variable as CMCs must be unique in CUCM. 5. When Client Matter Code Rules are enabled on the Service Group the Description Field will not be editable. 6. Click Save when complete. akkadian Provisioning Manager Express Version Release Notes 1/31/

28 To configure Forced Authorization Codes on End User Template: 1. Select End User from the Templates menu 2. Navigate to the Forced Authorization Code section 3. Check the Enable Forced Authorization Code Creation checkbox 4. When Forced Authorization Code Rules are enabled on the Service Group the Name Field will not be editable. 5. Enter a code or Global Variable in the Code field. In most cases you should use a Global Variable as FACs must be unique in CUCM. akkadian Provisioning Manager Express Version Release Notes 1/31/

29 Provisioning Enhancements Bulk Phone Swap apme now includes the ability to process Phone Swaps in bulk using a simple CSV template. To perform a Bulk Phone Swap: 5. Select Phone Swap from the Actions menu 6. Select the appropriate Service Group 7. At this point, you can download the CSV template by clicking Export located at the top right corner of the page. Optionally you can proceed to populate the remaining fields and Export the template with all the settings prepopulated. 8. Populate the Exported CSV Template and when complete, click the Import button to upload the template. 9. Upon uploading the Template, the system will process the phones swaps. Do no close your browser or navigate away from the page. 10. The process will complete and provide a summary of the processed items. Automatically Generate Dummy MAC address Support to automatically generate a unique dummy MAC address when provisioning. This feature will generate a dummy MAC using the Cisco supported BATXXXXXXXXXXXX MAC address format. This feature compliments the apme selfprovisioning service where users are provisioned with a Dummy MAC and can take ownership of a real device using our XML phone service. akkadian Provisioning Manager Express Version Release Notes 1/31/

30 View and Provision Results apme 4.8 now supports the ability to not only view the details of a provisioning action, but the ability to send those results with a summary or detail via . To view provisioning details: 1. After performing a provision, click on View Details 2. The Provision Detail window will open 3. Option 1 - Click on All Details to all the details of the provisioning action 4. Option 2 - Click on Summary to a summary of the provisioning action akkadian Provisioning Manager Express Version Release Notes 1/31/

31 5. Enter an address and optionally modify the content 6. When finished, click Send Overwrite Device Option When provisioning, apme now provides the option to overwrite an existing device. This means the same job can be used to add a user with a new device or akkadian Provisioning Manager Express Version Release Notes 1/31/

32 existing device of the same model and protocol, saving administrative overhead. If the device is not the same model and protocol, the overwrite existing device option will not appear. To overwrite and existing device: 1. Select a provision job with a template containing the same Model and Protocol as the target device 2. Enter the MAC address of the target device 3. The Existing Device warning will appear 4. Check the Overwrite existing data checkbox to overwrite the existing device 5. Check the Preserve current line associations checkbox to preserve the existing lines on the device Extension Mobility Auto-logout feature on Delete CUCM will not allow a Device Profile to be deleted when it is logged into a device. apme will now automatically logout the Device Profile from all devices before processing a delete. akkadian Provisioning Manager Express Version Release Notes 1/31/

33 Site Template Enhancements New Provisioning Options apme 4.8 adds several new provisioning options to Site Templates: Device Section Description Line Section Description This field provides the ability to configure the Device Description Field. This field does not support Global Variables. This field provides the ability to configure the Line Description Field. This field does not support Global Variables. External Phone Number Mask This field provides the ability to configure the External Phone Number Mask. This field does not support Global Variables. Line Groups This fields provides the ability to assign the line to one or multiple line groups. End User Section UC Service Profile This fields provides the ability to configure the end user UC Service Profile. Device Profile Section Extension Mobility This field provides the ability to configure the Device Cross Cluster CSS Profile Extension Mobility Cross Cluster CSS field. Unity Connection Section Alternate Extension This field provides the ability to configure the Alternate Partition Extension Partition field. akkadian Provisioning Manager Express Version Release Notes 1/31/

34 Site Template Bulk Import apme now provides the ability to import Site Templates in bulk using a CSV template. To bulk import Site Templates: 1. Select Site Templates from the Templates menu 2. Select the Site Template to use as the template 3. Click Export located in the upper right-hand corner to download the CSV template 4. Open the CSV template and populate with new site data 5. Save the CSV template to an accessible location 6. Return to Site Templates and click Import located in the upper righthand corner 7. Select the CSV file and click Upload to import. Select Overwrite Existing Templates to update existing Site Templates. akkadian Provisioning Manager Express Version Release Notes 1/31/

35 Provisioning User Interface Enhancements apme 4.8 adds several user interface enhancements. 1. The new Loading Modal provides enhanced status when apme is processing transactions. 2. The apply changes checkbox has been removed from all unnecessary provisioning actions. In certain actions, such as delete, the checkbox was unnecessary and was removed. 3. The Job description field adds the ability to provide an optional description to the Job and each template within the job. akkadian Provisioning Manager Express Version Release Notes 1/31/

36 Job Template Export and Import apme 4.8 adds support for exporting and importing Job Templates. Currently the Job export and import function uses the JSON format. JSON files can be manipulated using any standard text editor. The Job export/import function can be used to: Copy Jobs between different apme servers that share the same Template names Copy Jobs between Service Groups that share the same Template names Copy Jobs between different apme servers by modifying Template names Copy Jobs between Service Groups by modifying Template names Modifying existing Jobs by exporting the Job, modifying and importing with a different Job name To export Job Templates: 1. Select Jobs from the Templates menu 2. Select and open the Job to export 3. Click Export located in the upper right-hand corner to download the export file Editing Job Template Export File: 1. Open the Job Template export file 2. When the Job Template was exported, the Job name was removed to prevent the duplication attempts. To import the Job file, at minimum, the new Job Template name must be configured in the akkadian Provisioning Manager Express Version Release Notes 1/31/

37 export file. Populate the new Job name between the quotes after the name attribute as shown below. 3. Update any other desired attributes, such as template names, but ensure all values are valid or the import will fail. 4. Multiple Job Templates may be imported using the same file by creating an array. To create an array, the file must begin a [, end with a ] and each Job Template JSON string must be separated by a comma. Reference the examples below for details. Example of a one Job Template in a single JSON import file: {"name":"add Phone1","servicegroup_id":"US Cluster","job_access":"Administrator","job":[{"element":"phone","name":"Loc 7 - Common Area Phone","element_id":"device ","parent":null}]} Example of two Job Templates in a single JSON import file: 5. When finished, save the import file To import Job Templates: 1. Select Jobs from the Templates menu 2. Click Import located in the upper right-hand akkadian Provisioning Manager Express Version Release Notes 1/31/

38 3. Select and Upload the file to begin the import process 4. The system will import the Job Templates and display a status message in the upper right-hand corner when complete akkadian Provisioning Manager Express Version Release Notes 1/31/

39 Resolved Caveats Tracking Number PME-3346 PME-3390 PME-3413 PME-3187 PME-3370 PME-3418 PME-3419 PME-3442 PME-3457 Description CTI Route Point provisioning actions not showing in reporting Unassigned DN features for DN Pool should exclude Translation & Route Patterns Unity Connection LDAP VM users are being built with incorrect Title fields Processed Jobs not being sorted properly Phone swap fails when "&" (ampersand) is included in Speed dial label License Pool list is not showing correct header DN Pool Import template missing DN aging column GV converted from default type to list are retaining RegEx and Input Validation settings Unable to Bulk Provision Job Containing Unity Template akkadian Provisioning Manager Express Version Release Notes 1/31/