Thank you for posting to the SBS Newsgroup.
I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
My reply is a bit long, so please take your time to read and gather the
information as required.
1> A: From the information you have applied, we cannot determine whether
the issue is caused by SBS_LOGIN_SCRIPT.bat. Since lack of detail
information, I am not sure whether it takes long time to find the
SBS_LOGIN_SCRIPT.bat or it takes long time to execute the script. So please
see my following suggestions:
1. As Windows Server 2003 has AD Replication with the SBS 2K3 Server, there
should be SBS_LOGIN_SCRIPT.bat on the two DCs for remote clients. When
remote clients log on domain, they should query the SBS_LOGIN_SCRIPT.bat on
DC not SBS 2K3 Server, unless they need to access SBS Resource (e.g.
Please check, on one client workstation behind the Windows Server 2003,
open a command window, type "set" (without quotation marks), check
"LOGONSERVER=", is it the SBS 2K3 Server or Windows Server 2003?
2. You mentioned "The login script line \\servername\client\setup.exe /s
servername takes a long time to load", do clients behind the Windows Server
2003 experience slow log on issue? If yes, which step takes more time? For
example, Applying Group Policy or Apply Network Configuration, etc.
3. I do not suggest that remove the \\SERVER\Clients\Setup\setup.exe /s
SERVER entry in the logon script. For the setup.exe in the logon script, it
generally does the following job:
a. It works with the client apps component to install default client
application assigned by the wizard on the server and presents shortcuts to
customized apps delegated to clients/Installs apps.
b. Modifies machine time sync configurations at the registry level.
c. When run on a member server it will change your default gateway setting
to that of your SBS regardless of static entries under TCP/IP.
d. In addition, the following information is also highlighted from Spec
i. Gets & checks the name that it is valid
ii. Validates the requested IP address
iii. Adds it to the SBS Servers OU
iv. Specify a static IP & subnet mask (which server, if any is DHCP is also
v. Validates the requested static IP address
vi. No profile migration to the server will occur
vii. Connected printers will be published in the SBS AD
viii. Install tsweb activex control so tsweb will work for all ts clients
I think it is not good to move \\SERVER\Clients\Setup\setup.exe /s SERVER
from all client logon script. It may have some impact on your SBS network.
2> A: For your second issue, I need to gather following information for
1. Please explain in detail "Outlook does not auto configure with the
exchange account", what is the exact symptom? What exact steps do you "add
the exchange account manually"? I suggest that you fully explain the issue
so we can have a clearer image.
2. Did this issue occur before? Did you install any updates or make any
changes on the server, recently?
3. What profile do problematic clients use, Roaming or Local Profile?
4. Does this issue occur on all remote clients or several?
5. On the problematic client workstation, check whether there is any .prf
6. On the problematic client workstation, Control Panel -> Mail -> what is
the content inside "The following profiles are set up on this computer"?
7. On the problematic client workstation, run "eventvwr" (without quotation
marks), check whether there is any error. If yes, double click it, click
the Copy button and paste the full content to the Newsgroup.
Please take your time to perform the steps above and collect the
information for us to troubleshoot your issue. If anything is unclear,
please feel free to let me know. I am looking forward to hearing from you!
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:
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
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.
Subject: server/connectcomputer from remote offices
Date: 11 Nov 2005 11:17:49 -0800
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1131736674 30251 127.0.0.1 (11 Nov 2005
NNTP-Posting-Date: Fri, 11 Nov 2005 19:17:54 +0000 (UTC)
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.6) Gecko/20050226 Firefox/1.0.1,gzip(gfe),gzip(gfe)
Injection-Info: g14g2000cwa.googlegroups.com; posting-host=22.214.171.124;
Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:221407
I have an sbs server running at HQ on subnet 192.168.20.0, 2 remote
offices on 192.168.30.0 and 192.168.10.0. Each remote office has a DC
connected win 2003 std, successfully replicating the AD. The networks
are connected via lan to lan vpns handled by the routers.
I am able to get to the connectcomputer page after modifying the ip
restrictions in iis for the connectcomputer directory. I am able to run
the connect computer which is fine.
1. The login script line \\servername\client\setup.exe /s servername
takes a long time to load, this i feel is down to the vpn. Can I move
this setup to a local share and modify the script? Can I consider
removing this line altogether following a successful connectcomputer?
2. In nearly all cases, at the remote office, Outlook does not auto
configure with the exchange account, instead the outlook setup wizard
runs, where I have to add the exchange account manually... with 20 odd
users logging into each client machine, this is obviously most
inconvenient. Is there something I am missing in getting outlook to
Any pointers would be very much appreciated..