Using the License Manager

about the license manager docid\ hjmsvreybhe0xdorxmsw5types of licenses docid\ hjmsvreybhe0xdorxmsw5about license bundles docid\ hjmsvreybhe0xdorxmsw5using the license manager docid\ hjmsvreybhe0xdorxmsw5 about the license manager use the license manager to track your license usage for the demonstration or proof of concept deployment docid\ g8olkisyshsvioayypcuc and minimum production deployment docid 4c60s2zyg3bmxq48g88sz , the license manager is installed on the server along with the other components for the enterprise production deployment docid\ bhapgl 9cpnjelwecs8ll , the license manager is installed on the processing servers along with the other components during installation, the system configuration wizard enabled you to import one production license, one non production license, or both, depending on your landscape environment you can import additional licenses, if needed see importing licenses docid\ hjmsvreybhe0xdorxmsw5 types of licenses mainly uses production and non production licenses license type description expiration production used to access the production landscape of a tenant does not expire unless the mac address is unspecified in that instance, the license expires after 30 days if you move the license to a new server with a different mac address, then you must acquire a new license tied to the new mac address development a non production license used to access the staging and uat landscapes expires according to the maintenance agreement between your organization and not for resale a non production license, mainly used by ivanti service manager partners it can also be used for staging, uat, or testing if you already have development licenses expires after 30 days if you do not specify the mac address after you set the mac address, it expires according to the maintenance agreement between your organization and evaluation a non production license used by potential customers has the maximum number of named and concurrent user licenses expires after 30 days is not associated with a mac address there are two types of user licenses, for both production and non production licenses concurrent licenses for any user who is currently logged into the system this is a shared pool of licenses the concurrent license that is used is specified by the bundle that is specified for each role named user licenses specific to a certain user the user can log in to the system from many places at one time and it is counted as only one license you specify which users are named users in the employee record, and you can change which employees get a named user license at any time about license bundles list of license bundles and components docid\ hjmsvreybhe0xdorxmsw5assigning a bundled license to a role docid\ hjmsvreybhe0xdorxmsw5license tracking in neurons for itsm docid\ hjmsvreybhe0xdorxmsw5 has defined several license bundles, which are sets of modules, or user interfaces each role is associated with a license bundle list of license bundles and components license bundle components help desk dashboards and reporting incident management knowledge management mobile self service service catalog survey voice automation (optional add on) workflow automation service desk dashboards and reporting incident management knowledge management mobile self service service catalog survey voice automation (optional add on) workflow automation change management cmdb configuration management problem management service level management service management dashboards and reporting incident management knowledge management mobile self service service catalog survey voice automation (optional add on) workflow automation change management cmdb configuration management problem management service level management availability management event management financial management portfolio and project management release management the following are considered license add on modules add on module components discovery discovery voice voice mobile mobile assigning a bundled license to a role to assign a bundled license to a role, follow the procedure in the "assigning a bundled license to a role" topic in the online help by default, roles do not have a license bundle associated with them, so you must assign a license bundle to each role manually if you do not, you may get license violation errors logged in your system even though you have the correct licenses if you have imported licenses but do not see the correct license bundles displayed in the configuration console, clear the validation cache go to configure > cache management and then click reset cached validation lists only see the online help for more information license tracking in neurons for itsm you cannot use unless you have a license when you purchased , you also purchased a set number of licenses if needed, you can purchase additional licenses if you consume more seats than you have licenses for, the system does not log you out it does, however, log an event into a log file for example, if you have 10 concurrent licenses and try to log in 11 times, the system allows it due to the way that web browsers work, it is very possible for one user to consume more than one license for example, if a user logs in to using microsoft internet explorer and then opens google chrome and logs in again, another license is consumed if this happens, the system logs a license violation error that you can view in the license manager in the system audit information workspace using the license manager logging into the license manager docid\ hjmsvreybhe0xdorxmsw5configuring landscape information docid\ hjmsvreybhe0xdorxmsw5importing licenses docid\ hjmsvreybhe0xdorxmsw5viewing the discovery node count docid\ hjmsvreybhe0xdorxmsw5viewing the active licenses docid\ hjmsvreybhe0xdorxmsw5configuring the email address for notifications docid\ hjmsvreybhe0xdorxmsw5configuring the smtp settings docid\ hjmsvreybhe0xdorxmsw5working with scheduled jobs docid\ hjmsvreybhe0xdorxmsw5viewing reports docid\ hjmsvreybhe0xdorxmsw5 logging into the license manager the license manager uses the same credentials that are used to access the configuration database to log into the license manager, follow these steps in the start menu, click the down arrow to see the apps menu, and then click license server select a landscape enter your user id and password this is the same user id and password that you use for the configuration database click continue configuring landscape information you can create, edit, and delete information about the landscapes to which the license manager is associated log into the license manager click either configure landscapes in the top right corner of the login page or click configure landscape information from any page in the license manager the system opens a new browser window and displays the enter landscape information page enter landscape information page to allow the operations console to use this landscape, check used by the operations console on the line associated with the landscape the operations console can only use one landscape at a time to edit the information for an existing landscape, do the following a click edit on the line associated with the landscape the system displays the edit landscape page b make changes as needed c click save to delete the landscape information, do the following a click delete on the line associated with the landscape b click delete at the confirmation message when you configured using the system configuration wizard, the system automatically created a link to the landscape therefore, in general, you do not need to add a link to a landscape however, if you do need to add a new link to a landscape, follow these steps a click create new the system displays the create landscape page b in the configservice api url field, enter the url of the configuration server c check used by the operations console if the system should use this link to connect with the operations console the operations console can only connect to one landscape d click load landscape types and then select a landscape from the drop down list e click create importing licenses when you initially configured the license manager in the system configuration wizard, you imported either one production license file, one non production license file, or both (see configuring neurons for itsm docid\ rxdmdbks23uwnooqrk0oi ) if your deployment has multiple license managers, when you import a license, ensure that you are importing it on the server that has the same mac address as the license file for example, say you installed license managers on the following application server 1 with a mac address of aa🕙23🕙00 application server 2 with a mac address of bb🕙23🕙00 then you ask for and receive a production license for mac address aa🕙23🕙00 you import the license from the license manager that is installed on application server 1 after you have imported the license, the license managers on both application servers respect the license you do not need a second license for the second application server to import additional license files, follow these steps log into the license manager click licensing > import license files the system displays the licensing import license files page import license files page click upload license file navigate to and select a license file and click open the system adds the license to the system this page shows the following information field description file name the name of the license file that you uploaded expiration date the expiration date of the license file mac address the mac address associated with the license file self service self service is the bundle name the number of self service licenses contained in the license file broken into concurrent and named licenses service catalog service catalog is the bundle name the number of service catalog licenses contained in the license file broken into concurrent and named licenses service management service management is the bundle name the number of service management licenses contained in the license file broken into concurrent and named licenses click the delete icon to remove the license file and its associated licenses from the license manager click the show details icon to display the details the details contain the following information field description bundle the name of the bundle name the name of the module named licenses the number of named licenses contained in the license file concurrent licenses the number of concurrent licenses contained in the license file expiration date the date when the license expires if your deployment only has one tenant, the information displayed here is the same as in the list of imported license files section if your deployment has more than one tenant, this table displays the license distribution across the tenants field description tenant the name of the tenant self service the number of self service licenses allocated per tenant broken into concurrent and named licenses service catalog the number of service catalog licenses allocated per tenant broken into concurrent and named licenses service management the number of service management licenses allocated per tenant broken into concurrent and named licenses to distribute licenses among multiple tenants, click in a cell and change the number of licenses to allocate to a tenant the total number of licenses across the tenants cannot exceed the total number of licenses see allocating licenses across tenants docid\ hjmsvreybhe0xdorxmsw5 allocating licenses across tenants viewing the discovery node count this information tracks the trend associated with the discovery licenses and is based on the discovery count scheduled job log in to the license manager click licensing > discovery the system displays the licensing discovery page this page shows the following information field description tenant name the name of the tenant last scan date the date and time when the job was run nodes count the number of configuration items found during the job viewing the active licenses this page displays the active sessions on it does not show active sessions on the configuration database log in to the license manager click licensing > active licenses the system displays the licensing active licenses page active licenses page select a tenant from the drop down list this page shows the following information field description session id the session id associated with the logged in user user the user name of a logged in user role the role with which the user is logged in bundle name the bundle associated with the license associated with the user see about license bundles docid\ hjmsvreybhe0xdorxmsw5 add on modules any add on modules associated with the bundle see about license bundles docid\ hjmsvreybhe0xdorxmsw5 license taken time the time when the system used the license license type the license type can be named or concurrent configuring the email address for notifications log in to the license manager click configuration > email address the system displays the configuration email address page email address page enter the following information field description email address to use when sending emails from the license server the email address to use as the from email address for emails sent from the license manager email address to use when sending emails to ivanti software the email address to use as the to email address for emails sent from the license manager to ivanti software the system sends license usage information based on the license violation notification to frs scheduled job email address to use when sending emails to the system administrator the email address to use as the to email address for emails sent from the license manager to the system administrator of your organization the system sends license usage information based on the license violation notification to admin scheduled job click save configuring the smtp settings use this page to view and edit the smtp settings used to send emails the information on this page comes from the system configuration wizard log into the license manager click configuration > smtp setting the system displays the configuration smtp setting page smtp setting page the system displays the following information field description host the email server host port the port associated with the email server account the account associated with this tenant this is the same as the value in the username field on the email configuration workspace in the service desk console domain the domain associated with the account use ssl specifies if this account should use ssl select a tenant from the tenant drop down list check use this setting for email notifications to use these smtp settings for emails click save working with scheduled jobs the license manager has several predefined scheduled jobs these are used to send information to the administrator on a regular basis instead of sending an email every single time there is an event all violations are listed on the system audit information page the following are the predefined scheduled jobs that cannot be changed license capacity allocation notification job determines if your licenses are valid and that you actually have the licenses that you are allocating named license violation determines if you have more users listed as named users than you have named user licenses data integrity verification determines if the licenses have been modified discovery count determines if the licenses for your configuration items are valid the following are the predefined scheduled jobs that you can edit license violation notification to frs sends an email to ivanti software with information about license violations by default, this job is disabled license violation notification to admin sends an email to your system administrator with information about license violations log in to the license manager click system jobs the system displays the system jobs scheduled jobs page scheduled jobs page this page contains the following information field description module the name of the module can be either licensecore or heatmodule job the name of the job enabled specifies if the scheduled job is enabled start date the start date of this scheduled job start time the start time of this scheduled job next run date and time the next date and time when the scheduled job runs recur every the time period for the recurrence can be day, hour, or minute interval the interval for the recurrence for each entry, the system displays additional information at the bottom of the page field description module the name of the module can be either licensecore or heatmodule job the name of the job run time the date and time when the scheduled job was run details details of the job if the job is not successful, contains detailed information to see the job details in a larger format, click the show details icon at the end of the row you can edit the details associated with the license violation notification to frs and the license violation notification to admin scheduled jobs to edit a scheduled job, do the following a click the edit icon at the end of the row the system displays a dialog box b enter or change any of the following information field description job the name of the scheduled job you cannot change this name description a description of the scheduled job start date the start date and time enabled specifies if the scheduled job is enabled next run date time the next date and time when the scheduled job runs recur every specifies the recurrence for this job click save viewing reports you can view two types of reports in the license manager system audit information logs follow these steps to view the reports log in to the license manager click reports to view the system audit information, click system audit information the system displays the reports system audit information page see system audit information page docid\ hjmsvreybhe0xdorxmsw5 examples of the information on this page include license upgrades and license violations we recommend that you review the information on this page if you have any problems and then review the information on the log page see log page docid\ hjmsvreybhe0xdorxmsw5 system audit information page this page contains the following information field description tenant name the name of the tenant event log date and time the date and time of the log event subsystem the specific area can be license violation, license upgrade, or data integrity service class the type of information can be warning, info, debug, fatal, or error title a short description of the event details a longer description of the event operation result the result of the operation can be success or failure if you cannot see all of the columns, resize the columns that you can see so that the remaining columns are displayed click the show details icon at the end of the row to see the details if you cannot see the show details icon, resize the columns until it is displayed to view log information, click log the system displays the reports log page use this information for troubleshooting log page this page contains the following information field description subsystem the name of the subsystem can be email notification, import license, license upgrade, named license violation, or configuration service event log time the time and date of this log event details information about this log event log type the type of log can be info, error, or warning to see the log details in a larger format, click the show details icon at the end of the row