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 it a new
IP address.

 

-Malcolm

 

From: Brian Desmond [mailto:br...@briandesmond.com] 
Sent: Wednesday, 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

 

c   - 312.731.3132

 

From: Mei Ling Gallagher [mailto:meili...@newsys.com.au] 
Sent: Wednesday, June 02, 2010 1:23 PM
To: NT System Admin Issues
Subject: setting up 2008 server for remote office

 

Hi all,

 

My client is setting up their new remote office.  The main office has a
Windows 2003 DC with the subnet of 192.168.2.x.  The remote office will be
setup with a Windows 2008 R2 server and a subnet of 192.168.3.x.  Some users
in the remote office will need access to some data from the main office
server.  VPN are use for the connectivity between these two sites.

 

Would I be better to join the 2008 server to the current 2003 domain or
setup a brand new domain with a trust relationship??

 

The physical 2008 server is currently in the main office.  If I choose the
first option, should I run it up as a member server before moving it to the
remote office then join it to the 2003 domain??  Will this server able to
make a contact with 2003 server as they are on the different subnet?  

 

Any help would be appreciated.  

 

 

Thanks in advance.

Mei Ling

  _____  


Scanned by MailMarshal - Marshal8e6's comprehensive email content security
solution. Download a free evaluation of MailMarshal at
<http://www.marshal.com> www.marshal.com

  _____  

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to