I like to use the HP Softpaq Download Manager:

htp://www8.hp.com/us/en/ads/clientmanagement/drivers-bios.html?jumpid=va_r11260_go_clientmanagement_sdm#softpaq-download-mng

Then I like to sort by Date Published and be sure to use the latest driver.

It is definitely the latest from HP (Sep 6, 2011), but not sure if I select the correct one since there were at least 20 types of inf files.

http://community.landesk.com/support/docs/DOC-1143

We just added another Cause and Resolution:

Cause

• Another service on the server is using port 67

Resolution

• Run the "nestat -abn" command to find the service which is using port 67 and disable/reconfigure this service.

Unfortunately, I have nothing running on port 67 or neither the core server nor the PXE rep (should be netstat not nestat)

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
Can not obtain ownership information
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  RpcSs
[svchost.exe]
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
Can not obtain ownership information
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
Can not obtain ownership information
  TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
[sqlservr.exe]
  TCP    0.0.0.0:1434           0.0.0.0:0              LISTENING
[sqlservr.exe]
  TCP    0.0.0.0:2383           0.0.0.0:0              LISTENING
[msmdsrv.exe]
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TermService
[svchost.exe]
  TCP    0.0.0.0:4343           0.0.0.0:0              LISTENING
[issuser.exe]
  TCP    0.0.0.0:5007           0.0.0.0:0              LISTENING
[LDInv32.exe]
  TCP    0.0.0.0:9535           0.0.0.0:0              LISTENING
[issuser.exe]
  TCP    0.0.0.0:9593           0.0.0.0:0              LISTENING
[residentagent.exe]
  TCP    0.0.0.0:9594           0.0.0.0:0              LISTENING
[residentagent.exe]
  TCP    0.0.0.0:9595           0.0.0.0:0              LISTENING
[residentagent.exe]
  TCP    0.0.0.0:9972           0.0.0.0:0              LISTENING
[AMTNotifyService.exe]
  TCP    0.0.0.0:10347          0.0.0.0:0              LISTENING
[IpmiRedirectionService.exe]
  TCP    0.0.0.0:12176          0.0.0.0:0              LISTENING
[apmservice.exe]
  TCP    0.0.0.0:33354          0.0.0.0:0              LISTENING
[tmcsvc.exe]
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
Can not obtain ownership information
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
[wininit.exe]
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  eventlog
[svchost.exe]
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  Schedule
[svchost.exe]
  TCP    0.0.0.0:49181          0.0.0.0:0              LISTENING
[lsass.exe]
  TCP    0.0.0.0:49182          0.0.0.0:0              LISTENING
[AgentPortal.exe]
  TCP    0.0.0.0:49729          0.0.0.0:0              LISTENING
[services.exe]
  TCP    0.0.0.0:49733          0.0.0.0:0              LISTENING
  PolicyAgent
[svchost.exe]
  TCP    127.0.0.1:9535         127.0.0.1:62772        ESTABLISHED
[issuser.exe]
  TCP    127.0.0.1:9592         0.0.0.0:0              LISTENING
[residentagent.exe]
  TCP    127.0.0.1:21584        0.0.0.0:0              LISTENING
[collector.exe]
  TCP    127.0.0.1:51429        0.0.0.0:0              LISTENING
[tmcsvc.exe]
  TCP    127.0.0.1:52787        0.0.0.0:0              LISTENING
[residentagent.exe]
  TCP    127.0.0.1:62772        127.0.0.1:9535         ESTABLISHED
[rcgui.exe]
  TCP    192.9.201.46:139       0.0.0.0:0              LISTENING
Can not obtain ownership information
  TCP    192.9.201.46:445       192.9.200.144:55446    ESTABLISHED
Can not obtain ownership information
  TCP    192.9.201.46:445       192.9.201.72:2839      ESTABLISHED
