This article should help you work through this issue. You have already completed the leg work of finding out what the controller is, now you just have to modify the .OEM and you should be on your way.
I have tried the fix in the documentation but get the same error message.
when the error message appeared i started a new console and typed in the command, Diskpart list disk and i could se the hard drive, how can this be when it says my hard disk driver is not loaded?
i can see all the volumes aswell.
Can there be something wrong with the Diskpart script that it says in the error message?
the diskpart scripts should be in x:\ldclient. Just open it up in notepad and then go through the commands one at a time and see where it is erroring out on. should point you further into what is going on...
Hi i guess you meen LDclient in the winpe image.
I got 4 files there
Which on is it?
I read somewhere on the forum that wipedisk0 should be the one?
the text in it is:
select disk 0
create partition primary
1 of 1 people found this helpful
those files are tied to OSD when you choose a script, which you are not getting that far, so the commands in question are buried in your startnet.cmd
I'm on 9.0 so it could be different, but worth a check. On mine during winpe intialization, it calls diskpart /s diskpartcheck.txt (which is sitting in x:\ldclient)
i opened that file and the only command it does is select disk 0, if that fails it gives you the error that you had stated
couldnt find diskpartcheck.txt in the WinPE image under LDclient so i injected one myself with the same syntax as u descriped, IT WORKED
Now when i see the PXE boot menu and choose either capture or deploy the menu gets stuck and closes then nothing happens and the only thing i see is the Landesk PE background :/
Im using imageX for deploy, becouse of the image is of .wim standard.
looks like you are making progress...have you checked the logs and see where the job is halting at? \\%core%\ldlog would be where they are.
the logs say nothing really.
This is from a deploy:
from a capture:
I think there is something wrong with the mapping to the search path, when i use the command net use it says:
New connections will be remebered
There are no entries in the list
But when i booted into WinPE menu via PXE boot i choose my capture OSD script press enter nothing happens but when i then schedule the OSD script in a landesk console and start it againt the same machine the capturing begin. (this at the same time the pxe boot menu dissapears, so the computer is in some kind of "waiting for command" mode)
Seems like theres something wrong with a script or something.
When i boot into the manage WinPE menu and deploy the imaga via a LD console i get this message in the log
"0019B92F5D18","OK",0,0:00:00,2010-06-03 15:31:50,2010-06-03 15:31:50,"WINPE, TIMEOUT=1800"
"0019B92F5D18","OK",5,0:00:02,2010-06-03 15:31:50,2010-06-03 15:31:52,"diskpart /s X:\LDClient\rmvol.txt"
"0019B92F5D18","ERR_Fail",-1917190229,0:02:00,2010-06-03 15:31:52,2010-06-03 15:33:52,"drvmap.exe ***\ldosd 1077F9ABD886D315C99620D155D I: <qt/>\\perseus.***.se\Packages<qt/>, STATUS FACILITY=3513"
; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"
*** are the domain
Can there be somthing wrong with the acesss to the directorys? ive tried the account im using and i can acess the catalogs when im loged on as the user on a machine.
installed the patch reboot the core server and booted into WinPE menu and it WORKED it started totally automated
You have made my life much easier
No problem, glad I could help.