Deployment Solution

Greetings,

I'm in need of assistance as this has me baffled.

We are running Altiris 7.6, and WinPE 3.1.

The goal is to use one image for different systems (over 15 different types). We have an image sysprepped and had all local drivers installed originally on the image, but the driver pool was over 21 Gigs and it is growing. The goal is to have specific drivers copied over to the systems once the image is dumped onto the hardware.

I'm currently booting via a bootable USB key with the automation folder on it. I've been hitting a wall trying to copy drivers down from the DriverDB onto machines I'm trying to deploy.

I've tried the built-in copy with no sucess. The task will just time-out. I've tried replacing the Copy File function with just a standard xcopy script with no sucess either. Please note that I'm copying the drivers on the D:\ as the C:\ drive is the reserved partition. On bootup, D:\ becomes C:\

Above is an example of one of the copy file formats I tried. Is there a limitation of characters for the path to copy the files?

Example above had the username (to try and prompt for a password with no success)

Another example that shows one of my scripts using my username/password as part of the "run as"

Both tasks have been set to run with my admin account.

I've trolled the forums here trying various things with no sucess. I'm now at the stage to try and map the network drive where the driverdb resides but even this is a fruitless exercise. I can't seem to find information on how I can modify the startup.bat file for the automation system.

Just to be clear, that if the system is in Windows, both the copy file / xcopy work really well. But I need this to be done just after the image dump as when the sysprepped image boots up for the first time, it's trying to find drivers that are not at the location I have specified in the registry to look for.

Any help would be greatly appreciated!

Luc (Luke)

When you are running the task in WinPe, you can't specify any user to run the task as.

The task needs to run as system, cause in WinPe we do not have any users.

Indrek,

Thanks for the info, but how can I connect to the driverDB on the network? I still need to have it mapped in the script correct?

If I use the built in Copy File function, it asks for network credentials, so that option is completely off the table wihile in the automation system?

Indrek,

I think I got it to work.

I was able to run the task (I enabled the task to be visible in the intintial deployment menu) having it set to run as the Symantec agent, and then using the net use command (as per my second screenshot).

Now I just have to try it all bundled up (fortmat a drive, deploy the image, then copy the drivers, then reboot to production). 

Hi Luc, just wanted to share this link that might help you?  Our driver share exists on the network and gets copied to the workstation in automation depending on model.

https://www.symantec.com/connect/articles/simple-alternative-deployanywhere-hardware-independent-imaging-drivers