going to stand up a new 2k3 exchange server

[rasczak]

This is my first time dealing with exchange ever as an S.A. so please let me know what you think should be required. I know I need at least server 2k3 and exchange 2k3 software, but for those of you with experience in standing up mail servers, what other things should I look at?

 

[Saga]

Have setup numerous Exchange servers, outside from the hardware, Windows License/Software, Exchange License/Software, nothing else should be needed. If I recall correctly the Exchange 2003 install installs necessary IIS components by default - though it's been a few years since my last Exchange 2003 install, I've been dealing with Exchange 2007 since it was released.

Oh. I guess there are two suggestions:
1) If you're backing it up with something like Backup Exec, install that client BEFORE installing Exchange.
2) If you are installing some form of ScanMail have it picked out and read the Antivirus documentation before deploying Exchange as there are sometimes specific steps they need done during the Exchange install.

Outside from that, have fun and if you run into any snags feel free to PM me, I've encountered dozens of Microsoft classified "One-Offs" in my time so I'm an expert at discovering new problems. Enjoy.

 

[rasczak]

sweet! thanks! so we're pretty much set as far as what to quote. i have a backup plan for our domain set up around ntbackup (we have a backup exec license but i could not for the life of me figure that darned thing out. maybe i'll get back to it and get it working soon) will ntbackup be sufficient for exchange in your opinion?

 

[dphantom]

Below is a good basic link to installing a new Exchange 2003 server.

There are some considerations to think about and my list is far from inclusive.

Link

Current state/level of AD - run dcdiag and netdiag

Will you need front-end server for OWA

SSL for OWA - not necessary but I really, really recommend it

Configure firewall to allow inbound traffic to your frontend server or backend if no frontend

How will you handle migrate users pst files??

DNS changes necessary - who hosts your MX record

Do you have a public IP address available

Just a few things that popped into my mind.

 

[dphantom]

Originally posted by: rasczak
sweet! thanks! so we're pretty much set as far as what to quote. i have a backup plan for our domain set up around ntbackup (we have a backup exec license but i could not for the life of me figure that darned thing out. maybe i'll get back to it and get it working soon) will ntbackup be sufficient for exchange in your opinion?

Installing the backup exec license is pretty straightforward. It is deployed from the BUE server to the Exchange server and that is it.

Then you configure your backup job and select the Exchange Information Store and then under Settings, select Use Backup Exec GRT. That gives you indivdual mailbox and message restore capabilities. really nice when your VP comes to you and says he deleted an email and needs it back.

 

[rasczak]

Originally posted by: dphantom
Below is a good basic link to installing a new Exchange 2003 server.

There are some considerations to think about and my list is far from inclusive.

Link

Current state/level of AD - run dcdiag and netdiag

Will you need front-end server for OWA

SSL for OWA - not necessary but I really, really recommend it

Configure firewall to allow inbound traffic to your frontend server or backend if no frontend

How will you handle migrate users pst files??

DNS changes necessary - who hosts your MX record

Do you have a public IP address available

Just a few things that popped into my mind.

basically it will be an internal server (no out side connectivity) no need for OWA. as far as migrating mail, i'm going to migrate our mailbox stores for the pop3 service on our domain controller to wherever exchange happens to store the mailboxes. we'll see how that goes.

thanks for the link. I'll look through it today.