Re: Separate locations

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Thanks Chad...you caught my drift
"Chad A. Gross [SBS-MVP]" <chad.gross@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:9DD0EC08-F559-4BBA-A874-4AFC7A80FB49@xxxxxxxxxxxxxxxx
Yes, SBS 2003 and Server 2003 can co-exist in the same domain, and you can
have multiple domain controllers in an SBS domain, etc. Your only
restrictions are that SBS has to hold all FSMO roles (and thus be at the
root of the AD forest), you can only have a single AD domain, no trusts, and
you're limited to 75 users/devices . . .

As you deploy each satellite, you'll want to make sure and create a
corresponding site in AD Sites & Services, define the subnet for that site,
and associate the correct DC with that site as well.

Connecting everything together is the easy part. What you need to spend
time planning is the data flow & storage. With multiple sites, there's a
delicate balance between centralized storage and offline availability if the
VPN link is down. Spend the time identifying what data groups of users
need, what site(s) those users will be working from, and how you're going to
back it all up. Multiple sites can be a perfect imputus to moving users
over to SharePoint. If you have users who have a tendency to save stuff to
their Desktop / My Documents, you may want to look at configuring folder
redirection per site - but for that to really work, users would need to work
only from one site. If they went to another site and logged in on a PC
there, it would try to load their redirected folders across the VPN - and
that is going to be painful to say the least.

Have I mentioned how much I like the Terminal Server solution for remote
locations? :^)

--

Chad A. Gross - SBS MVP
SBS ROCKS!
www.msmvps.com/blogs/cgross

"Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:42B1C8A9-9BC2-406C-ACCE-5B2498849BEB@xxxxxxxxxxxxxxxx
> OK, so if I understand correctly... I would have SBS 2003 installed at the
> main office and server 2003 as DC's at the other satellite office.
> Establish
> a VPN connection and all users residing as the satellite office would get
> authenticated localy and access exchange via VPN on the SBS2003 Server.
> So,
> I'm assuming that Server 2003 and SBS2003 can coexist in the same
> domain???
>
> Ralph R.
>
> "Chad A. Gross [SBS-MVP]" wrote:
>
>> I believe Cris' comment about not having access to Exchange / shared
>> files
>> was in reference to if/when the VPN went down. If both sites had
>> internet
>> access when the VPN was down, the remote users could still access
>> Exchange
>> if Outlook over HTTP was configured, or via OWA in a worst-case scenario.
>>
>> Having said that, we have several clients with multiple locations linked
>> together using a persisten router-based VPN, with SBS at the main office
>> and
>> additional DCs at the satellite offices. The big thing you need to look
>> at
>> is what are your file requirements. If the remote users will need to
>> access
>> accounting or LOB apps that don't behave well across a slow connection,
>> then
>> you're much better off investing in a Terminal Server for the main office
>> and having users log on to the TS. Depending on the number of users, you
>> may want to deploy multiple TS boxes to allow for load balancing &
>> failover
>> if you need to take one offline for whatever reason. Personally, I
>> prefer
>> the TS solution because for one thing, it makes backup so much easier -
>> all
>> of your data is at the main location, so you don't have to worry about
>> backing up across those VPN links. But even then, you could use the
>> remote offices as off-site backup storage if you wanted to implement a
>> solution like Microsoft's Data Protection Manager that allows for
>> replication of datasets between DPM boxes.
>>
>> --
>>
>> Chad A. Gross - SBS MVP
>> SBS ROCKS!
>> www.msmvps.com/blogs/cgross
>>
>> "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message
>> news:uKVRAwJ0HHA.4236@xxxxxxxxxxxxxxxxxxxxxxx
>> >I don't see why Exchange would be a problem. A lot depends on the speed
>> >of
>> >the connection between the offices, and the volume and size of the files
>> >you're sharing. For example, I'd redirect the remote office users' My
>> >Docs
>> >to the remote server, rather than to the SBS.
>> >
>> > What applications will you be trying to use remotely, and what kind of
>> > a
>> > connection do you plan? Remote office scenarios seem to be getting
>> > more
>> > common, and maybe someone can weigh in with their own experience in a
>> > similar setup.
>> >
>> > Another idea would be to make the second server a terminal server at
>> > the
>> > main office, and just let the remote client PCs access that, with no
>> > server at the remote.
>> >
>> >
>> > "Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > news:0A734B4A-F12E-4D60-BA57-C0DECBA2A0E5@xxxxxxxxxxxxxxxx
>> >> That's just it... They need to share files/apps/etc. and deffinitly
>> >> have
>> >> the
>> >> ability to access the exchange server.
>> >>
>> >>
>> >> "Cris Hanna [SBS-MVP]" wrote:
>> >>
>> >>> You would install a standard Windows 2003 Server as a additional
>> >>> domain
>> >>> controller
>> >>> It should also be a DHCP server, DNS, and Global Catalog Server.
>> >>>
>> >>> Of course they would not have access to email or software on the SBS
>> >>> server
>> >>>
>> >>> --
>> >>> Cris Hanna [SBS-MVP]
>> >>> -------------------------------------------------
>> >>> Microsoft MVPs
>> >>> Independent Experts (MVPs do not work for MS)
>> >>> Real World Answers
>> >>> ---------------------------------------------------------
>> >>> Please do not contact me directly regarding issues
>> >>>
>> >>> "Ralph" <Ralph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >>> news:8B77A03E-92D0-4318-80DA-0BF700A77AC4@xxxxxxxxxxxxxxxx
>> >>> A client of mine has two seperate offices and would like to link
>> >>> them
>> >>> together. If I set up a VPN between them I'm pretty sure the users
>> >>> would
>> >>> authenticated and log in without a problem to an SBS 2003
>> >>> environment.
>> >>> However, if the link between the VPN is down then that's a whole
>> >>> new
>> >>> ball
>> >>> game. Can I establish local auhtentication running an SBS 2003
>> >>> environment?
>> >>>
>> >>> Thanks,
>> >>> Ralph R
>> >
>> >
>>
>>


Relevant Pages

  • RE: Remote Office Configuration Suggestions?
    ... The additional DC at the remote site, could not be the SBS server, as you ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to Connect to Server/Client Desktop using RWW
    ... Please post the results of an ipconfig /all for the sbs server. ... I did another test after turning off the firewall on the remote. ... If port 4125 was not forwarded on the sbs machine, ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Remote Desktop Problem
    ... connectivity issues in SBS Server: ... This newsgroup only focuses on SBS technical issues. ... |> this computer on the Remote tab of properties of My Computer on SBS ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot Connect via remote desktop
    ... please ensure the domain name vpn.XXX.co.uk resolve to the ... As you want to connect the SBS via VPN, I suggest you also perform the ... select Disable Routing and Remote ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)
  • RE: Adding a Remote Office Domain Controller
    ... For licensing question, the SBS 2003 supports the branch office scenario. ... We need configure licensing on the Windows DC server in the remote site. ...
    (microsoft.public.windows.server.sbs)