Syncing remote servers

[Jeff Viola]

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.

 

[emmanuel meurant]

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.

 

[Jeff Viola]

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.

 

[emmanuel meurant]

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.