Announcement

Collapse
No announcement yet.

Installation of Exchange 2003 on a standalone server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Installation of Exchange 2003 on a standalone server

    Hi there, I am fairly new to exchange server 2003, and as such, I am spending some time setting up various network configurations in a virtual environment. I have a couple of questions that relate to the following configurations.

    The first configuration was created on one system which ran the following services:

    Windows server 2003 ENT,
    DNS
    Active Directory
    Exchange Server 2003.
    XP client

    I have been told that it isn't reccomended to install exchange on the same machine as a domain controller. This also this seems to create issues when shutting down this particular server for maintenance or required reboots.

    My first question relates to the above, in that, is this advice correct and what advice would the members give for setting up a small business network that could stretch to no more than three servers.

    My second point relates to another test scenario where the following configuration was created:

    SERVER 1
    Win 2003
    Active Directory
    DNS

    Server 2 Mail Server
    DNS Secondary DNS Server
    Exchange 2003

    XP client

    The main question that I have is that, when exchange is installed as a standalone server away from the domain controller, Active directory is still installed on Server 2. I appreciate that Active directory is required for Exchange to function, and without it there would be no management of users for exchange to allocate mail boxes to, etc. However one thing I noticed was that when entering the Active directory console on the non domain controller, I was able to manage users, including creating users and pretty much all tasks that I would have beeen able to carry out as if this was the main domain controller. Any updates that were added from server 2 that had exchange installed were then replicated to server 1 the main domain controller. As I had not explicitly created the role on server 2 to act as a secondary controller, how does this work, and more importantly what are the security issues that we have. Again further advice on a good practice installation and implementation on a simalar configuration would be gratefully received.

    Apologies for the long post in advance.

    Jewen.

  • #2
    Re: Installation of Exchange 2003 on a standalone server

    It is always good practise to have Exchange on a dedicated machine that is not a domain controller. While Exchange will function on a DC, it is not best practises. There are many documents all over the internet that state this.
    That does not apply to Small Business Server. SBS has been tuned to run on a single box and does so very well.

    For a three server network, I always do the same thing...
    DC1
    DC2
    Exchange.

    The two DCs share the other network roles such as file sharing, printer server and management applications such as AV software etc.
    If there is something web based, for example WSUS then that will go on the Exchange server. That can then provide a single point of entry for web based applications both internally and externally.

    The changes that you are making in ADUC on the Exchange server do not have to be replicated. The ADUC is modifying the domain directly. It is the same thing that happens if you install the Admin Pack for Windows XP on to your desktop. You can then modify AD settings from there. Nothing you have said makes me concerned that something is wrong.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Installation of Exchange 2003 on a standalone server

      Hi there, thanks for your advice on my post. It was very informative.

      To clarify your final point, would I be correct that the ACDUC that I can access on the server with exchange and isn't a DC, is only a management console tool that is connecting to the DC server. If this is correct, I notice that the properties for a user the ACDUC that is viewed on the exchange server include the exchage tabs such as exchange features etc whereas the server that is the DC in its ACDU does not have the facility to view exchange features in a users proerties.

      Does this mean that to create accounts with mail boxes this will require to be administered through the exchange server rather than the DC?

      Thanks.

      Jewen

      Comment


      • #4
        Re: Installation of Exchange 2003 on a standalone server

        Exchange adds extensions to ADUC that allows the additional parameters of the user account for Exchange to be administrated.
        The best practise is to use ADUC on the Exchange server to create accounts and mail enable them.
        You can install the Exchange management tools on to any other machine, such as a domain controller, which will extend the ADUC functionality to allow management of the Exchange options, but that is not always a good idea in most environments.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Installation of Exchange 2003 on a standalone server

          Thats great,

          Thanks for your time.

          Jewen.

          Comment

          Working...
          X