Re: Remote office logon script - Long Delay

OK,
I'll REM out the line for setup for now and watch what happens. The users
grumble about the delay, but I tell them it's their first "free" break and to
stop complaining or we'll make them clock out while waiting ;)

Thanks for the help, I'll post my findings in the morning.
--
Sean


"kj [SBS MVP]" wrote:

Sean wrote:
I belive the AD site and subnets are configured correctly. Nothing is
showing in the logs and replication is occuring regularly and without
error.

DHCP is working correctly and seems to be keeping to it's assigned
subnet for each location.

I do not have WINS configured for the remote site, only the primary
location. I thought most apps aren't using WINS for anything much
anymore. Should this be configured?

Intersite messaging is set to Auto, I think I had to do this
initially to get the replication to work.

I don't push apps out to the clients and other than GPOs I don't do
much but serve files to the clients and mail. So setup.exe may not be
needed?

Used when you 'setup client computers' or 'setup client applications'. setup
looks for any changes and if it finds any then proceses what is needed. So,
you should be safe in turning this off for existing remote site users and
workstation.

WINS still has some uses, but not many. If your remote site is otherwise
working, I'd be inclined to wait for a reason to add WINS to the remote
site.




Sean wrote:
My first thought was DNs, but no erros or problems
browsing/accessing netwoprk resources. Users are on the systems at
the moment, so I'll post an IPConfig log as soon as I can.

This remote server was built using connect computer script, and is a
GC/AD server with DNS and DHCP for it's area.


Ah, that makes a *big* difference, or at least it can.

Is the remote server (DC) setup as a seperate AD site with the
subnets properly defined?

Is your intersite replication working properly? (you need to change
the Intersite Messagind service on the SBS server to "Startup:
Automatic")

Do you have a second WINS server and if so, is it configured for
push/pull replication to the SBS one?

With a second DHCP server and scope, are the remote workstation
getting DNS only from the local server or is the SBS server set as
#2?

Setup.exe isn't a large file but it may be generating a fair amount
of network traffic in it's execution. If everything else is
configured and working properly and you don't plan on the SBS server
distributing applications (from the SBS server) you might want to
configure the login script not to do this for the remote site.


Copying large files can be a real burden to the network, but no more
than I would expect for the bandwidth that is available.

Is there anything that can be done for setup.exe to improve it's
performance? Copy the folder?



Sean wrote:
I am running SBS 2003 (not premium) and have a remote server (win
2003) at a remote office. The offices are link through two
Sonicwall devices through a VPN tunnel. The remote office
connection is a 640K DSL and is slow, but works for the 3
employees.

I am experiencing an extremely long delay running the logon script
file. Seems the setup.exe file may be the culprit. My script has
only two lines but takes almopst 10 minutes to complete.

\\SERVER\Clients\Setup\setup.exe /s PHXSERVER
\\SERVER\ezaudit\ezstart /auto

I can watch the scripts progress and the setup line is the long
delay. No error messages are displayed, just seems to take too
long.


Any guidance on how to improve performance? My local systems are
done in 10-15 seconds.

Thanks in advance.

Well my first take would be that the remotes might be having
trouble;

a) resolving "PHXSERVER" back to the SBS server.
-or-
b) the clientsetup program "setup.exe" is passing suffecient data
across the link to slow things down.

....and I suppose it could be a combination or something else
altogether.

How did you setup (/connectcomputer?) the remote clients? Can you
do a ipconfig/all from a local client and one from the remote and
post the results?

--
/kj

--
/kj

--
/kj



.

Relevant Pages

  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... We have around 17 remote sites so using a DC for each would be expensive, and I can't see a benefit at the moment. ... also the DNS server. ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)
  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... We have around 17 remote sites so using a DC for each would be ... also the DNS server. ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)
  • RE: Group Policy, Firewall and RDP - Terminal Services
    ... I tried to tel net and ping the Clients by name and IP and received nothing. ... Re Ran CEICW on SBS server and VPN connector and still nothing. ... I went into the Group Policy and enable Remote Connection, ... I did mention that I CAN Remote into the Server right? ...
    (microsoft.public.windows.server.sbs)
  • RE: Group Policy, Firewall and RDP - Terminal Services
    ... the clients cannot be connected remotely. ... How to configure Internet access in Windows Small Business Server 2003 ... Allow Remote Desktop exception. ... Microsoft Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: TS Licensing problem
    ... I don't see why my activated W2000 TS server does't ... the remote computer. ... Remote clients are W2000 Pro and XP-Pro machines. ... but it wasn't my intention to mix up CALs and TS CALs! ...
    (microsoft.public.win2000.termserv.apps)