Example: biology

Software Support Licensing at CLS User Guide - Login Page

1 Software Support Licensing at CLS user Guide 2 History of Change Ver. Released Author Changes 2014-12-22 Cigdem Oestanas Initial Creation Chapter 1 2014-12-25 Taylan Sen Screen Shot Updates, Chapter 2 and Chapter 3 2014-12-30 Alfons Geier Introduction, Glossary and additional corrections. 2015-01-07 3 Table of Contents 1) Glossary .. 4 2) Introduction .. 5 3) Use case Transferring and activation of ordered/ unused licenses .. 7 a) System licenses and SSP licenses are ordered via one distributor in one order.. 7 b) Product and SSP are ordered separately via one Distributor .. 22 c) Product and SSP are ordered separately via two Distributors .. 26 4) Use case: Renewal .. 28 a) Before Expire Date on CLS .. 28 b) During renewal period .. 31 c) Re-Contracting / Re-Activation.

8 Image 1.a.1 - View License Assets – Licenses Delivered TRANSFERRING THE LICENSES: The Distributer logs into his CLS account. 1. Select the Transfer Licenses menu item. 2.

Tags:

  User, Software, Support, Licensing, Asset, Software support licensing at cls user

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of Software Support Licensing at CLS User Guide - Login Page

1 1 Software Support Licensing at CLS user Guide 2 History of Change Ver. Released Author Changes 2014-12-22 Cigdem Oestanas Initial Creation Chapter 1 2014-12-25 Taylan Sen Screen Shot Updates, Chapter 2 and Chapter 3 2014-12-30 Alfons Geier Introduction, Glossary and additional corrections. 2015-01-07 3 Table of Contents 1) Glossary .. 4 2) Introduction .. 5 3) Use case Transferring and activation of ordered/ unused licenses .. 7 a) System licenses and SSP licenses are ordered via one distributor in one order.. 7 b) Product and SSP are ordered separately via one Distributor .. 22 c) Product and SSP are ordered separately via two Distributors .. 26 4) Use case: Renewal .. 28 a) Before Expire Date on CLS .. 28 b) During renewal period .. 31 c) Re-Contracting / Re-Activation.

2 39 5) Use case: Expansion .. 40 a) Before Renewal Period .. 41 b) During Renewal 49 c) After Contract Expired .. 57 4 1) Glossary CLS: Central License Server CLS ID: The CLS-ID is a unique identifier at the Partner Service Contract Portal. ERM system: is Unify s SAP system F-Numbers: F-Numbers are licence numbers for products but also for contracting a system for Software Support (co-delivery) v2. They are further used for renewing the contract. The F-nrs can be seen at the accounts at CLS. LAC: License Activation Code to activate the Service contract for Software Support . PSC: Partner Services Contract Portal. PCM: The Partner Services Contract Database (PCM) is the database for the Partner Services Contract Portal (PSC). SIEL-ID: is a unique identifier which is assigned to each base license.

3 SSP: Software Support 5 2) Introduction Software Support is a service provided by Unify to its approved Partners. To be able to get the service for a system, it has to be under service contract. A service contract is established for a system if Software Support Service specific order items are ordered and assigned to a system. To be able to assign the service order items to a system these items are converted at the ERM systems to service specific licenses (F-numbers) which are then transferred to the Central License Server (CLS) which is Unify s License Management tool. At the CLS the service specific licenses have to be assigned to a system by matching to base and user / feature licenses the fitting amount of service licenses. Some general rules have to be kept in mind -The service licenses are used for both contracting a system for Software Support and for renewal of the service contract.

4 -The service licenses are matching to base and user / feature licenses of systems and are handled at CLS exactly like system base and user / feature licenses. So these licenses are also named service base license or service user license -Latest at CLS a unique identifier (SIEL-ID) is assigned to each base license. This makes each system uniquely identifiable, which is important for further handling the usage of Ticket Management, Expert Assistance, renewal etc. Also for the service base license an own SIEL is assigned. -Because Service and System licenses provide own SIEL ID s, with activation the service Siel is overwritten by the system Siel (Base license). This is to have a unique identifier for a system. Therfore als at the Partner Contract portal the SIEL if service base licenses is converted to the system Siel with activation -Service licenses fitting in type and amount must be matched to the system account at CLS If not fitting the SSP contract is not accepted and an error message is shown If a system is under SSP then system expansion (adding system licenses) can be done only together with expansion of SSP contract (adding the fitting SSP licenses) Same applies for renewal 6 -It is important that System and SSP licenses are transferred to the End customer account.

