Re: SBS2003 Client Setup Wizard Problem



Hi Merv and Shawn,

I wanted to let you know I finally found a work around.

I WAS NOT happy with adding users to the local admin group even for first
logon. Talk about alot of extra work!!! I have 75+ user that can login to any
machine at any time. I wouldn't know who and when to remove from the group.
The other reason - If I made even a small change to the script the users
wouldn't receive the change because they would no longer be in the local
admin group so the script would not run.

I knew there had to be a way to make this script run with only user
permissions because so many of my computers were working correctly and only a
few were not.

So the work arounds:

XP - make sure the users have "write" permission to the Windows\Temp folder

Vista - HKLM\Software\Microsoft\smallbusinessserver
Give users modify access to this key.

The scipts runs perfectly now on both machines.



""Shawn Shao [MSFT]"" wrote:


Hi Nick,

Thank you for posting here and also Merv's input!

From your post, I understand that domain users receive the following error message when some workstations logon
domain.

"Client Setup Wizard: The System cannot copy a file from the server to this computer. Make sure that the network cables
and devices are plugged in and functioning properly, and then try again to join this computer to the network."

For Vista machines, they will ask for User Account Control for permission to connect to the domain. If we grant the local
admin permission, the script runs successfully on either XP or Vista. If I am off base, please don't hesitate to let me know.

Based on my experience, when creating a SBS domain user account, there is option to create client computer for this user
account. If you do so, this user will be added to local admin user group on the client computers. Thus, this user account can
install software deployed by Client Setup Wizard. On the other hand, other accounts will not be added to local admin group
on this client.

By default, to run scripts or install software, local admin privilege is required. Thus, if you would like to install applications
under specific user account, you may need to add it to the local admin group first. I also suspect this issue can be related
to the programs installed on the different computers. If related programs have been installed properly. That's no need to
run the script, thus, no error will be encountered.

Some other troubleshooting steps for your reference:

Step 1: Based on my experience, the issue should lies in that there are two duplicate entries in the
SBS_LOGIN_SCRIPT.bat file. By default, it should be only one command \\SERVERNAME\Clients\Setup\setup.exe /s
SERVERNAME in it when you open it with notepad.

If there are two duplicate entries in the SBS_LOGIN_SCRIPT.bat file, please remove it from the SBS_LOGIN_SCRIPT.bat
file, and then logoff and logon the workstation to see if what happens.


Step 2: Manually run <\\servername\Clients\Setup\setup.exe /s servername> on one problematic workstation, do you
receive the error message?

Note: Please replace the "servername" with the valid server name in your side.

If there is any update on this issue, please feel free to post back.

Have a nice day!

Best regards,

Shawn Shao
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.



.



Relevant Pages

  • Re: Granting Domain Users Local Admin Rights
    ... login is added to the local PC with administrator rights. ... haven't been added as a local admin for local admin rights are ... Add the Interactive Users group as to the local admin group ... conference room computers and training room computers usually include ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Client Setup Wizard
    ... I'm running into a problem on about 4 of the computers. ... At Login (when client setup wizard script runs) on only a few of the ... If I change the the user to a local admin then I don't receive the ... Making users part of the local admin group is unacceptable. ...
    (microsoft.public.windows.server.sbs)
  • Re: Client Setup Wizard
    ... I'm running into a problem on about 4 of the computers. ... At Login on only a few of the ... If I change the the user to a local admin then I don't receive the ... Making users part of the local admin group is unacceptable. ...
    (microsoft.public.windows.server.sbs)
  • Re: Clip Art Error 0x8007000E Not enough memory
    ... I added them to the local admin group. ... > downloading these two files and installing them onto ... > I am able to insert Clip Art when I login to the TS ...
    (microsoft.public.windows.server.sbs)
  • Re: admin group in OU - help please
    ... Please do not send e-mail directly to this alias. ... > is not in a Local admin group the i get script error: ...
    (microsoft.public.win2000.security)