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 www.marshal.comhttp://www.marshal.com ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
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 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/ ~
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.comwrote: 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 www.marshal.com -- ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: setting up 2008 server for remote office
Maybe - I have no idea what the requirements, topology, stability, etc is here. Cached creds will work in the short term though. Thanks, Brian Desmond br...@briandesmond.com c - 312.731.3132 From: Richard Stovall [mailto:rich...@gmail.com] Sent: Wednesday, June 02, 2010 2:44 PM To: NT System 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...@live.com wrote: 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.commailto: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.commailto:br...@briandesmond.com c - 312.731.3132 From: Mei Ling Gallagher [mailto:meili...@newsys.com.aumailto: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 www.marshal.comhttp://www.marshal.com ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: setting up 2008 server for remote office
Is the new server going to be a domain controller? If so I what I've done in the past is join it to the domain and promote it to a DC at the main office and let it replicate with the existing server. When you move it to the remote office, first create a new Subnet in Active Directory Sites and Services for the remote office, then create a new Site and assign the new subnet to the site and move the new server into the site. Ralph Smith Gateway Community Industries 845-331-1261 x234 From: Malcolm Reitz [mailto:malcolm.re...@live.com] Sent: 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 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 www.marshal.com http://www.marshal.com Confidentiality Notice: -- This communication, including any attachments, may contain confidential inf ormation and is intended only for the individual or entity to whom it is add ressed. Any review, dissemination, or copying of this communication by anyon e other than the intended recipient is strictly prohibited. If you are not t he intended recipient, please contact the sender by reply email, delete and destroy all copies of the original message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
Re: setting up 2008 server for remote office
Too bad the main Domain is not 2008 as well then the remote DC could be a RODC with the added security. Jon On Wed, Jun 2, 2010 at 3:57 PM, Brian Desmond br...@briandesmond.comwrote: *Maybe – I have no idea what the requirements, topology, stability, etc is here. Cached creds will work in the short term though. * * * *Thanks,* *Brian Desmond* *br...@briandesmond.com* * * *c – 312.731.3132* * * *From:* Richard Stovall [mailto:rich...@gmail.com] *Sent:* Wednesday, June 02, 2010 2:44 PM *To:* NT System 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.com wrote: 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 www.marshal.com -- ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: setting up 2008 server for remote office
It doesn't need to be to support the RODC. Just need a single 2008 RWDC in the hub site Thanks, Brian Desmond br...@briandesmond.com c - 312.731.3132 From: Jon Harris [mailto:jk.har...@gmail.com] Sent: Wednesday, June 02, 2010 5:48 PM To: NT System Admin Issues Subject: Re: setting up 2008 server for remote office Too bad the main Domain is not 2008 as well then the remote DC could be a RODC with the added security. Jon On Wed, Jun 2, 2010 at 3:57 PM, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com wrote: Maybe - I have no idea what the requirements, topology, stability, etc is here. Cached creds will work in the short term though. Thanks, Brian Desmond br...@briandesmond.commailto:br...@briandesmond.com c - 312.731.3132 From: Richard Stovall [mailto:rich...@gmail.commailto:rich...@gmail.com] Sent: Wednesday, June 02, 2010 2:44 PM To: NT System 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...@live.com wrote: 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.commailto: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.commailto:br...@briandesmond.com c - 312.731.3132 From: Mei Ling Gallagher [mailto:meili...@newsys.com.aumailto: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 www.marshal.comhttp://www.marshal.com/ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
