Video Screencast Help

Deployment Server 6.9 automation task failure

Created: 20 Apr 2012 • Updated: 20 Apr 2012 | 2 comments

We are in the process of a migration from Windows XP to Windows 7. I have a DS 6.9 script task to copy drivers after the ghost image is applied. This task is failing in many instances but succeeding in other instances. The task appears to fail before it starts and gives a "Status Code" of 4. When the task is successful it works perfectly.

I have tried applying both the image task and driver copy task in the same DS job and also as separate jobs. The effect is the same - both successes and failures.

This issue has never been a problem during an XP imaging / driver copy process. The XP image was only about 750 mg compared to the 5.5g size of the Windows 7 image so I am wondering if there is a timeout issue. The ghost image task runs successfully for both XP and Win7.

We have 100 meg connections to the desktop and bandwidth tests show 45% utilization during the process. There are no errors on the DS server.

Any help will be greatly appreciated!

-----------

DS 6.9SP4

Driver Copy Script:

REM Copy Dell Desktop - Win7x86 Drivers
REM Copies Cumulative Desktop drivers into the inf  folder

if not exist "d:\windows\inf\x86" md "d:\windows\inf\x86"

xcopy /S /I \\nt18\express\Desktop\Windows7\Win7_Drivers\DellDesktopDrivers\x86" "d:\Windows\Inf\x86"

Comments 2 CommentsJump to latest comment

Mistral's picture

The status code of the script task is the return code of the last command (xcopy).

http://technet.microsoft.com/en-us/library/bb49103...

4

Initialization error occurred. There is not enough memory or disk space, or you entered an invalid drive name or invalid syntax on the command line.

So maybe its either really the disk space, or xcopy cannot access the file share, or the D: drive (do they have one?).

Greg Englund's picture

Thanks for your response.

After the Windows 7 ghost image is applied to the drive there are 2 partitions that the Windows 7 installation creates: a small unassigned system partition and the OS/boot partition. When it boots into Windows 7 the small sysem partition remains unassigned and the OS/boot partition is C. However, in the WinPE session the OS partition is seen as D. That is why in the script the drivers are copied to the D: drive while in WinPE. There is plenty of disk space since on that drive since it is, by default, the primary partition.

The image file is accessed from the same network share and it is successfully processed. The script task to copy drivers does not even appear to start. There is no command screen displayed and the first line of the script is not processed.

Since the whole process completes successfully in many instances on the same machine types, I don't think it has anything to do with the tasks themselves.

Is there a possibility that the script task uses a different port than the imaging task? Are there additional ports that need to be opened on the routers?

 

Greg Englund

Clark County Infrastructure Services

Clark County, Washington