12 Replies Latest reply on Feb 13, 2008 12:07 AM by CarstenW

    Deploying Image on a VMware workstation

    Apprentice

      Through via PXE booting on the VMware

      workstation. However its failing at line 24 in the process of the job.

       

      Below is a snippet that is taken from a log when PXe booting to managed PE menu.

       

      "TESTMMCLEOD","OK",0,0:00:00,2/8/2008 9:39:35 AM,2/8/2008

      9:39:35 AM,"WINPE, TIMEOUT=1800"

      "TESTMMCLEOD","ERR_Fail",-1917190229,0:02:01,2/8/2008

      9:39:35 AM,2/8/2008 9:41:36 AM,"drvmap.exe ASIAPAC\Administrator

      108A5173F2A0933255D0A30665D I: <qt/>
      otto\Image<qt/>, STATUS

      FACILITY=3513"

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

      Off","0 Unknown"

       

       

       

       

       

       

      last time i had this it was because of the account issue, but we have resolved

      this since. Any other ideas to check?? we are PXE booting to deploy the image

       

       

       

       

      Result- Unkown status CODE is (Ox8DB9FFAB,3513:65451)

       

       

       

      the below txt log is an error taken when PXE booting and selecting the OSD script-

       

       

       

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

      "TESTMMCLEOD","OK",0,0:00:00,2/8/2008 12:21:25 PM,2/8/2008 12:21:25 PM,"WINPE, TIMEOUT=1800"

      "TESTMMCLEOD","OK",230227968,0:00:02,2/8/2008 12:21:25 PM,2/8/2008 12:21:27 PM,"drvmap.exe ASIAPAC\administrator 108A5173F2A0933255D0A30665D I: <qt/>
      otto\Image<qt/>, STATUS FACILITY=3513"

      "TESTMMCLEOD","OK",230227968,0:00:00,2/8/2008 12:21:27 PM,2/8/2008 12:21:27 PM,"drvmap.exe ASIAPAC\administrator 108A5173F2A0933255D0A30665D H: <qt/>
      otto\ldmain<qt/>, STATUS FACILITY=3513"

      "TESTMMCLEOD","OK",0,0:00:02,2/8/2008 12:21:27 PM,2/8/2008 12:21:29 PM,"diskpart /s X:\LDClient\wipeDisk0.txt"

      "TESTMMCLEOD","OK",0,0:00:07,2/8/2008 12:21:29 PM,2/8/2008 12:21:36 PM,"cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:"

      "TESTMMCLEOD","ERR_Fail",-1917386763,0:00:01,2/8/2008 12:21:36 PM,2/8/2008 12:21:37 PM,"RunBatch -1 h:\osd\imaging imagew.exe /RN /O i:\HP_D530\ITM3000.IMG, STATUS FACILITY=3510, SYNC"

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

        • 1. Re: Deploying Image on a VMware workstation
          phoffmann SupportEmployee

          Open a command console and see if you can access those files (copy 'em) // run those commands (or even run IMAGEW) from the command-line.

           

          That'll at least give you a clearer indication as to whether you're facing either authentication or access-rights (if you can't access the file, then that's most likely what it is).

           

          Generally, imaging with/to VMWare is just fine - I do it in my lab all the time. I usually use it for demonstrations in fact, because there is pretty much a guarantee that you won't have any NIC-driver mess :).

           

          Paul Hoffmann

          LANDesk EMEA Technical Lead.

          • 2. Re: Deploying Image on a VMware workstation
            Apprentice

            so when i push the scehduled job to this virtual machine, it has LD agent installed. It gets half way through the job, when it boots up to the LD image screen thats when it fails. What cmds do i run??

            • 3. Re: Deploying Image on a VMware workstation
              Apprentice

               

              from the error log

               

               

               

               

               

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

              "TEST","OK",0,0:00:17,2/12/2008 9:51:35 AM,2/12/2008 9:51:52 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/bootfile.exe""

              "TEST","OK",0,0:00:17,2/12/2008 9:51:52 AM,2/12/2008 9:52:09 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/tlibr16.dll""

              "TEST","OK",0,0:00:16,2/12/2008 9:52:09 AM,2/12/2008 9:52:25 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/tlibr32.dll""

              "TEST","OK",0,0:00:17,2/12/2008 9:52:25 AM,2/12/2008 9:52:42 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/lddefrag.exe""

              "TEST","OK",0,0:00:16,2/12/2008 9:52:42 AM,2/12/2008 9:52:58 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/cicfgmgr.vxd""

              "TEST","OK",0,0:00:17,2/12/2008 9:52:58 AM,2/12/2008 9:53:15 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/cindis.vxd""

              "TEST","OK",0,0:00:16,2/12/2008 9:53:15 AM,2/12/2008 9:53:31 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/copyfile.exe""

              "TEST","OK",0,0:00:16,2/12/2008 9:53:31 AM,2/12/2008 9:53:47 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/winbom.ini""

              "TEST","OK",0,0:00:20,2/12/2008 9:53:47 AM,2/12/2008 9:54:07 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/ldvpe0.img""

              "TEST","OK",0,0:15:29,2/12/2008 9:54:07 AM,2/12/2008 10:09:36 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /dest="C:\ldvpe1.img" /p="http://10.132.1.50/landesk/vboot/ldvpe1.img""

              "TEST","OK",0,0:00:16,2/12/2008 10:09:36 AM,2/12/2008 10:09:52 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.132.1.50/landesk/vboot/tokreplw.exe""

              "TEST","OK",0,0:00:16,2/12/2008 10:09:52 AM,2/12/2008 10:10:08 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o  /dest="C:\Program Files\LANDesk\LDClient\ldiscan.cfg" /p="http://10.132.1.50/landesk/vboot/guid.pds""

              "TEST","OK",0,0:00:01,2/12/2008 10:10:08 AM,2/12/2008 10:10:09 AM,"<qt/>C:\Program Files\LANDesk\LDClient\tokreplw.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\ldiscan.cfg<qt/> DEVICEID={73EBF36C-65A3-654E-820E-6A2FF59E5561}"

              "TEST","OK",0,0:00:01,2/12/2008 10:10:09 AM,2/12/2008 10:10:10 AM,"<qt/>C:\Program Files\LANDesk\LDClient\tokreplw.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\winbom.ini<qt/> COMPUTERNAME=TEST"

              "TEST","OK",0,0:00:00,2/12/2008 10:10:10 AM,2/12/2008 10:10:10 AM,"<qt/>C:\Program Files\LANDesk\LDClient\copyfile.exe<qt/> c:\ldvpe1.img <qt/>C:\Program Files\LANDesk\LDClient\ldiscan.cfg<qt/> \ldclient\ldiscan.cfg"

              "TEST","OK",0,0:00:01,2/12/2008 10:10:10 AM,2/12/2008 10:10:11 AM,"<qt/>C:\Program Files\LANDesk\LDClient\copyfile.exe<qt/> c:\ldvpe1.img <qt/>C:\Program Files\LANDesk\LDClient\winbom.ini<qt/> \winbom.ini"

              "TEST","OK",0,0:00:16,2/12/2008 10:10:11 AM,2/12/2008 10:10:27 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /dest="C:\Program Files\LANDesk\LDClient\diskinfo.exe" /p="http://10.132.1.50/landesk/files/diskinfo.exe""

              "TEST","OK",0,0:00:01,2/12/2008 10:10:27 AM,2/12/2008 10:10:28 AM,"<qt/>C:\Program Files\LANDesk\LDClient\diskinfo.exe<qt/> update_winnt_sif <qt/>C:\Program Files\LANDesk\LDClient\winnt.sif.new<qt/>"

              "TEST","OK",0,0:00:01,2/12/2008 10:10:28 AM,2/12/2008 10:10:29 AM,"<qt/>C:\Program Files\LANDesk\LDClient\copyfile.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\ldvpe0.img<qt/> <qt/>C:\Program Files\LANDesk\LDClient\winnt.sif.new<qt/> \winnt.sif"

              "TEST","OK",0,0:00:11,2/12/2008 10:10:29 AM,2/12/2008 10:10:40 AM,"<qt/>C:\Program Files\LANDesk\LDClient\lddefrag.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\ldvpe0.img<qt/>, STATUS"

              "TEST","OK",0,0:00:01,2/12/2008 10:10:40 AM,2/12/2008 10:10:41 AM,"<qt/>C:\Program Files\LANDesk\LDClient\bootfile.exe<qt/> C:\Program Files\LANDesk\LDClient\ldvpe0.img /keep /bootunsafe, ASYNC"

              "TEST","OK",0,0:00:50,2/12/2008 10:10:41 AM,2/12/2008 10:11:31 AM,"WINPE, TIMEOUT=1800"

              "TEST","OK",230227968,0:00:01,2/12/2008 10:11:31 AM,2/12/2008 10:11:32 AM,"drvmap.exe ASIAPAC\administrator 108A5173F2A0933255D0A30665D I: <qt/>
              otto\Image<qt/>, STATUS FACILITY=3513"

              "TEST","OK",230227968,0:00:01,2/12/2008 10:11:32 AM,2/12/2008 10:11:33 AM,"drvmap.exe ASIAPAC\administrator 108A5173F2A0933255D0A30665D H: <qt/>
              otto\ldmain<qt/>, STATUS FACILITY=3513"

              "TEST","OK",0,0:00:01,2/12/2008 10:11:33 AM,2/12/2008 10:11:34 AM,"diskpart /s X:\LDClient\wipeDisk0.txt"

              "TEST","OK",0,0:00:13,2/12/2008 10:11:34 AM,2/12/2008 10:11:47 AM,"cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:"

              "TEST","ERR_Fail",-1917386763,0:00:01,2/12/2008 10:11:47 AM,2/12/2008 10:11:48 AM,"RunBatch -1 h:\osd\imaging imagew.exe /RN /O i:\HP_D530\ITM3000.IMG, STATUS FACILITY=3510, SYNC"

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

               

               

              • 4. Re: Deploying Image on a VMware workstation
                Apprentice

                 

                What state does it leave the VM session?  can you run a command prompt in the state that it is left in from the go menu?

                 

                 

                What type of drive emulation are you using in the VM session? SCSI? IDE? is the partition fix or variable length? Is it larger than the partition tant you are trying to put onto the vm session?

                 

                 

                Are the drives still mapped?

                 

                 

                if you have the network drives still maps you can try running:

                 

                 

                h:\osd\imaging\imagew.exe /RN /O i:\HP_D530\ITM3000.IMG

                 

                 

                If that fails you can try the unsupported

                 

                 

                h:\osd\imaging\imagew.exe /RN /C i:\HP_D530\ITM3000.IMG

                 

                 

                This is a different way of creating the Partition.

                 

                 

                That should be enough to try for now.

                 

                 

                 

                 

                 

                 

                 

                 

                 

                 

                 

                • 5. Re: Deploying Image on a VMware workstation
                  Apprentice

                  i have two options when it gets stuck. You have the LD image screen with the button GO. One for NEW CONSOLE and RESTART COMPUTER

                   

                  When i select New Console im faced with a cmd prompt showing :\i386\system32>   **SEE ATTACHMENT***

                   

                  In the logs im seeing this line common.... what can this mean? and what cmd would i type to do it manually?

                   

                   

                   

                  "000C2956AB5D","ERR_Fail",-1917386763,0:00:01,2/12/2008 12:01:55 PM,2/12/2008 12:01:56 PM,"RunBatch -1 h:\osd\imaging imagew.exe /RN /O i:\HP_D530\ITM3000.IMG, STATUS FACILITY=3510, SYNC"

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

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                  I have tried two ways of imaging-

                   

                   

                   

                   

                  1) A vm when it has a xp build and landesk agent installed. i scehduled the OSD script job for this machine and failed.

                   

                   

                   

                   

                  2) A Vm booting in via the PXE boot menu.

                  • 6. Re: Deploying Image on a VMware workstation
                    Apprentice

                    What happens when you type h: or i: from the prompt in your screen shot?

                     

                    If you can get to both what happens when you try to run imagew from its location on h: drive?

                     

                     

                     

                    What type of hard drive controler emulation are you using? is this the same vm you captured from?

                     

                     

                    Try typing the comand in my original post, that starts from h:\....

                     

                     

                    If that fails but you can get to h: try the /c option instead of the /o and see if that helps.

                    • 7. Re: Deploying Image on a VMware workstation
                      bnelson Employee

                       

                      "000C2956AB5D","ERR_Fail",-1917386763,0:00:01,2/12/2008 12:01:55

                      PM,2/12/2008 12:01:56 PM,"RunBatch -1 h:\osd\imaging imagew.exe /RN /O

                      i:\HP_D530\ITM3000.IMG, STATUS FACILITY=3510, SYNC"

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

                       

                       

                       

                       

                       

                      Check that you don't actually have that space in your script between imaging and imagew.exe. Remove the space and replace it with an \. That should fix that portion.

                       

                       

                      • 8. Re: Deploying Image on a VMware workstation
                        Apprentice

                         

                        DO NOT remove the space on that command line!!

                         

                         

                         

                         

                         

                        That is the correct syntax for the RunBatch command.

                         

                         

                        • 9. Re: Deploying Image on a VMware workstation
                          Jared Barneck SupportEmployee

                          Tarmour is correct, the space is there by default.

                           

                          Runbatch parameters asks for the source directory as one parameter and the file to run as a second paramter, hence the space.

                          • 10. Re: Deploying Image on a VMware workstation
                            Apprentice

                             

                            It will really make things easier, if you give us the output (from the cmd window you pictured in your attachment) of ipconfig (/all), dir h:, dir i:, dir h:\osd\imaging and dir i:\HP_D530.

                             

                             

                            There is a way to translate the error codes of the log to a somewhat meaningful description, but....(anyone to the rescue?)

                             

                             

                            --

                            bis denn dann

                            Carsten

                             

                             

                            • 11. Re: Deploying Image on a VMware workstation
                              Apprentice

                               

                              When on the device of the targeted vm i ran this in the cmd-
                              coreserver\ldmain\osd\imaging\imagew.exe

                               

                               

                              selecting restore and then trying to do the deploy the image it then told me there wasnt enough space for this image to proceed with. This is where i think my problem is.

                               

                               

                              thanks for your help and assistance to all

                               

                               

                               

                               

                               

                              • 12. Re: Deploying Image on a VMware workstation
                                Apprentice

                                Mmmh...yes, always an issue to take account of. In general: build the image on a partition as small as possible to make it work on most systems later. We build on a 3 gig partition, because we are putting a lot of stuff (Office and the like) into the image and 2 gig was too small. But all our VMs are running with a 4 gig virtual disk, so no problem with our image.