This article applies to LANDESK Management Suite 9.6

Issue:

When running a scheduled task to deploy the PXE Representative it fails.

Workaround:

The PXE Representative can be manually installed by following these steps:

1. Push the "PXE Representative Removal" script to the PXE representative and then reboot the PXE representative once removal is complete.
2. Copy Setup_PXEProxy.exe from the core under Managementsuite\landesk\files to the PXE Representative.
3. Manually run Setup_PXEProxy.exe on the PXE Representative.
4. Verify that the LANDesk(R) PXE MTFTP Service and LANDesk(R) PXE Service are both installed and started.
5. On the PXE representative, verify that within Program Files (x86)\LANDesk\PXE\System\images\ there are four folders:
   
   

• Boot
• EFI
• IA32 EFI
• x86pc

   6. If missing files, the Setup_PXEProxy.exe may be corrupt.  Obtain a clean copy of the Setup_PXEProxy.exe from an LDMS or Service Pack installation package.

HII (DISM) is failing on all of my models and not picking up sepecified drivers either. I am running LDMS 9.5 SP2. I have tried this on 5 different models and it always fails. I am including a dism log file from one of my laptops as well as a picture of what WinPE is telling me when it does fail. I have verified that the "problem drivers" are in fact inmy driver depository on the core and I have rebuilt the driver db as well.

If anyone can help, it would be appreciated!

Mike

Hi there,

I'm trying to deploy images using a Preferred server with a provisioning task, but instead of grabbing the image file from the preferred server the client node being provisioned always resort to the core server. Other software distribution task works perfectly all right with preferred servers. Any ideas?

Environment

• LANDESK Management Suite 9.5
• LANDESK Management Suite 9.6

Issue

• Some console users are configured with a specific role and scope assigned.
• You want them to be able to schedule a template against a new bare metal device.
• However, even if they are able to create a new bare metal device, then they are not able to see them in the Management Console.
• How to resolve this without assigning to the user the right to see all the managed nodes?

Cause

Even though the user has the correct rights in terms of provisioning management and bare metal device creation, when a new bare metal device is created, if this is not a member of one of the scopes the user is allowed to see, the device doesn't appear in their console, even if its creation has been successful.

Resolution

1. Login to the Management Console with an administrative account

2. Create a new query that matches the field Computer | Type = Bare Metal Provision

3. Create a new scope from query and select the query created above

4. Assign to the affected user the right to see the new scope

5. Verify that the user is now able to see the bare metal device they have created having them logging into the console

6. Associate the bare metal device to a provisioning task and start it

Problem:

Customer has the image uploaded, but it is complaining about the same file, he has tried uploading the image a couple times, the file is is asking for is there, and this continues to happen.

Cause:

The length of the computer name.

Resolution:
Changed it from 12 characters to 9 characters and it worked just fine.

Hi there,

I asked my networking colleague to include the "LANDesk(R) PXE Service" to the monitoring. He said, that the brackets are a problem for Nagios, but found a way to escape them with a special character. He says that it still does not work. --> No services matching ^LANDesk(R) PXE Service found : CRITICAL.

Can someone help or does anyone have this included in the monitoring?

Thanks for you help!

Hi all

HII failes with this message:

Failed to download the driver.db3 file - HII will not continue

Failed to get driver files list.

ProcessDrivers failed.

Any idea what is happening and how to go about fixing it.

I have had rebuild HII DB and it did so just fine but apparently it is still not working.

I surely can scrap this DB and make a new one but it would require redoing all the custom Asignments and all and i would rather avoid it if possible at all.

Thanks

I started with the provisioning and unattend templates  with the Deploying Windows 7 best known methods article.   I had to do some tweaks to get it to actually deploy the image to my machine but now it deploys and labels the drives properly.  Now  however I am getting an error during the inject script section of the template. in the status it gives me the error [80001501H] The web service responded with an invalid call"  

If I look at the inject script action in the provision history, I have the internal value result code of : -2147478271

