General discussion

Locked

setting up an exhchange server for first time

By rerun27 ·
Can anyone tell me about the right placement of an exchange server if you are only using one server?(internal vs. dmz)
-how all that will work with public/private ip subnets being used
-how all the dns should work

the exchange server will have to talk with the domain controller, which is running dns. it should have a public ip right? how will it talk to the domain controller? will the firewall do all the work or will dns do all the work as long as the firewall rules are correct?

will i need change public dns records, or create internal dns records?

what are the different issues that will happen when setting up the exchange server for about 30 users.

how will i create the user mailboxes?
what other settings will i need to know about?

i have been looking for a step by step set of instructions regarding planning, setup, testing, and rollout for a brand new enviornment.

any help would be appreciated.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

MSExchange.org

by AristonCC In reply to setting up an exhchange s ...

There are a TON of tips and tricks on http://www.msexchange.org for Exchange related tasks. We currently have our Exchange server completely hidden behind the firewall. The firewall forwards the SMTP traffic internally.

You should start looking around the internet for white papers on Exchange deployment. Your questions are very basic and can be answered any of a number of different websites.

Collapse -

To do

by brian.kronberg In reply to setting up an exhchange s ...

1. If at all possible, use an ISA server to publish your Exchange server to the Internet. When properly configured, it is the most secure way to use Exchange from outside your organization. Read up on ISA at http://www.isaserver.org. They have MANY tutorials on how to effectively securely publish Exchange.
2. Since you only have 30 users, have you looked at SBS 2003 R2? It will make your job MUCH easier as a network admin. If you go this route, get a membership to http://www.smallbizserver.net for great information on how to properly set up SBS.
3. I would highly recommend that you use a split DNS setup and install your AD environment to something like ad.company.com where company.com is your external DNS. Read more about this here. http://tinyurl.com/aadwq

Now, if any of this seems above your head, hire a consultant for help designing your network. You can still do the work, but get some help answering your questions up front. Good luck.

Collapse -

Go to Microsoft

I would highly suggest going to Microsoft's site and reading up on their white papers for Exchange Deployments. They have case studies and other tips that would definitely help. I also agree about contacting someone who might have a little more understanding of setting up the network. Your questions are good ones but you are making it harder on yourself then it needs to be. If you already have a firewall there is no need to get a public IP address for your Exchange Server as the firewall can route the traffic. You would need to set up an MX record for DNS with your current ISP, who I would take it is currently handling your public DNS records. If that is the case they could probably even help you set up the rule or offer suggestions for configuring your firewall. Otherwise go to your firewall provider and get assistance from them they definitely should be able to assist in that area. Again good luck and check out Microsoft's site. It is their product they should know how to set it up properly.

Collapse -

thank you

by rerun27 In reply to Go to Microsoft

thank you for all your replys i appreciate it, i am going to go with sbs, it will have isa firewall built in, also placement will be behind a sonicwall. i will create an mx record pointing to the firewall and the firewall will forward packets. because the dc/dns/exchange will be on one server and behind the firewall it will make it much easier to setup and to manage services. i will still need a static ip from isp for the firewall. thank you for the websites and the advice. now they want to put a tape drive and backup software on the machine too, talk about pushing it.

Collapse -

Tape alternatives...

by brian.kronberg In reply to thank you

Instead of buying a tape drive, look into external USB hard drives to see if it will fulfill your the disaster recovery needs. Or look into the Iomega Rev. Tape drives are a good choice, but look at your options and their respective prices before you commit.

Collapse -

help

by rerun27 In reply to setting up an exhchange s ...

i have been looking all over for a clear explanation on setting up this server and adding users to it, then being able to confirm that it works. can anyone help me out? this is a little overwhelming for me.

Collapse -

MS HOL

by brian.kronberg In reply to help

http://www.microsoft.com/windowsserver2003/sbs/techinfo/training/handonlab/default.mspx

Start with Microsoft's Hands On Labs. This, and smallbizserver.net, should give you all that you need.

If you need more, PLEASE, get a small business server consultant in early in your design phase. Some things cannot be corrected later, like naming your domain. By default SBS uses company.local. This screws up Macs if you have them and can be difficult to configure certificates.

Back to Software Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums