Exchange 2000 Server Help

How to join two or more exchange servers over a vpn tunnel and route the users mail to the correct server.

i have a client that has 3 offices and they are connected through a VPN tunnel. All the mail is routed into the mail server we will call this server1. From server 1, we have two other offices. Each has an exchange server. The users in the remote office are currently connecting to the email server over the VPN and the responce times are SLOOOOOWWW. we want to route the mail to the server 1, and then from there, route the mail to the server 2 or server 3 depending on which office the user resides. we have already created all the mailboxes on server 1 and so we will need to move the mailboxes once the routing is set up. Here is the steps we used to set up the servers and route the mail.

It happens to everyone at least once. Your exchange server fills up and the database is too large to mount anymore. What can you do?!? Well the answer is to move the exchange database and transaction logs to a new partition on the server to free up some space. If you don't have another partition, GET ONE and then follow these directions.

1) To move the transaction logs first unmount the exchange stores if they are not already.

Next, right click on the first storage group and click properties. On the general tab, change the TRANSACTION LOG LOCATION by clicking browse and point it to a new BLANK FILE ON THE NEW PARTITION.

In this article I give you the method I use to backup exchange database using a backup script and windows scheduler.

1) Locate the exchange database

This would normally be located at c:\program files\exchsrvr\mdbdata

2) Create a path to backup to.

mkdir c:\backup

3) Create a new notepad document and paste the following code into it.

------------------------------------------------------
net stop msexchangeis

xcopy "c:\program files\exchsrvr\mdbdata" "c:\backup" /e /c /y /d

net start msexchangeis

pause
-------------------------------------------------------

name this file backup.bat

In this Article, I will discuss how to move your Microsoft exchange store off that ugly windows 2003 small business server onto the more robust windows 2000 server / exchange 2000 server. This article assumes that you have already installed windows 2000 server, applied all the updates, have a copy of the old 2003 small business server data handy with all the files intact or in a backup some where. This is a real life scenario as I’m writing this as I’m doing it. I have a company that had a small business 2003 server with exchange and I’m _upgrading_ to windows 2000 server with a separate exchange server 2000 box. This is done to spit up the tasks the server must perform. The first server becomes the file server and the second becomes the exchange server. This has the added benefit of having a backup DNS server and a backup Domain controller should anything happen. Also, if anything were to go wrong with one of their servers, the other one will be unaffected. The users would only lose access to 50% of their functionality instead of 100% loss when your one small business server goes down. Yes I know I could have gone with the 2003 server and 2003 exchange server but I already know this works and have had some quirky problems with the 2003 setup. As of the writing of this article, I don’t consider 2003 server to be stable enough to warrant its use. But then again maybe I’m just being stubborn. Anyway this was written for anyone that wants to accomplish what I’m about to do now. That is to take a small business 2003 server and break it up into two windows 2000 servers, one being the file server and the other being the exchange server. Ok now here we go...