Logos on a references page tell you who the clients are. They do not tell you what was done. These seven case studies describe the starting point, the solution and the result – with the figures and the technology behind them. The services involved are listed in our overview of services.
Recurring disruptions in the area kept cutting sites off from the central systems. Instead of a single measure, the result was a concept covering five different failure scenarios – UPS, backup lines, standby servers, replication and Veeam.
A branch-based business with a shared booking system. Six separate server roles, a central SonicWall firewall and centrally controlled Wi-Fi – all administered from one place.
File server, Exchange, booking server, mail archive
Around 100 workstations, 150 mailboxes, 1.2 TB of email and 2 TB of company data. Not simply moved but divided up: Microsoft 365 for communication, a data centre for everything else.
A Windows RDS farm of five servers supplies a network of 106 branches. Designed and implemented by INFONET, then handed over to the client's in-house administrator team.
A data security service provider with around fifty administrators of its own: after migrating to new Windows and Exchange servers, permission inheritance had gone through to everything. Even the management and accounting data were open.
In 2015, a German airline needed a piece of custom software up and running by the date of an official visit by the then Federal Chancellor. The previous provider pulled out, and the other vendors approached quoted four to six months. There were three and a half weeks left before the deadline.
If one of these situations sounds familiar, let us talk about it. The initial consultation is free and, if need be, ends with us telling you that your current solution is fine.
Arrange a consultation
A note on confidentiality
For reasons of confidentiality, we only publish client names and contact persons with their express consent. If you have a specific interest, we are happy to put you in personal contact with a reference client after checking with them.
What these projects have in common
Four things that were the same in every one of these projects
Map the dependencies first. Only once it is clear which system brings which business process to a halt can you decide what needs to be redundant – and what does not.
Centralise where it saves effort. A change you make once instead of a hundred and six times is the real gain. That applies to applications, firewall rules and Wi-Fi alike.
Migrate in stages, with a fallback plan. None of these migrations was a single-day cutover. Anything that does not work as expected has to be reversible.
Then keep supporting it – or hand it over properly. An environment that only its builder understands is not a solution; it is a dependency.
Free initial consultation
Does one of these situations sound familiar?
Then a conversation is worthwhile. We look at your environment, tell you openly where we see risks, and what can be changed with reasonable effort.
Mon–Fri 9 am–6 pmEmergency support outside these hours by arrangement
Your choice about external services
This website works without cookies, without tracking and without advertising networks. For one optional feature we embed content from an external provider. Doing so transfers your IP address to that provider – which only happens if you allow it.