Does anyone know how I go about generating a new certificate and there must be some problem with existing one on server and PXE representatives?
Did you try opening a console on the PC you are trying to image and see if you can map the location manually using a net use statement? I don't think the certificate is an issue here from my experience.
Yes I can map a network drive manually using drvmap via the console. This is the reason I thought the PXE deployment was using a certificate.
As I understand it, the point of the drvmap.exe is to do the same as a net use command but decrypt the password hash on the line. If you are able to map with the same id on the line using the net use I would recommend verifying you typed the password correctly in the OSD script?
I really don't understand now as the drvmap command works even using the encrypted password! Why should it work when I manually type the command, but not when LANDesk executes it using an OSD script?
REMEXEC18=ldrun drvmap.exe SHDC\serviceadmin 10858A3FFC3BE4B050118212739 I: """\\shdcvs8\landesk""", STATUS FACILITY=3513
"WS4376VM1","ERR_Fail",-1917253785,0:00:21,1/28/2011 9:11:22 AM,1/28/2011 9:11:43 AM,"ldrun drvmap.exe SHDC\serviceadmin 10858A3FFC3BE4B050118212739 I: """\\shdcvs8\landesk""", STATUS FACILITY=3513"
; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"
Its the script that I found to be the issue on our core...
try advance edit and use the "domain\username" (instead or domain\username) from the drvmap.exe line..
if that fails remove the ldrun= before the drvmap..see if that works-i've the same problems..
Simon, basically drvmap does a net use command using the domain\username on the line and then decrypts the hash on the line to supply the password. So if you can do a manual drive map with net use then something appears to be wrong with the id\password combo.
I agree with Steve and make sure there are no quotes on that line except for the actual drive path.
Eventually found a fix so a tip for anyone in the same sitatuation don't rely on LANDesk v9 to copy the correct cbaroot certificate to the boot.wim file (used by v9 instead of peboot.img) . I have had to inject the all the .0 certificates to the following folder in boot.wim (cba8\cbaroot\certs) using imagex to mount and commit.