Re: Remote office users slow logon



Sean <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
OK, Lets see if I have all this.....

Lanwench - My AD is working between sites and it is setup as you
suggested. Are you telling me to split the SBScomputers OU into two
groups, one for each site? Does this affect anything else?

No, if you do it right. I personally like splitting out my OUs for many
reasons - for example, I don't put laptops in SBSComputers, but in a
parallel OU called SBSLaptops. If I had a remote location, I'd create a
third parallel OU called something logical.

Cliff - I was unsuccessful on a previous attempt to move the
setup.exe file accross the tunnell and have it run. I didn't use DFS
just copid the folder. Isn't DFS going away?

No....where did you hear that?

VPN is great, but file access across that tunnel will still not be great. A
well-configured Terminal Server in the main office is the most bombproof
addition you can make.

I would surely like to
use it now that I have enough bandwidth. As for moving from AD to GPO
scripts, are there any how tos on this as I generally stay out of
those areas for my own good.....

It's really pretty straightforward if you use group policy at all. Just
remember - do not edit the existing policies unless you are *very*
confident, know what you're doing, and have done this successfully in the
past . Always create & link your own at the appropriate OU level. Using GPMC
makes this easy.

Les - When I disabled the script entry things were good, but printers
and stuff weren't setup or wouldn't revert back to our defaults on
login, so I should try and fix this first, and as a last resort,
coment the line out.

Did I get this right?

I just installed a T1 at my remote office and am still experiencing
1.5 - 2 minute login times.

I am running SBS 2003 standard and Server 2003. There is a pair of
Sonicwall TZ-170s with a site-site VPN tunnel bridging the two
offices. Remote server is a BDC and replicates correctly with SBS.
There are no errors in any logs between the two servers. I have a T1
connecting each office to the internet.

Each user sees the black login script window and we are waiting for
the
setup command to run/complete.

I tried rem'ing the line out and everything works fast. I know
several posts here ask what this does, and I know this don't work
right without it, so......

Any suggestions on how to improve the login time for these users,
the SBS local users finish the script in 10-20 seconds, versus 1.5
minutes.....

File transfers and access are quite fast, so I don't think it's a
network issue, and now I have upgraded our old DSL to a T1 at this
remote office and would have expected this to be better.

Thanks in advance.
--
Sean



.



Relevant Pages

  • RE: Remote office users slow logon
    ... Lanwench - My AD is working between sites and it is setup as you suggested. ... minute login times. ... I am running SBS 2003 standard and Server 2003. ... Each user sees the black login script window and we are waiting for the ...
    (microsoft.public.windows.server.sbs)
  • PKZIPC, ASP and WSH
    ... this script locally when logged in as the user that is setup in IIS. ... -script works fine locally on the server. ...
    (microsoft.public.scripting.wsh)
  • Re: Offsite Backup Using VPN
    ... I'm trying to figure out if it's possible to setup and automated ... script to launch and login to a VPN connection with a remote server ... server to my local PC. ...
    (microsoft.public.windows.server.general)
  • Re: How to set permission for Shell.Application when using BrowseForFo
    ... > browse the windows folders from within a script block in HTML web page. ... > can fully control the server and can setup the permission whatever I want. ...
    (microsoft.public.scripting.jscript)
  • Re: How to configure for Two different IP subnets
    ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
    (microsoft.public.windows.server.networking)