5 Only then the SSP contract is valid -SSP contract is only properly created if the transfer process is followed: Unify account -> Distributor / Reseller account -> End customer account The following chapters now describe in detail the handling of system and SSP licenses in various use cases and steps. The first use case describes how a system is taken under contract (either if ordered newly or also for installed base). The second use case describes how a service contract, which will expire during next 90 days is renewed. The third use case describes how a system under service can be expanded. 7 3) Use case Transferring and activation of ordered/ unused licenses a) System licenses and SSP licenses are ordered via one distributor in one order. An order is transmitted to the CLS in one LAC as the System licenses and SSP licenses were ordered together.

6 The licenses are ordered via XX and location on the XY account. Before the licenses can be activated on the according account, they need to be transferred. As a result the ownership of the licenses change. The current license owner will become the Partner Company of the transferred licenses and the selected New Owner Company will become the Sold-to company. Note: You can only transfer licenses that have neither been used for license key generation nor have already an End user Company assigned. Example: LAC 1 consists of: F31505-K147-C1 OS Voice V8 Base F31505-K147-C4 OS Voice V8 UC Server F31505-K147-C2 OS Voice V8 Dynamic user F31505-K147-C7 S Voice V8 SuSE 3 Year Upgrade Protection F31505-K148-A512 SSP for OpenScape Voice V8 Dynamic user Contract F31505-K148-A511 SSP for OpenScape Voice V8 Base Contract 8 Image - View License Assets Licenses Delivered TRANSFERRING THE LICENSES: The Distributer logs into his CLS account.

7 1. Select the Transfer Licenses menu item. 2. Enter the License Authorization Code (LAC). 3. Enter the Partner Company to the Current License Owner field and click SEARCH. 4. The search result will only show licenses that do not have already an End user Company assigned and still have available Quantity (un-used). If you tick the check box next to the Product name, all contained features are selected. You can deselect features which you do not want to transfer by un-ticking the checkbox next to the feature name 9 Image Transfer Search 10 5. Select the licenses to be transferred and click TRANSFER 6. At the Transfer Men : a. First the New Owner Company has to be set. Either you enter the name or search for the company (by using the magnifier glass). b.

8 Then check the LAC Generation Rules section. Here you can choose the method how the LAC for the transferred licenses is defined. If you want to transfer all licenses linked to a LAC, you can use Keep existing LACs. c. Otherwise the best choice is to let the system generate a LAC for you (Create new system-generated LACs - 1 LAC for this transaction). d. If you do not want to transfer all licenses linked to the LAC, use the Licenses to Transfer section. Click onto the Plus icon to open this section. e. In the Licenses to Transfer section you see all selected licenses with their available quantity. If you only want to transfer a partial quantity, change the values in column Quantity to Transfer appropriately. f. In section Header Information you can assign the properties Sales Order #, Delivery Note # and Purchase Order # to the new LAC.

9 G. It is possible to download or receive via email a comma separated list with the generated new LAC(s) via email or download. This is controlled in section LAC Delivery Rules . h. As an optional way you can trigger an email that informs and invites the new license owner to the CLS After providing all data click NEXT. 11 Image Transfer Target Company Selection 12 7. On the confirmation page you may enter Customer Notes. Please verify the entered settings. If the data is correct click FINISH. Image Transfer Confirmation 8. As result of the transfer, the license quantity of the original licenses will be decreased and new licenses will be created. Once the license transfer is complete, click the Enter another Transfer button to start a new transfer workflow if required.

10 13 Once the licenses are located on the Reseller Account ( CLS terminology: SOLD TO account). The reseller log onto CLS and has to perform the Transfer Process to the account of XXXX. Activation Process: 1. Select the Generate and download license keys menu item. 2. Enter the LAC as the search criteria and click SEARCH Image Search for the Licenses to be Activated Activation with SSP Contracting 3. Select Product and Feature that you want to activate click Generate Key Note: The SIEL IDs for base and SSP base SIEL IDs are different. 4. Enter details to generate the license key a. Locking ID (MAC address) of the target hardware b. Quantity of licenses Optional: Enter Alias Name of the target hardware (any title to identify the computer) and click NEXT.


Related search queries