1 of 1 people found this helpful
That is interesting.
I know WinPE used to run a command that is supposed to disconnect most unused drives, including the multi-card reader, so this doesn't happen. I have to assume that this script is failing for some reason.
I can't remember the scripts name...There is a batch file in the WinPE image that is run by Startnet.cmd, that should disconnect many drives. It might be Remove.Bat.
You can change your script to a larger drive letter, but that is annoying.
in OSD the script that removes all the drive letters is the REMEXEC line
REMEXECXX=diskpart /s X:\LDClient\rmvol.txt
this starts out the OSD process by removing all the volume drive letters and prepare it for mapping drive letters.
According to the log you provided, that line was removed or LANDesk didnt put it in there when you saved your script.
Just add the line after your WINPE, TIMEOUT=1800 and you should be good to go, like this:
REMPING17=WINPE, TIMEOUT=1800 REMEXEC18=diskpart /s X:\LDClient\rmvol.txt
Many thanks to both of you! EMiranda, your answer was a little more specific so I'm happy to award you your choice of a cigar or a kewpie doll. <G>
Strange thing though - my OSD scripts did have the necessary diskpart commands, but it looks like they were in the wrong place - after the drive mapping commands. Not sure how that happened. Here's a snippet from my OSD script before I fixed it...
REMEXEC18=ldrun drvmap.exe SERVICEACCOUNT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX I: """\\2305deploy\deploy$""", STATUS FACILITY=3513
REMEXEC19=ldrun drvmap.exe SERVICEACCOUNT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX H: """\\2305ldcore1\ldmain""", STATUS FACILITY=3513
REMEXEC20=ldrun sdclient /f /o /dest="X:\LDClient\LDPathExist.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/LDPathExist.exe", STATUS
REMEXEC21=ldrun LDPathExist.exe """I:\imaging\images\W7x64P02A.TBI""", STATUS
REMEXEC22=ldrun LDPathExist.exe """H:\osd\imagew 2\imagew.exe""", STATUS
REMEXEC23=diskpart /s X:\LDClient\rmvol.txt
REMEXEC24=diskpart /s X:\LDClient\WIPECLEANDISK0.TXT
I fixed this by moving the REMEXEC23 command up to REMEXEC18, and then renumbering all the lines between so there wouldn't be duplicates.
Thanks again for the rapid response!
I never been offered a kewpie doll. thanks!
Glad EMiranda hooked you up, I was out of town and not in front of a Core Server and I've been low on sleep since...
Anyway I couldn't remember rmvol.txt or whether it was called by the script of by startnet.bat.
Thanks for the post. We recently started using the S20 model and our script was also out of order. After modifying it works like a champ
I did an advanced edit on the OSD object but the next time i go in and make a change the script reverts back to REMEXEC23 being out of place. Where is the default script located so i can change this permanently?