akkadian Provisioning Manager Express · akkadian Provisioning Manager Express Version 4.11.04...

akkadian Provisioning Manager Express

Version 4.11.04 – Release Notes September 14th, 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/2017 0001 © http://www.akkadianlabs.com/apme/

http://www.akkadianlabs.com/apme/

akkadian Provisioning Manager Express Version 4.11.04 Release Notes 2

Table of Contents

4.11.04 - Upgrade Notes .................................................................................................... 3

4.11.04 – New and Changed Features ............................................................................ 19

4.11.04 - Resolved Caveats .............................................................................................. 20

4.11.02 – New and Changed Features ............................................................................ 21

4.11.02 - Resolved Caveats .............................................................................................. 23


4.11.04 - Upgrade Notes

Provisioning Manager Express 4.11 contains major platform updates, therefore

aPME must be migrated to 4.11 using the backup and restore process.

Supported Migration Path from Previous Versions of aPME

From To Supported Method

4.11.02 and above 4.11.04 Direct upgrade

4.7.02 and above 4.11.04 Backup and Restore to New 4.11 OVA

4.1.08

4.11.04 Two-step upgrade: 1) Upgrade to 4.10.08 2) Backup and Restore to

new 4.11 OVA.

4.5.02

4.6.02, 4.6.04, 4.6.06 & 4.6.08

Please review aPME 4.10 release notes when migrating from versions prior to

4.7.02.

Process to Migrate to aPME 4.11:

Step 1 – Generate a New License

Whenever you deploy a new aPME OVA, it requires a new license. Generating a new

license is easy and can be done in the Akkadian Labs Client Portal. When you

purchased your software from Akkadian Labs, you should have received a welcome

email containing instructions to access the portal. Portal access is generated based

on your corporate email and if you don’t remember your password, it can be reset

from the login page.

1. Go to http://portal.akkadianlabs.com

2. Log into the portal using your email address and password. If you forgot

your password, click the “Forgot Password” link to receive password reset

instruction via email.

http://portal.akkadianlabs.com/

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRxqFQoTCP--5P-khskCFULsJgodBqQDGg&url=https://www.business.govt.nz/companies/news-updates/public-notices/company-removals-notices&psig=AFQjCNEzqFR7vapn7sGrHjoiEDsBxn2lDw&ust=1447259790151133


3. In the portal, select Licensing from the left navigation menu.

4. Locate your existing aPME license entry and click on the license key.

5. Locate the license activation and click on the icon to open the license

details.

6. Select the “Revoke License” checkbox.

7. Enter a reason for the license revoke and click Save Changes.


8. Once the license has been revoked it will allow for a new license activation

using the License Key.

Step 2 – Backup Existing aPME

The next step is to back up your existing aPME server in preparation for the migration

to 4.11.

To Perform a Manual Backup:

1. Log in as PMEAdmin or as an Administrator

2. Select Backup and Restore from the System menu

3. Click Backup and save the file to a safe location

Step 3 – Shutdown aPME

Before you can deploy the new 4.11 OVA, the current aPME server needs to be

shutdown. Do not delete the existing server until you have completely validated

the new server is working.


To Shutdown aPME:

1. In the VMWare Console, locate the existing aPME server.

2. Document the existing settings which include:

a. Server hostname

b. IP Address, Gateway, Subnet Mask & DNS server(s)

c. Virtual machine CPU and Memory configuration

3. Power down the server using VMWare.

Step 4 – Deploy the new aPME 4.11 OVA

To Deploy aPME:

Step 1 - Download the latest akkadian Provisioning Manage Express 4.11

OVA to a location accessible by the vSphere client.

Step 2 - From the vSphere client select Deploy OVF Template from the File

menu.

Figure 6.0.1 – Deploy OVF Template

Step 3 - Select the OVA from computer or network location and click Next to

continue.


Step 4 - Review the License Agreement and click Next to continue.

Step 5 - Specify the name and location for the VMware machine and click Next to

continue.


Step 6 - Specify the VMware Host / Cluster and click Next to continue.

Step 7 - Specify a host within the cluster and click Next to continue.


Step 8 - Specify the storage location for the virtual machine and click Next to continue.

Step 9 - Select Thick Provision Lazy Zeroed and click Next to continue.


Step 10 - Select the Destination Network for the virtual machine and click Next to

continue.

Step 11 - Verify the virtual machine settings. The initial OVA deploys with with 1 vCPU

and 4GB of Memory, but should be set to the match the original aPME virtual

machine settings.


Step 12 - Click OK to complete the deployment. To adjust the virtual machine CPU and

Memory, locate the newly deployed virtual machine in vCenter, right click on the

virtual machine and select Edit Settings.

Step 13 - On the Hardware tab, select CPU and adjust the setting to provide the

required number of cores for your environment.

Step 14 - After adjusting the CPU, click on Memory and adjust the settings to provide

the required resources for your environment. When completed, click OK to commit

the changes.

Step 15 - Power on the virtual machine and proceed to Step 18.

Step 16 - Select “Power on after deployment” and click Finish to deploy the OVA.


Step 17 - When the deployment is complete, click Close.

Step 18 - Locate the virtual machine in vSphere and open a console.

Step 19 - When the server boot process is complete, the system will arrive at a login

prompt. Login using:

Username – akkadianuser

Password – akkadianpassword


Step 20 - From the Akkadian Appliance Manager main menu, select option 1 to

Configure Network.

Step 21 - Select option 1 to configure the network setting.


Step 22 - Follow the prompt to configure the network settings for your environment.

Step 23 - Select option 7 from the network configuration menu to configure the

hostname. It is recommended the hostname is entered using the fully qualified

domain name.

Example – apme.yourdomain.com


Step 24 - Optionally you may configure the server time by selecting option 2 form the

