How do I configure SBS to allow branches of an organization send out intra and inter mails through their Microsoft office outlook?

An organization that has been using OWA(for its remote offices) now intends to use Microsoft Office Outlook to send and receive intra and inter mails on the same domain.
They are- at the moment- configured thus:
1. The HQ uses a live IP address on its server; so that remote offices can point to the server
    for OWA
2. Suffice to say that remote offices only requires internet access to access their mails through
    OWA. And their mailboxes reside at the HQ
I need to know the upgrade required
What are the changes required on their domain?
How do i go about installation/configuration to achieve this?

Who is Participating?
Rob WilliamsConnect With a Mentor Commented:
The EBS home site is:
It is not a case of simply downloading a manual and installing.
Using multiple Exchange servers also requires considerable study and testing as well as a substantial investment for Exchange and DC servers at each site. This latter is only done within very large companies since a single Exchange server can easily support well over 1000 users, either local, or local and remote.

Most often sites are tied together using VPN's which effectively extends the corporate network to the additional sites and allows users to work as if physically located in the main office.

I would recommend setting up and testing a site-to-site VPN and rpc/http services so that you are familiar with them. I think you will find these will more than satisfy your e-mail needs. I have several clients with a single head office and SBS and remote clients all over North America and each uses Outlook in the same way whether in the main office, remote office, or on the road.
Rob WilliamsCommented:
If the clients are remote from the SBS, your best bet is to use rpc/http, which works extremely well with the Outlook client, is secure, and acts exactly the same as if they were using Outlook within the office. This is simply enabled by running the Configure e-mail and Internet connection wizard on the SBS, and if you have remote web workplace set up, browse to that page and there is an option "set up Outlook via the Internet" which will give you the exact details to configure Outlook for your domain.
Rob WilliamsCommented:
ps- the following link will give you some details regarding the rpc/http service:
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

matrixsolicitorsAuthor Commented:

I think i need to re-phrase my question thus:

How practicable is it; for an org. to install SBS for its Head office with its own user license, then install same SBS with another set of licenses for its branches while both share the same domain?

A client;as mentioned earlier says he would like to make its branch run a standalone dedicated server with thier own SBS running because he does not want them to use OWA anylonger.

My own concern is that; during installation of SBS for the Head office, their domain address was required, now if i am to repeat same installtion at their branches using the same domain, what implication would it have on the overall communication architecture?
Rob WilliamsCommented:
>>"How practicable is it; for an org. to install SBS for its Head office with its own user license, then install same SBS with another set of licenses for its branches while both share the same domain?"
Can't be done. The e-mail gets sent to the appropriate domain, how can that domain be at two physical locations.

You can connect the two sites by VPN, but SBS has very special requirements where it must be the primary domain controller of its domain. You can have SBS at one site, a VPN connecting the two sites and an server 2003 std second domain controller at the second site. This can make for faster access to shares using DFS, and faster logons and authentications, but e-mail would still be on the SBS at the other site. However, e-mail would work in exactly the same manor as if all users were at the primary SBS site, only reception of e-mail would be a little slower. Much simpler though than OWA.

How many users are at each site?
matrixsolicitorsAuthor Commented:
I agree with your response i.e "The e-mail gets sent to the appropriate domain, how can that domain be at two physical locations"

There are over 50users at each site.

The issue is that client insist he wants users at remote location be able to use Microsoft outlook in the exact way and manner people at the Head office uses theirs. Does this imply that we migrate out of SBS completely? and would we need sub domains for the various branches? He has been refering to larger multinationals like SAP; Chevron e.t.c that they uses Microsoft office Outlook  at their various branches worldwide to communicate with each other without using OWA.

I am really keen to know how these orgs. do their!!!
matrixsolicitorsAuthor Commented:
Sorry, I meant their are 50 users at the HO and 10users at the remote location. He has plan to expand soon
Rob WilliamsCommented:
Firstly keep in mind SBS has a limit of 75 users, and cannot work with sub-domains. Also there can only be one SBS in a given network segment, and you cannot have 2 SBS servers using the same public domain name.

Large multi-national companies use Server 2003 with separate Exchange servers. This can be set up to replicate with multiple sites/multiple Exchange servers or simply one Exchnage server and the 2 options listed below for SBS. Though multiple Exchnage servers would work for you, the cost for less than 100 users would probably be quite prohibitive.

Smaller companies often use SBS, but with one of two methods, as mentioned:
1) A VPN connecting the two sites, which is most common
2) rpc/http, which requires no VPN, and can be used from anywhere
Both of these two methods from the client perspective work exactly like Outlook in a server/office environment. Using the VPN is actually the same, just the connection is a little slower, something that with e-mail the user could probably not detect. Rpc/http on the other hand uses a basic internet connection and the only difference is when Outlook opens the first time, the user has to enter their user name and password. In both cases the user uses the same Outlook client in the same mannor as workers at the SBS site.

Both of the above methods work with Standard Exchange as well, should the 75 user limit be a problem. There is also a new "big brother" for SBS called EBS (Essential Business Server) which allows for up to 250 users and is more robust in that it uses 3 servers instead of the one that SBS uses.
matrixsolicitorsAuthor Commented:
Hi Robwill,

Since it is just the two of us talking on this; could you give me a link to details on EBS as this may help me understand how to install and configure i.e If i need to advise a client on EBS.

On the main issue, would you advise on how multinationals use exchange to manage servers across continents. I may be able to use this to solve this present clients problem. If possible a link to manuals as well.

I have link to rock-sbs; kindly bear that in mind.
matrixsolicitorsAuthor Commented:
Many thanks Robwill, I will try these steps, then revert back to you.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.