WinPE - Automation - Copy File To

davestrachan's picture

Hi,



I was hoping someone could help me with the issue im having.



Im trying to run a "Copy File To" job against a system that is in WinPE2.1.



Anything I try to copy it with a destination of "c:\" will come back with...

Status: "The system cannot find the drive specified."

Status Code: 15

Module: Win32



I have a vbscript that runs before that creates the "C:" for me.



I have noticed under "properties > drives" nothing is listed and belive this could be the issue.

This is still the case even after I run a "Get Inventory".



Has anyone seen this before?



Cheers

Dave

Richard Taylor's picture

Dave,

have you checked using a disk utility you've actually got a live partition there to write to mate? sounds like it's missing... r

davestrachan's picture

Hi ricodjs,



Thanks for the reply



Just to let you know, the partition is getting created. I can use diskpart inside winpe to see this.

I can also change to the c:\ itself within the winpe command prompt and create directorys and files.



Cheers

Dave

jdan's picture

As an alternate, you could try using a script task, and use the FIRM utility which comes with DS. This is a utility that can read and write files from/to file systems. Or what about using a script job, and just use a DOS COPY command?

drumgod1's picture

quote:
Originally posted by: jdan

As an alternate, you could try using a script task, and use the FIRM utility which comes with DS. This is a utility that can read and write files from/to file systems. Or what about using a script job, and just use a DOS COPY command?




As far as I know, with WinPE, you can't use FIRM copy commands or DOS scripts while in it. We were going to switch to WinPE from DOS BootWorks, but I have several scripts that needed to run before WinXP got to the mini-setup (where it loads hardware drivers, names the computer, and joins the domain). We have scripts to FIRM copy AClient to the computer, a Sysprep Token Exchange to rename the computer and join it to the domain, plus a Run Once command included in the SysPrep to install AClient under the Admin account & reboot the computer. Those scripts don't work under WinPE. There are other ways to get around this by including AClient in your image, but we didn't have time to change the entire way we do things just to get one model of computer to image from a specific deployment server. We created a work around.



I would like to get into WinPE a bit more, but I don't know if we'll have time before our licensing runs out this summer. Symantec has changed our licensing to be per user instead of per machine and I work for a school district with over 24,000 students and staff. This can get VERY expensive, plus they've raised the prices on their maintenence fees. It seems like anytime Symantec buys a great company, they make changes in the software or licensing that make it hard to continue using the product. Sorry for the rant. I just remember the deployment console software being more stable before Symantec bought Altiris.



Mike