This chapter teaches you how to set up a Windows-based network around a single support server used for updates, patches, tools, installation bits, and DHCP services.
A Highly Available Windows Server Architecture
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
“single support server” is mutually exclusive with “Highly Available”, or am I missing something?
I guess “Windows” too is mutually exclusive with “High Availability”
Why not a linux/bsd box with Samba ?
Because this is an article on Windows Server, not Linux/BSD.
Despite what many trolls here think, in the real world Windows is very prevelant in both the data center and enterprise.
I already knew how this is done, but still a pretty good article nonetheless.
If windows was high availbility software, then why did LAX crash because somebody forgot the weekly reboot of the server?
If it was the third party program why did Windows have to be restarted instead of just a timed restart of the program. It is a lot faster to restart a program than an OS. A program crashing shouldn’t take out the OS. If it was the OS that needed the reboot because poor memory management then it isn’t ready for the data center now is it. Every other enterprise ready OS can deal with a program that misbehaves except for Windows.
Note I do own & use Windows computers. I have run win2k Pro, I have also seen win2k pro eat my network card drivers because it was bored. Yes they were the default drivers that come with Win2K as well. I also have spent days trying to get sound working under Linux. Both are why I now own a Powerbook.
A Highly Available Windows Server Architecture, how desperate!
Like the ugly kid at the school dance, who is “highly available” to anyone. Or the crap free software quarter-back yelling “I’m open! I’m open!” to a team that ignores him.
Pah!
Pfft pfft ooooh!