RE: Syncing remote servers

Tech-Archive recommends: Fix windows errors by optimizing your registry

One more precision for exchange, for a small number of users at the remote
site (under 20), I would not install an additionnal exchange server.

You will this way remain with a simple messaging architecture and in case of
short failures, you can still work in outlook if you activate the caching
features of outlook 2003 (this is the default when you creates the outlook
profile).



--
mcse 2000 - mcsa 2003 and still a lot to learn...


"Jeff Viola" wrote:

Thank you.

Jeff

"emmanuel meurant" wrote:

I would do the following :

Stay with only one domain, add a domain controleur at the remote site (and
maybe also use it as a local file server).

Create a specific site in "AD Sites and Services" for the new site to be
able to manage the synchonisation planning.

This would ensure quick login and access to data.




--
mcse 2000 - mcsa 2003 and still a lot to learn...


"Jeff Viola" wrote:

Here is what I'm trying to do. (if there is a better way let me know).

I have a small domain with 1 Win2003 Domain Controller that is also the file
server. Another domain controller that is the Exchange server and another
Win2003 server that is used for sql and terminal services.

I want to setup a remote site with basically the same setup, but I want to
be able to sync the servers through a VPN. Should I setup the second site
as a completely different domain and then just do a trust between them?
Would this allow the users to maintain only one password? What happens
when the communication is broken between the sites? Are the users and
password somehow synced to the remote location? Need help understanding
this? Same for emails?

Or is it better to use the main location as the Main Domain Controller and
the remote site as a tree in the forest? If the main site goes down can I
still connect to the remote site? What if the main domain controller server
is lost can the tree take over that responsibility?

I'm setting this up for disaster recovery and business continuation. If the
main site is lost (either temporary or permenant) I want to be able to
continue working at the remote location with current data, accounts on the
server.

Thanks for help with this.
.

Relevant Pages

  • Re: Recommended Setup
    ... yes the second server at the remote site as a Domain Controller for faster logons with a site to site VPN connection to the main office. ... Small Business Server Specialist ... SBS 2000 - microsoft.public.backoffice.smallbiz2000 ...
    (microsoft.public.windows.server.sbs)
  • Re: Replication of Small Business Server 2003
    ... The remote office has to be on a different subnet to allow proper routing. ... Windows SBS 2003 is the only server at the main office. ... as a domain controller in the existing domain and configure the new ...
    (microsoft.public.windows.server.sbs)
  • SecurityFocus Microsoft Newsletter #152
    ... MICROSOFT VULNERABILITY SUMMARY ... Real Networks Helix Universal Server Remote Buffer Overflow ... ... NEW PRODUCTS FOR MICROSOFT PLATFORMS ...
    (Focus-Microsoft)
  • Re: Possiblity of adding a second Exchange server to an SBS2003 domain
    ... On the CALs, You'll loose the 5 CALs from the remote SBServer, and ... The Exchange Server 2003 is running here as well ... we have a remote office with 6 users. ...
    (microsoft.public.windows.server.sbs)
  • SecurityFocus Microsoft Newsletter #140
    ... Cafelog b2 Remote File Include Vulnerability ... Webfroot Shoutbox Remote Command Execution Vulnerability ... Pablo Software Solutions Baby POP3 Server Multiple Connection... ... Microsoft Windows XP Nested Directory Denial of Service... ...
    (Focus-Microsoft)