How would you manage PCs across 80 or more branches?

November 18, 2026 5 answers
Asked by _q37!vexnilo.8

Most branch PCs use local accounts, and the network equipment and internet connections vary by location. Head office has Active Directory and a FortiGate firewall. Would domain joining PCs over branch VPNs make sense, or is there a better way to centralize management?

Answers

Bren

First figure out what actually needs traditional AD. Are branch users accessing domain-dependent applications or file shares, or is the main goal consistent sign-in, configuration and support?

If the latter, Entra ID joined PCs managed with Intune are worth pricing out. That avoids making every workstation dependent on a tunnel to head office for routine management. Check application compatibility, Windows editions and licensing before committing, though. Cloud management doesn't remove the need for reliable internet or a consistent network baseline.

Ravlivo.2m:

Compare the ongoing per-user licensing cost with the cost of branch gateways and support. The cheaper option isn't obvious without the user count and existing licenses.

Reply to this answer
_h62!plivexo.9

Central AD with site-to-site VPNs can work if there are real on-premises dependencies. I'd standardize the branch gateways and configurations rather than build 80 different little networks. Dynamic public addresses can work when the branch initiates the tunnel to a reachable head office endpoint, but check the gateway features, ISP restrictions and reconnect behavior in a pilot.

Don't assume the existing head office firewall is sized for the job. Check tunnel capacity, throughput with security inspection enabled, internet bandwidth and redundancy. Also decide which traffic actually needs the tunnel. Sending all branch internet traffic through head office adds demand and makes that site a much bigger failure point.

_c41+lathefox.7:

Dual internet links at critical branches are worth considering if outages have a significant business cost. Test failover rather than assuming a second circuit will make it seamless.

Reply to this answer
Tavrixa-3m

For an AD design, plan the outage behavior before deciding where the domain controllers go. A previously signed-in user may be able to use cached credentials on a domain-joined PC, but a new user or a password change can create trouble without a reachable controller. Central file shares won't be available over a failed connection either.

Keep at least more than one domain controller for resilience and configure AD Sites and Services around the actual subnets. A local controller at a larger branch may help with authentication and DNS during a WAN outage, but it adds a server to secure, monitor and maintain. A read-only domain controller may be worth evaluating where physical security is a concern. Test DNS, sign-in, policy processing and application access with the link deliberately disconnected.

Reply to this answer
7t!drimvori_381

I'd start with an inventory and a few standards, not a purchase order for 80 firewalls. Document the users, PCs, applications, local accounts, connectivity and existing equipment at each site. Talk to whoever maintains the current setup and find out why the branches differ.

Then pick a small pilot with a mix of reliable and awkward connections. Agree on ownership, support capacity and a rollout budget before expanding. A project this size needs more than a domain join script.

Reply to this answer
6w+tinbadger_352

Profile migration deserves its own pilot. Joining a PC to a domain or Entra ID doesn't automatically turn the existing local profile into the new user's profile. Inventory local data and application settings, back them up, and test a supported migration method on representative PCs.

Have a rollback plan and a way to access the machine if the new sign-in fails. Check files, browser data, printers and application access with the user before removing the old account or profile.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions