New Domain/Exchange 2003 1

[loyalist]

Hello,

I am new to building and administering exchange servers and my company has purchased Windows 2003 server along with Exchange 2000. This is a new company and I am currently building the network/domain from scratch. I know that installing exchange 2000 on W2K3 can be rather messy and I would prefer to avoid the hassle so I really feel that I only have 2 options, either install Exchange 2000 on W2K or install the beta of Exchange 2003 on W2K3 into production and then hopefully be able to license the beta as some have suggested. The company is in desperate need of a mail service and I have to build something right away. Does anyone out there have any sound practical advice as to which would be better in my situation and for that matter any links that would provide me with guidelines and best practices for the installs of either exchange 2000 or 2003. My preference is to run W2K3 in native mode however if anyone feels that this solution will not be practical or too risky(ie running a beta in production) given my current situation feel free to offer pros and cons. Finding configuration information for Exchange 2003 has been frustrating to say the least.

Thanks in advance,

Loyalist

 

[gcdhnjgfhfgsxh]

Hi

Ok... well Exchange 2003 is available as the full completed version available for immediate trail download of 120 days. When it is officially released (with office2003) you can instantly upgrad your trial version to the full version without having to reinstall any of the systems. Check out..

http://www.microsoft.com/exchange/evaluation/trial/2003.asp

Make sure that the new server is upto the challenge though. Depending on the amount of users you will be having make sure that you have at least 1GB RAM, all the minimum specs are given by microsoft but in my personal opinion i would at least double thows recomendations

Configuration of exchange 2003 has hardly changed from 2003, you wont notice much difference

How many users do you have, are they located in one office, please provide more info

Best Regards

Dave

http://affy.dynu.net

 

[loyalist]

Thanks Dave,

I have a Dell 2550 with dual 1.13ghz pentium 3 processors, 1 gb of memory and 2x18gb, 2x36gb hard drives each configured for raid 1 on two channels of an internal perc3di controller. My company currently has approx 50 users and plans to double in size within one year. 2 remote locations, one will be connected via vprn and will login directly connected to domain and another site with currently only 4 users who will access via cisco vpn clients to a pix firewall(eventually office will grow in size and will convert to branch office vpn). There will also be remote sales staff who will also require vpn access. There is a definate requirement for owa.

Just beginning to build W2K3 domain controller this morning, it will also serve as dns,dhcp,file and print server. Ideally would like to run in native mode if possible, anxious for all the benefits and seamless integration with dns and mail server.

Curious about placement of mail server, initially planned on placing in dmz however wondering about risks/benefits of this scenario. Would like to eventually implement front end/back end mail servers and therefore wonder if initial deployment should be inside instead of dmz(issues/concerns about later moving mail server back inside if initially deployed in dmz).

Looking for assistance in partition configuration to optimize mail server and help in installing and configuring exchange. I have already downloaded the beta of exchange 2003 in anticipation of implementing this solution.

Thanks again,

Loyalist

 

[gcdhnjgfhfgsxh]

Hi

However, that server is more than sufficient to handle your needs. Running the server in native mode will be fine solong as you have windows 2000 clients and above there wont be a problem, its also more secure that way. My personal server (yeah its exchange 2003 for 2 users LOL) is located in my DMZ and works fantastic, i dont even get any spam into any of the mail boxes that i have set up. When configuring the server, set it so that backgrpound services get priority on the CPU as it is unlikely that you will be using this as a work station so is better to optimise for services rather than programs. Moving the server to a back office will not be a problem in the future neither would it be placing it in the back office and passing the mail through the fire wall.

Hope this helps

Dave

http://affy.dynu.net

 

[loyalist]

Thanks Dave, if I don't get this to work they may be looking for another admin ;-)

In regards to building and configuring the exchange server any advice or any good links for this. Should I just follow the exchange 2000 guidelines?

 

[gcdhnjgfhfgsxh]

Following the 2000 guide lines will be fine for most standard servers... unless you are doing anything 'weird' with the configuration, setting it up as you would a 2000 server should be fine

Dave

http://affy.dynu.net

 

[loyalist]

Thanks again, wish me luck