Can not obtain ownership information
  TCP    192.9.201.46:1433      192.9.201.46:49470     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49472     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49474     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49475     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49476     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49477     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49646     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49749     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49781     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49782     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:49783     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:50184     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:50185     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:52830     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:58879     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:61895     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:61896     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:61897     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:61966     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:61967     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:61969     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62052     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62098     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62194     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62195     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62307     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62336     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62337     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62338     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62339     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62340     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62345     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62346     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62351     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62352     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62353     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62358     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62359     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62499     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62717     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:1433      192.9.201.46:62777     ESTABLISHED
[sqlservr.exe]
  TCP    192.9.201.46:49470     192.9.201.46:1433      ESTABLISHED
[apmservice.exe]
  TCP    192.9.201.46:49472     192.9.201.46:1433      ESTABLISHED
[apmservice.exe]
  TCP    192.9.201.46:49474     192.9.201.46:1433      ESTABLISHED
[LDInv32.exe]
  TCP    192.9.201.46:49475     192.9.201.46:1433      ESTABLISHED
[LDInv32.exe]
  TCP    192.9.201.46:49476     192.9.201.46:1433      ESTABLISHED
[LDInv32.exe]
  TCP    192.9.201.46:49477     192.9.201.46:1433      ESTABLISHED
[LDInv32.exe]
  TCP    192.9.201.46:49646     192.9.201.46:1433      ESTABLISHED
[AlertService.exe]
  TCP    192.9.201.46:49749     192.9.201.46:1433      ESTABLISHED
[BrokerService.exe]
  TCP    192.9.201.46:49781     192.9.201.46:1433      ESTABLISHED
[SchedSvc.exe]
  TCP    192.9.201.46:49782     192.9.201.46:1433      ESTABLISHED
[SchedSvc.exe]
  TCP    192.9.201.46:49783     192.9.201.46:1433      ESTABLISHED
[SchedSvc.exe]
  TCP    192.9.201.46:50184     192.9.201.46:1433      ESTABLISHED
[LANDesk.ManagementSuite.Licensing.UsageService.exe]
  TCP    192.9.201.46:50185     192.9.201.46:1433      ESTABLISHED
[LANDesk.ManagementSuite.Licensing.UsageService.exe]
  TCP    192.9.201.46:52830     192.9.201.46:1433      ESTABLISHED
[SchedSvc.exe]
  TCP    192.9.201.46:58879     192.9.201.46:1433      ESTABLISHED
[LANDesk.ManagementSuite.Licensing.UsageService.exe]
  TCP    192.9.201.46:61895     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:61896     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:61897     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:61966     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:61967     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:61969     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62052     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62098     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62194     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62195     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62307     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62336     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62337     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62338     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62339     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62340     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62345     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62346     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62351     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62352     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62353     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62358     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62359     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62499     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62717     192.9.201.46:1433      ESTABLISHED
[w3wp.exe]
  TCP    192.9.201.46:62752     192.9.201.213:49155    TIME_WAIT
  TCP    192.9.201.46:62759     192.9.201.18:445       ESTABLISHED
Can not obtain ownership information
  TCP    192.9.201.46:62769     192.9.201.24:445       ESTABLISHED
Can not obtain ownership information
  TCP    192.9.201.46:62771     192.9.201.24:135       ESTABLISHED
[spoolsv.exe]
  TCP    192.9.201.46:62775     192.9.201.101:8014     ESTABLISHED
[Smc.exe]
  TCP    192.9.201.46:62777     192.9.201.46:1433      ESTABLISHED
[LDInv32.exe]
  TCP    192.9.201.46:62778     192.9.201.46:1433      TIME_WAIT
  TCP    192.9.201.46:62779     192.9.201.46:1433      TIME_WAIT
  TCP    192.9.201.46:62780     192.9.201.46:1433      TIME_WAIT
  TCP    192.9.201.46:62781     192.9.201.46:1433      TIME_WAIT
  TCP    192.9.201.46:62782     192.9.201.213:135      TIME_WAIT
  TCP    192.9.201.46:62783     192.9.201.46:1433      TIME_WAIT
  TCP    192.9.201.46:62813     192.9.201.46:1433      TIME_WAIT
  TCP    192.9.201.46:62814     192.9.201.46:1433      TIME_WAIT
  TCP    [::]:80                [::]:0                 LISTENING
