380 likes | 400 Views
Learn how to navigate the KRS screens, retrieve keycodes, generate keycodes from URNs, use eAuthorization codes, and change the Distributor of Record.
E N D
Course Title: Keycode Retrieval System (KRS) – CS 1000Course ID: KR101 Issue: 1.0
"This session falls under the confidentiality agreement and therefore is subject to non-disclosure"
Course Aims & Objectives • How to Navigate the KRS screens for CS 1000 • How to Retrieve CS 1000 keycodes • How to Create Keycodes from URNs • How to Use eAuthorization Codes • How to Change the Distributor of Record
Course Chapters • what is KRS? • eBus landing page • Left menu overview • Docs/Forms/Guide • Distributor of Record Change • Part 1: Introduction • Part 2: Retrieving Keycodes • Part 3: Generate Keycode Using URN • Part 4: eAuthorization Code Overview Note – View Note Pages for each slide for more details. Select ‘View” then “Notes Page”, or in “Normal View” use your mouse at the bottom edge of the slide to split the window and view the notes under each slide
eBusiness Tools Landing Page – to access all the tools ! • www.avaya.com/ebizn (Americas, Asia) • www.avaya.com/ebizu (Europe, Middle East, Africa) • Alternate direct KRS access: www.avaya.com/krs (Global)
Choose KRS Product Family Select “Product Family” = Communication Server 1000 Press <Go> button TIP : After a product family has been selected, to change product families, click <Keycode Retrieval> to return to this page 2. 1.
CS1000 KRS Left Menu • Retrieve Keycode– view and download the current keycode(s) for a site • Retrieve History – view and download all keycodes ever made for the site • Generate Keycode – generate keycodes using Authorization Codes – numeric or electronic • Download KMT – download the Keycode Management Tool (KMT) to view and compare downloaded keycodes • Documentation, Forms & USER GUIDE – links to the KRS documentation repository • PLDS Software Download – PLDS will open in a new browser window (must be registered for PLDS) • Generate Using URN – generate a keycode for a product using a URN and the MAC address for the license server • eAuth Code Management – links to the PO History report and several links to functions for eAuth Code Administrators • Contact Global support – links to Avaya ITSS page to enter support tickets on line and to view existing support tickets • Keycode Access Request – documents the process to change Distributor of Record 1. 2. 3. 4.
Documentation, Forms & User Guides 3. 1. 2. Select <Documentation, Forms & USER GUIDES> Double click the desired folder, select the desired form and right mouse click to save it to your computer Click on <KRS Documentation> for access to the <Release Notes> and <Training> folders
Keycode Access Request When a Partner other than the 'Distributor of Record' needs to download or generate keycodes for an installed system 1. Select <Keycode Access Request> from the left menu in KRS Follow the instructions listed on the page 2.
Course Chapters • Part 1: Introduction • Part 2: Retrieving Keycodes • Part 3: Generate Keycode Using URN • Part 4: eAuthorization Codes Overview • Current by product • Current – All • All historical • KMT • When not Dist of Record • View Contracts • View Auth Code History
Retrieving “Current” Keycode for a Specific Product • Query a Keycode by entering: • System ID (site ID), or Product ID* • Avaya Order number • Customers PO# and then clicking on the Search button. • Partial entry of search data and * wildcard searches are supported • System Id’s and order numbers are not case sensitive • Press the <Search> button • Select desired site • Press the <Continue> button 1. 2. 1. 3. 4. 2.
Viewing “Current” Keycodes Select Product Line KRS retrieves the keycode as soon as a selection is made and displays it directly below along with Product Information Change the ‘Product Line” selection to view keycodes for other products associated with the site Note: If you are not the Distributor of Record (DOR) for a site, then the site ID can be retrieved with a view of the “Product Information” display only. The actual keycode can not be viewed or downloaded. A site ID must be re-mapped in order for another Partner to view or download the keycode. 1. 2.
Download the “Current” Keycode 1. To download the keycode for the currently selected product, select the <Download Keycode> button at the bottom of the “Retrieve Keycode” page Select the <Save> button on the “File Download” window Select where to store the file on your PC, the file name and press the <Save> button 2. Note – many of the smaller keycodes are simply displayed in a text editor where they can be saved 3.
Download “All” Keycodes for a Site To download all current keycodes for all products for the current site in one operation. 1. 2. Select the <Download Envelope> button at the bottom of the page, when viewing the keycode on the “Retrieve Keycode” page Select the <Save> button on the “File Download” window Select where to store the file on your computer Press the <Save> button 3. 4.
Retrieve all Historical Keycodes for a Site 2. 1. 3. • Select <Retrieve History> option from the left menu • Enter search criteria & select <Search> button • Select the desired site and select the <Continue> button • KRS will display a list of every keycode produced for the site • Use the check boxes to indicate which keycodes you wish to view in detail • Select the <Retrieve Keycode(s)> button 4. 5. 6.
Retrieve all Historical Keycodes for a Site - continued 1. • View the chosen keycodes by selecting from the “Product List “box • Download “Individual Keycodes “or “All Keycodes” as described previously 2.
KMT Tool – Download & Install The Keycode Management Tool (KMT) is used to view and compare keycode files that have been downloaded from KRS 1. Select the <Download KMT> Option from the left menu Select the <Save> button on the “File Download” window Select where to store the file on your computer Press the <Save> button Double click on the icon to initiate the Setup Wizard The README.TXT file will open automatically and includes an Overview and the User Guide 2. 3. 4.
Using the KMT Tool View a .Key file –Select <Browse> to find a keycode file on your computer Select the product from the Product list Tools/ Compare –to compare 2 different .key files Tools/ Search –to search for a keycode file on your computer Tools/ Management –allows for the manipulation of keycodes move, deleted etc. File/Print Preview Current or all – to view individual keycodes or all keycodes as they would print File/ Print All or Current – to print keycodes 4. 3. 1. 2. Note: There is no technical support available for the KMT Tool
View Services Contract(s) Phil - 1. Select the <View Service Contract(s) > button at the bottom of the page, when viewing the keycode on the “Retrieve Keycode” page Note: Only users from the Distributor of Record for a site will see contract details Non Distributors of Record may receive a message indicating that a contract exists, but no contract details will be displayed
View Auth Code History ‘Auth Codes Used” are summarized on the “Retrieve Keycode” page. Details can be viewed by: 1. Selecting the <View Auth Code History> button at the bottom of the page 1.
View Auth Code History • Displays chronological keycode creations, including: • Date Auth Code used • Authcode # • Code and Type of license enabled • Order # details
Course Chapters • Part 1: Introduction • Part 2: Retrieving Keycodes • Part 3: Generate Keycode Using URN • Part 4: eAuthorization Codes Overview
Generate a Keycode Using a URN • Keycodes for products using MAC address (ex. Contact Center and CRQM) may be produced and saved differently on KRS depending on the information available at the time of order: • Method 1: License Manager MAC address available at time of order • Keycode License file sent to the KRS • Retrieve Keycode License file is identical to the retrieval process used for all other application keycodes – use Site ID , MAC address or URN to initiate the search • Select the Aux ID by selecting the _01 selection • Method 2: License Manager MAC address not available at time of order • Keycode license file will not be generated and will not ship with the order • If the Licence Manager MAC address is not available, a Unique Reference Number (URN) is created that is associated with the site ID • The keycode must be generated and retrieved via KRS using the URN, after shipment when the MAC address is known
Generate Using URN Access KRS for CS 1000 and select the <Generate Using URN> option from the left menu Enter the URN and MAC address(es) for the keycode to be generated. If no License Manager Standby Server has been purchased, then any Standby Server MAC entered will be ignored. Select <Continue> Reenter the MAC address(es) – this ensures no human error in typing Select <Confirm> 2. 1. 3. 4.
Generate Using URN - continued If the MAC addresses entered match, KRS will generate the keycode license. This can take a few minutes. Once KRS obtains the generated keycode, it will be automatically retrieved and displayed for the user on the standard “Retrieve Keycode” page, where it may be viewed and downloaded per the normal process 1.
Keycode License Regeneration • A new license is required if one of the license servers fails or needs to be replaced. The new license is regenerated for the MAC address of the new license server. • KRS typically supports a <Regenerate Using URN> option in the left menu. However, this option has been temporarily removed to resolve errors with the function. • Until the <Regenerate Using URN> option is available once again in KRS, contact Avaya Technical Support if Keycode regeneration is required
Course Chapters • Part 1: Introduction • Part 2: Retrieving Keycodes • Part 3: Generate Keycode Using URN • Part 4: Authorization Codes Overview • eAuth Codes • Numeric Auth Codes • PO History Report • Generate Keycode • Using Combo Codes Refer to ‘Auth Code Functionality” training for further details, including screen by screen details of the “Generate Keycode” process
CS 1000 Authorization Codes • eAuth Codes are merchandise software licenses purchased via a Purchase Order (with or without EC) that are electronically fulfilled by KRS • KRS is used to access the purchased eAuth Code licenses and assign them to a System ID to generate a keycode • All registered KRS users have the ability to generate keycodes using the electronic Auth Code Process. No Admin access is required! • CS 1000 eAuth Codes are accessed via Purchase Orders • Resellers use Numeric Authcodes (in lieu of PO’s) to generate Keycodes, as they do not have access to their distributor’s PO’s on KRS • Distributors must convert the electronic Auth Codes to Numeric Authcodes and provide them to the Resellers
Some Notes about Authorization Codes • Authorization Codes are considered merchandise, and therefore, are not covered by the EC quote engineering guarantee: • Auth Codes are intended for simple SW license expansions only. Please ensure that the software licenses added via Authorization Codes will not adversely impact the system’s performance. • When adding software licenses using Auth Codes, it is important to ensure that the existing DSP limits have not been exceeded since adding software licenses outside of the EC tool could override any DSP engineering in place • EC is required for new system software, software upgrades or complex expansions which require engineering • Note: eAuth Codes and Numeric Auth Codes are the only way to expand a CS 1000 system on Rls 3.0 - 5.5 software. These expansions cannot be configured with Enterprise Configurator (EC). • How are Auth Codes corrected if they are assigned to the incorrect System ID? • Order Management must be contacted for a new keycode • A chargeable remake fee will be applied
CS 1000 eAuth Code Administration eAuth Code Administrators are critical as they notify users within their company when a PO has become available on KRS for generating keycodes • PO History Reports • Allows Users & Admins to generate a report which shows license consumption • Inventory Reports • Allows Administrators to generate a report which lists POs in their inventory • Return Credit Reports • Allows Administrators to generate a return credit report which deactivates the Auth Codes purchased on a PO. Report is required as proof of returned eAuth Codes • Manage Email Notification • Allows Administrators to set up a list of recipients that will receive an Email notification whenever a purchase order is posted (“activated”) on KRS for generating keycode licenses from the purchased eAuth Codes • Manage Admin Users • Allows the Primary Administrator to set up additional secondary administrator user (SAU) access • Numeric Authorization Codes (Distributors only) • Allows eAuth Distributor Administrators to generate Numeric Authorization Codes that can be used like paper authcodes to generate keycodes Refer to ‘eAuth Code Administration” training for further details
Purchase Order History Report • All users have access to Purchase Order History Report • Shows eAuth Code licenses ordered and used by Purchase Order • Numeric Auth Code Histories by PO# are viewable for users with Distributor privileges 1. Select <Purchase Order History Report> from left menu, under eAuth Code Management Select <Download Report> button to download the report if desired 2.
Generate Keycode System Id’s are not case sensitive 3. 4. 5. Log-in to KRS Select Product Family = <Communication Server 1000> Select <Generate Keycode> from under “Product Control” in the left menu Enter the “System ID” of the CS 1000 system to generate keycode for Select <Continue>
Generate Keycode – Process Summary Refer to ‘Auth Code Functionality ” training for screen by screen details of the “Generate Keycode” process • Add eAuth Codes by PO: • Search for the PO used to purchase the eAuth Licenses by enteringsearch value and select the <Go to PO> button to display the PO details • Enter Quantity of Licenses to be applied to the keycode and <Continue> • For Combo codes (rls 3.0-5.5 only) – distribute the Qty taken among the licenses types • Confirm Quantities and <Continue> • Search for more POs to add eAuth License58s to the same keycode if required or • Add Numeric Auth Codes (Resellers only) • Enter Numeric Auth Code # • <Add> to validate and add to the list • For Combo codes (rls 3.0-5.5 only) – distribute the Qty taken among the licenses types • Add more Numeric Auth Codes as desired • To Remove: Check box next to validated Auth Code then select <Remove> 2. 1. and ** KRS validates the selected licenses for applicability (ie. service level etc). No engineering rule validation on the system ID is performed. <Go To Summary> to validate** selected licenses Select <Generate Keycode>
Retrieve Keycode Once KRS obtains the generated keycode, it will be automatically retrieved and displayed for the user on the standard “Retrieve Keycode” page • Use the <Download Envelope> and <Download Keycode> buttons to download the keycode– see part 2 of this training for details 1.
Generate Keycode - Using Combo Codes • A combination Auth Code delivers several license types in a single order code • One order code for Digital, Analog and/or CLASS licenses • Applicable for CS 1000 Rls 3.0 to 5.5 systems only • The Digital, Analog, CLASS licenses were replaced by the TDM license in Rls 6+ • The KRS user must identify the type and number of each license • Search for PO used to purchase the eAuth Codes or enter the Numeric Auth Code • Enter Quantity of the License codes to be applied to the keycode • For KRS Step 4: Distribute “Qty Taken” amongst Digital, Analog and Class. All licenses must be assigned • Select the <Continue> button 2. Sum of values entered must equal ‘Qty Taken’ 3. 4.
Generate Keycode - Using Combo Codes KRS will confirm the licenses selected from the PO(s) and report the distribution of Analog, Digital and/or Class features chosen by the user • Select the <Go to Summary> button, when ready to generate the Keycode Resellers may also distribute combo licenses when generating keycodes from Numeric Auth Codes 1.
Generate Keycode - Using Combo Codes 9 • Once the licenses are validated,** KRS will present a summary of the new keycode contents, and highlight the changes ** KRS validates the selected licenses for applicability (ie. service level, etc). No engineering rule validation on the system ID is done. • Click <Generate Keycode> to complete the generation process – the keycode will be displayed on the “Retrieve Keycode” page where it can be viewed and downloaded