Trellix License Management Services (LMS) is the Trellix function that “certifies our customers’ software deployment”. It is responsible for “validating your organizations’ adherence to the terms of your End User License Agreement (EULA) and Support Agreement(s)”, which the page calls collectively the “Agreements”.[1] The same page sets out Trellix’s position on subscription and perpetual licences, Technical Support, grant numbers and renewals. It is the most detailed public statement of how Trellix expects customers to count and certify usage. The overview is in Trellix licensing.
Editions
LMS describes two key forms of licensing.[1]
| Licence type | Term | Maintenance |
|---|---|---|
| Subscription | Two-year product licence term[1] | Technical Support included in the first year; the second year needs an additional one-year Technical Support agreement[1] |
| Perpetual | Indefinite[1] | Renewable annual Technical Support contracts, chosen separately[1] |
In both cases the licence itself confers no maintenance rights. LMS states that “a license agreement does not confer maintenance rights for the customer to upgrade to new versions or update the product”. The right to new versions or new virus signature files comes only through a Technical Support agreement.[1] The page quotes the EULA’s Updates clause: the licence “is limited to the version of the Software delivered by Us” unless a separate maintenance contract is bought. After the maintenance period, no further revisions or upgrades are available without a new licence.[1] Catalog: Subscription licences: two-year term, support included in the first year only; Perpetual licences need renewable annual support for maintenance; The licence covers only the version delivered.
Metrics
LMS refers customers to the Product Entitlement Definitions for the meters used by each product and suite.[1] In practice, its programmes measure deployment in nodes reported by ePolicy Orchestrator. LMS’s own example of noncompliance is “companies utilizing more nodes than purchased”.[1] ePO licensing reports “capture total machine counts, total usage per product, by OS type, etc.”, and an LMS specialist can help compare them with the licences on the grant letter.[1]
The Grant Letter records the SKU, quantity and subscription or support period of each purchase. It refers to the Product Entitlement Definitions for the licence type.[3] The grant number gives access to downloads. ePO - On-prem, for example, is downloaded “using a valid grant number”, entered with the email address associated with the product.[4] The ePO licence key then populates the Software Catalog with the licensed products.[7] Catalog: The Grant Letter states SKU, quantity and subscription or support period; Downloads require a valid grant number and the registered email address.
Counting / floors
Run ePO and compare with grants. LMS calls running license management tools such as ePO, and comparing deployment numbers with active grants, a best practice for staying compliant with the EULA.[1] Three LMS answers affect how the count is made:
- Inactive agents. If ePO appears to overstate managed nodes, LMS provides version-specific instructions for the ePO inactive Agent cleanup tool to remove inactive agents such as retired machines.[1] Catalog: Remove inactive ePO agents before counting nodes.
- Home and student use. Devices used at home or by students are subject to the EULA or Master License Agreement and must be included in the deployment certification.[1] Catalog: Home and student use devices count in a deployment certification.
- All grants together. A review is “not specific to a single grant number”. It covers total current licences and deployment for all products in use.[1] Catalog: A licence review covers all grants and products.
No minimum quantities are published on the LMS page.
Virtualization & partitioning
The LMS page does not address virtual machines. The Product Entitlement Definitions and the EULA Supplement (Network) listed on Trellix’s legal page are the governing documents.[5] Appliance-level virtualization rules are covered in Trellix appliance, network and email security licensing.
Cloud / BYOL
Moving from ePO - On-prem to ePO - SaaS requires an ePO - SaaS tenant with an active subscription. Before migrating, the customer should identify inactive systems and exclude them.[6] Catalog: ePO - SaaS shows subscriptions and utilization; migration needs an active subscription.
Programs
Software Deployment Verification
Software Deployment Verification is designed to keep customers compliant with their Agreements. The customer runs specific ePO reporting where applicable and certifies all current usage. If an overage is found, a true-up against the active grant “would immediately follow”.[1] LMS describes these requests as periodic reviews under the Agreements, including the EULA. If the customer is found out of compliance, an LMS specialist works with it to restore adherence.[1] Due dates are not extended, but customers may work with their License Specialist and Sales Account Manager.[1] Renewing support does not close a review, because a certification of deployment is still required.[1] Catalog: LMS validates adherence to the EULA and support agreements; Deployment verification ends in a true-up for any overage.
Technical Support and grant IDs
Trellix describes signature file (.DAT) updates, engine revisions and new software versions as software maintenance. Access to all of them is provided under Technical Support.[1] A current Technical Support agreement is required for product updates and upgrades, including engine and .DAT updates, under both subscription and perpetual licences.[1] The grant number supplied with the support agreement is used to download them.[1] LMS adds a caution. DAT and engine updates can currently be downloaded without a valid Grant ID, but “This does not legally entitle a customer to do so.”[1] Catalog: Updates, upgrades and DAT files require a current Technical Support agreement.
Renewal Enablement Policy
When support expires, the customer is no longer entitled to product updates, upgrades or technical phone support. Some functionality stops by itself, while other functionality requires the customer to stop using updates.[1] To keep using support features after expiry, the customer must renew “and you may be required to pay any accrued out-of-compliance fees”.[1] There is no grace period. A renewal made after expiry is back-dated to the expiry date, and LMS recommends sending purchase orders several weeks before expiry.[1] Catalog: No grace period for support renewal; late renewals are back-dated; Renewal after expiry may include accrued out-of-compliance fees.
Migration support
A customer moving to a competitor must keep support current until the product line has been completely removed from the environment, including all nodes and users. If a true-up review adds licences, those licences are sold with a 12-month support term and cannot be sold with a shorter one.[1] Catalog: Keep support current while migrating away; true-up licences carry 12 months of support.
Noncompliance and piracy
LMS defines noncompliance as use that violates the Agreements. Its examples are using more capacity or nodes than licensed, and accessing future versions after support or maintenance has expired.[1] The Antipiracy Policy goes further. It treats under-reporting installations acquired through volume purchase agreements, using subscription software past its expiration date, and accessing .DATs, updates or upgrades without a current agreement as forms of piracy. It also recommends regular audits that compare installed software with licence documentation.[2] Catalog: Noncompliance includes excess nodes and post-expiry version access; Use after subscription expiry and support access without agreement are piracy.
Taken together, these documents show that Trellix’s compliance model rests on three records: the grant letters, the ePO deployment report, and the support expiry dates. A licence position is incomplete unless it reconciles all three. That framing is editorial; the underlying statements are cited above. See true-up and license compliance.
Out of scope
This page does not quote the Technical Support and Maintenance Terms or the Thrive service descriptions, which are published as PDFs. It also does not cover hardware support, which has its own warranty and support documents on Trellix’s legal page.[5]