Can not obtain ownership information
  TCP    [::]:135               [::]:0                 LISTENING
  RpcSs
[svchost.exe]
  TCP    [::]:443               [::]:0                 LISTENING
Can not obtain ownership information
  TCP    [::]:445               [::]:0                 LISTENING
Can not obtain ownership information
  TCP    [::]:1433              [::]:0                 LISTENING
[sqlservr.exe]
  TCP    [::]:1434              [::]:0                 LISTENING
[sqlservr.exe]
  TCP    [::]:2383              [::]:0                 LISTENING
[msmdsrv.exe]
  TCP    [::]:3389              [::]:0                 LISTENING
  TermService
[svchost.exe]
  TCP    [::]:9535              [::]:0                 LISTENING
[issuser.exe]
  TCP    [::]:47001             [::]:0                 LISTENING
Can not obtain ownership information
  TCP    [::]:49152             [::]:0                 LISTENING
[wininit.exe]
  TCP    [::]:49153             [::]:0                 LISTENING
  eventlog
[svchost.exe]
  TCP    [::]:49154             [::]:0                 LISTENING
  Schedule
[svchost.exe]
  TCP    [::]:49181             [::]:0                 LISTENING
[lsass.exe]
  TCP    [::]:49729             [::]:0                 LISTENING
[services.exe]
  TCP    [::]:49733             [::]:0                 LISTENING
  PolicyAgent
[svchost.exe]
  UDP    0.0.0.0:123            *:*                   
  W32Time
[svchost.exe]
  UDP    0.0.0.0:161            *:*                   
[snmp.exe]
  UDP    0.0.0.0:162            *:*                   
[snmptrap.exe]
  UDP    0.0.0.0:500            *:*                   
  IKEEXT
[svchost.exe]
  UDP    0.0.0.0:4500           *:*                   
  IKEEXT
[svchost.exe]
  UDP    0.0.0.0:5007           *:*                   
[LDInv32.exe]
  UDP    0.0.0.0:5355           *:*                   
  Dnscache
[svchost.exe]
  UDP    0.0.0.0:9595           *:*                   
[residentagent.exe]
  UDP    0.0.0.0:33354          *:*                   
[tmcsvc.exe]
  UDP    0.0.0.0:33355          *:*                   
[tmcsvc.exe]
  UDP    0.0.0.0:38293          *:*                   
[pds.exe]
  UDP    127.0.0.1:50050        *:*                   
[ReportingServicesService.exe]
  UDP    127.0.0.1:50945        *:*                   
  ProfSvc
[svchost.exe]
  UDP    127.0.0.1:59041        *:*                   
[lsass.exe]
  UDP    127.0.0.1:59043        *:*                   
  LanmanWorkstation
[svchost.exe]
  UDP    192.9.201.46:137       *:*                   
Can not obtain ownership information
  UDP    192.9.201.46:138       *:*                   
Can not obtain ownership information
  UDP    192.9.201.46:65041     *:*                   
[tmcsvc.exe]
  UDP    [::]:123               *:*                   
  W32Time
[svchost.exe]
  UDP    [::]:161               *:*                   
[snmp.exe]
  UDP    [::]:162               *:*                   
[snmptrap.exe]
  UDP    [::]:500               *:*                   
  IKEEXT
[svchost.exe]
  UDP    [::]:4500              *:*                   
  IKEEXT
[svchost.exe]

The PXE boot Menu is hanging on IP. The network of Lenovo laptop is Intel PRO/1000 LAN Adapter Software but it doesn't have a vista version. i tried W7 it didn't work. I've tried to inject Vista driver from Intel website it didn't worked.

I need to Capture image prior to deploy it on 74 laptops and i'm blocked.

May you please help?

What version and patch level of LANDESK are you on?

When you run sysprep /generalize /oobe, you are "cleaning" the image of the driver, so it cant load the storage driver (even on the same machine).