If I look in the ldprovision log file from the client I get the following....

2013-06-18 21:32:57(1064-1024) ldProvision:*********  Begin an action - Inject_script

2013-06-18 21:32:58(1064-1024) ldProvision:Do EnvironmentCheck

2013-06-18 21:32:58(1064-1024) ldProvision:Is WinPE Action=1, Is WinPe Environment=1

2013-06-18 21:32:58(1064-1024) ldProvision:Session Data: <variables/>

2013-06-18 21:32:58(1064-1024) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\InjectScriptHandler.exe" http://myserver/LdLogon/Provisioning/windows/InjectScriptHandler.exe)

2013-06-18 21:32:58(1064-1024) ldProvision:Process exit code:0

2013-06-18 21:32:58(1064-1024) ldProvision:The file (X:\ldprovision\InjectScriptHandler.exe) was successfully downloaded

2013-06-18 21:32:58(1064-1024) ldProvision:Download handler ok.

2013-06-18 21:32:58(1064-1024) ldProvision:Launching action handler [InjectScriptHandler.exe] with parameters ["]

2013-06-18 21:32:58(1064-1024) ldProvision:handler launched.

2013-06-18 21:32:58(1064-1024) ldProvision:Reporting action status: 5 to core

2013-06-18 21:32:58(1064-1024) ldProvision:Call web service GetStatusString()

2013-06-18 21:32:58(1064-1024) ldProvision:Start TryallWebService Attempt:0.

2013-06-18 21:32:58(1064-1024) ldProvision:End TryallWebService Attempt:0. ExitCode:0

2013-06-18 21:32:58(1064-1024) ldProvision:StatusString = The Web service responded with an invalid call.

2013-06-18 21:32:58(1064-1024) ldProvision:Call web service SetActionStatus()

2013-06-18 21:32:58(1064-1024) ldProvision:Start TryallWebService Attempt:0.

2013-06-18 21:33:02(1064-1024) ldProvision:End TryallWebService Attempt:0. ExitCode:0

2013-06-18 21:33:02(1064-1024) ldProvision:End of action - Inject_script

2013-06-18 21:33:02(1064-1024) ldProvision:Last action failed

2013-06-18 21:33:02(1064-1024) ldProvision:**********************************  End processing actions  **********************************

The injectscripthandler.exe log is below..

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateHeaderFile - X:\ldprovision\setupinstall.header.txt

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateBodyFile - X:\ldprovision\setupinstall.body.txt

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Args = -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml" http:/myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:going to call x:\cba8\httpclient.exe -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml" http://myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:start Try httpclient No=0.

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:end Try httpclient No=0.exitCode=0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Exit Code of InstallCallHTTPClient = 0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0, value is false

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:invalid result

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0

2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:An internal error has occurred with the management product.

I can navigate to the path where webservice.asmx is located and seems to be fine there at least from a different computer in a web browser, and I have the drive mapped where the unattend file is located.

Any advise on where to check would be greatly appreciated..  I can't tell if it is something in IIS, or if there is somewhere else I have a file missing...  Any help would be appreciated.

Thanks

Chris

Hello,

When attempting to boot a laptop via PXE for imaging, I get the "PXE-E11 - Arp Timeout" error after selecting the WinPE Menu option on the F8 menu. I see the BOOT SERVER IP, then the error. Any ideas?

J. 

Hi,

I am having trouble installing the PXE representative.  Like many other posts I’ve read:

https://community.landesk.com/support/message/75035#75035

https://community.landesk.com/support/message/67341#67341

It says it installed successfully but in fact it has not.  I’ve also looked at this:

https://community.landesk.com/support/message/73264#73264

Here are some lines from the osdrep.log file on the machine I am trying to install the PXE rep on:

MSI (s) (D0:F0) [18:29:24:077]: Product: LANDesk(R) PXE Proxy -- Installation failed.

MSI (s) (D0:F0) [18:29:24:077]: Windows Installer installed the product. Product Name: LANDesk(R) PXE Proxy. Product Version: 1.0.4. Product Language: 1033. Manufacturer: LANDesk. Installation success or error status: 1603.

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

Action ended 18:29:23: InstallExecute. Return value 3.

Action ended 18:29:24: INSTALL. Return value 3.

Here is an entry in the event log is during the install

Failed to connect to server. Error: 0x800401F0

And another:

Product: LANDesk(R) PXE Proxy -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

Here is the CJ-PXE Representative Deployment log file:

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

"PXEREP","OK",1605,0:00:00,6/2/2014 6:11:38 PM,6/2/2014 6:11:38 PM,"MsiExec.exe /q /X{F238CE99-6614-4072-9D20-1D2FA7ED951A}"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:39 PM,6/2/2014 6:11:39 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\bootmenu.1, C:\Program Files (x86)\LANDesk\LDClient\bootmenu.1, TOREMOTE"

"PXEREP","OK",0,0:00:01,6/2/2014 6:11:40 PM,6/2/2014 6:11:41 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\bstrap.0, C:\Program Files (x86)\LANDesk\LDClient\bstrap.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:42 PM,6/2/2014 6:11:42 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\dosundi.1, C:\Program Files (x86)\LANDesk\LDClient\dosundi.1, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:43 PM,6/2/2014 6:11:43 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootmenu.0, C:\Program Files (x86)\LANDesk\LDClient\bootmenu.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:44 PM,6/2/2014 6:11:44 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\dosundi.0, C:\Program Files (x86)\LANDesk\LDClient\dosundi.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:45 PM,6/2/2014 6:11:45 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:46 PM,6/2/2014 6:11:46 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd_x64.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd_x64, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:48 PM,6/2/2014 6:11:48 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd_ia32.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd_ia32, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:49 PM,6/2/2014 6:11:49 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.sdi, C:\Program Files (x86)\LANDesk\LDClient\boot.sdi, TOREMOTE"

"PXEREP","OK",0,0:00:02,6/2/2014 6:11:50 PM,6/2/2014 6:11:52 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.wim, C:\Program Files (x86)\LANDesk\LDClient\boot.wim, TOREMOTE"

"PXEREP","OK",0,0:00:02,6/2/2014 6:11:53 PM,6/2/2014 6:11:55 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot_x64.wim, C:\Program Files (x86)\LANDesk\LDClient\boot_x64.wim, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:56 PM,6/2/2014 6:11:56 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootx64.efi, C:\Program Files (x86)\LANDesk\LDClient\bootx64.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:57 PM,6/2/2014 6:11:57 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootia32.efi, C:\Program Files (x86)\LANDesk\LDClient\bootia32.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:59 PM,6/2/2014 6:11:59 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootmgr.exe, C:\Program Files (x86)\LANDesk\LDClient\bootmgr.exe, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:12:00 PM,6/2/2014 6:12:00 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\pxeboot.0, C:\Program Files (x86)\LANDesk\LDClient\startrom.0, TOREMOTE"

"PXEREP","OK",1603,0:00:09,6/2/2014 6:12:01 PM,6/2/2014 6:12:10 PM,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\sdclient.exe<qt/> /p="http://128.8.118.44/landesk/files/osdrep.msi" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}" /disableclientqueue"

