4 Replies Latest reply on Oct 30, 2008 1:58 PM by keos

    Deploying Images to Workstation


      I've seen a demonstration prior to getting LANDesk installed in our company where the user was able to schedule a task and reimaged a computer.  What's interesting about this process was the task was setup on the Core or Console and launched.

      The workstation which had the Agent installed on it, rebooted itself and automatically started WinPE (or some virtual partition).  It then connected to the server and the image started cascading to the workstation.  This is very similar to Ghost Console, which I'm very excited about.  Unfortunately that demonstration was awhile ago and I can't remember how to go about it.  Does anyone know the steps involved?


      Thanks in advance.

        • 2. Re: Deploying Images to Workstation
          Jason SupportEmployee

          Vboot is really quite simple to setup. I am assuming you already have your OSD Scripts created-so we will skip that part of the process.


          As you stated Vboot is done from the console to a client that already has a agent installed and running. It behaves much like a software distrubtion task.


          1) Right click on the OSD script that you want to use in the console and choose schedule


          2) Drag a managed client(s) to the newly created scheduled task(the task name will the name of your script)


          3) start the task.


          There is a little more information on the vboot process in the 8.8 User guide page 223



          This process is referred to as Vboot as well as agent-based deployment


          • 3. Re: Deploying Images to Workstation

            Perfect, vboot is what I saw just didn't remember what's it call...


            I'm gonna try this method out... will post back.


            Thank you Jason

            • 4. Re: Deploying Images to Workstation

              Ok, it does work..for the most part.  1 issue came up, but that's probably due to my configuration (or lack of knowledge on this part)


              Symantec Ghost prompts me for the span files, I checked the command it the "-auto" parameter is there to tell GHOST to automatically search the directory for the next  file.   The entire drive is mapped/mounted it should work.  Why it is prompting me for the file?


              Second is the invisibility of the process (which is actually great), Ghost Cast server is running, I have no idea from where.  The process completes without me ever seeing where the GhostCast server is running from.  Aside from the issue above, this is exactly what I want.  This would be great if the workstation is near the Core server.  If the workstation I'm ghosting is on a different subnet, in another region I prefer the GhostCast server to be running from the server in that subnet.  In this setup, is ghostcast server running on the Core?  I could remove Symantec Ghost to prove this but that's a little excessive, to prove this point.


              I'm very happy about this process so far, it's what I want to achieve.  Once I've proven this method works with Symantec Ghost, and from the local server I will be testing it with Imagew V2 to compare the speed difference.  Who knows, we may not need Symantec altogether. Please help, I feel like I'm so close to a solution.


              I added the script below, hopefully someone brillent (or more knowledgeable then me) can point me in the proper direction.


              BTW LDMS8.8 SP2


              ScriptName=SK Unattended Deploy Oct 3008
              ScriptDescription=Unattended Deploy images to Managed Workstations
              ImageToolCmd="RunBatch -1 h: ghost32.exe -clone,mode=load,src=i:\ELEMEN~2.GHO,dst=1 -sure -auto", STATUS FACILITY=3511
              ImageToolCmdsFile=\\NSCLANDESK.NCDSB.COM\LDMAIN\LANDESK\FILES\SK Unattended Deploy Oct 3008.txt
              DESCRIPTION=Unattended Deploy images to Managed Workstations
              NAME=SK Unattended Deploy Oct 3008
              REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/bootfile.exe"
              REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr16.dll"
              REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr32.dll"
              REMEXEC3=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/lddefrag.exe"
              REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cicfgmgr.vxd"
              REMEXEC5=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cindis.vxd"
              REMEXEC6=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/copyfile.exe"
              REMEXEC7=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/winbom.ini"
              REMEXEC8=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/ldvpe0.img"
              REMEXEC9=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="C:\ldvpe1.img" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/ldvpe1.img"
              REMEXEC10=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tokreplw.exe"
              REMEXEC11=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="%LDMS_CLIENT_DIR%\diskinfo.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/diskinfo.exe"
              REMEXEC12=<qt/>%LDMS_CLIENT_DIR%\diskinfo.exe<qt/> update_winnt_sif <qt/>%LDMS_CLIENT_DIR%\winnt.sif.new<qt/>
              REMEXEC13=<qt/>%LDMS_CLIENT_DIR%\copyfile.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\ldvpe0.img<qt/> <qt/>%LDMS_CLIENT_DIR%\winnt.sif.new<qt/> \winnt.sif
              REMEXEC14=<qt/>%LDMS_CLIENT_DIR%\lddefrag.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\ldvpe0.img<qt/>, STATUS
              REMEXEC15=<qt/>%LDMS_CLIENT_DIR%\bootfile.exe<qt/> %LDMS_CLIENT_DIR%\ldvpe0.img /keep /bootunsafe, ASYNC
              REMPING16=WINPE, TIMEOUT=1800
              REMEXEC17=diskpart /s X:\LDClient\rmvol.txt
              REMEXEC18=drvmap.exe LSS206\Administrator 1059B87282FC8095C867C011362 I: <qt/>\\lss206.ncdsb.com\images<qt/>, STATUS FACILITY=3513
              REMEXEC19=drvmap.exe LSS206\Administrator 1059B87282FC8095C867C011362 H: <qt/>\\lss206.ncdsb.com\packages<qt/>, STATUS FACILITY=3513
              REMEXEC20=diskpart /s X:\LDClient\wipeDisk0.txt
              REMEXEC21=cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:
              REMEXEC22="RunBatch -1 h: ghost32.exe -clone,mode=load,src=i:\ELEMEN~2.GHO,dst=1 -sure -auto", STATUS FACILITY=3511
              REMEXEC23=sdclient /f /o /dest="X:\LDClient\diskinfo.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/diskinfo.exe", STATUS
              REMEXEC24=sdclient /f /o /dest="X:\LDClient\assvol.txt" /p="http://%CUSTJOBHOSTIP%/landesk/files/assvol.txt", STATUS
              REMEXEC25=tokreplw X:\LDClient\assvol.txt partition=1
              REMEXEC26=diskpart /s X:\LDClient\assvol.txt
              REMEXEC27=cmd /c copy /y X:\LDClient\guid.pds C:\LDISCAN.CFG
              REMEXEC28=tokreplw C:\LDISCAN.CFG DEVICEID=%Computer - Device ID%
              REMEXEC29=tokreplw C:\LDISCAN.CFG IMAGEPATH=\\lss206.ncdsb.com\images\Elementary_Live_607.gho
              REMEXEC30=sdclient.exe<qt/> /f /o /dest="x:\ldclient\fixvista.bat" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixVista.bat"
              REMEXEC31=sdclient.exe<qt/> /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/fixntfs.exe"
              REMEXEC32=sdclient.exe<qt/> /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe"
              REMEXEC33=RunBatch -1 X:\LDCLient x:\ldclient\FixVista.bat
              REMEXEC34=diskinfo extend_last_partition
              REMEXEC35=reboot, timeout=2