Comments on: Problems with microsoft exchange server http://itknowledgeexchange.techtarget.com/itanswers/problems-with-microsoft-exchange-server/ Sat, 25 May 2013 05:16:43 +0000 hourly 1 By: petroleumman http://itknowledgeexchange.techtarget.com/itanswers/problems-with-microsoft-exchange-server/#comment-41980 petroleumman Tue, 12 Jul 2005 08:29:52 +0000 #comment-41980 Hello,

Two words of advice with your situation, before you perform an upgrade of your Exchange 2000 server, get it working correctly on a Server 2000 platform first! Performing an upgrade on a broken Exchange application can only compound your problems. Once you have cleanly installed and configured your Exchange 2000 server, an upgrade of both the OS and Exchange to 2003 platform would be a bennificial move to make, considering you have the budget to do so.

Second, if you are running Exchange on a DC, DON’T! Place your Exchange server on a dedicated box if at all possible. Running Exchange 2000 or 2003 for that matter opens the door to all kinds of AD related quirks, besides the performance hit your going to take running on a DC.

Good Luck!

]]> By: rloveall http://itknowledgeexchange.techtarget.com/itanswers/problems-with-microsoft-exchange-server/#comment-41981 rloveall Tue, 12 Jul 2005 07:37:39 +0000 #comment-41981 I’m sorry to say that ebellardino is absolutely correct. I loaded Exchange 2000 on a Windows 2003 server and was unable to send mail to my other Exchange 2000 box even though I could send and receive mail to the Exchange 2000/Windows 2000 server to/from outside. I did an inplace upgrade of the Exchange 2000 to Exchange 2003 and “presto” everything started working.
Microsoft does give you an incompatibility warning when installing Exchange 2000 on a Windows 2003 server but who reads those things anyway? :-)

]]> By: paulieeddie http://itknowledgeexchange.techtarget.com/itanswers/problems-with-microsoft-exchange-server/#comment-41982 paulieeddie Mon, 11 Jul 2005 11:42:46 +0000 #comment-41982 Applying the latest service pack helps a great deal, but does not correct everything. Upgrading to Exchange 2003 would be the best choice. In the mean time, apply the most recent service packs to Exchange 2000.

]]>