Frequently asked questions

Yes. Many services are available per device or per hour, without long contracts.

Yes. We start with a health check, then take it over.

Remote support works anywhere; on-site work outside cities is scheduled as a visit.

You do. We hand over everything, and keep it current while we support you.

Each wave has a planned window agreed with you and a tested way back; most services move with a short cut-over.

We wipe it to a recognised standard or destroy the drives, give you certificates, and recycle through authorised e-waste handlers.

It depends on the estate; fewer servers and rooms usually cut power, space, licences and support. The discovery report gives your figure before you commit.

They are the lines we support in depth; ask about others.

Yes, after a health check.

We compare both over three years for your workloads; steady workloads are often cheaper on your own hardware.

Yes, in phases with temporary power and cooling where needed.

Yes, under an AMC.

A small room is usually a few weeks from survey to handover; we work in phases so systems stay up.

It depends on your size, features used and skills; we compare costs and risks before recommending anything.

Yes: a pilot with a few non-critical machines comes before any wave.

It depends on your licences, size and skills; Hyper-V suits estates already licensed for Windows Server Datacenter, Proxmox is cost-effective for many others.

Yes: a health check first, then a staged clean-up with rollback.

Yes, role by role, with no big-bang cut-over.

For most organisations a few days, ending with a report ranked by risk.

For many on-premises estates, yes; co-management with Intune lets you move gradually to the cloud.

Yes: alert tuning removes noise so real problems stand out.

Yes, under a managed service, including upgrades to new releases.

Yes, when it's patched, backed up and monitored like any other system; that is what we do.

Yes, with response times in your contract.

No: we provide the support, with response times in your contract, and use vendor subscriptions where they're worth it.

We restore them on a schedule and report the result.

Often, yes: most slowness is in a few queries or missing indexes.

Yes, after a health check of its configuration, backups and security.

A site survey shows coverage gaps and interference before anything is bought.

If you have several branches or depend on cloud apps, it usually pays for itself in uptime and simpler links.

Usually yes; the survey tells us what to keep, reconfigure or replace.

A private VPN keeps your traffic, keys and logs under your control and lets you decide exactly who reaches what.

Their key is revoked in minutes, and access stops everywhere.

With split tunnelling only work traffic uses the VPN, so everyday browsing is unaffected.

Yes: we find unused and overlapping rules and remove them in stages, with your approval.

We start in monitor mode, tune the rules, then switch to blocking.

Yes, after a review of its rules and firmware.

Usually the reverse: blocked ads and trackers never load.

Add it to the allow list from the dashboard, or ask us.

No: it's an extra layer that stops many threats before they load; keep endpoint protection too.

MFA everywhere, patching, backups you've tested, and an access review. We can do all four in weeks.

Yes: we prepare the evidence and fix the gaps found.

No: certification is done by an accredited body; we help you get ready and fix the gaps.

Only if the copies are offsite, can't be changed by ransomware, and have been restored successfully recently.

At least yearly for the full plan, and monthly for sample restores.

It depends on how fast you need to recover; cloud-based DR often costs far less than a second site.

No. Steady workloads are often cheaper on premises; we compare over three years before recommending.

Yes, with shared policies and monitoring so it doesn't double the work.

The one that fits your applications, skills and data-location needs; we compare them for your case.

Small estates take weeks; large ones run in monthly waves. The discovery step gives a firm plan.

Every wave has a tested rollback until you sign it off.

Most moves happen in planned windows outside working hours, with a short cut-over.

Not always. For a few services, plain containers are simpler; we'll say so.

Yes, with upgrades, monitoring and on-call support.

Rarely: most applications run in containers with small changes to configuration.

Write one environment as code, then repeat it.

No: every change is reviewed and approved before it runs.

Usually within weeks: the first automated pipeline removes most manual deployment steps.

It depends on the estate; the first review shows the figure before you commit.

No: we size from real usage and keep headroom.

As a fixed-price review, or as part of a managed service.

No: changes follow a process you approve, and you keep all passwords and documents.

Yes, for example only servers, or only one site.

Usually monthly, by servers, devices or users.

A monitoring platform run by ServerWorks vendors' own management tools.

No: we tune thresholds and only tell you what needs your attention.

Yes, read-only monitoring access, plus admin access you approve for fixes, all logged.

Yes, where parts are available; we also help plan its replacement.

Yes, per call at time-and-materials rates.

Targets by priority and city are agreed in the contract.

The equipment listed in the contract, the visits per year, and repairs; parts are included or charged as agreed.

Yes, under FMS, for business hours or in shifts.

Often yes: one avoided outage usually costs more than a year's AMC.

Usually per user or per device per month.

Yes: accounts, device, email and access ready on day one.

Business hours as standard, extended or 24×7 by contract.

Yes: mail, calendars and contacts are copied before the switch, and the cut-over happens out of hours.

Yes: retention isn't the same as a backup you control.

Both work well; the choice depends on the tools your team uses daily. We'll recommend for your case.

Usually missing SPF, DKIM or DMARC records; we check and fix them.

Yes, with no downtime for visitors.

Yes, after a quick review of its technology and security.

By certified wiping software or physical destruction, with a certificate per device.

Yes, alongside hardware warranties.

Where it has resale value we can arrange it, after certified data wiping.

Typical lead time.

Yes / process.

Yes, start with a short engagement and extend it.

You do, as set out in the contract.

Yes, after a code and hosting review.

A first usable version often takes a few weeks; we agree the scope and dates before starting.

Often yes; we'll recommend native only where it matters.

Yes, under your developer accounts.

If people use it daily or offline, an app; otherwise a mobile-friendly web app is often enough.

Messages wait and retry; nothing is lost, and we're alerted.

Often, through files, databases or a small adapter.

Yes: integrations are monitored and fixed when a connected system changes.

We choose services and settings where it doesn't, or run models privately.

We test it on your real cases before launch and keep measuring.

Running costs depend on usage and the model chosen; we estimate them in the use-case report.

n8n when data must stay on your servers or volumes are high; Make for quick cloud workflows. We'll recommend per case.

It retries, then alerts us, and we fix it.

Yes: we can train them and keep the important ones under review.

Yes: a pilot with a few devices proves the value before rollout.

You do; it can stay on your own servers.

A few sensors on one machine or room for some weeks, enough to prove the value before rollout.

Agreeing definitions is the first step of every project.

Not always; small estates can report straight from a copy of the data.

Yes, on a schedule you choose, from hourly to daily.

Typical duration for a small company.

No. The report is yours to act on with anyone.

Usually monthly, plus board or leadership reviews each quarter.

No: sometimes the best fix is a simpler process, not software.

We agree the measure (hours saved, errors, turnaround) before starting.

One process usually takes a few days of workshops and analysis.

We prepare people for exams; official certification courses are run only where we're authorised.

Yes, in a safe copy or a lab built to match.

Yes, live online or on site; labs work either way.