"PXEREP","OK",0,0:00:50,6/2/2014 6:12:11 PM,6/2/2014 6:13:01 PM,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE<qt/> /NTT=128.8.118.44:5007 /S="128.8.118.44" /F /SYNC /NOUI"

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

I’ve tried chasing down these various error logs but they quickly become a morass.

LDMS 9.5 SP2

I have built several 2012 R2 servers and I am not able to install the PXE Rep.  I have tried manually installing the MSI as well as through the console. The osdrep.msi just fails.  Anyone else running into this?

What I get when running the osdrep.msi is:

The Event Log shows this:::

Product: LANDesk(R) PXE Proxy -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

Can Provisioning be set or changed to Verbose? Currently we get very little feedback from the template. It would be nice to see the progress of ImageX in real time. We are running 9.5 sp1.

Note: In LANDESK Management Suite 9.6 the software distribution architecture has been completely redesigned, and the case of templates taking a long time to start should be improved or eliminated.

Issue

The provisioning task is failing to load. It will attempt to load the template and retry for 40 attempts and then the job hangs and the client stays in the WinPE screen or brings back the template section window.

Logs on the core may indicate a few different errors:

In prov_schedule.exe.log:

    This log is located in \\core\ldmain\log

Template is not flattened, will attempt to flatten.
Flattening  template failed.

