IServ · baramundi
System & client management for education.
IServ supports communication, teaching and organisation at school. baramundi focuses on central endpoint management. We support the setup and administration of either system independently. The choice depends on the tasks your existing environment already covers.
Platform & endpoints
School use and endpoint operation at a glance.
Two different focuses, with overlap in device management. Either system can be used independently.
IServ
School platform
Accounts and permissions
School accounts, groups and access rights define who can use which services.
Communication and teaching
Email, messenger and video conferences support communication. Files and tasks provide material for teaching.
School devices and software
IServ also provides device management and software and operating system deployment, depending on the deployment model.
baramundi
Central endpoint management
Deploy endpoints
Prepare software packages and operating systems for controlled installation on supported devices.
Updates and administrative tasks
Distribute patches and configurations through agreed workflows. Automate recurring administrative tasks.
Inventory and support
Record hardware and installed software. Remote support is available with the relevant module.
Available functions depend on deployment model, modules, licences and supported devices. Before rollout, agree which system handles installation, updates and configuration.
IServ: school platform and everyday school use
For an IServ setup, we review user structures, required modules and the suitable deployment model. Existing directory services, servers and networks are included in the plan.
thiwico supports setup, migration, administration and training. Before handover, the agreed access paths and functions are checked with the people responsible at your organisation.
baramundi: central endpoint management
For management with baramundi, we review the device estate, required applications and supported versions. Software packages and installation workflows are tested on pilot devices first.
The rollout sequence, maintenance windows and exceptions are agreed around actual use. Required additional modules are assessed against administrative tasks and existing licences.
Use existing management or add specific capabilities
IServ and baramundi overlap in device and software management. Adding another tool is therefore not an automatic next step. We first review the capabilities already available and identify specific unmet administrative needs.
For school communication and user organisation, IServ is the relevant focus. For central endpoint administration, we review existing management and, where useful, baramundi. If both systems are used, responsibilities for installations, updates and configurations are assigned explicitly to avoid conflicting changes.
Start with a pilot, then plan the rollout
We assess the existing environment, prioritise requirements and prepare the necessary access and configuration. Software and settings are tested on selected devices first. We then agree the sequence of work, maintenance windows and how to handle exceptions.
The transition includes checking agreed functions and providing clear technical documentation. Changes to sign-in procedures or working practices are discussed with the people responsible. Training and further support are planned around your needs.
Administration after deployment
New users, different course software and replacement devices continually change the environment. We carry out agreed administration tasks, check deployment status, investigate errors and record relevant changes. Maintenance windows and responsibilities also need to reflect how the systems are used.
A working endpoint depends on networks, servers and backups as well. We account for these dependencies when making changes, so individual software tasks are planned in the context of the wider environment.
Questions about system and endpoint management
Do IServ and baramundi always need to be used together?
No. We assess the tasks your existing systems already handle and where additional management would help. IServ includes its own device and software functions. Whether to use baramundi depends on your endpoint and operational requirements.
Can we keep using our existing computers?
This depends on the hardware, operating systems, applications and their support status. We assess the inventory and establish which devices can be retained, need changes or should be replaced.
Can you support a move from LogoDIDACT?
Yes. For the transition to IServ, we assess accounts, data, functions in use and endpoint requirements. Our migration page explains the process and the current supplier information.
What should your endpoint management cover?
Tell us about your school platform, devices and applications. We can then discuss setup, changes and ongoing administration.