You can force sysprep to leave the drivers, but that can get messy and cause other problems with your image.

http://technet.microsoft.com/en-us/library/ee832798(v=ws.10).aspx

Probably the best way is to use your current image and then inject the appropriate storage driver. This is very easy in Provisioning with the HII template action, but if you are using normal OSD You can do the same thing with dism.exe.

After you restore the image, but before you reboot, try this.http://technet.microsoft.com/en-us/library/dd799258(v=ws.10).aspx

specifically "Dism /image:C:\test\offline /Add-Driver /driver:C:\test\drivers /recurse"

-Tracy

Make sure when you add the NIC driver to the WinPE image you use the x86 version.

And depending on which version of LANDesk you have, you may need the Windows 8 x86 driver.

-Tracy

Hello, I have been busy this morning so didn't get a chance to update this post.  I found the issue.  I included a bunch of AHCI drivers from different manufactures in the HII installation which apparently causing a conflict. The OS boots up after I removed the chipset driver from HII.

Did any of these answers help?  If so, please mark helpful or correct. 

I am able to capture and image and deploy an image using ImageX but after the image is deployed we end up with 2 OS boot options. Is there a command that we need to add to the advance script so it will olny have one and will just boot directly to the OS?

Here is my Advance script

Task=8

ScriptName=RCASBaseImageX

ScriptDescription=RCASBaseImageX

MCast=0

FallBackNIC=

UseFallBackNIC=FALSE

ImageUserName=imageadmin

ImageDomain=schools

ImagePassword=1082BD11EEDD8F0594052707226

ImageToolType=4

ImageUNC=\\tclandesk\rcas\Images\Uploads\RCASBase.wim

ToolUNC=\\landesk1\ldmain\osd\imaging\imagex.exe

Partition=1

ImageToolCmd=cmd /c RunBatch -1 h:\osd\imaging imagex.exe /apply i:\Images\Uploads\RCASBase.wim 1 C:, STATUS FACILITY=3513, SYNC

ImageToolCmdsFile=\\LANDESK1\LDMAIN\LANDESK\FILES\RCASBaseImageX.txt

IsSysPrepImage=0

ConfigAdvancedMCast=0

UseWOL=FALSE

WOLSeconds=120

DiscoveryType=0

MaxTMCThreads=5

MinTMCSleep=1

MaxTMCSleep=200

BANDWIDTH_WAN=100

BANDWIDTH_LAN=100

SubrepTTL=14

TargetTTL=2

[OWNER]

GUID=e8eb0e49-b848-4205-8ed4-9c26f2771ab1

OSDPLUG=TRUE

DESCRIPTION=RCASBaseImageX

NAME=RCASBaseImageX

TYPE=WinPE

[JOBPARAM]

ABORT_ON_CMD_FAILURE=1

TASK_COMPLETION_ENABLED=FALSE

[MACHINES]

REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/bootfile.exe" /disableclientqueue

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr16.dll" /disableclientqueue

REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr32.dll" /disableclientqueue

REMEXEC3=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/lddefrag.exe" /disableclientqueue

REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cicfgmgr.vxd" /disableclientqueue

REMEXEC5=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cindis.vxd" /disableclientqueue

REMEXEC6=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/copyfile.exe" /disableclientqueue

REMEXEC7=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tokreplw.exe" /disableclientqueue

REMEXEC8=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.img" /disableclientqueue

REMEXEC9=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/ChangeBCD.exe" /disableclientqueue

REMEXEC10=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="%LDMS_CLIENT_DIR%\BCD" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/BCD.dat" /disableclientqueue

REMEXEC11=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe" /disableclientqueue

REMEXEC12=<qt/>%LDMS_CLIENT_DIR%\ChangeBCD<qt/> <qt/>%LDMS_CLIENT_DIR%\bcdedit.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/>

REMEXEC13=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="C:\boot.wim" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.wim" /disableclientqueue

REMEXEC14=<qt/>%LDMS_CLIENT_DIR%\copyfile.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/> \boot\BCD

