Exchange servers integration
Microsoft has a line of products that support their active directory structure that they stole from Novell. One of these offerings is the exchange server. This server has been around for many years and has morphed into what it is today. Any mail administer will usually handle it’s main mail gateway using sendmail – or other Unix or Linux flavor to handle the routing. Then for internal mail – the gateway passes back to the exchange server. This leaves most of the routing controls unnecessary. For those who do not have an it administrator that can handle the Linux deployment. They opt for SaS (Software as a Service) or hardware made and managed by a 3rd party.
Exchange Server the Online Server
The exchange server comes in modules. Now you are no longer required to punch a hole in the firewall to accommodate your mail server. You will be required to buy another license if you wish to run a separate server from your mail server. However, Microsoft was nice enough to include the module with the exchange server. Why hassle? Unless you don’t really know Linux or Unix and free opensrouce I guess you should buy into it.
Windows 2008 AD with Mail Included
In my humble opinion, they should get rid of the almighty exchange server and intergrade the calendar services into active directory. Currently –it’s purchased separately from Windows 2008 server, and it will require it’s own Windows 2008 Server license to run it. From my experience with Exchange Server, it’s way more complex then it needs to be. The incorporation of a command line to satisfy the hard core of us systems administrators didn’t booed well.
Windows 2008 Server in your DMZ
I generally don’t like to put windows in the DMZ. But when I do – I do not attach it to the internal domain – and if I need AD like security on multiple boxes in the DMZ I will ad it’s own active directory domain. The reason for a DMZ is to spate your internal network from the public facing Internet. Windows will leave ports open by default – without you knowing. Netstat from the command line will show you open ports. Linux is not like that. If you do not run a service – the port will not open. Many services run on windows by default. Many documents about how to “harden” windows I’ve read and been forced to follow. Simple fact its– if it’s public facing – I prefer not to use windows server.
