Managed ILMT Services

Q: What exactly do you do as part of managed ILMT?

We keep your ILMT running properly so the data is always audit-ready. That means monitoring agent health, updating the software catalog, generating and reviewing compliance reports, and flagging anything unusual. You get a quarterly summary of where things stand and a direct line to us when something comes up.

The Problem with "We'll Get to ILMT Later"

Here is what we see again and again: a company installs ILMT, runs the initial reports, and then nobody touches it for months. The IT team has other priorities. ILMT sits there, technically running, but slowly going stale.

Then IBM sends an audit letter.

Suddenly everyone needs ILMT data from the last two years. But 30% of the agents have stopped reporting after a round of server patches. The software catalog hasn't been updated since the last ILMT version upgrade. Half the bundling rules still reference entitlements the company sold off eighteen months ago. Getting this data into shape under audit pressure takes weeks and costs far more than maintaining it would have.

That is the gap our managed service fills. We keep your ILMT environment healthy on an ongoing basis, so the data is always there when you need it.

What We Actually Do

Agent Health Monitoring

BigFix and ILMT agents break more often than most people expect. A Windows update changes a firewall rule. A Linux server gets reimaged without the agent package. A VM gets cloned and two agents start reporting with the same ID. We catch these issues within days, not months, and work with your ops team to fix them before they become gaps in your compliance data.

Report Generation & Review

We do not just generate reports and email them over. We read them. We look for things like a PVU count that jumped 40% since last month (usually a misconfigured VM, not actual growth), servers that appear in BigFix but not in ILMT, or products showing up that nobody remembers installing. You get a clean summary with anything that needs your attention flagged.

Software Catalog Maintenance

ILMT identifies software by matching file signatures against its catalog. If the catalog is outdated, it misses things, or worse, misidentifies them. We keep the catalog current, add custom signatures for your non-standard installations, and make sure bundling rules actually match what your Passport Advantage agreements say.

Quarterly Compliance Reviews

Every quarter we compile a compliance summary: what looks good, what needs attention, and what changed since last time. Think of it as a health check for your IBM license position. If something is heading in the wrong direction, you will know about it months before an auditor would.

Tired of Worrying About ILMT?

Tell us about your environment. We will let you know if managed services make sense for your situation. No sales pitch, just an honest assessment.

Schedule a Free Consultation

Is This the Right Fit?

This service works best for companies that run IBM software across at least a few dozen servers and do not have someone dedicated to ILMT full-time. If you have a single DB2 instance on one server, you probably do not need us. A one-time setup and some documentation will do.

But if your environment looks more like this, we should talk:

Multiple data centers or cloud environments with IBM middleware (WebSphere, MQ, Db2, Spectrum and similar)
An ILMT installation that "works" but nobody has really looked at in a while
An IBM audit on the horizon, or one that already happened and you do not want to repeat the experience
An IT team that knows ILMT exists but treats it as somebody else's problem

How It Works in Practice

We start by reviewing what you have: ILMT version, agent coverage, reporting history, software catalog state. This usually takes a few days and gives us a clear picture of where things stand. No surprises later.

From there, we set up remote access (VPN or jump host, whichever your security team prefers) and agree on a monitoring and reporting cadence. Most clients go with monthly reports and quarterly reviews, but we adjust based on how dynamic your environment is. A company migrating to cloud needs more frequent checks than one running a stable on-prem setup.

We handle the day-to-day. You get the summaries and flag anything that needs a decision on your end. That is it.

Frequently Asked Questions

What exactly do you do as part of managed ILMT?

The short version: we keep your ILMT running properly so the data is always audit-ready. That means monitoring agent health, updating the software catalog, generating and reviewing compliance reports, and flagging anything unusual. You get a quarterly summary of where things stand and a direct line to us when something comes up.

How often do you check our ILMT reports?

It depends on your environment. For most clients we run and review reports monthly. If you are in the middle of a migration or have a large, rapidly changing infrastructure, we do it more frequently. Stable environments with few changes can often go quarterly. We figure out the right cadence together during onboarding.

Do you need to be on-site?

No. Almost all of our managed ILMT work is done remotely. We connect through VPN or a jump host, whatever your security team is comfortable with. We have worked this way with clients across Europe for years and it works well. We schedule regular video calls to walk through findings together, and we are available by email or chat in between.

How is this different from a one-time ILMT review?

A one-time review tells you where you stand right now. It is a snapshot. Managed services keep things clean on an ongoing basis. The difference matters because ILMT data degrades over time. Agents go offline, the catalog gets stale, new servers get deployed without agents. A review done six months ago will not help you if your environment has changed since then.