What version of LANDesk are you running?
The "quick" answer is that we pull the device name out of the database.
Not having much informatoin on this, I'm assuming you're talking about a SYSPREP OSD image? In that case, the mini-scan (IP address, MAC-address) is used to determine the devicename. I.e. "He who hath this MAC-address is the devicename we'll use".
That's the short of it.
Bit more context and such would be helpful - such as the LDMS version you use (/what service pack you're on), and generally a bit more of a description as to what's going on exactly.
- Paul Hoffmann
LANDesk EMEA Technical Lead
Yea what Paul said.....
Once you boot the pc with PXE boot, and get the OSD menu, click on Go (lower left corner), and select new console to get a dos prompt. Run an ipconfig /all to get the MAC address, use this to search in LANDesk to find and then delete it. Then try the OSD option. Good luck.
We're using Landesk version 220.127.116.113. Did the ipconfig already, searching in Landesk for the device using both MAC and IP address and nothing comes up, otherwise I would have tried to delete it. But in the log itself it is pulling the hostname for the MAC address from somewhere else. Again, when I get to the PXE menu, I would select the OSD I want, the menu disappears, then all I see is the Landesk background and it stay in that state. I can't even remote into the computer for it doesn't even show up in Landesk either during PXE boot.
Your solution worked. My concern is that anytime the OSD process hangs after selecting from the PXE menu, you would need to delete the record from the DB and then your reimaged machine would not get it's original name. Did LANDesk ever give you any information on why or provide a patch for this?
Why you have to delete the device is a good question? Is there a task already scheduled to that device that is interfering? It would be interesting to know the root cause. Probably little is done to root cause this because the issue is such a simple fix: Delete the device and try again.
If we figured out the root cause, it might be something easier, like deleting the device from a failed task, or something that we could patch so it just didn't fail.
However, it would be quite time consuming to debug.
Fo now, you want to delete the device and then re-add it so the name will be there. Use the CSVImport tool.
Since it is only one device, you might just create a little miniscan with the mac and device name and drop it into the ldscan directory. That way you delete the device, readd the device with the correct name, and it should work.
I would have linked the CSVImport document, but it may have been removed. It was http://community.landesk.com/support/docs/DOC-1534 but that isn't working currently. I emailed the community admins and maybe the article was disabled accidently and can be restored or fixed.
I have run into this before but I was able to solve the issue by increasing the free space size of my WINPE image.
That is interesting. It may be related to an exising task. It happens in test when I'm running repeated tasks. I don't know how often but its enough to notice. In production, its not practical to run csvimport. We'll simply delete the record and have the tech rename it once the OSD task completes. We just need to add that to our process documentation.