Well, in general if Paul Bowden tells me something isn't a good idea (if I can avoid it) with relation to Exchange I tend not to argue the point too heavily if there are other architectural solutions which will acheive the desired objective. If there aren't other solutions to the problem, then I bite the bullet and do what has to be done.
I've installed Exchange on a DC and not. All other things being equal, I much prefer on not. In Exchange 5.5 the directory related operations consumed approximately 20 - 25% of the total resources Exchange was using. All other things being equal, I like to plan for as much growth as reasonably possible on a single Exchange box before adding additional Exchange servers into an environment. If my GC responsibilities are offloaded to another machine, that gives me an additional margin for growth. -----Original Message----- From: Petri To: Exchange Discussions Sent: 11/6/2002 1:56 PM Subject: RE: Exchange 2000 and GC It is great to see the real reasons why I should not do this. I have always got an answer like: "..in my mind its not a good and MS doesn't recommends..". Just a few comments about the list: 1. When you have a real problems they are always quite complexity 2. agree 3. if you create a separate site for these GC, then normal user load doesn't reach these GCs. 4. Only replication. 5. agree 6-7. true ! Do I have saw dreams or is it so that in Titanium there will be somekind small directory ? But many thanks of the list. .-Pepi-. > You also want to consider the more applications/processes you run the > more likely one of them will stop working. This translates into > downtime. If for some reason your GC stops replicating or answering > requests and the normal recovery steps don't work, you may have to > reboot. It is the same for any additional processes you run on any one > machine. > > To summarize: > > Reasons not to have and exchange and a GC on the same machine > > 1. Added troubleshooting complexity > 2. Added DR complexity > 3. Added CPU load > 4. Added network load > 5. Added disk I/O > 6. Added hot-fix and SP complexity (dealing with interactions of > hotfixes) > 7. Domain Controller Security Policy _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:leave-exchange@;ls.swynk.com Exchange List admin: [EMAIL PROTECTED]
