License Management
- Understanding License Management
- Microsoft SQL Server - license requirements with virtualization
- Licensing in cluster of hypervisors with automatic load balancing
- Licensing of multiple versions of same software for same consumer
- Agentless discovery and inventory
- Automatic change of license model with downgrades
- Charts in Licenses
- Configure remote application usage and platform access tracking
- Consolidating license requirements for suites
- Data object model for license management
- Examples of software suite consolidation
- Extent of license model change with downgrades
- License assignment
- Background processing for license management
- License mobility with virtual machines
- License requirements
- Logic behind license entitlement
- Manage compliance with 'concurrent use' license model
- Microsoft SQL Server - License models provided by LIS
- Microsoft Windows Server - License models provided by LIS
- Notifications about active processes in License Management
- Object model for License Management
- Oracle Database Worksheet
- Permissions for navigation items in the Licenses application
- Permissions to actions available in the Licenses application
- Permissions to dialogs available in the Licenses application
- Permissions to previews available in the Licenses application
- Priorities used when assigning downgradeable licenses
- Report - Cost Saving Potential
- Report - Financial Risk Assessment
- Report - License Inventory
- Report - Software Compliance
- Report - Software Usage Saving Potential
- Settings for License Management
- Settings relevant for creation of license requirements
- Single engine activation for License and Asset Management
- What are fingerprints
- What are license models
- What is a license
- What is a software product
- What is consolidation of license requirements
- Use Cases in License Management
- Adding base licenses to a license
- Adding base licenses to a license conversion
- Apply LIS template to software products
- Automate license requirements for client access (CAL)
- Automate license requirements for Matrix42 Enterprise Service Management
- Changing ownership of a license (transferring a license)
- Checking for possible entitlement of license requirements
- Checking status of software products
- Checking usage status and possible entitlements of licenses
- Create license requirements for Microsoft Extended Security Updates (ESU)
- Create license requirements for Software-as-a-Service (SaaS)
- Create license requirements from remote application usage
- Create license requirement rules
- Creating a license from a SKU
- Creating license requirements manually
- Dealing with a discontinued LIS template for a software product
- Defining license requirements for software products
- Fixing failed validation of an invalid license
- Handling the end of maintenance for a license
- How to improve display of AD groups
- Importing licenses using the standard template
- License edit form
- License requirements created from Service Catalog bookings
- License requirements originating from Active Directory permissions
- License requirement rules in examples
- Recognizing commercial software from fingerprints
- Setting a baseline for software products
- Setting a license custodian for software products
- Setting confirmation mode for software products
- Setting notifications about expiring licenses
- Set reporting scope for software products
- Trend analysis for software products
- Unused installations for software products
- Updating a license based on matching SKUs
- Using license pools to provide licenses and control entitlement
- Using several license models for a single software product
- Validation of purchased license when saving changes
- Viewing the license library for software products