CauseImage tool path incorrect
or could be disk spaceResolutionIn the Capture script (edit), do the following.
- Go to the Image Information
- Look at the Image Type
- If this says LANDesk ImageW V2 look at the UNC path to the imaging application and verify that it is \CoreServer\LDMain\OSD\Imaging\2.0\Imagew.exe
Check for enough HDD space to store image.
Like Ty mentioned it could be a storage issue.
Looking at the log
"002170C74EE5","OK",17,0:00:05,1/5/2009 3:41:35 PM,1/5/2009 3:41:40 PM,"H:\osd\imaging\2.0\imagew.exe /b /uy /d:0 /rb:0 /max:2GB /f:"i:\LD002170C74EE5""
this line took 5 seconds to run. the most common reason for this is either it can not read the H: drive to start the image tool or it can not write to the I drive.
To test this REM out the Reboot line with a ; (place the semicolon infront of that line)
Rerun the script yes it will still fail but the machine will not reboot. After it flashes and is done open a console window in WINPE change to the H: drive can you do a Dir? Change to the location of imagew.exe can you see it?
If yes to both change to the I drive. If no it is a permission issue when mapping that H: drive.
Once in the I drive try to make a Directory if it fails adjust permission until it works. Also you can check available space.
If both mapped drives are working fine next step would be to run the imaging line manually. If it fails what error does it give it you?
The plot thickens!
* I've freed up about 30 GB on the drive. It had about 10 previously.
* I have checked the H and I drives. Both are accessible, and I can write to the I drive. I am using the domain administrator as the authentication username and password.
So, I decided while the console was open to go to the 2.0 IMAGEW and run it. As I began, I got this message:
LanDesk OS Deployment (2.15)
It appears that you do not have the proper authority to access the hard drives.
Please note that you must run this program with the administrative privileges for the local machine.
You can do this by right-clicking the program icon and selecting "run as"
Where should I go from here?
... and this appears to hit to the real problem. It can't find the hard disk. Looks like I need to find a driver for it.
Yes WinPE also needs drivers for the hard drive.
Here are some examples: