Fixed-price health check

Find out how healthy your LoadMaster really is

Load balancers are the classic forgotten appliance. We review your LoadMaster's configuration backup and logs offline, so nothing connects to or changes the appliance, and you get a written report on its health with the evidence behind every finding.

Request a LoadMaster health check
Fixed priceFixed scope, confirmed once we know how many LoadMasters you run, then a walkthrough of the report

Who books this

  • You inherited a LoadMaster that nobody documented
  • It has run quietly for years and nobody has checked the certificates, firmware or failover
  • A licence renewal is coming up, or you were on MELA licensing and had to move
  • You are deciding whether to stay on LoadMaster or move, and want to know what it actually does first
  • Something went wrong recently and you want to know what else is waiting

What you get

  • Prioritised findings rated red, amber or green, each with the evidence behind it
  • An inventory of your virtual services and the real servers behind them
  • A side-by-side comparison of both nodes, where you run a high-availability pair
  • Firmware, lifecycle and support status, and certificate checks
  • Recommended improvements, and the checks still outstanding, because an item we could not check is not a pass
  • A walkthrough of the findings, with the next actions agreed with you

What we need from you

  • A native configuration backup from the LoadMaster. You export it, or we do with your access
  • The system, warning, boot and audit logs from the same appliance
  • For a high-availability pair, a backup and logs from each node, so the two can be compared
  • Certificate exports, if you want the certificates checked in more depth. This part is optional
When not to book this

If the LoadMaster is being retired in the next few weeks, or somebody already patches the firmware, renews the certificates and tests the failover on a schedule, this will mostly confirm what you know. If all you need is where your model sits in its lifecycle, the lifecycle table on our Kemp partner page answers that for nothing.

Other assessments

  • Microsoft estate review: Forty-five minutes and a written summary. What you are licensed for, what is switched on, where the gaps are, and what we would fix first.
  • Security posture review: Most of what we find is not missing products. It is features you already pay for that were never switched on. Forty-five minutes to find out which.
  • Cloud cost review: Non-production running around the clock, orphaned resources nobody decommissioned, and licences still assigned to leavers. Forty-five minutes to quantify yours.
  • Cyber Essentials readiness check: The five control themes, checked against what you actually run. Most first-time failures are the same handful of things, and all of them are cheaper to fix before you apply.
  • Application compatibility assessment: Migrations do not stall on operating systems, they stall on a handful of applications nobody can account for. This sorts your estate into the four groups that actually matter, before you commit budget to any of it.
  • Virtual desktop review: Whether you are choosing between Azure Virtual Desktop and Windows 365 or already running one and paying more than you expected, this is the same review: what the estate is doing, what it costs, and what it should cost.
  • Copilot readiness check: Copilot does not grant anyone a single permission they did not already have. It just makes what they already had very easy to find, which is why the permissions work belongs before the licences and not after.
  • Backup and recovery review: Everyone has a backup. Far fewer have a restore. The question worth answering is not whether jobs are running, it is when somebody last proved one and how long the business would be down.
  • Application and reporting discovery: Most bespoke software goes wrong at scoping rather than in the build, and the most valuable thing a first conversation can do is establish whether you should be commissioning software at all.
  • Endpoint and Intune review: Not whether Intune says the estate is compliant, but whether that means what you think it means: what is enrolled, what has gone quiet, which policies are actually winning, and what you could prove if somebody asked.
  • DfE digital standards baseline: Sixty minutes against all twelve DfE digital and technology standards, the six core ones first. You get a governor-ready summary of where you stand and a dated plan for each gap, whether or not anything else follows.
  • RDS health check: Connection Broker, Session Hosts, Gateway, Web Access, licensing, profiles and load balancing, reviewed as one estate. You get an executive summary to take to budget approval, the technical findings with their root causes, and a rectification path in the order we would do it.