Thank you,
Petr Jankovský
There are several choices to allow remote users to utilize your SBS server
and its resources, and it depends on your goals as to what course you take.
I would lean towards putting a terminal server in the main office and having
the users connect via RWW. That gives me control of the servers and the
users are able to work if the link to the main office is down but theirs is
up, as they could still browse the inet and perform most of their functions.
However, there is a case to be made for placing a second DC in the remote
office, adding GC role and AD-integrated DNS to it, and joining all the
remote computers to the domain. You would want to insure that the link was
good, and that the two DC servers could communicate easily and without
errors. Most would recommend setting the server up in the main office, then
moving it to the remote office.
In the above case, the home office systems should look for DNS and DHCP only
from the SBS, and the branch office should look to the remote DC for these
services.
I would probably make the two offices very dis similar IP addresses, such as
192.168.16.0/24 for the home office and 10.0.0.0/24 for the branch office.
Stay away from those IP's that are used by home routers and such.
192.168.0, 192.168.1 etc will cause conflicts if you establish VPN's.
Larry
"Petr Jankovsky" <stu...@gmail.com> wrote in message
news:%23bT$%23PtFI...@TK2MSFTNGP02.phx.gbl...