REMEXEC15=<qt/>%LDMS_CLIENT_DIR%\lddefrag.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/>, STATUS

REMEXEC16=<qt/>%LDMS_CLIENT_DIR%\bootfile.exe<qt/> %LDMS_CLIENT_DIR%\boot.img /keep /bootunsafe, ASYNC

BEGINWINPE=TRUE

REMPING17=WINPE, TIMEOUT=1800

REMEXEC18=diskpart /s X:\LDClient\rmvol.txt

REMEXEC19=ldrun drvmap.exe schools\imageadmin 1082BD11EEDD8F0594052707226 I: """\\tclandesk.schools.rcas.org\rcas""", STATUS FACILITY=3513

REMEXEC20=ldrun drvmap.exe schools\imageadmin 1082BD11EEDD8F0594052707226 H: """\\LanDesk1.schools.rcas.org\ldmain""", STATUS FACILITY=3513

REMEXEC21=ldrun sdclient /f /o /dest="X:\LDClient\LDPathExist.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/LDPathExist.exe" /disableclientqueue, STATUS

REMEXEC22=ldrun LDPathExist.exe """I:\Images\Uploads\RCASBase.wim""", STATUS

REMEXEC23=ldrun LDPathExist.exe """H:\osd\imaging\imagex.exe""", STATUS

REMEXEC24=diskpart /s X:\LDClient\wipeDisk0.txt

REMEXEC25=cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:

REMEXEC26=ldrun cmd /c RunBatch -1 h:\osd\imaging imagex.exe /apply i:\Images\Uploads\RCASBase.wim 1 C:, STATUS FACILITY=3513, SYNC

REMEXEC27=ldrun sdclient /f /o /dest="X:\LDClient\diskinfo.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/diskinfo.exe" /disableclientqueue, STATUS

REMEXEC28=ldrun sdclient /f /o /dest="X:\LDClient\assvol2.txt" /p="http://%CUSTJOBHOSTIP%/landesk/files/assvol.txt" /disableclientqueue, STATUS

REMEXEC29=ldrun sdclient.exe /f /o /dest="x:\ldclient\RMVOLLETTER.TXT" /p="http://%CUSTJOBHOSTIP%/landesk/files/RMVOLLETTER.TXT" /disableclientqueue

REMEXEC30=ldrun tokreplw X:\LDClient\assvol2.txt partition=1

REMEXEC31=diskpart /s X:\LDClient\RMVOLLETTER.TXT

REMEXEC32=diskpart /s X:\LDClient\assvol2.txt

REMEXEC33=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixvista.bat" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixVista.bat" /disableclientqueue

REMEXEC34=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/fixntfs.exe" /disableclientqueue

REMEXEC35=ldrun sdclient.exe /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe" /disableclientqueue

REMEXEC36=ldrun sdclient.exe /f /o /dest="x:\cba8\FixWindows.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixWindows.exe" /disableclientqueue

REMEXEC37=ldrun x:\cba8\FixWindows.exe 1

REMEXEC38=cmd /c copy /y X:\LDClient\guid.pds C:\LDISCAN.CFG

REMEXEC39=ldrun tokreplw C:\LDISCAN.CFG DEVICEID=%Computer - Device ID%

REMEXEC40=ldrun tokreplw C:\LDISCAN.CFG IMAGEPATH=\\tclandesk.schools.rcas.org\rcas\Images\Uploads\RCASBase.wim

REMEXEC41=ldrun x:\Windows\system32\bcdboot.exe C:\Windows

REMEXEC42=ldrun diskinfo extend_last_partition

REMEXEC43=ldrun reboot, timeout=2

The multiple installs must be in the image you are using. You will most likely need to rebuild your image machine and make sure to use advanced options and format the drive before the OS install

Dave,

i'm using LANDesk 9.0 SP2 (WinPE 2.0).

Tracy,

the issue i'm facing is that Lenovo doesn't provide windows vista driver for the network adapter i have.