In provisioning.log:

    This log is located in \\core\ldmain\log\provisioning. 

Unable to find the history task

or

Unable to find template for computer idn ###

Causes and Resolutions

First, make sure that the latest service pack and the latest component patches are applied to the core.

Scheduler service being stopped

• If the scheduler service is not running, provisioning jobs will not start.
• DCOM errors can cause the scheduler service to stop.

Resolution

• Change the service to run as a Domain Administrator and start the Scheduler service. Once this is done, the provisioning task should work.
• Reset the password for the admin account that was running the LANDesk and LANDesk1 COM+ objects. This prevents the scheduler service from failing which prevents the provisioning template from running.

Current Provisioning Task in Progress on Selected Machine

• If a provisioning task has already been assigned to the machine in question, the task will fail. If you review the provision.log file on the core you will see a line "Computer is Busy with another task {taskID}"

Resolution:

1. Determine the TaskID from the log, Go to your Core and delete that task.
2. Delete client from database
3. PXE boot client, or run a manual inventory scan from the device
   1. A Manual scan can be initiated from WinPE by running X:/Windows/System32/Startnet.cmd from a command prompt
4. Run the provisioning task

Corrupt Template

• A corrupt template can prevent correct scheduling. One cause if this is if a template is imported, the drop down boxes are not filled in as they were pointing to objects from the previous core. For example, Software Distribution actions do not have a package specified. Same with Configure Agent actions. Also any actions with scripts will have this issue.
• Another way to determine if your template is not configured properly is by reviewing the Provisioning.log on the core. If you see the following:

INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Action LANDesk.Provisioning.Business.PAction_Distribute_software
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Got package ID 60, requesting snippet
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Requesting snippet for packageId 60
INFO    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Requesting SWD snippet with task IDN 2214, package ID 60
ERROR    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : Exception encountered trying to get snippet (LANDesk.ManagementSuite.SoftwareDistribution.Business.PackageNotFoundException): This package has been deleted.
ERROR    PROV_SCHEDULE        8/18/2011 5:06:50 PM    : GetSoftwareSnippet failed

Resolution:

• Recreate the template, or make sure that all dropdown boxes and options are configured in the template and all included templates.
• If you are getting the error where you are unable to get the Software Snippet, you will need to go into your Provisioning Template and make sure that all software packages are available and working. Determine which package is failing and resolve the software package. Save your template and retry the provisioning task.

Template is trying to perform an invalid action

• Error when attempting to save template

• Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error.

• Resolution:
  • If you are adding included templates to a main template you will want to start with adding the included templates one at a time until you find the problem template. Then address the specifics of that template and what it is doing. Try to recreate a new template that duplicates the problem template and see if you get any errors while saving the template.

Example Customer Situation:

The problem template was one that used the Update Registry action item and the Registry Operation of Import File. Because the file that was being imported was a combination of different registry export files, and remarked out descriptions had been added to the file, the template would return error: "Cannot save changes to the template . Verify that the template name you have chosen is not already used by another template. Database Error." The initial problem came from the fact that the original template did save when maybe it should not have, which caused the provisioning task to fail and the Prov_Schedule.exe.log file to show "Flattening template failed". Once we isolated the issues with the remarked out lines in the reg file and removed them, the template saved and the provisioning task worked properly.

In the customers environment, having the remarked out comments failed, but in a test lab the customers reg file worked fine. After getting the reg file to import and save, we found that the script failed on the reg file when trying to run it. What we discovered is that in his situation, the header in the reg file that says: "Windows Registry Editor Version 5.0" was causing it to fail, but I was unable to duplicate any of his problems in my lab. This seems to be a unique situation and may or may not apply to other customers that are having the 40 of 40 retries issue.

• LANDesk is trying to find a provisioning task from a failed distribution

  • The provisioning log will show  "Unable to find the history task".
    
    Resolution:

1. Delete client from database
2. PXE boot client, or run a manual inventory scan from the device
3. Run the provisioning task
   
   

Environment:

LDMS 9.6

Review Date:

9/15/2014

Error Message:

DrvLoad: Unable to load X:\InstalledDrivers\...\e1d6432.inf (Error 0x80070002)

Problem:

When WinPE is attempting to load a driver, it fails.

Cause:

When going through an OSD or Provisioning task , WinPE uses drvload.exe to access drivers. If drvload.exe is unable to load a driver successfully for use, different actions can fail, including making network connections which are required for performing OSD and Provisioning tasks.

Solution / Workaround:

• Load the drivers' .inf file onto a thumb drive and attach to the machine that is booting into WinPE.
• Identify the thumb drives assigned drive letter
  • Open a New Console

• Type diskpart then press Enter.

• Type list volume then press Enter. This will dislay assigned drive letter.

• Identify the drive letter for the thumb drive.
• Type exit and press Enter.

• Next try mounting the driver from the thumb drive using the command: X:\Windows\System32\drvload.exe [usbDriveLetter]:\[path_to_driver]\[driver_name].inf

Example: The driver in this example is located on the root of C:\

X:\Windows\System32\drvload.exe C:\e1c6432.inf

• If the driver is compatible, the console will display: DrvLoad: Successfully loaded [usbDriveLetter]:\[path_to_driver]\[driver_name].inf

Example:

DrvLoad: Successfully loaded C:\e1c6432.inf

• If the driver is not compatible, the console will display an error.

Note: The error may vary.

Example:

DrvLoad: Unable to load c:\BadDriver.inf (Error 0xe0000100)

• If manually attempting to use drvload.exe to load a driver fails, this must be corrected before OSD or Provisioning tasks can work.

Possible Causes of a Failure

• The test may have selected the wrong file.
• Dependent files may be missing that are needed as a reference by the *.inf file.
  • .dll, .cab, .sys files may be dependencies for the driver. Try adding them if available.
• The driver file added may be corrupted. Try re-downloading and testing.
• The driver selected may be incorrect. Try a different driver.
  • Windows Blue drivers have been seen to work in some circumstances where Windows 8.1 x86 drivers did not.

Can someone please tell me if this is a bug or is it by design?

We can see the SCN file get created under the \\coreserver\ldlogon directory but the bare metal server never gets committed to the database. The same process works fine adding it from the core server.

Applies to LANDESK Managment Suite 9.6

Issue:

How to capture a Windows 8.1 image with a provisioning template using IMAGEW.EXE v2.

How to capture a Windows 8 image with a provisioning template using IMAGEW.EXE v2.

How to capture a Windows 7 image with a provisioning template using IMAGEW.EXE v2.

Solution:

Follow the instructions in the LD96Capture document attached to this article. The document only shows Windows 8.1 but the same steps will work for Windows 7 or Windows 8. The instructions work whether the computer is doing a BIOS boot or a UEFI boot.

Hi All,

I have never posted a question on this community before so here goes!

We are running LDMS 9.5 SP2

I have been using LANDesk for a little while now, I am just looking for some guidance on an issue I am seeing. Periodically our OSD tasks are slowed down dramatically. Each time they are there are long delays between the task status being sent back to the core and the next stage of the task starting.

Please see the selected part from an SDClient_Task log, can you all let me know if this a blatant delay with core receiving the status? Or if it is normal?

Fri, 12 Sep 2014 10:39:52 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3526

Fri, 12 Sep 2014 10:55:50 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\AcroReader\11.0.04\silent_install.cmd) is not in cache

Fri, 12 Sep 2014 11:14:44 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3524

Fri, 12 Sep 2014 11:26:17 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Flash\install_flash_11.9.900.170.cmd) is not in cache

Fri, 12 Sep 2014 11:28:20 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3524

Fri, 12 Sep 2014 11:44:26 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Flash\install_flash_11.9.900.170.cmd) is cached locally

Fri, 12 Sep 2014 11:56:53 Sending task status, cmd line -coreandip=LONLDCP01003:10.193.248.89 -taskid=7822 -retcode=229392397 -pkgid=3525

Fri, 12 Sep 2014 12:12:49 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Shockwave\12.0\sw_lic_full_installer_12.0.7.148.msi) is not in cache

12:13:52 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=3525

Fri, 12 Sep 2014 12:25:01 File (\\CORENAME\ldpackages\Software\Global Apps\Adobe\Shockwave\12.0\sw_lic_full_installer_12.0.7.148.msi) is cached locally

Fri, 12 Sep 2014 12:25:03 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229965824 -complete -pkgid=3525

Fri, 12 Sep 2014 12:37:23 processing of package is complete, result 229965824 (0x0db50000 - code 0)

on, 15 Sep 2014 06:01:55 Sending task status, cmd line -coreandip=CORENAME -taskid=7822 -retcode=229392397 -pkgid=1778

Mon, 15 Sep 2014 06:18:07 File (\\CORENAME\ldpackages\Software\Global Apps\Winzip\17.5\install_winzip.cmd) is cached locally

Kind Regards,

D

please get the screen

Issue

Sometimes it is necessary to manually inject drivers into the Boot.wim file to allow client computers to properly recognize the network card, USB3 or other devices.

This is most easily done with the Deployment Image Servicing and Management tool, commonly known as DISM. 

DISM is also the utility LANDESK Hardware Independent Imaging employs to install drivers during the HII step of Provisioning Templates and OSD Scripts.

Resolution

Here are the steps to setup for and inject the drivers into the boot.wim file with DISM.

Preparation

1. Create the following folders on the root of the C drive:
   

   C:\Mount
   C:\Mount\Drivers
   C:\Mount\BootWIM
   

2. Copy the drivers you wish to inject into the C:\Mount\Drivers folder
3. Copy \Program Files(x86)\LANDESK\ManagementSuite\landesk\vboot\boot.wim to the C:\Mount folder.

Execution:

1. Open a CMD prompt as Administrator.
2. Navigate to "C:\Mount".
3. Use the following DISM commands to mount the Boot.wim:
   

   DISM /Mount-Wim /WimFile:C:\Mount\boot.wim /Index:1 /MountDir:C:\Mount\BootWIM

4. Use the following DISM command to add the driver:
   

   DISM /Image:C:\Mount\BootWIM /Add-Driver /Driver:C:\Mount\Drivers /recurse

5. Use the following DISM command to unmount the Boot.wim:
   

   DISM /Unmount-Wim /MountDir:C:\Mount\BootWIM /Commit

Cleanup and Deploy

1. Copy the newly updated Boot.WIM file from the mount folder to the \Program Files(x86)\LANDESK\ManagementSuite\landesk\vboot\ folder.
2. If desired, you can delete the C:\Mount folder and its contents.
3. Redeploy your PXE Rep.
4. PXE Boot your client and verify the drivers are being correctly recognized now.

I'm new to LD and the person who was going to train me has been sick for a month, so I'm trying to learn on my own.  I've created an image and have done a few test deployments, but this is happening consistently.  I've compared my OSD script to another that works and other than username, password, and file locations/names, they are the same.  Any suggestions as to what might be going on and how to troubleshoot this?  The images (the working one and mine) are W7 64bit.

Much thanks