11 Replies Latest reply on May 1, 2008 8:06 AM by mdereus

    Trouble with OSD drive mapping and drivers

    Rookie

      Since upgrading to 8.8 we recreated our Windows XP image and it was working fine after getting the PXE network driver situation straightened out.  We are unsure what happened, but now after selecting the image in the PXE menu nothing happens.  Opening the console window and checking the drive mappings shows that the X: and I: drives are not mapped.  I can map them manually with the same credentials that are entered in the deploy script.  From there I can launch H:\osd\imaging\imagew.exe, manually kick off the image restore and it finishes succcessfully.  Reboot the computer and it begins loading the sysprep image as it should, though when the first menu comes up to click Next neither the USB keyboard or mouse work.  I'm suspecting this is because the drives didn't map properly so none of the drivers got copied over.  I have created a new deploy script with the same as the old one that had been working fine up until now and that didn't work either.  Is there a log file that I can look at to see what's happening?  Beyond this I'm stumped as is my coworker who has been using LANDesk much longer than I have.

        • 1. Re: Trouble with OSD drive mapping and drivers
          Jason SupportEmployee

           

          Can you post your OSD log?

           

           

           

           

           

           

           

           

          • 2. Re: Trouble with OSD drive mapping and drivers
            Rookie

            Where can I find that?  I looked around for it  and searched here for the answer to no avail.

            • 3. Re: Trouble with OSD drive mapping and drivers
              Jason SupportEmployee

              The logs are located in the following place.

               

              "
              corename\ldlog" -- or Program Files\LANDesk\ManagementSuite\log

               

               

              it will be named CJ-name of script date.log

              • 4. Re: Trouble with OSD drive mapping and drivers
                Rookie

                The only OSD log in there is from 4/22 and that's when it worked as it should.  I just tried running it again, clicked the image from the PXE menu, hit OK and nothing happened after the window closed.  No new log file appeared.

                 

                • 5. Re: Trouble with OSD drive mapping and drivers
                  phoffmann SupportEmployee

                  Have a look if your Core still has a "LANDesk Management Agent". In 9 out of 10 cases of this symptomatic description, the service is no longer there.

                   

                  That's the crucial bit of service that would pick up the "I'm ready" from the client and then go about telling the client what to do.

                   

                  You can re-register it in the following way:

                   

                  Run "residentagent.exe /register" from the "C:\Program Files\LANDesk\Shared Files\"-directory.

                   

                  Paul Hoffmann

                  LANDesk EMEA Technical Lead.

                  • 6. Re: Trouble with OSD drive mapping and drivers
                    Rookie

                    The LANDesk Management Agent service was running already, but I re-registered it anyway and rebooted the core server.  Tried imaging again and it got further, a couple of console windows came up as if it was trying to image but it didn't do anything of the sort and rebooted saying NTLDR was missing.  Though this time it did create a log.  I did hide the domain and user name.

                     

                    "Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:22 AM,4/30/2008 10:59:22 AM,"WINPE, TIMEOUT=1800"

                    "00145E647DCB","OK",5,0:00:02,4/30/2008 10:59:22 AM,4/30/2008 10:59:24 AM,"diskpart /s X:\LDClient\rmvol.txt"

                    "00145E647DCB","OK",230227968,0:00:01,4/30/2008 10:59:24 AM,4/30/2008 10:59:25 AM,"drvmap.exe domain\user password I: <qt/>
                    Cpwap200a04.domain\landesk<qt/>, STATUS FACILITY=3513"

                    "00145E647DCB","OK",230227968,0:00:00,4/30/2008 10:59:25 AM,4/30/2008 10:59:25 AM,"drvmap.exe domain\user password H: <qt/>
                    landesk.domain\ldmain<qt/>, STATUS FACILITY=3513"

                    "00145E647DCB","OK",0,0:00:01,4/30/2008 10:59:25 AM,4/30/2008 10:59:26 AM,"diskpart /s X:\LDClient\wipeDisk0.txt"

                    "00145E647DCB","OK",0,0:00:02,4/30/2008 10:59:26 AM,4/30/2008 10:59:28 AM,"cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:"

                    "00145E647DCB","OK",230031360,0:00:00,4/30/2008 10:59:28 AM,4/30/2008 10:59:28 AM,"RunBatch -1 h:\osd\imaging\imagew.exe /RN /O i:\850F2200.IMG, STATUS FACILITY=3510, SYNC"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:28 AM,4/30/2008 10:59:28 AM,"sdclient /f /o /dest="X:\LDClient\diskinfo.exe" /p="http://10.1.10.225/landesk/files/diskinfo.exe", STATUS"

                    "00145E647DCB","OK",0,0:00:01,4/30/2008 10:59:28 AM,4/30/2008 10:59:29 AM,"sdclient /f /o /dest="X:\LDClient\assvol.txt" /p="http://10.1.10.225/landesk/files/assvol.txt", STATUS"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:29 AM,4/30/2008 10:59:29 AM,"tokreplw X:\LDClient\assvol.txt partition=1"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:29 AM,4/30/2008 10:59:29 AM,"diskpart /s X:\LDClient\assvol.txt"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:29 AM,4/30/2008 10:59:29 AM,"sdclient /f /o /dest="C:\sysprep\sysprep.inf" /p="http://10.1.10.225/landesk/files/Deploy-NEw.inf", STATUS"

                    "00145E647DCB","OK",0,0:00:01,4/30/2008 10:59:29 AM,4/30/2008 10:59:30 AM,"sdclient /f /o /dest="C:\ldsleep.exe" /p="http://10.1.10.225/landesk/files/ldsleep.exe", STATUS"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:30 AM,4/30/2008 10:59:30 AM,"tokreplw C:\sysprep\sysprep.inf COMPUTERNAME=LD00145E647DCB"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:30 AM,4/30/2008 10:59:30 AM,"cmd /c copy /y X:\LDClient\guid.pds C:\LDISCAN.CFG"

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:30 AM,4/30/2008 10:59:30 AM,"tokreplw C:\LDISCAN.CFG DEVICEID="

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:30 AM,4/30/2008 10:59:30 AM,"tokreplw C:\LDISCAN.CFG IMAGEPATH=
                    Cpwap200a04.domain\landesk\850F2200.IMG"

                    "00145E647DCB","OK",0,0:00:01,4/30/2008 10:59:30 AM,4/30/2008 10:59:31 AM,"sdclient.exe<qt/> /f /o /dest="x:\ldclient\fixvista.bat" /p="http://10.1.10.225/landesk/files/FixVista.bat""

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:31 AM,4/30/2008 10:59:31 AM,"sdclient.exe<qt/> /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://10.1.10.225/landesk/files/fixntfs.exe""

                    "00145E647DCB","OK",0,0:00:01,4/30/2008 10:59:31 AM,4/30/2008 10:59:32 AM,"sdclient.exe<qt/> /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://10.1.10.225/landesk/files/bcdedit.exe""

                    "00145E647DCB","OK",0,0:00:00,4/30/2008 10:59:32 AM,4/30/2008 10:59:32 AM,"RunBatch -1 X:\LDCLient x:\ldclient\FixVista.bat"

                    "00145E647DCB","OK",5,0:00:04,4/30/2008 10:59:32 AM,4/30/2008 10:59:36 AM,"diskinfo extend_last_partition"

                    "00145E647DCB","OK",-2147481750,0:00:06,4/30/2008 10:59:36 AM,4/30/2008 10:59:42 AM,"reboot, timeout=2"

                    ; "Job Complete","1 Done","0 Failed","0 Off","0 Unknown"

                    • 7. Re: Trouble with OSD drive mapping and drivers
                      cknott SupportEmployee

                      If you look at the time stamps in the log you are running the script in about 4 seconds.  Check and make sure that the hard drive can be seen from within WinPE using diskpart.exe.  Run "diskpart.exe" Type in "list disk"  You should see something come back about disk 0 online.  If it says No disks found or something like that then you need to add the SATA drivers to the WinPE image file.

                       

                      If that works, then manually map the drives using net use, and then run imagew.exe manually and see if you can restore it that way.  Running it manually will also sometimes pop an error that doesn't show up in the console.

                       

                      Thanks,

                       

                      Chad

                      • 8. Re: Trouble with OSD drive mapping and drivers
                        phoffmann SupportEmployee

                        Aye - the next problem (after Management Agent) is usually lack of being able to address SATA drives.

                         

                        Note that some BIOS'es have a "compatibility"-mode or "legacy"-mode for the SATA drives, this allows you to read the SATA drives without needing a special driver.

                         

                        If your BIOS does NOT have this, then you do need to add the storage driver to the WinPE image, as without it, it will not be able to see the disks.

                         

                        Chad's instructions on how to check this are quite good.

                         

                        Paul Hoffmann

                        LANDesk EMEA Technical Lead

                        • 9. Re: Trouble with OSD drive mapping and drivers
                          Rookie

                          The new Lenovo desktops all have the SATA settings in the BIOS, I change them out of habit.  I ran diskpart.exe and did "list disk", disk 0 was online.  Manually mapped H: and I:, ran imagew.exe, restored the image and rebooted.  It booted to the Windows XP Setup Wizard but neither the USB keyboard or mouse work.  This did not make a log file.

                           

                          After running diskpart again and making sure disk 0 was online and manually mapping the drives I tried running the OSD script again and it acted the same way of opening and closing the command windows quickly, creating a similar log file, rebooting and giving an NTLDR missing error.

                          • 10. Re: Trouble with OSD drive mapping and drivers
                            phoffmann SupportEmployee

                            ?:|

                             

                            That's a mite strange.

                             

                            What laptops specifically are those? Could be a platform specific thing potentially ... (albeit, we don't usually have problems with Lenovo's) ... hmmm

                             

                            Paul Hoffmann

                            LANDesk EMEA Technical Lead.

                            • 11. Re: Trouble with OSD drive mapping and drivers
                              Rookie

                              Right now I'm working on Lenovo M57 small form factor desktops and IBM IntelliStation M Pro workstations.  Both are acting like this.