• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 220
  • Last Modified:

Need to break up our exchange users.

I am currently running Exchange 2000 on Windows Advanced Server 2000 with AD 2000.  

Our execs are very quickly filling up the message stores and slowing the entire companies email down.  Particularly when they do a search through their gigs of email.

I would very much like to move the execs off to their own machine so that they can only effect them selves.  What is the best way to do this and still allow everyone the ability to share calenders and what not.

  • 3
1 Solution
Running a second exchange server is something which is very easy to do. Basically, you get the new server and set it up as a member of your existing organization. (You'll probably need to go to 2003 Standard or Enterprise, depending on your needs)
Get the new server fully patched from Windows Update or your WSUS server.

Once the server is a member of the organization you can transfer the mailboxes you want to onto the new server, there's tools built-in to AD to do that.

I would also recommend that you get a third server installed in the organization called a front-end exchange server. That server doesn't store any mailboxes but is instead used as a gateway and relay server to the other mailbox servers (the backend servers). You would configure your front-end as the server which receives the mail (the MX record). The server receives all the mail and then passes it onto either of the two mailbox servers depending on which person's mailbox it is intended for. Also, when using OWA, user's connect to the front-end and then it passes queries to either of the backend servers, no need to give out two different addresses.

Since the servers are members of the same Exchange organization you don't lose any of the exchange functionality like sharing calendars etc. All users are still listed in the GAL.

If your execs have several gigs of mail then I would consider getting the second server as Exchange 2003 Enterprise, it is more lenient on the maximum sizes of mailboxes etc.
Here's a step-by-step guide to what you'd have to do:

Second mailbox server
1. Install the hardware and setup Windows 2003 server on the new machine.
2. Make the server a member of your existing domain.
3. Install Exchange as usual; follow the setup procedure and make it a member of the existing domain.
4. Upgrade the Exchange 2003 installation to service pack 2.
5. Move the mailboxes across (do a test one first to make sure it all works)
Here's a guide to moving mailboxes: http://www.msexchange.org/tutorials/Exchange_2003_Move_Mailbox_Wizard.html

As above except you don't do step 5. Instead:
5. Configure as front-end server. (In ESM you right-click the server, properties, check "This server is a frontend server"
6. Change your port forwarding to go to the new server's address on port 25. Change MX record if necessary so mail goes to new server.
7. Setup outgoing mail, by DNS or smart host.

That should get you running. You don't HAVE to have a front end (it will work with mail arriving at one and it will move it across to the other one if necessary) but things could start getting complicated so I would recommend it.

You only need standard exchange 2003 for the front end.
louisbohmAuthor Commented:
OK... But...

We do have an OWA already which is a seperate machine in our DMZ.  Also, I am NOT able to upgrade to win 2003 and/or Exchange 2003 at this time.  I have budgeted that upgrade for next year.  So I have to stick with Win 2000 Advanced and Exchange 2000.

Is it still possible???  Do I have to have 3 mail servers (not counting the OWA server)????

Well yes, that should still be possible with Exchange 2000. I don't see why not...

Note you don't have to have a front-end. If you don't, you can leave your current set up as is. Mail will arrive at your current server as normal, which will then either deliver to the mailbox on that server or detect that it's destined for a mailbox on the other server and route it to that one accordingly. A frontend just makes things easier, that's all.

You may want to consider when you upgrade to 2003 making the machine in the DMZ a 2003 front-end and then upgrading the other two backends to 2003 also.
How are you going to purchase you additional Exchange 2000 license? You cannot buy either Exchange 2000 or 2003 now. You will have to purchase Exchange 2007 and use downgrade rights. Now the ironic thing is that Exchange 2007 standard edition allows multiple storage groups and mailbox stores. However for your version you will have to pay for Enterprise Edition of Exchange 2007.

Exchange 200x in a DMZ is not a good idea either...


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now