License Management. If Licensee is the academic institution using the Licensed Software for teaching purposes, Licensee will manage all student licenses through a license server provided by Licensor in accordance with guidelines provided by Licensor. Licensee agrees to provide reports describing the number of licenses Licensee has issued in each period upon Licensor’s request.
License Management. You may obtain, assign, renew, and transfer licenses to JetBrains Products and Services, or manage them using other options available. You may also provide license management permissions to other people using JetBrains Account Services.
License Management. Notwithstanding the result of any Revocation request, CI Plus LLP may, but is not required to, take into consideration whether the facts and circumstances brought to light in connection with such request, even though they may not satisfy the current Revocation criteria, may represent a breach of the Licensee’s license under the Effective Interim License Agreement in connection with which corrective action by CI Plus LLP and the Licensee may be appropriate.
License Management. Notwithstanding the result of any Revocation request or associated arbitration, CI Plus TA may, but is not required to, take into consideration whether the facts and circumstances brought to light in connection with such request, even though they may not satisfy the current Revocation criteria, may represent a breach of the Licensee’s license in connection with which corrective action by CI Plus TA and the Licensee may be appropriate.
License Management. Contractor will be responsible for managing all Microsoft software licenses sold under this contract and will be responsible for tracking all license expiration dates, potential renewals and maintenance options. Contractors may also offer any reporting capabilities that would allow Customers to view Customer specific information of all Microsoft software purchased under the Contract. If offered, Customer specific information will, at a minimum, include the following information: • Agency/OEU name; • Date of purchase; • Software title; • Number of licenses purchased; • License term; • License expiration date; • Name of individual who placed the order and any contact information available; and • Any other pertinent information.
License Management. Subject to FNT's prior written approval of FIS'S proposed acquisition of FNT Software and the related Pass Through Expenses, upon FNT's request, FIS shall obtain in FNT's name, comply with and maintain (for so long as used to support Services) all software licenses for FNT Software. FIS shall maintain, substantially current, a log of all FNT Software and FIS Software used or accessed by FNT or its customers and upon FNT's request from time to time shall provide FNT with a Report (i) identifying all current software comprising FNT Software and FIS Software used or accessed by FNT or its customers, and (ii) describing any unresolved disputes or contract claims arising under those licenses obtained by FIS in FNT's name.
License Management. Respondent is to document their detailed proposed plan for managing all Microsoft software licenses sold under the Contract as described in section 7.6.2, License Management.
License Management. LSP will document its plan for managing all Microsoft software licenses sold under the Contract. License management should include, but is not limited to the following: • Tracking of Software Licenses sold to ensure that Customers are fully aware of future expiration dates well in advance of expiration to ensure that licenses do not lapse unless intended by the Customer. • License tracking support (website and vendor assistance as needed) • Tracking of individual licenses and server licenses exempt from Chapter 282, Florida Statute, requirements. • Standardization of customer (agency/OEU) names to facilitate ease of tracking licenses purchased. • Provide a single contact for license tracking and a trained licensing specialist to assist Customers with licensing questions. After Contract award, the LSP will update the plan, as needed, and will provide a copy of any revised plans to the Department’s Contract Administrator.
License Management. Allows you to manage the licenses for components installed with Foglight or Foglight for Virtualization, Enterprise Edition, but not enabled. NOTE: Foglight for Virtualization, Enterprise Edition version 8.5 and Foglight for Storage Management 4.3.5 have a common installer. ▪ Activate XenDesktop trial license. Activates the 40-day trial version of Foglight for Citrix XenDesktop and XenApp. For more information, see the Foglight for Citrix XenDesktop and XenApp documentation. ▪ Activate Storage Management trial license. Activates the 45-day trial version of Foglight for Storage Management. After the trial is activated, you can start creating Storage Management agents using the Start monitoring storage devices link.For more information, see the Foglight for Storage Management User and Reference Guide. ▪ Add a new license. Allows you to quickly access the Manage Licenses dashboard. For more information on licenses, see the Foglight Administration and Configuration Guide.
License Management. Allows you to manage the licenses for components installed with Foglight or Foglight for Storage Management, but not enabled. NOTE: Foglight for Virtualization, Enterprise Edition version 8.5 (or later) and Foglight for Storage Management 4.3.5 (or later) have a common installer. ▪ Activate Foglight for Virtualization trial license. Activates the 45-day trial version of Foglight for Virtualization, Enterprise Edition. When the activation process completes, Foglight for Virtualization, Enterprise Edition (with Storage functionality) becomes the main entry point for monitoring your environment. For more information, see the Foglight User Guide and the Foglight Administration and Configuration Guide. ▪ Add a new license. Allows you to quickly access the Manage Licenses dashboard. For more information on licenses, see the Foglight Administration and Configuration Guide.
