Did it ever work before?
Does it create a log in
Are you using WinPE?
The deployment use to work before , but from past few days its not working. I am using WinPE for Windows deployment.
Some logs are showing and some logs are not i.e. if i have tried deploying the images on 6 machines simultaneously than log of only 4 machines are shown.
What does the log say? any errors? Is it executing anything?
1 of 1 people found this helpful
Check your deployment log. If the log reports the machine is off, then your inventory service is either behind, or your computer is not sending a scan in to "check in" with the core server.
You can try restarting the inventory service.
From within WinPE you can open a console and type winpeshl and push enter. This will initiate another inventory scan and bring up your pxe boot menu again.
You can also simply type pxemenustart to just bring up the PXE boot menu.
Check those logs and give us some more info though.
I have attached the logs.
Let me know if any other settings have to be done.
what's happen if you start your installation manually in WinPE? Does the command line work?
I've a bit problems with this line
"RunBatch -1 h:\osd\imaging imagew.exe /RN /O i:\OPERAT~1\Marsh\-IMAGE00.IMG, STATUS FACILITY=3510, SYNC"
Did you test another filename (without the minus symbol) and did you test a other path?
Is your share reachable?
Did you read this documents:
You will want to run the following command line in WinPE:
<RunBatch -1 h:\osd\imaging imagew.exe /RN /O i:\OPERAT~1\Marsh\-IMAGE00.IMG
The STATUS, FACTILITY and SYNC commands are used by the LANDesk scripting code and are not valid commands in WinPE.
Here's a helpful tip for troubleshooting OSD scripts.
1. Open the script in Advanced Edit through the console.
2. Go to the end of the script and place a semi-colon before the line that contains the reboot action and save the change.
3. Run the script on the client machine. It will still fail, but it will leave you in WinPE to be able to take a look at serveral things.
Make sure that the I: and H: drives mapped successfully by running a net use command. You can manually run the imaging command line listed above, or you can call imagew to launch the GUI and follow the steps to restore the image. Check to make sure that both sharing and NTFS permissions have been allowed for the specified account in the script for both the I and H drives You will need at least write access on both shares.
In my case inventory server was stopped.
So what happened LANDesk had wring IP for this MAC address. So search MAC address from that PC in landesk and see which IP it have in LANDesk.