Discussion on:
View:
Show:
This was informational! I have always wondered why these tasks are almost always overlooked by some people......then when their server is attacked, hacked, or disabled through a virus, or DDoS, they complain about Windows security not being up to snuff. LoL! I may not have used Windows server products in over 10 years, (Ubuntu Server, and a few Linux clients / laptops!) But it seems that Microsoft has finally gotten closer to making the "perfect server OS"
On my network, we have a network firewall (Sonicwall) and we have Windows Firewall enabled on our servers.
Is there an advantage to disabling host-based firewalls?
Is there an advantage to disabling host-based firewalls?
As you grow the number of servers that need to talk to one another, the host-based firewall configuration tasks start to become a bit more unwieldy. Of course, whether or not the host firewall is used is specific to individual organizations. I've seen some that use them and some that don't.
Example: When deploying System Center, I generally recommend that admins deploy all of the System Center servers behind a single firewall and to not run a firewall on each of the servers. There are simply too many ports to keep track of for smaller shops and that front end firewall is often a "good enough" solution.
Scott
Example: When deploying System Center, I generally recommend that admins deploy all of the System Center servers behind a single firewall and to not run a firewall on each of the servers. There are simply too many ports to keep track of for smaller shops and that front end firewall is often a "good enough" solution.
Scott
Most of us "assume" that everyone knows things - when quite the opposite is true. Operating systems change as does all software, and articles such as this are irreplaceable for their nuggets of knowledge. Thanks Scott for taking the time, always appreciate reading from someone who has "been there". Time saving for any harried Net Admin who has yet to set up a Server 2012 - especially as there is very little literature (as of this date) actually available.
For an extra boost of speed, almost all these things, and much more, can be automated using Windows Deployment Services (WDS) for installing new systems. WDS can perform the entire setup and automatically join the new system to the domain without lifting a finger, other than making sure PXEBoot is first in the boot order. The domain policy can then set most everything else up, from the firewall policy, to Windows Update settings, on down to the automated installation of malware/virus software.
Let me add my thanks for this summary, Scott. From someone who found the massive UI changes from server 2008 to 2012 a bit frustrating to find stuff - I mean, when one has to google how to shutdown/restart the darn server because of the "disappearance" of the start button - and no I haven't worked with any Windows 8 clients yet - I am always in awe of the team at Microsoft whose job is must be to figure out how to move stuff around between major o/s versions in the most inscrutable way... (And can someone explain to me why, after it taking awhile even to find the "search box", typing 'windows update' into it doesn't return any results???) Anyway, I guess I'm getting used to it now. Thanks again Scott!!!
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
