How are you accessing the Ghost program and Image file in your Deploy Image Step?
We don't use Ghost anymore but for imagew (landesk app) you need to map a drive to the LDMain share and another drive to the Image share. Then when you deploy the image you use the drive mappings. If you map the drives you can then specify the credentials needed to access the files.
For example: Add action, Give it a name - Map Image drive, Type = Map/Unmap Drive. OK. Select Map drive as operation type, Enter the UNC path and a drive letter you want to use. We use I: for the images and L: for the LDMain share. Don't forget to fill in the DOMAIN\username and password for the share.
Repeat for the Ghost imaging software share.
When you deploy the image don't use UNC but use the Drive letters you have just defined.
When I created the deploy image step I just told it the location of my previously created image and ghost32.exe. I figured that as the PXE boot was authenticating to the core server which contain these that I would not need to map a drive.
Looking at what you have suggest can see how that will work, I just thought the PXE agent would have been more intelligent than that seeing as it has already spoken to the Core server.
Thanks for your help
Im now getting an error when trying to Map_drive
return code is:67
Is there anywhere I can find a comprehensive list of these error codes?
I dont know of a comprehensive list of codes.
When you get the error code go to the machine being provisioned and start a new console. On the client, in the WinPE environment the provisioning log is located in the x:\ldprovision directory. Use the notepad comand to open it. (notepad x:\ldprovision\ldprovision.log)
There is also another log to check at file://%5C%5Cyourcoreserver%5Cldmain%5Clog%5CProvisioning. This may also give some useful information.