jassyca
Posts: 225
Joined: 20.Jul.2006
Status: offline
|
In case you need specifics to convince management (ie, about Exchange on a domain controller).. If your company intends to use Outlook Web Access, that means that the outside world will have web access to your domain controller. Thus, if that web server is hacked, that means your domain controller was also hacked. If that doesn't send shivers down their spines, nothing will. (If you intend to use Outlook Web Access, whether your Exchange server is on a domain controller or not, do a search on Microsoft's site for "IIS Lockdown" utility and the URL scanner. That will at least protect your server from the inexperienced skript kiddies out there.) Exchange also tends to be something of a pig on your server. It loves it some resources, mm, baby! If you ever need to reboot your Exchange server, that means that you're also rebooting your domain controller thus people could have problems logging on or accessing network resources during that reboot. It also means if your Exchange server gets really busy (like, someone emails a newsletter to a ton of people), authenticating users to the domain comes in a poor second. Next, Microsoft doesn't admitt it but Exchange 2000 does have problems with memory leaks (do a search on this forum about it and see how many hits you get!) Enough that you probably want to seriously consider scheduling a regular reboot. I reboot our server once a week. That's probably overkill. On the other hand, my husband is also a Windows administrator. Their Exchange server resides on a domain controller. He can tell when the server needs to be rebooted because after he creates a new user, the user won't appear in the address book no matter how many hours you wait. Reboot, and, poof, the user's name suddenly appears in the address book. But, until then, everyone thinks you aren't doing your job getting the new guy set up because his name isn't in the address book. (You, slacker, you. ) Alright, now let's talk about that missing Exchange server. First, I'd like to know what role it used to play in your domain. Was it the only Exchange server? Was it also a domain controller? If you're not sure, go to one of your current domain controllers, logon as a domain administrator and open "Active Directory Sites and Services". Open "Sites" and there will be at least three sub-trees under there. One of them does NOT look like a folder icon and the "type" will be "site". On our domain, that one is called "Admin" but yours might be called something else. Open that and you'll see a folder called "Servers". Open "Servers". Expand every server that you see listed. Do you see the missing Exchange server? What do you see listed under it? Let us know what you see.
|