SME offices, practices and consulting teams · Remote support or on-site visit depending on the blocker · Workstations, Microsoft 365, network and printers
A single locked account or an unresponsive shared drive can stop an entire Lausanne office mid-morning. Most of these blockers get fixed remotely within the hour; a technician only travels out when a router, a cable or a physical device turns out to be the real culprit, and every ticket ends with a short note on what actually happened.
In Lausanne, most support requests come from small and mid-size offices: a consulting firm, an accounting practice, an agency or a service SME running on a shared network and Microsoft 365. A single blocked mailbox, a locked shared drive or a printer that stops responding can slow down a whole floor, so triage starts by measuring how many people are actually affected.
The stack is usually familiar: Windows or Mac laptops, Microsoft 365 for mail and files, a local Wi-Fi network, a shared printer and sometimes a VPN back to a head office. Diagnosis checks accounts, licences, permissions and network configuration remotely first, since most of these issues never require touching a physical device.
On-site visits are reserved for what remote access genuinely cannot fix: a router, a switch, cabling, a printer that needs a hands-on look, or a workstation with a hardware fault. Once the fix is confirmed, a short report explains the likely cause and what, if anything, is worth watching next.
Proof is not a fast-response slogan. It comes from a fix that was verified with the actual user, a cause that got documented instead of guessed at, and a report the office manager can read without needing a technical background.
A password reset that did not sync everywhere can lock a mailbox on one device while it works fine on another. The fix checks cached credentials, multi-factor authentication and connected devices, then walks the user through a clean re-authentication instead of guessing at a reset.
A stuck print queue often traces back to a corrupted job, a driver mismatch after an update, or a printer that silently dropped off the network. The fix clears the queue safely, checks the driver on affected machines, and confirms the printer answers again before closing the ticket.
A recurring, time-based drop usually points to interference, an overloaded access point or a scheduled task on the router rather than a random fault. Logs and signal checks narrow down the cause before any equipment is touched or replaced.
Permission changes made for one project can accidentally cascade to another team's folder. The fix reviews recent permission changes, restores the correct access level, and confirms with the affected team that the drive behaves as expected again.
The number of people affected, the shared resource involved and any recent change are confirmed before a fix is attempted, to avoid guessing at the wrong cause.
Closing the ticket depends on the affected person confirming the fix works, not just on a technical check that looks correct.
The report states the likely cause, what was changed and whether a follow-up review is genuinely worth scheduling for the office.
Office downtime works better when the impact is scoped before any action: who is blocked, which shared resource is involved, and whether hardware is genuinely at fault. This method keeps most fixes remote and confirms them before closing.
04 steps
One person or the whole office: urgency is set by how many people are actually blocked and what work depends on the affected account, drive or device.
Accounts, Microsoft 365, permissions, VPN and configuration checks happen remotely first, since most Lausanne office incidents never require touching a physical device.
A technician visits the office only when a router, switch, printer or workstation genuinely needs to be checked, reset or replaced in person.
The fix is retested with the affected user before closing, and a short report explains the likely cause and anything worth watching.
The scope covers four incident families common to Lausanne offices: workstation and account issues, network and printer troubleshooting, shared drives and backups, and follow-up when the same problem recurs. Each request is triaged by how many people are affected.
A slow Windows laptop, a macOS session that won't sync, a locked Microsoft 365 account or a licence that stopped working are the most common blockers in a Lausanne office. Diagnosis checks the account, the device and the affected app in that order, so the fix targets the real cause instead of a symptom.
Shared mailboxes, OneDrive syncing, Teams access and multi-factor authentication are part of day-to-day support, not an afterthought. Once corrected, the fix is documented so the office manager or the team lead knows what changed and what to watch if the same issue starts to repeat.
An office Wi-Fi that keeps dropping, a printer that refuses new jobs or a VPN that won't connect can stop several people working at once, and the cause is not always obvious from the symptom alone. The fix starts by isolating whether the source is the device, the router, the printer itself or the internet line.
Most connectivity issues in a Lausanne office get resolved through a remote configuration check. A technician goes on site only when a router, switch, access point or printer needs to be physically inspected, reset or replaced, and that step is always explained before it is scheduled.
A shared drive that suddenly denies access, a file that seems to have vanished from OneDrive, or an uncertain backup are recurring issues for office teams that rely on cloud storage day to day. Before touching anything, available versions, permissions and sync status are checked to avoid making the problem worse.
Recovery only closes once the person who reported the issue confirms the file or the share is back to normal. The follow-up note lists what was restored, what stayed uncertain, and whether a backup review is worth scheduling for the team.
When the same printer jam, the same Wi-Fi drop or the same account lockout comes back every few weeks, a one-off fix stops being enough. Follow-up reviews the office network, shared accounts, backup health and ageing hardware to reduce how often the team gets interrupted.
This is only proposed when it makes sense for the size of the office: a short list of priorities, a note on what a provider should coordinate, and documentation the next person can actually use, without pushing a maintenance contract that does not match how the team works.
The goal is restoring the team's work first, then documenting the cause clearly enough that recurring issues get noticed and addressed.
Since most office blockers are account, permission or configuration issues, a remote session usually restores access without waiting for a technician to travel across Lausanne.
Mailboxes, OneDrive, Teams, shared drives and licences are treated as core scope, not an add-on, because that is what most Lausanne office incidents involve.
Every fix closes with a short, readable note on the cause and the fix, so recurring issues get spotted instead of quietly repeating.
The answers cover what is handled remotely, when an on-site visit becomes necessary, how Microsoft 365 issues are treated, and what information speeds up a fix.
Yes. Mailboxes, OneDrive, Teams, shared calendars, licences and multi-factor authentication are part of standard scope for Lausanne offices.
No. Most account, permission and configuration issues are fixed remotely. A visit is scheduled only when hardware, cabling or an access point genuinely needs a physical check.
Yes. Print queue, driver and configuration issues are checked remotely first; an on-site visit follows only if the printer itself needs to be inspected or replaced.
Scope is confirmed first: whether it is one account, a shared resource or the network itself, since that changes both the priority and the fix.
Yes, once available versions, permissions and sync status are checked. Data protection comes before any recovery attempt.
Yes, but only proposed when it makes sense: follow-up is sized to a small or mid-size office, not sold as a default add-on.
Yes. VPN configuration, login issues and access to shared resources for remote staff are covered as part of standard support.
Yes. Impact is scoped first — how many people are blocked and which shared resource is affected — then a remote fix is attempted immediately, with an on-site visit scheduled only if the office itself needs a technician present.
Yes. Every ticket closes with a short note on the likely cause, what was changed, and whether anything is worth watching next.
Support in Lausanne, Renens, Pully, Prilly and Épalinges, with IT requests in nearby municipalities coordinated as needed.
Share what is blocked, how many people are affected, any error message and whether the issue touches a workstation, Microsoft 365, the network or a shared drive, so the fix can start on the right channel straight away.
