Context
In early April, a government institution—a new client—contacted our company after facing increasingly frequent breach attempts and infrastructure infections.
Initially, the request covered protection for more than 40 devices. The infrastructure came with several key constraints:
- some workstations were still running Windows 7;
- servers were running Windows Server 2016;
- centralised management with an on-premises console was required;
- procuring the software required a specific document package and expert opinions from the State Service of Special Communications and Information Protection of Ukraine (SSSCIP).
At that stage, the client did not need extended cloud features. The goal was not to buy the most feature-rich bundle, but to get a sufficient baseline level of protection for the actual infrastructure.
In April, the initial 40+ device scope could not be funded due to budget constraints, so the project resumed once funding was approved.
Objective
We needed to find a configuration that would simultaneously:
- protect as many workstations as possible within the available budget;
- account for computers still running Windows 7;
- cover the Windows Server 2016 server infrastructure;
- provide centralised management with local / on-premises deployment;
- prepare the exact procurement documentation package required.
One explicit requirement was not to include features the institution did not currently need. There was no reason to propose a pricier configuration with extra cloud capabilities.
Solution: why 26 licences cost less than 25
In late July and early August, the institution returned to the procurement. Available funding was enough to cover 25 computers.
We could have simply quoted the requested quantity. Instead, before preparing the quote, we checked the current ESET licensing price tiers.
That revealed an important detail: stepping into the next quantity tier meant the total price for a 26-computer licence was lower than for 25.
As a result, we offered the client 26 licences instead of 25.
25 → 26: more protected workstations at a lower total licence cost.
No contrived "percentage savings" and no cutting corners on the required scope—just checking the actual licensing tiers before placing the order.
For the client's current needs, we selected ESET PROTECT Entry with on-premises management. This matched the real situation: the institution needed sufficient baseline protection for its workstations and servers plus a centralised console, and its infrastructure could host the management server locally.
How the work was carried out
1. Re-verified the scope and pricing
Once funding became available, we confirmed the actual procurement scope, checked ESET pricing tiers, and proposed 26 workstations instead of the requested 25.
We then finalised ESET PROTECT Entry with local centralised management.
2. Prepared the procurement documentation
Within our supplier responsibilities, we handled the procurement paperwork and prepared the agreed document package:
- contract;
- invoice;
- certificate of completion (act);
- SSSCIP expert opinions;
- certified copies of documents with signatures and stamps;
- a licence certificate confirming official software acquisition.
The document set was tailored specifically for this procurement—without making a blanket claim that the exact same pack fits every government institution.
3. Supported the launch of the new management console
Technical deployment inside the infrastructure was handled by the client's external system administrator.
Baisk-S did not step over the administrator's role, focusing instead on our part of the support:
- helping navigate the new centralised management system;
- assisting with the transition from the previous Business Account to ESET PROTECT Hub;
- answering questions that came up during setup.
This kept responsibilities clearly divided: the administrator stayed in control of the infrastructure, while Baisk-S served as the coordination point for ESET, licensing, and paperwork.
4. Found a transitional scenario for Windows 7
Workstations running Windows 7 required separate attention.
Microsoft no longer supports this operating system, so installing antivirus software does not fix vulnerabilities in Windows 7 itself or turn it into a modern supported platform.
After checking the machines that had the necessary security updates installed, we were able to select a compatible earlier version of ESET.
This is not a "keep Windows 7 forever" solution, but a practical transitional workaround for a constraint that already existed in the client's environment.
Results
By the end of this phase, the government institution received:
- ESET PROTECT Entry;
- licensing for 26 workstations;
- server infrastructure protection;
- centralised on-premises management;
- an agreed supplier documentation package;
- support for the external system administrator during deployment and console onboarding;
- a compatible transitional option for part of the existing Windows 7 fleet;
- the flexibility to review and expand the configuration later as the infrastructure evolves.
Most importantly, the client got a sufficient baseline level of protection without paying for features they do not need right now.
Project in numbers
26
workstations covered by the final licence
25 → 26
more protected PCs at a lower total licence cost
April → August
from initial inquiry to delivery once funding was approved
What's next
Budgeting for next year is currently under discussion.
The next step will depend on how the institution's infrastructure changes. Options include increasing the number of protected endpoints, revising the configuration, or potentially moving to cloud management.
We will also assess whether maintaining an on-premises management server remains practical for their setup. Once again, the next decision will be driven by actual requirements, infrastructure, and budget—not by pushing a more expensive bundle.
Deal handled by: Mary Gladka — Certified ESET Product Specialist | Baisk-S
Questions and answers
Can ESET be used on Windows 7 computers?
In a specific environment, this depends on the condition of the operating system, installed updates, and availability of a compatible ESET version.
Windows 7 is no longer supported by Microsoft. This option should therefore be treated as a transitional workaround for existing legacy infrastructure, not as a recommended setup for new systems. Having ESET installed does not restore Windows 7 support or patch vulnerabilities in the operating system itself.
Why were 26 licences cheaper than 25?
Vendors can use different pricing tiers depending on the number of licensed endpoints. In this case, moving into the next tier resulted in a lower total cost for 26 computers than quoting 25.
That is why, before placing an order, we check not only the exact seat count requested by the client, but also the current licensing tiers.
Prices and quantity tiers are verified for each individual quote and are subject to change.
Can ESET PROTECT be used without a cloud console?
In this project, the client chose on-premises centralised management because they had the infrastructure to host the management server locally.
That model matched their current requirements. For any other organisation, the choice between on-premises and cloud management should be made separately based on its infrastructure and tasks.
What documents did the government institution receive with the licence?
For this project, we prepared the contract, invoice, certificate of completion (act), SSSCIP expert opinions, certified copies of the required documents, and a licence certificate.
The exact set of documents is defined per procurement and depends on the tender terms and the customer's requirements.
