1 of 1 people found this helpful
Rem out the reboot command at the end of your OSD script and try again. While under PE open a command prompt and see if you can view the C: drive. My guess is for whatever reason is it can't see the C: drive.
If you can see the C: drive check to see if c:\unattend.xml exists. You can also try to run the command manually to see if an error message is displayed.
"ldrun sdclient /f /o /dest="C:\unattend.xml" /p="http://coreserver/LANDESK/FILES/E6320%20-%20Win7x86%20GMBH%20-%20Deploy.xml" /attemptpref, STATUS"
Also from a windows machine, try browsing to the xml file in a web browser"
http://coreservername/landesk/files Make sure you can see and download the xml file from a machine in the same area.
That is correct, when I tried navigating to the C drive afterward in a command prompt, I could not (the reboot would not happen after this failure, so I was able to get some of the info I needed). I will try to download the answer file manually and see what I get, then I will post results. Thanks for the reply.
Well I tried navigating to the URL to download the XML file and was able to do so. I suppose the reason it is failing is due to a couple actions prior to injecting the XML since it is not able to get to the C drive. I did notice on the previous line, that fixwindows.exe returned a "1" exitcode rather than the typical "0" for success. I am just not sure what .exe is responsible for each action required to set the drive up.
I am running into the exact same issue. Did you have any luck?
I can't remember anymore what the issue was. But I think I may have had to re copy the image over, and/or resave the OSD script. Some of the first things I would check:
- Make sure your WinPE image has all the proper drivers for your SATA controller (usually extra drivers are not needed for the drive controller though)
- Make sure you re-save your OSD script after copying over an updated image (it keeps some sort of hash on the files or # of image files when saved)
- Verify your credentials are correct throughout the script (this has threw me for a loop several times due to fat fingering passwords)
- Make sure your client is able to download preferredservers.dat onto the X drive locally (can't remember what subfolder it is, maybe search through it), and to a "type" on that file to make sure it contains the proper host in there.
- Try your OSD script on a seperate computer to rule out hardware issues.
- Try your OSD script on your local site with an alike computer to see if the same problem happens
Anyway, hope that helps. Good luck.