System Configuration in Rwanda
New systems and devices configured to your standard image and policy, not left at defaults.
System configuration sets up new computers and devices to one consistent, secure standard, so every member of staff starts with a working, protected device connected to email, files and printers, with their data moved across and the old device dealt with properly. Any organisation buying new devices, rebuilding problem machines or onboarding staff needs it. This page covers the hands-on setup standard, for any organisation. Automating device setup through Microsoft’s cloud tools is covered by Microsoft Intune device management.
What is system configuration, and who needs it
It’s the definition of a standard build for your desktops and laptops, and the work of applying it: operating system, security settings, applications, connections to your systems, device management enrolment and data migration. It suits organisations replacing a batch of devices, onboarding new staff regularly, or living with a fleet where every computer was set up differently.
The problem it solves
Devices straight from the box, or set up differently by whoever was available, cause two kinds of trouble. Security gaps: no encryption, staff with administrator rights, missing updates and no management. Support overhead: every device behaves differently, so each problem has to be diagnosed from scratch. A defined standard applied consistently closes the gaps and makes support faster.
What our standard build includes
- Supported operating system: Windows 11 or a current macOS, with all updates applied. Windows 11 requires a supported processor and TPM 2.0, so we check new purchases meet it.
- Disk encryption with recovery keys stored centrally, never on a sticky note.
- Standard user accounts, with administrator rights kept separate.
- Security software and firewall active and centrally managed.
- Business applications installed in their approved versions.
- Email, files, printers and Wi-Fi connected.
- Device management enrolment where you use it, so policies and updates follow the device.
- Asset record: serial number, user, purchase date and warranty.
The standard is written down and agreed with you, then reviewed when your systems change.
Different roles may need different builds. Finance staff need the accounting system and stricter access; field staff need offline-capable applications and a longer battery life; reception may share a device. We keep the number of builds small, usually two or three, so consistency isn’t lost, and record which build each device received.
Moving people from old devices
The move to a new device is often where data gets lost. We check what’s stored only on the old device, move files into OneDrive or a shared location wherever possible, carry across bookmarks and application settings, confirm email and shared files work, and only then wipe the old device. Wiping uses a method suited to the drive type, because simple deletion or reformatting leaves data recoverable.
What the work involves
- Agree the standard for each device type and role.
- Prepare the build process, automated or documented.
- Configure each device and record it in the asset list.
- Migrate the user’s data and settings.
- Hand over in person, checking sign-in, email, files and printing.
- Wipe and retire or reissue the old device.
What’s included and what’s not
Included: standard build definition, device setup, application installation, data migration, and secure wiping of replaced devices.
Not included unless bundled: designing and running a Microsoft Intune environment (see Microsoft Intune), the devices themselves (see IT Equipment Supply) and software licences.
Typical timelines and what drives cost
A single device takes a few hours by hand, less with automated provisioning. Defining a standard for the first time takes one to two days. Cost is driven by the number of devices, how many different builds are needed, applications to install, the amount of data to migrate and whether devices are set up on site or prepared in advance.
Equipment typically used
Device management tools such as Microsoft Intune and Autopilot where available, deployment and imaging tools where they aren’t, application packaging, drive wiping tools and an asset register.
Common mistakes we see
New laptops handed over at factory settings. Staff given administrator rights for convenience. Encryption without stored recovery keys. Every device built differently. Files left only on the old laptop, which is then given away. And no asset record, so nobody knows who has which device or when its warranty ends.
.CLnYnaU8_1JOeBB.webp)
IT Support & Managed Services
Related services
-
User Technical Support
Direct support for staff on the systems they use daily, not just the infrastructure behind them.
-
IT Infrastructure Maintenance
Ongoing upkeep across network, server and endpoint infrastructure under one maintenance plan.
-
Managed IT Support
An outsourced IT function — helpdesk, monitoring and maintenance — for teams without one in-house.
Insights
Related reading
-
.axBI9cHA_Z1CMqlS.webp)
, 4 min read
Common System Configuration Mistakes Rwandan Businesses Make
A handful of specific mistakes recur in how businesses configure devices — here's what they are and how each one creates avoidable support burden.
-
.DwIvkzVM_17wdD.webp)
, 4 min read
How Much Does System Configuration Cost in Rwanda?
System configuration cost depends on device count, configuration complexity, and whether consistent imaging is used — here's the breakdown.
Frequently asked questions
What does 'configured properly' actually mean for a new laptop?
A current, supported operating system with all updates; disk encryption on; a standard user account rather than everyday administrator rights; security software active; the organisation's applications installed; email, files and printers connected; and the device enrolled in management where you use it. It's handed over working, secured and recorded in your asset list.
Can you set up multiple devices consistently, not just one at a time?
Yes, and that's where a standard matters most. We define the configuration once, then apply it the same way to every device, either automatically through Microsoft Intune and Autopilot or with a documented build process where those aren't available. Consistent devices are faster to support, because a fix that works on one works on all.
How long does configuring a new device typically take?
A single device built by hand usually takes a few hours, including updates and applications. With automated provisioning, most of that happens unattended, and a batch of laptops can be ready in a day. Moving a user's files and settings from an old device adds time, depending on how much data they have.
Does this include data migration from an old device?
Yes. We move the user's files, browser bookmarks and application settings, and make sure email and shared files reconnect. Where possible we move files into OneDrive or a shared location rather than onto the new laptop alone, so they aren't tied to one device again. The old device is then wiped properly before reuse or disposal.
Should staff have administrator rights on their own laptops?
Generally no. Everyday use with administrator rights lets malware install itself with full control, and lets well-meaning staff change settings that break security or support. Staff work as standard users, and software they need is installed centrally or through an approved self-service catalogue, so they aren't blocked from getting work done.
Tired of waiting days for IT help?
Tell us how many users and devices you support. We’ll propose a support plan with response times written in.