i tried to inject a driver from intel website for Vista 32bit but in vain.

the network adapter i have on the machines is: Intel(R) Ethernet Connection I218-LM

redrider1940 is right, it could be down to an issue with your source machine.  I've also seen this from "clean" images.  If you run bcdedit in Windows it will return details of the boot manager and boot loader.  Since you are seeing two boot loaders you need to make a note of the duplicate identifier value (usually something like this {cf21078c-6cd0-11e2-ab54-dc36a25fd8ae} ) then as you are already downloading bcdedit.exe to WinPE (see REMEXEC35 in your script), you can add a new line to run bcdedit.exe /delete {cf21078c-6cd0-11e2-ab54-dc36a25fd8ae} to do away with the additional entry. I'd run it after line 41 once BCDboot has been run  Windows will then load as normal. Its a workaround, but it should get you to where you want to be.

Hope that helps

Martyn Ayers

MarXtar Ltd/MarXtar Corporation

http://landesk.marxtar.co.uk

LANDesk Expert Solution Provider

The One-Stop Shop for LANDesk Enhancements

- Wake-On-WAN">http://landesk.marxtar.co.uk/Products/MarXtar/Wake-On-WAN/LANDesk%20Wake-On-WAN.html">Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing

- State">http://landesk.marxtar.co.uk/Products/MarXtar/State_Notifier/LANDesk%20State%20Notifier.html">State Notifier - Real-Time Device & User State Inventory Updating & Alerting

Update - New Stand-Alone State Notifier Console for Service Desk Operators

Update - State Notifier now detects machine and user Idle states

Update - WoW & State Notifier now integrate for even more functionality

ldm-lb,

You can check what version of drivers you need here:

http://community.landesk.com/support/docs/DOC-27542

The WinPE version you are on is not listed on the page, but subsequent versions are listed and will show you the logic that it is based upon.

Here is a Microsoft document that explains the different NDIS version of drivers that are required for each OS:

http://msdn.microsoft.com/en-us/library/windows/hardware/ff567893(v=vs.85).aspx

When you extract out the Intel drivers from the ProWin32.exe download (use 7-zip or WinRAR to extract), you'll end up with subfolders that are grouped by the NDIS version.  There may be a WinPE folder within the NDIS folder, but in those folders you'll see INF files named in this convention "e1c62x32.inf" or "e1k6232.inf".  The first 3 characters refer to the card model, the second 2 (62 in this case) refer to the NDIS version and the "x32" or "32" refer to 32 bit driver or 64 for 64 bit.  If you open the INF file in notepad, you can see the model card the driver is for. 

I apologize if this information is too basic and does not directly answer your question.  I did quite a bit of playing around with this before I figured this out and I hope this information could help someone else out.

Since you are on an older version and service pack of LD, you may want to look into upgrading.  I believe that some of the older drivers are built into the LD WinPE releases on more recent service packs.

Good luck.

David,

You are going to continue facing this problem by using something based on Windows PE 2.0.  

I would definitely recommend upgrading to at least LDMS 9.0 SP4.   Ideally you should look to upgrade to LDMS 9.5 SP2.

You don't need to immediately update your LANDesk clients, but if you update your core and consoles you will be a lot further ahead.

Well I tried doing the deployment using sysprep OOBE generalize and the partition problem went away. As well all the drivers remained intact except for video.

+1 to what David said. You are going to be in a work of hurt until you update your version of WinPE.

-Tracy

If you don't have any service running that uses UDP port 67 then it means there are no PXE representatives installed in your client node neither in your core server (at least there should be one in the subnet where you are trying to boot from PXE).

This is a netstat output from my PXE epresentative:

My advice: try to uninstall and then redeploy the PXE script again to these client nodes and in case it doesnt fix the issue look for errors in the computer event viewer. Also try to deploy the PXE representative to some different computers to see if these install correctly the LANDESK TFTP and PXE services. It should not be difficult to find the offending culprit.

I ended up installing the PXE rep on my Core Server, even though that is not suggested.