We have a new Lenovo ThinkStation S20 that is giving us some problems with OSD. In approximately 6 attempts to run our OSD task we have had only one success. The OSD task runs ok on other machines.
Analyzing the failures I found that they all gave a Return Code of "-85" and the LANDesk OSD job showed a result of "Unknown status code (0x8DB9FFAB,3513:65451)".
The task log was very brief...
"23050254SW13153","OK",0,0:00:00,8/3/2011 1:29:14 PM,8/3/2011 1:29:14 PM,"WINPE, TIMEOUT=1800"
"23050254SW13153","ERR_Fail",-1917190229,0:02:00,8/3/2011 1:29:14 PM,8/3/2011 1:31:14 PM,"ldrun drvmap.exe psd70ad\ServiceAccountX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX I: """\\2305deploy\deploy$""", STATUS FACILITY=3513"
; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"
I eventually realized that the OSD task is failing because the Drive letter "I:" is already in use - this computer has a built in Multi Card Reader that in WinPE is using drive letters F: G: H: I: and J:.
My question is - should I edit my OSD scripts so that they use different drive letter mappings, or is there an easy way to make my scripts work with the default mappings of "H:" and "I:"? To put it another way, can I modify the PXE environment so that it always reserves Drive H: and I: no matter what devices are found on the computer? (My problem with editing the OSD scripts is that the whole problem could come back if we receive another new computer model with even more storage devices. I suppose I could choose a really high drive letter for my OSD scripts like "X:" and "Y:".)
If anybody has experience with this problem I'd be glad to see your solution or workaround. And if anybody comes across this thread because OSD is failing with Return Code "-85", then check in your Win PE boot and see if drive H: and I: have been used by a storage device.