I may have just beeing doing something wrong. I was able to get it working. I feel stilly now. :-(
Hi, I just migrated to Landesk 9 and have the same error.
What did you end up doing to fix the problem? I`ve been scratching my head for two days now.
For people that fall on this posting with the same problem.
In LD8.8 our jobs used a custom sysprep.ini and we used "ExtendOemPartition=1"
When we migrated to LD9 we just copies what we were doing in LD8. LD9 has a command to extend the partition before the first reboot right after the image has been copied to the hard drive.
So the solution is to either remove the ExtendOemPartition=1 line in the sysprep.ini or REM the extend command in Advance Edit. " ;REMEXEC44=ldrun diskinfo extend_last_partition"
Hope that helps someone.
Thanks for this post - I have been banging my head against the desk for a couple days now as well. I tried just about every thing I could think of mass storage driver wise and nothing.. Bios tweaking you name it. I rememeber using the bios compatibility mode in MDT and SCCM.. Figured Landesk had some sort of "magic" built in to solve this issue but couldnt put my finger on what it was. So THANK YOU for this. Glad Im not the only one
One last tib bit for any one else that stumbles onto this post
If you want to use "ExtendOEMPartition =1" in you sysprep ini then absolutly make sure you install this hot fix before you sysprep you unatteneded image. This is another work around to this issue