Error message from Client Setup wizard when new user logs on to client computer

[MobileMemory]

We have SBS 2003 recently patched to SP1. We have created a new user and have tried to log him on to a client pc (XP Prof' SP2). When we do this we are seeing the following error. Any ideas.

"The system cannot copy a file from the server to this computer. Make sure that the network cables and devices are plugged in and fuctioning properly and try again to join to this computer network"

many thanks in advance.

Sam

From your post, my understanding on this issue is: the new user gets the
following error message when he wants to log to a workstation:
====================================
"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 try again to join to this computer network"
====================================
If I am off base, please feel free to let me know.

As for the error symbol, I would like to suggest that you try the following
method first and see if the issue resolved:

1. On the SBS server, open Windows Explorer and go to C:\Program
Files\Microsoft Windows Small Business
Server\ClientSetup\Clients\response\<clientcomputer>.

2. Open the apps.dat with Notepad. This is actually an XML file.

3. Find the app id "{F28193FE-08F8-4eae-B714-D425838F46FE}", then note down
the value of the associated attribute "refcount".

4. On the Windows XP client, click Start, click Run, type "regedit" and
click OK.

5. Locate the registry key
HKLM\Software\Microsoft\SmallBusinessServer\ClientSetup, double-click
{F28193FE-08F8-4eae-B714-D425838F46FE} in the right pane, and change the
data to the value of "refcount" that we get in step 3.

If the registry value {F28193FE-08F8-4eae-B714-D425838F46FE} doesn't exist,
manually create it:

Value name: {F28193FE-08F8-4eae-B714-D425838F46FE}
Value type: REG_DWORD
Value data: The value of "refcount"

If the issue persists, please perform the following test on the client
workstations:

1. Please manually run <\\SERVER01\Clients\Setup\setup.exe /s SERVER01> on
one client workstation, do you receive the error message?

2. If we can not reproduce the issue by manually running
"\\SERVER\Clients\Setup\setup.exe /s SERVER", please insert a "pause"
before the "\\SERVER\Clients\Setup\setup.exe /s SERVER" command in the
\\servername\sysvol\<domain>\scripts\SBS_LOGIN_SCRIPT.bat, so that we can
start File before the logon script actually runs. Sample
SBS_LOGIN_SCRIPT.bat:

pause
\\SERVER01\Clients\Setup\setup.exe /s SERVER01

3. If user received the error message, let's use Filemon to determine what
file is failed to copy.

Please create a folder on your desktop, download Filemon from
http://www.sysinternals.com/ntw2k/source/filemon.shtml to the folder.
Launch Filemon, reproduce the issue. Once you get the error, click the
small magnifying glass icon to stop the capturing. Next, go up to File ->
Save and save the log. Save it with a .LOG extension.

Please send to the filemon log to my working mailbox:
v-stezhu@microsoft.com.

Also please help me collect the following information:

1. On one client workstation, run "ipconfig /all", are they pointing to
only the IP address of the SBS internal NIC for DNS? Please run the command
on one workstation and the SBS server box and paste the output in the
newsgroup or mail it to me.

2. Please send me the SBSClientApps.log file in the "C:\Program
Files\Microsoft Windows Small Business Server\Clients" folder (on the
client) for analysis.

3. If you log on with domain admin account on this problematic workstation,
will the issue occur?

Please send all files to my working mailbox: v-stezhu@microsoft.com.

Hope above information helps. I am happy to be of assistance to you and
look forward to your reply.

[MobileMemory]

This has now been resolved. it was due to firewall issues.

Many thanks for all your help.

Thanks for your efforts on taking time to let me know that this issue has
been successfully resolved. I am very glad to hear that. Your cooperation
and efforts on this issue are very much appreciated.

Should you have any other technical questions in the future, please don't
hesitate to let us know by posting in our newsgroups. It's always our
pleasure to be of assistance.

[bysizsols]

Hi guys,

Sorry for bumping such an old thread.

I'm having the same error, but here it is on most (if not all) of the PCs in the company.

I followed Steven's steps above. The client's F28193FE-08F8-4eae-B714-D425838F46FE registry key already has the correct value (which is 1, the same as the refcount on the server).

I followed the additional steps, and the one that worked for me was putting a 'pause' line in the logon batch file. That stops the errors, but it requires users to press a key (which they'd rather not have to do). To try and avoid this, I've tried, in place of 'pause', different commands to add a delay. I've tried 'ping -n 30 -w 1000 0.0.0.1 > NUL' and 'choice /d y /t 30 > nul', and even with a 30 second delay, I still get the error messages after that 30 seconds.

Does anyone know why 'pause' works, but neither of the other commands do? Is there another command I can use?

I'd be very grateful for some help on this.

Kind regards,

Aaron

The "sleep" command may be an alternative.

Implementing the WAIT Command in a Batch File
http://malektips.com/dos0017.html

Batch file SLEEP Command
http://malektips.com/xp_dos_0002.html

Windows Server 2003 Resource Kit Tools
http://www.microsoft.com/downloads/d...DisplayLang=en