Microsoft exchange 2003

pts.
Tags:
Active Directory
Availability
Bandwidth
Cabling
Cisco
DataCenter
Desktops
DHCP
DNS
Hardware
Hubs
Juniper Networks
Lucent
Management
Microsoft Windows
Network monitoring
Networking
Networking services
Nortel
OS
Project management
Routers
Security
Servers
SQL Server
Switches
Hi guys, i just got a contract in a new company tha wants to start using microsoft exchange 2003. could you kindly explain how to go about cinstalling and configuring their network for exchange. thank you

Answer Wiki

Thanks. We'll let you know when a new response is added.

What part do you have questions about. Do they have active directory yet? How big are they? Are they prepared to isolate the exchange server from the internet using a firewall and email relay, (highly recommended)? Do they require clustering to accomodate failover?

The internal network shouldn’t require changes if it is a sound design. On the other hand, I wouldn’t even consider installing exchange unless it is well protected from the internet.

As you may guess from these questions, your request covers a lot of territory. I suggest you start by reading the documents at this link:
http://www.microsoft.com/technet/prodtechnol/exchange/2003/deployment.mspx
When you have specific questions, post them here.

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Japeters
    Installing Exchange 2003 your first time is a daunting task. If you've done it before, it's pretty easy. If you have the time to play with it at the customer site (without looking like you don't know what you're doing), by all means check out the abundant information and white papers on Microsoft.com. If you are getting enough money for the install to justify it, I'd recommend making a support call to help you get through your first attempt to make sure the customer is satisfied (microsoft charges $199 i think for a single incident, and will walk you through it on the phone until completion. Hydra Network is usually a cheaper alternative you might consider, as they only charge $99 per incident per day--plus they can take over for you if you get swamped and do most of the work remotely for an extra charge). There are so many ways to implement and so much to consider, that you really would need to narrow down this question or provide a lot more info on the customer requirements and expectations. To get any useful feedback from this forum.
    0 pointsBadges:
    report
  • TheVyrys
    I have to say I am appalled that you would have a contract with a company to provide a service you don't even yet know about. I guess that if you set yourself large challenges, you get large results. I can relate to that.....sort of. As reflected above, there are many things to consider. More information will be needed to provide good answers. My recommendation first off though is to encourage them to move to a Windows Server 2003 environment if they have not done so already. good luck to you, and I'm not being sarcastic. Sometimes just doing it is how you learn.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Here's a late answer to your question...from the previous posts you can see there are a lot of ways to set up a secure Exchange organization, all of which will require much more detail to answer. So, on that note let's start with the basics, hardware. Make sure before anything, that you have a solid server to work with. Your going to want to avoid installing Exchange on a DC (if at all possible)and certainly don't want to piggy back it with resource intense applications such as SQL server or other database type applications. Exchange is a resource hog and performance will suffer if you make it share. If your client's budget allows, have them purchase a dedicated server for Exchange to run on. Make sure you plan enough storage for the environment as mailboxes will fill fast and some sort of redundancy. A hardware RAID 5 is a good choice as it gives you hot-swap options. Dual processors would be a good call and don't skimp on the RAM! A full gig at least is recommended. This should get you started. To be successful do your homework and draw up a plan to work from. There are a lot of little things that can easily be overlooked. Exchange is not difficult to set up if you have some background, but for a novice it's very easy to sink over your head fast! Good Luck!
    0 pointsBadges:
    report
  • Ghigbee
    Having just finished migrating a client from Exchange 5.5 to Exchange 2003 I can safely say that you need to either setup a test lab to mimic their network and do the install, or at the least setup VMWARE or Microsoft Virtual PC and build virtual servers. By doing this you can find the basic pitfalls and document your procedure for the install. I used Virtual PC as a platform for the migration tests and also used it to generate screen shots for documentation that the client requested. You don't necessarily need to buy Windows server 2003 and Exchange 2003 either since you can download trial versions from Microsoft that work just fine. Just my 2 cents worth. Hope it helps
    0 pointsBadges:
    report
  • Bigshybear
    Make sure you also include specialized antivirus software to check the inbound e-mail, either on the firewall, on an inbetween computer, or on the mail server itself. Make sure you add backup software and hardware. and think about antispam software.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following