RE: server/connectcomputer from remote offices

Hi Brandy

I think I may have been misunderstood.

The SBS server is in Location A
I have a replica w2k3 std server config'd as a dc in location B
Also, I have a number of client workstations in Location B

We can connect the workstations in Location B to the sbs domain with no
problem. We are able to log on the users of those workstations also, no
problem, not slow...

What is actually a nuisance, is the default logon script runs as that user
logs on. That's fine, but, as the first line in the script is:

\\serverinlocationA\clients\setup...... etc it means that the whole setup
executable has to be pulled down across a relatively slow vpn link, therefore
it takes a while for the cmd window to disappear...

You have already made clear why this script needs to run, in terms of client
set up etc.

To resolve this issue, I have enabled replication of the clients share
across to the server in location B as well as the one in Location C
This is now accessible via \\domain\dfs\clients....

I have checked that the workstations in Location B are logging onto the
local dc also.

As setup.exe configures outlook with the exch server account, the reason it
wasn't is that we were not allowing enough time for the setup.exe to run all
of its processes. Again, it is taking a while because of the relatively slow
VPN.

What I am actually trying to achieve is for those workstations in Location B
(and C) to look towards a local server for setup.exe and all of the
clientapps. This I feel is best achieved via the dfs and frs.

I still do not know what servername on the end of that line means.. should
it point to a domain as suggested here:
http://msmvps.com/bradley/archive/2005/03/15.aspx

Thanks for your posts, and apologies for my lack of clarity!

Ian

""Brandy Nee [MSFT]"" wrote:

> Hello Ian,
>
> Thank you for posting back!
>
> I am sorry that I am not sure why you plan to modify the SBS_LOGIN_SCRIPT.
> I wonder whether this is because you have concern on clients' slow log on
> domain issue. If this is the case, I suggest that we perform a test to see
> whether slow log on issue comes from the SBS_LOGIN_SCRIPT. To do so, please
> see:
>
> 1. Expand to Server Management\Standard Management\Users.
>
> 2. On the right panel, right click one problematic client account who is
> experiencing slow log on issue.
>
> 3. Go to Properties, Profile tab.
>
> 4. Delete the Logon script.
>
> 5. Ask the user to log on domain again to see whether the issue will be
> solved or not.
>
> Actually, DFS uses FRS for replication, and FRS is a multi-master
> replication method. So users can access shared folders locally.
>
> I suggest that you go to one problematic client workstation, and SBS
> Server, open a command window, type "ipconfig /all" (without quotation
> marks), copy and paste the full content to the Newsgroup.
>
> [Note]: Please do not edit any result.
>
> Please take your time to perform the steps above and collect the
> information for us to troubleshoot your issue. I am looking forward to
> hearing from you!
>
> Best regards,
>
> Brandy Nee
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> --------------------
> >Thread-Topic: server/connectcomputer from remote offices
> >thread-index: AcXvXoRTBhHVIY3nQaS/Bz8t5YrN1Q==
> >X-WBNR-Posting-Host: 194.164.243.133
> >From: =?Utf-8?B?bW9vc2hjYWNh?= <mooshcaca@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <1131736669.607227.8210@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> <1Re6KSP6FHA.3796@xxxxxxxxxxxxxxxxxxxxx>
> <055EB71C-B832-47B4-AD25-6AF01F764517@xxxxxxxxxxxxx>
> <fjmIY9m7FHA.832@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: server/connectcomputer from remote offices
> >Date: Tue, 22 Nov 2005 04:16:07 -0800
> >Lines: 168
> >Message-ID: <02F795D8-2006-4CE4-8DB6-5CC48CFEE9CD@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:224586
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi Brandy
> >
> >I have enabled DFS for the setup folder, which is replicating across the 3
> >dc's.
> >I will be modifying the logon script to point at
> >"\\domain\dfs\clients\setup.exe /s servername"
> >
> >I have not done this yet as I am not sure what "servername" on the end of
> >the line actually does...
> >
> >I will also be replicating the clientapps share, though I have not
> completed
> >this yet.
> >
> >Just to clarify, the second issue raised at the beginning of this thread
> >will be resolved by getting the above correct...
> >
> >Thanks for the links :-) they were very helpful in getting the dfs up and
> >running.
> >
> >Ian
> >
> >
> >
>
>
.

Relevant Pages

  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)
  • RE: (Very) Slow browsing server shares - Net Work Monitor shows ca
    ... If this issue happen only when browse shared folders on SBS from one XP ... client computer, this will be a client side error. ... click to check the "Hide All Microsoft Services" ... Digitally sign communications (if server ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... internal client Remote Desktop via RWW. ... Please perform the steps on the SBS and internal client computers: ... Click Remote tab, tick Enable Remote Desktop on this computer ... On the SBS server, click Start, click Run, type "regedit" (without the ...
    (microsoft.public.windows.server.sbs)
  • RE: trouble with shared fax service
    ... Thank you for posting in SBS newsgroup. ... install fax service on client computers. ... the SBS server or on the client workstation. ... and then choose 'Install' for the 'Fax Services' item. ...
    (microsoft.public.windows.server.sbs)
  • Re: Small Biz Design
    ... After we installed SBS 2003 successfully on the server box, the Client ... >When we setup SBS 2003 server using installation disks, ...
    (microsoft.public.windows.server.sbs)
Loading