I'd definitely use the existing domain. Communication between subnets will
happen by way of the router/firewall device handling the VPN tunnel.
Thanks,
Brian Desmond
br...@briandesmond.com
c - 312.731.3132
From: Mei Ling Gallagher [mailto:meili...@newsys.com.au]
Sent: Wednesday, June 02,
, June 02, 2010 13:28
To: NT System Admin Issues
Subject: RE: setting up 2008 server for remote office
I'd definitely use the existing domain. Communication between subnets will
happen by way of the router/firewall device handling the VPN tunnel.
Thanks,
Brian Desmond
br...@briandesmond.com
up 2008 server for remote office
*I’d definitely use the existing domain. Communication between subnets
will happen by way of the router/firewall device handling the VPN tunnel.
*
* *
*Thanks,*
*Brian Desmond*
*br...@briandesmond.com*
* *
*c – 312.731.3132*
* *
*From:* Mei
Admin Issues
Subject: Re: setting up 2008 server for remote office
I agree. Should she also consider making the new server a DC + Global Catalog
for login purposes when connectivity between sites is lost?
RS
On Wed, Jun 2, 2010 at 3:13 PM, Malcolm Reitz
malcolm.re...@live.commailto:malcolm.re
: Wednesday, June 02, 2010 3:13 PM
To: NT System Admin Issues
Subject: RE: setting up 2008 server for remote office
Yes, no reason to create a new domain.
I'd build the new server at the main office and join it to the domain.
There should be no issue with then moving it to the new office and
giving
:* RE: setting up 2008 server for remote office
*I’d definitely use the existing domain. Communication between subnets
will happen by way of the router/firewall device handling the VPN tunnel.
*
* *
*Thanks,*
*Brian Desmond*
*br...@briandesmond.com*
* *
*c – 312.731.3132
Issues
Subject: Re: setting up 2008 server for remote office
I agree. Should she also consider making the new server a DC + Global Catalog
for login purposes when connectivity between sites is lost?
RS
On Wed, Jun 2, 2010 at 3:13 PM, Malcolm Reitz
malcolm.re...@live.commailto:malcolm.re