Skip to content
What we do 01
Service Plans 02 Compliance 03 See it in action 04 About us 05 Our story 06 Clients 07 Accreditations 08 Insights 09 Contact 10 Free IT Audit & Health Check TeamViewer QuickSupport TeamViewer full client
Ballito +27 32 586 0815
info@lantekcomputers.com
Skip to content

3 September 2026LANTEK Computers

A business with people in Sandton and people in KwaZulu-Natal has a specific version of a common problem. Not distance, which mostly does not matter any more. The problem is that arrangements tend to grow up separately in each office, and then diverge until they are two businesses sharing a name.

The symptoms are recognisable. Files exist in two places and nobody is sure which is current. One office has a server and the other does not. Each has its own way of doing something. And there is one person in one of the offices who understands how it all fits together, which means the other office is waiting on them.

What should be central, without exception

These are the things that should exist once and be reached from anywhere, because having two of them is what causes the divergence.

Identity. One set of accounts, one place people sign in, one place access is granted and removed. Two separate account systems means somebody leaving is closed in one office and still working in the other, which is both a security and a licence problem.

Files. One store, reached from both offices. The single most common source of trouble in a split business is two copies of the shared drive and no clarity about which is authoritative. Somebody eventually works a day on the wrong version.

Mail. Already central for most businesses, and it should stay that way rather than being split by domain or by office.

Telephones. If the phone system belongs to the person rather than the desk, then an extension works in either office and calls route by role rather than by building. This is the change that makes two offices feel like one, and it removes the arrangement where each office has its own PABX and neither can transfer to the other. Teams Phone instead of a PABX covers what that involves.

Backup and monitoring. One view of both sites. Two separate arrangements means two things to verify and one of them will be the one nobody checks.

Documentation and the asset register. One list covering both sites, so somebody can answer what is in the other office without telephoning it.

What genuinely has to be local

A shorter list than people assume, and it is worth being strict about it, because anything unnecessarily local becomes a divergence later.

The network in the building. Switches, wireless, cabling, and the internet connection. Each site needs its own and each needs to be properly specified rather than accumulated.

Somebody who can be there. For hardware failures and for the days nothing works. This is the real question in a split arrangement and it is dealt with below.

Printing and scanning. Local devices, though the configuration should be managed centrally.

Anything attached to physical equipment. Access control, cameras, a machine on a floor.

The question that actually decides this

Not where the servers are. Who is on site when something needs hands.

Remote support handles the great majority of problems from anywhere, and a provider in one province manages an estate in another without difficulty. What remote support cannot do is replace a failed switch, or help at all when the internet at that site is down, which is precisely when help is needed most.

So the arrangement has to answer: for each office, who attends, how quickly, and what does that cost. Three workable models:

One provider with people in both provinces. Cleanest, because there is one party accountable for the whole estate and no gap to fall into.

One provider centrally, with a local contractor for hands. Works, provided the contractor takes instruction from the provider rather than from the office, and provided the provider still owns the outcome. It fails when the local office starts telephoning the contractor directly, because then changes happen that the provider does not know about.

Separate providers per office. The arrangement to avoid. It produces exactly the divergence described at the top, and when something spans both sites, each party can reasonably say it is the other’s.

If you have two providers today, that is the thing to resolve first, ahead of any technical change.

What tends to go wrong specifically

One office is treated as the head office and the other as a branch. Usually reflecting where the directors sit rather than where the work is. The branch waits longer, gets older equipment and is consulted last, and the resentment shows up as people building their own arrangements.

Changes are made in one office and not the other. A setting adjusted in Sandton and not in KwaZulu-Natal, and six months later nobody can explain why the two behave differently.

Onboarding differs. A new starter in one office gets a working setup on day one and in the other they get whatever machine was free.

Nobody owns the connection between them. If the offices need to reach each other’s systems, somebody has to be responsible for that path. Frequently nobody is.

What to do first if this is you

In this order.

One, establish whether identity is genuinely central, and if not, make it so. Everything else is easier afterwards. Two, find out how many copies of the shared files exist and decide which is authoritative. Three, get one asset register covering both sites. Four, resolve who attends each office and make one party accountable for both.

None of those is a large project and together they remove most of the friction.

The upside people miss

A split business has a continuity advantage a single-site business does not, and almost nobody uses it deliberately.

If identity and files are central and both offices can work independently, then one office losing power, connectivity or access to the building does not stop the business. The other carries on. That is genuinely valuable in South Africa, and it costs nothing extra once the centralisation above is done. It is worth stating as a benefit rather than leaving it as an accident.

What we cover from Gauteng is on IT support in Sandton, and from KwaZulu-Natal on IT support in Ballito. If you are running two offices and it has started to feel like two businesses, describe the setup to us or email info@lantekcomputers.com, and we will tell you which of the four items above would make the most difference.