Distribution choice
Choose a Linux distribution around applications, available skills and maintenance arrangements, then verify the exact release and relevant packages before defining the operational scope and who will be responsible for its upkeep.
Linux
Linux servers for SMEs in French-speaking Switzerland: select a suitable distribution and prepare security, updates and service recovery with Sunitech.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

Linux can provide the foundation for business applications, web services, internal tools or container platforms. Selection depends on the application, available skills and operating requirements. For an SME in French-speaking Switzerland, a server should remain manageable even when its original installer is unavailable. We identify services, dependencies and responsible people before defining installation and ongoing support. Necessary access and procedures must be transferable.
Choose a Linux distribution around applications, available skills and maintenance arrangements, then verify the exact release and relevant packages before defining the operational scope and who will be responsible for its upkeep.
Prepare Linux services around their dependencies, accounts and resource requirements, with documented configuration and checks that confirm applications work after installation or a change to the system on which they depend.
Organise Linux updates by distinguishing distribution repositories from software added separately, then assign responsibility for each component needed to operate the service and keep track of its own maintenance and compatibility requirements.
Define accounts and privileges on Linux systems, protect connection methods and document recovery access, so that interventions remain attributable and authorised people can take over administration when the usual operator is unavailable.
Select Linux checks that reveal failures or resource constraints worth addressing, then organise alerts, logs and expected responses with the owners of the hosted applications and the people responsible for operating them.
Identify the Linux data, configurations and dependencies required for recovery, then test restoration in an appropriate environment rather than assuming that copying files alone is sufficient to restart a usable business service.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Installation, configuration and support.
Protection of data and access.
Monitoring, updates and optimisation.
Backup strategy and disaster recovery planning.
Tenant management, backups and administration.
A local, responsive and available team.
We start with your teams’ needs, business applications and organisational constraints.

Share client files between colleagues, with appropriate access and documents that are easy to find.

Protect patient records and maintain the tools needed for consultations.

Find plans and files on site while keeping control of access for everyone involved.

Organise access for employees, elected representatives and volunteers, and make handovers easier when teams change.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Roles, permissions and protections suited to the agreed scope.
Identified dependencies, with backup and recovery arrangements to prepare.
Documented joiners, leavers and changes in responsibility.
Accessible configuration, licence and upcoming renewal records.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Linux is not a single distribution with one uniform maintenance policy. Ubuntu and Debian, for example, publish their releases and support conditions. We check the distribution required by the application publisher, available packages and possible maintenance extensions. An IT audit helps identify older systems and additional repositories. The schedule must account for both the operating system and software installed outside its repositories.
Installation defines accounts, permissions, network services, updates and collection of useful diagnostic information. Access keys and secrets should be protected and recoverable by authorised people. We document dependencies and test service restoration. Managed IT can cover agreed monitoring and interventions. Where an application uses Docker, follow-up should also include its images, volumes and compatibility.
A system available without a paid licence is not maintenance-free. Updates, backups, migrations and incidents require time and skills. Commercial support may be needed according to the application and desired commitments. We also review external dependencies, hosting accounts and data recovery. A release labelled stable must still be checked against support dates and fixes actually available for the components in use.
Should the newest release always be selected? Not automatically. Application compatibility, maintenance duration and migration options should guide the choice.
Can every update be automatic? Some tasks can be automated after validation, but a restart or major change may interrupt an application. We define checks and maintenance windows around the affected services, with a route back to a known state.
The Ubuntu release cycle presents maintenance coverage. The Debian releases page describes branches and their support. These sources illustrate why the distribution, version and components need identification before an operating schedule is proposed.
Review of your needs, comparison of options and clearly explained priorities.
Preparation, configuration, testing and coordination with the relevant providers.
Agreed support scope, documentation, licences and next steps.
A project? A question?
An initial conversation to understand your situation and decide on the next steps together.
Contact us