Exchange 2000 server and ms outlook 2000 installation,configuration

Microsoft Exchange 2000
Microsoft Outlook
Microsoft Outlook 2000
Hi, I am going to deply MS Exchange 2000 server in my organisation, Before that we have no message system, Now we have 200 systems of windows XP/Windows 98 with MS Windows 2000 Advanced Server. Pls guide me how to Install and Configure MS Echange 2000 Server and MS Outlook 2000.What r the parameters are required to configure.If Possible pls send the step by step method for installation and configuration. Thanks. Dips chinmoy

Answer Wiki

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

That is quite an involved topic, but there are various tutorials available online that can get you started. The following is a link to planningand installing Exchange 2000.

Hope that helps you,

Discuss This Question: 6  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.
  • ExchDude
    Another thing you might want to decide is how you want your users to check mail while they are away from the office; do you want them to use Outlook Web Access or RPC/HTTPS, etc. Each one requires a different way to design the Exchange site.
    0 pointsBadges:
  • bmarone If possible, you should start with Ex2003. Most of the above tutorial would still apply. But Ex2000 mainstream support is already expired, though patches are good thru 2010. Mainstream support on Ex2003 lasts until 2009. Life-cycle info at Also, with Ex2003 you can download and use the Deployment tools, which is its own step-by-step and is very easy to follow. Make sure you download the latest, and also the latest admin pack for your SP levels. You should be at Win2003 SP1 and Ex2003 SP2. Most important thing, Ex2000+ depends on Active Directory, which relies heavily on DNS. The important thing, your Exchange/Outlook client machines and all Exchange servers should point to the MS AD server for DNS. If you already have an internal non-MS DNS and want to keep it, the best solution is to install DNS on Windows2003, pointing it to your current DNS as the upstream if necessary. I view MS as a necessary evil as much as the next guy. Unfortunately, you will prevent a lot of problems by using their DNS server for AD/Exchange, or more easily resolve problems that do arise.
    0 pointsBadges:
  • InfosysMgmt
    Although I've not actually installed and configured Exchange 2000 server I agree with other responders that planning for DNS is one step in the process you definitely want to understand before going live. Improperly, or inappropriately configured DNS could cause valuable time loss for an already taxed IT team.
    115 pointsBadges:
  • Astronomer
    I agree with the previous answers about DNS. Before we upgraded from exchange 5 to 2003 we did a general house cleaning of our domain structure. We consolidated the four domains into a single tree and used active directory integrated DNS internally. External references were forwarded to linux DNS servers in the DMZ. After all of this work, when it came time to migrate exchange, it went very smoothly. I have no doubt it would have been much rougher if we hadn't cleaned up the domains first. rt
    15 pointsBadges:
  • Stevesz
    If you have no experience with Exchange, or mail servers in general, you should probably consider hiring a consultant who is familiar with Exchange, and utilize him to help you set it up and teach you how to administer it. You can do the reading thus far presented and learn a few things that will help your search for a consultant who knows what he is doing. The other suggestions are valid also. I do agree that you should go with Exchange 2003. The current Exchange 2007 is meant more for large corporations in the way it is designed and meant to be deployed, so don't let anyone talk you into that. Microsoft is said to be at work on a version of 2007 that is more suitable for smaller deployments, such as the one you are contemplating. You will want to upgrade at least your DC's to Windows 2003 prior to Exchange 2003 deployment for the Active Directory improvements and how Exchange 2003 will mesh with AD, which will make it a pretty powerful mail solution for your organization. You will also want to remove any remain 98 machines as well, unless they serve a specific purpose that requires 98 (not many). You'll also want to use Outlook 2003 with Exchange 2003 so that everyone can take advantage of the advantages Exchange/Outlook 2003 working together that is not available with Exchange/Outlook 2000 or Exchange 2003 / Outlook 2000.
    2,015 pointsBadges:
  • Wrobinson
    Installing Microsoft Exchange Server and Outlook are not complicated tasks; however, designing a solution suitable for your environment and managing that solution requires advanced knowledge of both products, as well as your organization. First off, if you do not have experience with Exchange then I do not recommend installing Exchange Server 2000 because it is well past its half life in terms of mainstream support. Instead, I would recommend using Exchange Server 2003, though it is nearing its own support half life. There are a lot of enhancements -- performance, security and funtionality-wise built into 2003 that are not in 2000 that will make life easier for you as an administrator, as well as your end users. Exchange Server 2007 -- contrary to comments made earlier, is not made for the enterprise or SMB per se. It is highly flexible in its design and can be deployed in a number of scenarios and environments accordingly. Some of the native high-availability and disaster recovery features are aimed at helpin non-enterprise organizations achieve service levels of enterprise organizations at a lower cost. E2K7 is very command-line oriented, though SP1 will provide additional support for administrative tasks in the GUI. Depending on the time frame in which you intend to have this new messaging system up and running, you may want to do some reading on TechNet, and If your need is immediate, then you may wish to engage a Microsoft Certified Partner to help you with designing and implementing a solution for your organization and help you manage it. If you prefer reading offline, then you may look for some Microsoft Press books on the version of Exchange that you intend to install or some other titles such as the "Unleashed" series by SAMS Publishing. Microsoft Exchange is tightly integrated with Active Directory and heavily dependant on DNS. You will need to ensure that you have a healthy Microsoft Windows Server 2003 (or 2000) Active Directory environment before attempting to implement Exchange.
    5,625 pointsBadges:

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.

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


Share this item with your network: