Creating a new domain is waaaaay too much complication for no reason. They'll work on your existing domain just fine. And, if the Exchange server is at your home office, there's no particular need for a DC at that site either. Logon traffic for that few users shouldn't be significant. The biggest use of bandwidth will actually be printing and file saving to the local f/p server from the remote terminal server.
Malcolm From: Roger Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, 10 January, 2008 17:22 To: NT System Admin Issues Subject: New Remote Office We have a new remote location coming online in a couple months and are working on our IT plan. There will be a permanent VPN between the two sites. We plan for the remote users (about 20) to access their apps via a terminal server here, but they'll also have a local file and print server. The Exchange server resides here We're unsure whether to make that location a separate domain with trusts between the two or add them to the existing domain and make their local F/P server a DC of the existing domain. The Exchange server resides here and permissions are already set for the users who will be relocating. What are the relative merits of a remote DC of the existing domain versus creating a new domain and adding the trusts? How much data would be moving across the wire for A/D syncs? Roger Wright Network Administrator Evatone, Inc. 727.572.7076 x388 ____ If your mind goes blank, remember to turn down the sound. This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
