I'll just throw this out there: I was tasked with the same requirement of backing up people's desktops 6-7 years ago and the solution that I went with was some home-grown Powershell scripts and using the built-in VSS service on the workstations.
I grab the bare necessary files to rebuild a workstation and then dump the backups to the user's home directory on the server (which is then automatically backed up). Take a look at the scripts I wrote
Here's the rub -- if the company owns significant address space, they're likely using it for their internal systems as well, not external access only.
I worked at Eastman Kodak for a number of years (who, at least at one point, owned a significant amount of public IP space) and we used public IPs for all of our internal systems as well, no NAT'ing private address ranges.
I'd recommend you look at something like the Meraki MX64/MX64W at all three locations, it will do all of the necessary tunneling and filtering you need (with the advanced security license), as well as allow you to monitor what is happening on the network.
Additionally, it's all cloud managed so you can view and configure the device from anywhere.
I deploy these at work for our remote offices, and just purchased a similar setup at home (an MX64 and two MR18). I can filter what my kids get to as well as easily support remote backups and administration at my parents home.
It took 70 years for voyager to reach the heliopause
Um, actually the Voyager probes were launched in the late 70s, so it's been less than 40 years.
A return trip would certainly take a while longer due to slowing down, sample gathering, and then managing to accelerate back home. But this wouldn't be the first time that projects have begun that are longer than a typical human lifespan.
This doesn't have anything to do with a kernel fork; indeed, in the Windows world you're using the same kernel and drivers regardless of workstation, server, etc.
This has more to do with the support systems in place, eg, using standard init scripts, leaving logs in text format, etc.
I saw the announcement yesterday afternoon, and found it listed already in my available games (since I had previously purchased it for Windows, under WINE).
It works wonderfully under Linux: it's faster, uses less resources, and doesn't crash nearly as often as it did under WINE.
I'm extremely happy, as this was one of the few reasons I still have a WINE install in place.
I used to prefer spicier, but age has not been kind and now I can't handle more than a half-dozen jalepeno slices without paying for it later.
That said, I'd prefer flavor over heat.
Long time or not, this is a good thing for Microsoft to do, as well as for the community in general.
Unfortunately, however, it's under a non-commercial license, so any FreeDOS developers still need to avoid contact with it to avoid any IP complaints.
I did what you suggested, spent about 10 minutes looking around.
Yes, there are buildings, and yes there are cars. But, I saw hardly any cars (mainly buses, and only a handful of those), and I also didn't see any parking lots. So, either I completely missed it, or you're seeing something I'm not.
Just for kicks, I looked up a list of the world's poorest countries, and picked #1, Congo. While I don't see as many industrial/high-rise buildings in the cities (definitely many more individual homes) I see more cars and other signs of human travel and habitation.
is asinine. It's not difficult to put a noscript tag with a reasonable explanation for clients. All production sites should have graceful fall-back for accessibility and other client issues anyway.
It is difficult to soar with the eagles when you work with turkeys.