Did you edit the ini file after creating it in the console?
It looks like you need to put in the proper mapped drive for the image. I believe that LANDesk defaults to H for the imaging tools, and I:\ for the images.
in my case:
REMEXEC22=h:\2.0\imagew.exe /r /o /d:4 /f:"i:\HP\HP.TBI" /rb:0
when you are in WinPE, open a new console and try to access the I:\ drive and see if your images are listed.
Unless you changed the drive mapping to G:\, you shouldn't have anything in WinPE when you try to access the G drive.
ewade is correct. The error message is sort of bogus (unable to obtain lock).You normally get this on the drive you are trying to backup/restore and imagew can't obtain exclusive access to the drive. I think it is getting confused since g: is not /d:0. One thing that can help you when you have issues with v2 is to gen a log file:
Thanks for the info, I'm a little confused now, this is using multicast:
I boot a number of laptops into managed WinPE, then target the machines with a deployment task. Once it starts, I get a "Multicast software distrobution" window, and it appears that its just copying the image to.. somewhere. (Where would that be exactly?)
When the job fails, I can pull up a console on the machines to be imaged and when I change to drive G:\ and DIR, I see my image. I never set it up that way, I was under the impression that the image file was copied locally then used locally by imagew.
Not multicasted in a long time but you are correct. It copies the image locally then images from there. So try the log file entry above and see what it says. It appears that something is preventing imagew from getting exclusive access to your image file.