Imaging -- Error:Invalid image file or file not found
Submitted by DParent on 18 July, 2008 - 11:59.
I had to reinstall Deployment and PXE Server. I recreated the PXE boot file. I can PXE boot my workstations, but when I try to run an image job I get the error: "invalid image file or file not found." The the workstation just does a continous reboot till I turn it off. I have all the right drive mappings setup in the PXE config utility. I imported my jobs from when I used to be able to image. So I know that is setup correctly.
Any ideas on this would be greatly appreciated.
hum...
have you tried browsing to the image file while in PXE to verify it is in the same location the job is pointing to? You can run a wait command for that PXE option and it will stay in PXE until another job is run or the computer is rebooted.
In the past I had the same
In the past I had the same problem , after some tests I found the problem was related to the wrong remote shared folder where was located the image.
No Luck
I browsed to the location. reconfigured diiferent drive mappings, still no luck. I am baffled by this one.
I did see that I am getting the drive letters when the workstation is booting up by going into the diagnostics menu. I did get the drive letters. But as soon as I execute an image job, that is when it fails.
Did you try to run the
Did you try to run the Rdeploy.exe manually ? For this test you have to add the wait or other command to breck the imaging script, after run the .exe by the right location.
My two cents
I also have run across this problem a couple of times:
* Once the resolution was a corrupted job after it had been imported. Basically recreate your job and each task within.
* The other time there was issue with PXE redirection and the shared drive letter not being correct. Check and double check shared folders and drive letters.
Another possibility did you move/copy your image file to a different location. I have also seen corrupted image files as well.
Good luck!
Fixed the Invalid image file error
RDploy worked.
So I ended up checking the config settings for DS in the control panel. I needed to setup the drive mappings there. When I reinstalled DS it wiped them out.