Servetome local server not found software#

If the users won't be able to do anything if that network connection is down, then why add the additional headache of physical servers at each site? Every application we have is hosted either online or in our data center if a remote site loses it's connectivity, there's no point in the users being able to sign in (since we run Virtual Desktop, they wouldn't even be able to do that, but I've been in your world with clients logging directly into workstations on site as well). I'd echo what mpk said early on, and seems re-inforced by your statements-this all depends on what your applications really expect. Doesn't need to be anything fancy just enough bandwidth to keep thing going if something happens. Someone also mentioned redundant internet links which wouldn't be a bad idea even with site DCs. 500 devices trying to download something like Microsoft office from a single location all at once is a big choke point. Especially at wherever you host your primary DCs and storage. Having site level DCs Greatly improves performance and reliability and keeps you from eating up the bandwidth on your links.

You could set things up with just VPN links and no site DCs but I wouldn't recommend it. Or use azure or AWS if you want to simplify infrastructure and pair down on what you have to manage. Setup primary and secondary DCs and storage at your main location (which I'm assuming is where your office is).

Servetome local server not found software#

Setup DFS to replicate software packages to each site so that the workstations don't eat up bandwidth when you push out software. Definitely put a read-only DC at each location.