configure network menu.

Step 25 - It is recommended you change the default Akkadian Appliance Manager

password by selecting option 4 (Web Server Configuration Menu) from the main

menu and then selecting “p” (Change Current AAM Password”).


Step 26 - When all configurations are complete, select “s” from the network

configuration menu to save the configuration and restart the network.

Step 27 - From the main menu, select Reboot Server to finalize the configuration.

Step 28 - When the system returns to the login prompt, the akkadian Provisioning

Manager Express virtual appliance deployment is complete and can be accessed by

going to https://{Server IP or Name}/pme.

Step 4 – Activate aPME License

To activate the license file:

1. Log into aPME using PMEAdmin as the username and password

2. Select Licensing from the System menu

3. Paste the License Key from Step 1 into the “Enter License Key” field,

complete the remaining fields, and click Submit.

4. If the aPME server is isolated from the Internet, an offline activation

will be required. In the Akkadian Client Portal, access the aPME

license as outline in Step 1. Click the “Offline PME License Activation”

button and complete the required fields to generate and download

the file.

5. In aPME select Choose File from the Upload License File section

6. Click Upload to upload the license file

7. Refresh the browser to view the updated license information


Step 5 – Performing a System Restore:

The last step to complete the migration to aPME 4.11 is a system restore.

To Restore aPME:

1. Log in as PMEAdmin

2. Select Backup and Restore from the System menu

3. Click Browse and select the backup file from Step 2

4. To restore the original SSL certificates, select the “Restore Certificate”

checkbox. The server hostname must be the same as the original

server’s hostname, or the certificate restore will not work properly.

5. Click Restore to process the system restore

Step 6 – Post Upgrade Tasks:


There are a few important tasks to perform after the upgrade.

1. Synch all application servers. This includes, CUCM, CUC, UCCX and

UCCE if applicable.

2. The migration process should have migrated all existing UCCX

servers to the new UCCX section under Application Servers. The

migrated UCCX server(s) must be assigned to the appropriate

Service Group(s) before performing any provisioning.

3. aPME includes an archiving feature for both logs and reporting. By

default, archiving is set to 6 months for new installation, but will not

be enabled for aPME migrations. It is best practice to configure

archiving to prevent all the aPME disk space from being consumed.

Example Archiving Configuration


4.11.04 – New and Changed Features

No new features in this release.


4.11.04 - Resolved Caveats

Tracking

Number Description

PME-3743 Directory Number search may timeout when using multiple DN pools.

PME-3804 Running multiple jobs with Phone Groups may fail.

PME-3806 • Running multiple jobs may fail with parser error.

PME-3812 • Archive temp files are not being properly cleaned up res

https://fidelus.atlassian.net/browse/PME-3706



4.11.02 – New and Changed Features

Provisioning Manger Express has many great new features. For details on these

features or configuration, please refer to the aPME 4.11 system Administration

Guide.

Tracking

Number Description

PME-3516 Expanded Unity Filtering support

PME-3550 Remove Shared Intercoms from Visual Phone Editor service

PME-3614 Add support for bulk jobs which include phone groups

PME-3616 Add support for adding CUCM Translation Patterns

PME-3617 Add support for adding CUCM Route Patterns

PME-3618 Add automatic scheduled UCCX agent provision to support provisioning a

CUCM user and UCCX agent in a single job.

PME-3619 Create UCCX as its own Application Server to provide support for multiple

UCCX servers integrated to the same CUCM cluster.

PME-3646 Allow BLF destination number to be selected at Provision

PME-3647 Phone Swap Enhancements – Migrated default template mapping to

Service Groups to provide better user experience

PME-3648 Add support for adding agent line to single device to restrict the agent line

from being added to more than one device during provision.

PME-3649 Add the ability to automatically send email to end user after provisioning

PME-3663 Expand ability to push DN to multiple LDAP attributes in Active Directory

PME-3670 Add support for automatically manage aPME users with Active Directory

Groups

PME-3671 Add support for Cisco Spark to automated LDAP monitoring user deletion

PME-3698 Add support for UCCE to automated LDAP monitoring user deletion

PME-3682 Add Single Number reach configuration support to self-service portal

PME-3687 Allow provisioners to export their individual audit reports

PME-3701 DN Pools - Allow the same number in the “From” & “To” fields to support a

range with a single directory number.

PME-3702 Phone Swap Enhancements - Bulk Swap has been enhanced with an

advanced search function to locate devices to be swapped.

PME-3708 Add Class of Service support for Unity Connection Editing Templates

PME-3709 Add Partition support for Unity Connection Editing Templates

PME-3716 WebEx - Add support in templates for Personal Meeting Room and

Collaboration Meeting Room

PME-3718 Remove case sensitivity requirement for device owner id in bulk provision

PME-3734 Prevent user from seeing templates if not selected in service group

PME-3735 Phone Control - Added support for located phones by Extension Mobility

logged in user.


Tracking

Number Description

PME-3736 Add branding capability to Self-Service Portal

PME-3772 Allow for DN Pools with no route partition


4.11.02 - Resolved Caveats

Tracking

Number Description

PME-3587 MAC - Editing Password/Pin fields are shown in reporting logs

PME-3685 Self-Service portal Visual Phone Editor display issue with single

expansion module

PME-3706 • MTP Preferred Originating Codec not displaying correctly templates

PME-3771 • Visual Phone editor fails when line has no partition

PME-3745

Site Template Unity Connection Alternate Extension does not override

Unity Connection Template Setting

PME-3774 Parser Error when trying to re-activate or a de-activate a Webex user



akkadian Provisioning Manager Express · akkadian Provisioning Manager Express Version 4.11.04...

Documents

Transcript of akkadian Provisioning Manager Express · akkadian Provisioning Manager Express Version 4.11.04...