Pre-Paid Entitlement Upgrade
Audience: Customer
Module Scope: This process shows the
upgrade selection option for entitled or paid
upgrades at the point of activation.
Upgrading with Pre-Paid Maintenance (e.g. SSU or SA)
 Upgrade activation can happen in the following ways:
– When activating an entitlement for which an upgrade is available (upgradeable entitlement). You can
then choose to activate either the new version or the current version. For example, when you
activate an entitlement for SuperServer version 1.0, and an upgrade is available, you can activate
either version 1.0 or version 2.0.
– When activating an entitlement used to implement an upgrade (upgrade entitlement). You can then
choose the upgrade path to apply the entitlement to. For example, upgrading from SuperServer 1.0
to SuperServer 2.0 requires that you purchase the SuperServer Upgrade. When you activate the
SuperServer upgrade, you are able to change your SuperServer 1.0 entitlements to SuperServer
2.0.
– When upgrading activated items. For example, if you have already installed SuperServer version
1.0, you can upgrade those licenses to version 2.0.
 These types of upgrade activation require that you:
– Select the upgrade path. For example, if you are currently on SuperServer 1.0, you may be able to
upgrade to either version 1.5 or version 1.7.
– Specify the quantity to upgrade
– Provide a valid maintenance contract that shows the customers is covered by SSU or Support
Advantage or other similar maintenance that provide pre-paid upgrades.
© 2012 Avaya Inc. All rights reserved.
2
Note on Pre-Paid Maintenance (e.g. SSU or SA
 Customers with Pre-Paid upgrades will generally see orders from SAP with “Entitle” codes
that are priced at $0 when requesting upgrades.
 Most “Entitle” codes WILL NOT flow to PLDS and thus no LAC will be provided. This is
NOT an error.
 PLDS associates the customers’ pre-paid upgrade entitlements with their records in PLDS
when purchased.
 If the customer is entitled to pre-paid upgrades, the Pre-paid upgrade path in PLDS will be
enabled for the specific product(s) covered under SSU or SA for example.
 If pre-paid upgrades have been purchased and you are not seeing the Pre-Paid upgrade
path, you will need to contact the PLDS Helpdesk and provide proof of maintenance
coverage with pre-paid upgrades.
 Please NOTE that providing the SAP order with the “Entitle” codes is NOT considered
proof of maintenance.
 PLDS relies on attach of pre-paid upgrades to the customers’ records in PLDS but typically
an SAP order is still required even though the “Entitle” codes will not flow to PLDS. This is
just to ensure all systems receive notice that the customer is upgrading so that if a call is
placed into support, they are aware of what version is being asked about.
© 2012 Avaya Inc. All rights reserved.
3
Upgrading
 Pre- Paid Upgrade
– Scenario “FREE” (eg: Pre-Paid)
– Customer has SS + U or Upgrade Advantage and receives upgrade notification to
upgrade from version 2.0 to 4.0.
 The Upgrade page displays if:
– More than one upgrade path applies to the upgrade activation
– You can specify the quantity to upgrade
– The upgrade requires that you provide proof of eligibility for the upgrade.
© 2012 Avaya Inc. All rights reserved.
4
Upgrading
 The upgrade function supports:
– Multiple upgrade paths
– Upgrade from V2.0 to V3.0
– Upgrade from V2.0 to V4.0
– Knows what is needed to upgrade
– Can be used to “Request” what is needed
– Once path is selected, automatically displays LACs that match the criteria of what is
needed.
Server 1
Server 1
Host ID: 12-34-56-78-01-12
Host ID: 12-34-56-78-01-13
12 Licenses of v 2.0
12 Licenses of v 4.0
Upgrade
Licenses
© 2012 Avaya Inc. All rights reserved.
5
Pre-Paid Upgrade
Go to Activation > View Activation
Record
Be sure to go to Assets > View Entitlements to
verify the product is entitled to an upgrade. The
Assets screen should show SSU entitlements for
specific products.
© 2012 Avaya Inc. All rights reserved.
6
Pre-Paid Upgrade
1. Enter Search criteria, License Host,
Host ID, Group Name or Group ID.
See “Searching for Entitlements” job
aid for further details.
2. Click Search
© 2012 Avaya Inc. All rights reserved.
7
Pre-Paid Entitlement Upgrade
Verify a Pre-Paid option is available.
For this example the Interactive
Response will be upgraded using
the Pre-paid Option.
• Click Upgrade to continue
© 2012 Avaya Inc. All rights reserved.
8
Upgrading Entitlements
1. Review/confirm results.
2. Click Next.
© 2012 Avaya Inc. All rights reserved.
9
Pre Paid Upgrade Option Selection
Select the Pre-Paid Upgrade path
and click the Select button
When selecting from the drop down upgrade
path selection, be sure to click “select” once
the desired option has been chosen.
© 2012 Avaya Inc. All rights reserved.
Select Next to specify additional
upgrade specifics and/or be advised
of any upgrade pre requisites.
10
Verifying System Information
1. Confirm system information.
2. Click Next
© 2012 Avaya Inc. All rights reserved.
11
Activating Upgrade Entitlement
© 2012 Avaya Inc. All rights reserved.
• Click Next to continue
12
Confirming upgrade
1. Accept the EULA (End User Legal
Agreement)
2. Enter information for the user who
should also receive the activation
detail.
3. Enter additional notes if
necessary.
4. Click Finish.
© 2012 Avaya Inc. All rights reserved.
13
Downloading new License File
• Updated license file will be sent to
the email address specified.
• The file can also be saved by
choosing Save to File
© 2012 Avaya Inc. All rights reserved.
14