1 of 1 people found this helpful
Hi, if you look in the
coreserver\ldlog share you should see a log called CJ-OSD-SCRIPT NAME.LOG. If you can please post the log here. Also, check that you have an ip address and that the WinPE image is seeing the hard drive of the machine.
From a new console cmd window run an IPCONFIG. If you get an address then its ok there. Then type in "diskpart.exe". Once it loads, type in "list disk". It should come back and say disk 0 online XXXgb. If it says No fixed disks available then you need to use the Driver Injection Wizard from the console and install the SATA controller drivers into the WinPE image file.
Thanks for the quick response.
"AMADEUS","OK",0,0:00:00,4/30/2008 1:13:50 PM,4/30/2008 1:13:50 PM,"WINPE, TIMEOUT=1800"
"AMADEUS","ERR_Fail",-1917191470,0:02:03,4/30/2008 1:13:50 PM,4/30/2008 1:15:53 PM,"drvmap.exe Landesk\brandon.crowe 2090E686474A4943C401105D5A64E481D3C18757C20 I: <qt/>
Landesk\ldmain<qt/>, STATUS FACILITY=3513"
; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"
Thats the text in that file you wanted me to paste in. As far as IPCONFIG and the diskpart, both of those look good to go.
Anymore help would be greatly appreciated!
We typically see this when there is something amiss with the user\pass that has been entered for the OSD script to use. Try the following:
Check the following in the script GUI (right-click on OSD script and choose Edit):
1. Verify that the credentials entered are correct for the type of account:
a. If the account is a domain account, then the domain tag must be provided with the user account in the script.
For example: mydomain\myaccount
b. If the account is local on the core server or file server, then make sure there is no domain tag.
2. If the password has changed on the account, update the password in the script.
3. Verify the account has been added to the Sharing and Security permissions on both the image share and the tools share.
4. Recreate the capture/deploy script and add it to the PXE Boot Menu tab.
5. Verify if there are any hardware devices on the target machine that may already be using the I: or H: drive.
Essentially, what is happening, is the script is attempting to create a mapped drive (I:) to the
landesk\ldmain share and this process is failing. This is usually an incorrect password or invalid permissisons issue. The key with the permissions is that both the sharing and security permissions should explicitly allow the specified account. Additionally, instead of using your personal account, you may want to create a service account for use with OSD as you will need to update all scipts any time your password changes.
I put down the landesk core server name instead of my domain name.... /shame mode
thanks for the help guys!
I am having the same issue, but have not been so lucky. I have a valid IP and it finds the HD, but nothing happens for my Optiplex 755.
If anyone can help, here is the log file from my capture:
"(OFF) 00217044D559","OFF","N/A","0:00:00","10/9/2008 1:12:39 PM","10/9/2008 1:12:39 PM","N/A"
; "Job Complete","0 Done","0 Failed","1 Off","0 Unknown"
Please verify that that LANDesk Inventory service is running on your core.
Thanks, I will hopefully have an answer tomorrow. We just deployed a core server in the DMZ and I believe the Security Team missed some UDP ports.
They are updating the FW rules tonight so I can test again in the morning.