Setting up exchange, 1 domain name, 2 offices

Discussion in 'Windows Small Business Server' started by Janetdeb, Oct 12, 2009.

  1. Janetdeb

    Janetdeb Guest

    I have been setting up exchange within SBS for a while now but have come
    across an issue with a new setup.
    The customer has 1 domain name i.e however they have 2
    separate offices. They have been using pop accounts and wanted to go over to
    exchange in their head office. Which i have done, running in line with their
    pop accounts for the time being, however spotted the obvious flaw that when i
    redirect the mx records to the head office the pop accounts at the 2nd office
    will stop working.

    Could i have some suggestions as to what is the best solution moving
    forward? The 2nd office is currently running a workgroup, file and print
    server and dont want to move to exchange yet, but will in a year or so.
    I did try looking at connecting the 2nd office via outlook using the rpc
    over interent to the head office, but couldnt get it to work. Also not sure
    this is the way forward if they want to move to exchange down the line..

    any help would be appreciated.....
    Janetdeb, Oct 12, 2009
    1. Advertisements

  2. Hi Janet:

    If you have enough SBS licenses to cover both offices, absolutely, Outlook
    over RPC. You have to follow the document exactly, litereraly, word for

    And you should ditch the pop3 asap and have all the mail centrally located
    in the company exchange server.

    Or, if there are other reasons for this, you could install a Terminal Server
    in the main office and have the users connect to that.

    Or Outlook Web Access on RWW.

    Please post the resolution to your
    issue so others may benefit
    Get Your SBS Health Check at
    Larry Struckmeyer[SBS-MVP], Oct 12, 2009
    1. Advertisements

  3. Janetdeb

    Merv Porter Guest

    Outlook via RPC over Internet may be the preferred way (and we should be
    able to get it to work). You could also have the branch office use OWA
    (Outlook Web Access) to get/send their mail...
    https// ( points to the WAN
    IP address of your SBS server).

    Another way would be to use OWA after logging into RWW.

    Make sure you have added a CAL to the SBS server for each of the branch
    office users.

    There are also ways of continuing on with POP3 at the branch office but I
    think it would be preferable to have them use an Exchange mailbox in the
    main office.

    Configuring the Outlook 2003 RPC over HTTP Client
    Merv Porter, Oct 12, 2009
  4. Janetdeb

    Janetdeb Guest

    Thanks to you both for your quick responses.

    I have an issue with the customers not wanting to change to OWA as i did
    think that would be the solution, but they are not very IT literate so
    changes are a big problem, hence the outlook over the internet idea.

    I have taken a look at the link of how to set this up and see that it states
    the following:

    The Outlook 2003 profile must be configured to use RPC over HTTP while that
    machine is connected to the internal network and can access the Exchange
    Server via TCP port 135.

    I am not sure how to do this, as i realise this solution was probably
    created for laptop remote user who could take their laptops to the exchange
    server for configuration. I have allowed port 135 through the firewall but
    do i need to configure anything else on the server to allow this to work. I
    am running SBS 2003.

    Also i may have another issue in that some of the client machines at the
    branch are running outlook 2007. It is still possible to set this up?

    thanks in advance

    Janetdeb, Oct 13, 2009
  5. Janetdeb

    Merv Porter Guest

    That link was probably a bad example. Once you have Run CEICW and set up
    the SBS server, you can use the link in RWW to set up RPC over HTTP on the
    remote workstation:

    From a past post...
    Here's what works for me 100% of the time when I am setting up RPC over
    HTTP: go to the workstation I am setting up for RPC, and go to
    https://servername/remote . Login, and then click on the link laveled
    Outlook over the Internet. This will display customized, step by step
    instructions. If you follow them to a T (including using the internal .local
    domain name when indicated) it should work.

    Now, one other thing is that you must have port 4125 (RWW) and 443 (SSL) on
    your external router pointing to your server. See:

    SBS2003 - Required Ports

    To use Outlook 2003 RPC over HTTPS your client PCs must trust the root

    How to Deploy RPC over HTTP for the First Time in Small Business Server 2003
    (Standard or Premium)

    Outlook 2007 should work with SBS 2003 and RPC over HTTPS.

    Merv Porter [SBS-MVP]
    Merv Porter, Oct 13, 2009
  6. Janetdeb

    Janetdeb Guest

    Great thanks for your help in this, it worked like a dream on 5 of the
    machines all connecting and syncing with exchange, accessing the public
    folders etc. too

    however i have 1 workstation that says it's connected to exchange when you
    login to outlook however it won't update the folders, continues to say trying
    to update.... and if you try and send and receive it seems to hang and
    nothing comes into the mailbox however i know there are messages waiting as
    when you login to OWA there they are?

    any clues please...

    thanks in advance

    Janetdeb, Oct 20, 2009
  7. Janetdeb

    Merv Porter Guest

    See if the user can receive email by opening Outlook in safe mode:

    Go to start | run | (type): Outlook.exe /safe

    Merv Porter [SBS-MVP]

    Merv Porter, Oct 20, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.