Announcement

Collapse
No announcement yet.

Exchange at second site: Setup confusion

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

  • Exchange at second site: Setup confusion

    Ok, firstly a reminder of what we have:

    Site 1: Domain-site1
    2x DC's, 2k3 std.
    1 running Exchange 2003

    VPN to Site 2

    Site 2: Domain-site2
    1x DC, 2k3 Std x64

    Both sites connect to the Exchange server via Outlook in Cached mode. For users at 2nd site, this is slow, so want to setup 2nd Exchange for that site, which could potentially take over main exchange server as well, if ever needed.


    So, being x64 I found out 2k3 wont install on x64, so figured xchange 2k7 would do the trick. However it obviously mentions about the need of the server being in the same site as the 1st Exchange server.

    So, my question is this:
    How do I get an Exchange server setup on the server at the 2nd site? Am I entering the world of Virtual servers? (never been down that road before!)

    Any advice would be greatly recieved. Thanks.
    James
    MCP

  • #2
    Re: Exchange at second site: Setup confusion

    You could just install a second server at site-2, and make sure it's x32. in my mind - that seems to be the easiest solution for now.

    Exchange and DCs should not be co-hosted..(unless it's sbs)
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Exchange at second site: Setup confusion

      This is what I am wondering. I don't have the funds for a second hardware box tho, so are you suggesting a virtual x86 server 2k3 to run exchange on the x64 box?
      James
      MCP

      Comment


      • #4
        Re: Exchange at second site: Setup confusion

        uhmmm.. it would be a solution... :P I would try and avoid it myself, because with 2k3 you're lookin at virtual pc or virtual server, and to my mind they aren't an ideal scenario for production systems. (Of course, that assumes we'r enot harming your existing installation.. if you chose to go hyperv or esx, then it's a bit different..)


        you may be better off increasing the available bandwidth between the sites maybe ?
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment


        • #5
          Re: Exchange at second site: Setup confusion

          Hmm, there is no need that the Exchange 2007 server have to be in the same site as the Exchange 2003 server. You should be able to setup a new Exchange 2007 server at site 2, but make sure you know what you are doing, since this means a migration szenario from Exchange 2003 to Exchange 2007 and if you already have bandwidth issues migrating mailboxes from Exchange 2003 to Exchange 2007 might be a pain.

          Comment


          • #6
            Re: Exchange at second site: Setup confusion

            I'm only going by what the install says. It wont let me go any further, saying that the server needs to be on the same domain and in the same site.
            James
            MCP

            Comment


            • #7
              Re: Exchange at second site: Setup confusion

              I wouldn't be recommending an Exchange 2007 deployment in this scenario, unless it is on a separate machine.

              When you install Exchange on a domain controller, it becomes the ONLY domain controller that ALL Exchange servers will use. That includes your server in the other location.
              While a single server deployment on a domain controller is fine, when it comes to multiple Exchange servers it simply comes down to All Exchange servers on domain controllers or none.
              Running DCPROMO on a server with Exchange installed is also not supported and will usually break Exchange.

              Then we take in to account the fact that the first Exchange 2007 server should be implemented with care, because of its unique role for the co-existence.

              You haven't said how many users you have, but a VM's performance is going to be pretty poor unless the storage is well specified.

              If the X64 system is of very good hardware specification then you could look at P2V it, then rebuild the original chassis to something like ESXi. Put the original server back (now in a VM) and reduce its memory. Then you can build a second machine with Exchange 2003.

              Using the existing hardware as it stands is going to cause you nothing but problems, not only short term but long term as well. Exchange 2007 shouldn't be deployed without some thought - it is a major upgrade.

              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

              Working...
              X