Hi everyone.

I'm working on replacing our old MSDT server for OS deployment purposes and have been moderatly successful with some assistance from Landesk reps.

I've run into a challange and I'm unable to find the information needed to point me to the solution.

My deployment is fine up until Action_Type=Distribute_Software. At this point, the deployment appears to go no further.

There's no indication as to issues in any log files I'm able to identify, or event viewer. The process just stops.

#CoreApplications is the repository of all OS deployment related apps that are potentiall installed.

#Provisioning Task Group refers to the specific Apps for this task and in which order we want them installed in.

I've checked C:\LDProvisioning and C:\Program Files\Landesk\LDClient\Data for any active log files to indicate what's causing the process to simply stop.

We have no other existing issue with our Landesk server, and we've had no issues with deploying packages to existing computers.

Any suggestions of where to look next?

Hi,

I used LDMS 9 SP4

I have a Dell 7240 with Windows 8.1, i want to used provisioning for deploying but while the step "SET ACTIVE" it fails and i can see the message "The active command can only be used on fixed MBR"

I used UEFI boot on the PC.

Thx.

Benjamin

When any of my provisioning templates run, I have a patch system task that runs in the template.  Before upgrading to 9.5SP1, the patch system task worked.  Now, after the upgrade, the task runs and says it was successful but no patching is done.  It just blows threw the task and marks it complete.

I tried creating a new task using the same patching group but to no avail.

Anyone have any ideas?

Jeff

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

We have been using 9.5 SP1 HII assigned drivers packages for install within Windows for a couple months now.  It has been correctly identifying the needed assigned driver packages and installing them.  However, not sure when this started yet, it does not appear to be running correctly on any reimages anymore.

I created a Distribution Package to install USB 3.0 driver on an E6530 while in Windows 7.  Tested the Distribution Package, it installs the driver, returns code 14, which I set in the console to be success.  However, when I assign this Distribution Package to HII (Dell Inc., Latitude E6530, Windows 7, Architecture=Both), the Distribution Package doesn't run - no files downloaded/cached for it - no local SDClient.log for it.  The drivers.db3 and associated files/folders have been replicated via LD content replication.  I removed the machine from the Scheduled Task from previous Package testing.  I removed and reassigned the Package to HII - still same HIIClient.log every time.  Please note that the console reports this as a success, and seems to now happen on any machine that has an assigned driver package!  Here is the HIIClient.log below:

*****************  Starting HIIClient *****************

Command line args: /uncpath /taskid 3128

Running in Windows

GetImageSystemDirectory: c:\Windows

GetImageSystemDirectory: c:\Windows

HII Proxy Location: http://<core>/LANDesk/ManagementSuite/Core/Core.WebServices/hii.asmx

Driver path found: \\<path>

Determining OS version and architecture.

OS Major version: 6 

OS Minor version: 1

OS Product type: 0

Major and Minor version and product type gathered.
GetImageSystemDirectory: c:\Windows
Architecture is: X86

source path to download: \\<path>\drivers.db3
dest path for download: c:\Windows\LDDriverStore\drivers.db3
Thu, 24 Apr 2014 08:37:53 About to call DownloadFiles (1 files) with these settings:
Thu, 24 Apr 2014 08:37:53 m_allowedBandwidthWAN: 100
Thu, 24 Apr 2014 08:37:53 m_allowedBandwidthLAN: 100
Thu, 24 Apr 2014 08:37:53 m_maxDiscoveryThreads: 15
Thu, 24 Apr 2014 08:37:53 m_discardPeriodSeconds: 604800
Thu, 24 Apr 2014 08:37:53 m_preserveDirectoryStructure: 1
Thu, 24 Apr 2014 08:37:53 m_bUseWanBWForPush: 0
Thu, 24 Apr 2014 08:37:53 m_bSynchronize: 0
Thu, 24 Apr 2014 08:37:53 m_downloadControl: SourceOnly
Thu, 24 Apr 2014 08:37:53 m_preferredServerControl: AttemptPreferredServer
Opening SQLite3 database at location: c:\Windows\LDDriverStore\drivers.db3

Device manufacturer discovered as: Dell Inc.
Device model discovered as: Latitude E6530
Found MakeModel_Idn 20
Detected package: 'E6530 USB3.0 Driver Post Install' assignment for device: 'IUSB3\ROOT_HUB30&VID_8086&PID_1E31&REV_0004&SID_05351028'
Getting software snippet from http://<core>/LANDesk/ManagementSuite/softwaredistribution/apmservice/PackageInfo.asmx
Requesting for PackageID: 1138, TaskID: 3128
Request:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><GetSWDPackageSnippethttp://tempuri.org/"><PackageId>1138</PackageId><ldTaskIdn>3128</ldTaskIdn></GetSWDPackageSnippet></soap:Body></soap:Envelope xmlns="11383128>
Found httpclient.exe at C:\Program Files\LANDesk\Shared Files\httpclient.exe
SWD package E6530 USB3.0 Driver Post Install return code: 1
Downloading from downloadfiles!
Thu, 24 Apr 2014 08:38:32 About to call DownloadFiles (0 files) with these settings:
Thu, 24 Apr 2014 08:38:32 m_allowedBandwidthWAN: 100
Thu, 24 Apr 2014 08:38:32 m_allowedBandwidthLAN: 100
Thu, 24 Apr 2014 08:38:32 m_maxDiscoveryThreads: 15
Thu, 24 Apr 2014 08:38:32 m_discardPeriodSeconds: 604800
Thu, 24 Apr 2014 08:38:32 m_preserveDirectoryStructure: 1
Thu, 24 Apr 2014 08:38:32 m_bUseWanBWForPush: 0
Thu, 24 Apr 2014 08:38:32 m_bSynchronize: 0
Thu, 24 Apr 2014 08:38:32 m_downloadControl: SourceOnly
Thu, 24 Apr 2014 08:38:32 m_preferredServerControl: AttemptPreferredServer
Download return count: 0
OS Version: 6.1
No drivers were found that matched the hardware.
GetImageSystemDirectory: c:\Windows
*****************  Finish HIIClient *****************

I have a 9.5 environment which used to run 8.8.  My previous colleague deployed PXE representatives to various clients in the network.  These are all running the old version and have not (will not) update to the latest PXE rep.  I don't know how to locate these clients with the old PXE Rep.  But while they're out there, they continue to plague my deployments by hosting the old image (and the deployment fails).

Any suggestions to locate all PXE reps in the network?  (1500 computers)

Landesk 9.5 SP2

After Provisioning a Dell OptiPlex 7010 using HII it freezes. blue screens and /locks up after 10 minutes or so. After exhaustive troubleshooting I've narrowed it down to the intel management engine drivers.

It was picking the drivers from another model so I assigned the drivers from the ones I downloaded from Dell for this model. This caused it to not install the drivers and it showed with a yellow exclamation in Device Manager. Of course this also causes it to NOT blue screen, freeze or lock up.

Any one else having problems with a Dell 7010 and drivers?

Hi,

we have an issue with the HII Driver Management. I tried populating the db for a HP EliteBook2170p. So far it worked for all the pnp drivers which are perfectly installed during the first startup after the image deployment. Now we have a dedicated graphics card driver (Intel) which should be installed instead of the "default-vga-grphics card" (don't know if its called like that in english, just a guess).

So here is what I did:

- created a package with the setup files and the correct command line

- went to HII Driver Management and selected "Assign"

- chose the correct Make, Model, OS and Architecture. It showed me a list from a captured inventory with all the drivers in there

- selected "Driver Package" and the respective device out of the device list on the left (the hardware id is the one i can see in the device manager on the HP machine)

- created a provisioning template with a HII action in "system configuration"

- scheduled the template and ran it on the client but nothing happened

All the configurations were done on the core directly. We are running 9.5SP2 with no component patches so far. Does anyone have a similar issue? Am I doing something wrong?

I am using a provision template and when I install my default agent vulscan kicks off.  This slows down the provisioning process greatly as the template does not progress until vulscan completes.  How can I stop vulscan from running when the agent is installed.  I am using the "Install Agent" action item in the template and there are no command line aparamenters to use.

Thanks,

Jim

When creating an USB bootable media is there a way to make it Win PE 4 32 bit ? This is for provisioning of a tablet and you can not boot to lagecy USB, which I have done on others and it worked fine. System is LD 9.5.2

Thanks

This article describes the new features and changes in the OS Provisioning tool in LANDESK Management Suite 9.6.

The focus on changes for OS Provisioning in LDMS 9.6 has been geared towards simplifying the process.

The older "OSD" product has been removed from the product and has been fully replaced by the Provisioning product.

LANDESK Provisioning takes the previous OSD concepts and extends them even further  LANDESK Provisioning offers true end-to-end Provisioning of a device from a "Bare Metal" metal state (No Operating System installed) to completely imaged, software installed, domain joined, LANDESK Agent installed, etc.

OSD is gone?  What happens now?

There is no upgrade process for existing OSD Scripts.    It will be necessary to create provisioning templates to perform the previous imaging tasks that OSD did.  Remember, Provisioning is not just for deploying images.  It can be used to distribute software, patch systems, execute scripts, etc.

The beauty of Provisioning is that you can chain an endless array of actions together.

New!   Simplified template creation process

LDMS 9.5 and subsequent service packs simplified the Provisioning templates and consolidated previously complex actions.

LDMS 9.6 furthers this by include simple template creation "wizards" to build a template foundation.

Creating a capture job has been simplified down to 5 steps within a single dialog:

1. Select “Capture Template” under “New Template”
2. Select “Capture template”
3. Select “Capture Image”
4. Name the template and give it a description.
5. Enter image file storage location.

Similarly, LDMS 9.6 has simplified creating a Deploy Image template into a single dialog:

New!  "Smart Partitioning" actions

There are two new partitioning actions that are referred to as "Smart Partitioning" actions.

Auto Assign Partitions

• Assigns standard drive letters to OS and Boot partitions
• This action discovers the OS partition and possible separate boot partitions and automatically assigns them standard driver letters.

• Action results: 
  
  Windows 7 and higher with separate boot partition including all UEFI:

OS Partition will be mounted as C:

Boot partition will be mounted as S:

         Windows XP and Windows 7 and higher with a separate boot partition:

OS/Boot partition will be mounted as C:

Create default partitions

• Assigns the default partitions for either UEFI or BIOS based computers.
• This action creates standard partitions as recommended for Microsoft operating systems (Windows 7 and newer)
• This prepares the disk for use with ImageX or other file based imaging tools.  The action will detect UEFI and BIOS based computers and configure the partitions.  Sector based imaging tools such as ImageW do not need this action.
• OS partition will be mounted as C:
• Boot Partition will be mounted as S:

LANDESK Provisioning takes advantage of the new "self-organizing" multicast.  This and other improvements to the software distribution model provide drastically improved imaging and software deployment speeds.

New!  "Installed Mapped Software" action

LANDESK Management Suite 9.6 offers a new "smart migration" feature that allows you to use your Software License Monitoring data to install or reinstall software as part of an imaging and system migration solution.  IProducts can be linked to packages, and in turn called as a group through a single "Install Mapped Software" action.

In addition any standard LANDESK query can be created as a "product" within the Software Licensing Monitoring tool.    An example of the use of this would be if you wanted to install software on laptops only, you could create a LANDESK query that would return results for only laptops.

"Smart migration" can also be used to upgrade or change software:

Examples:

Upgrade example: Map Office® 2010 to Office® 2013

Change software example: Map iTunes® to VLC Media Player

New!  "Device Name Prompter" action

This action changes the %ldhostname% variable to what is typed in.  This is to be run before an inject script action.  When the "Device Name Prompter" action runs it will pop up a windows asking the operator to enter the desired computer nam.e

Improved!   PXE Boot option configuration

• PXE Boot options have been moved from the "Configure Services" menu.  They are now located in the OS Provisioning tool under the "Preboot" dropdown.
• Changes made to the PXE boot options take effect immediately, no need to redeploy a PXE representative.  The client makes a web service call to download the F8 PXE Boot menu options.

New!   Disconnected Provisioning

This new option allows you to deploy templates from a thumb drive.

To create, put in the USB device,  right click the template, and choose  “Create disconnected template”.    (USB thumb drive will be formatted) .  The template will deploy the image, do CTOS,  install the agent (Self-contained.exe) and attempt any other action that does not require a core connection.

With connection to the core, Distribute Software, Patch System and other core-dependent actions will succeed.

New!   "Launch Template" action

This new action is used in migration scenarios for migration from one computer to another computer.  This action utilizes machine to machine mapping.  The actions from the launched template are not included into the sections of the current template, it is run entirely just after the first template.

Improved!   Change  Changes to the "Wait" action

• You can now cancel a provisioning “Wait” action.  Previously you had to wait until the timeout, or until the file existed that the Wait action was set to wait for.
• Wait actions are often used in troubleshooting to give someone a chance to into the command prompt in Windows PE to manipulate or view the file system or registry.

Improved!   Various Enhancements

• Better resizing of Template UI
• Ability to copy and paste from template  to template.
• Multiple templates can be open simultaneously
• Defaults to Windows PE for Boot Environment and Windows for Target OS rather than "
• Auto-naming of actions
• Action name and description shows on Client UI.
• History auto-refreshes.
• Wait UI can be cancelled.

I have been having a lot of trouble trying to install the client on one particular HP model. It is an HP ProDesk 405 G1 MT. The machine will get a BSOD after the client has been running its installation for 10 minutes. I'm not if the machine is having an issue with the mirror driver or not.

I spoke with HP and they had me reinstall Windows. I did that and was able to successfully install the client. I was also able to create my image successfully. The problem is when I deploy the image, the machines will get a BSOD while the Landesk client is being installed. The agent version is 9.50.3.2. Anyone have any ideas on a solution?

Thanks.

Patrick

Hi, I am having a problem with HII not installing the driver for a usb3.0 hub in Windows 7 x86.

HII detects the usb root and installs the driver, but not the usb hub.

It is an intel motherboard with usb 3.0 onboard.

SQL lite view of the drivers.db3 (select * from devices where inffiles_idn = 82)

If you build a fresh install of Windows 7, a single unknown usb device is shown, give it the usb3.0 driver and it installs a usbroot device. Then another unknown device appears, give it the usb driver and it installs a usb hub.

How do I troubleshoot this to fix it? attached is the driver .inf file for the usb3.0 hub.

Thanks!

Hi everyone,

I have something really odd I am trying to accomplish with LANDesk provisioning and wasn't sure if any of you might know how to do it or if it even can be done.

Right now I have a USB hard drive I boot off of. The hard drive loads Win PE and then executes a batch file with menu options. The menu pauses and allows the user to select an option and then the batch file executes the option they select (such as deploying the Windows 7 image, secure wiping the hard drive, etc...). The batch file and associated script files do all the work as long as they are executed in the proper order and I am pointing to the correct file paths where they are stored.

I'd like to be able to PXE boot into LANDesk provisioning and use the same process as what is on my drive. Essentially I just want to use LANDesk Win PE to PXE boot and then have it execute my custom batch file and scripts that I am already using on my external drive. I tried creating a template to do this. Basically, I pick the template after PXE booting and I have it map a drive to the install files and the batch file menu. This does what I ask. It maps the drive and executes the batch file, but the batch file doesn't allow for users to pick an option and the template closes.

Is there an easier way to set this up in LANDesk, or am I crazy for trying to use LANDesk provisioning to do something like this?

Thanks for any help you can provide,

Josh

Hello,

We're on Landesk 9.5 SP2 and have a weird issue during provisioning.  What we're seeing on some models is that after running CTOS, Landesk doesn't wait for the first startup(after sysprep) to finish.  It just keeps moving on to the next tasks as soon as the network drivers are installed.

Our images are sysprepped and captured as TBI files.  Our provisioning tasks removes the disk partitions, deploys the image, run HII, then CTOS, and then supposed to run some more tasks after it starts up and auto logs into an administrator Windows account.  But it's not waiting for the first startup to finish.  I can see by refreshing the Landesk task that it moves onto the System Configuration section even before all the drivers have finished installing and whatever it is doing is interrupting that first startup, causing it to fail with the message "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click 'OK' to restart the computer. and then restart the installation."

Restarting doesn't help.

We've now added Wait 300 seconds as the first task in the System Configuration section as a workaround so Windows can finish and reboot.  Has anyone else seen this happening in their environment?  Our call to Landesk support ended up with them saying the same thing - just add a wait time.  We didn't have this issue in Landesk 9.0.  It always waited until after the first startup to finish and reboot before continuing any tasks,.

Thanks,

Peggy

Hi, does anyone have templates for creating a provision with GPT. I am having issues that it does not reboot after the ctos.

Thanks,

My capture image provisioning task keeps failing.  For some reason it is not getting the credentials from the preferred server.  Here is the log of MaptoPrefferedHandler

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:******Mapping to: \\tech\landesk\Images

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:Drive letter = f

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:Mode - Require Direct, no preferred server.

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:Could not get credentials for preferred server.

2014-04-02 17:40:07(1236-1232) maptopreferredhandler.exe:End of Map Drive.  Path used: - \\tech\landesk\Images\.

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:******UnMapping Drive

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:Drive letter = f

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:Could not map or unmap drive. Error code: 2250

2014-04-02 17:40:07(928-1296) maptopreferredhandler.exe:End of UnMap Drive.

Here is the template:

Any help would be greatly appreciated,

Mike

Hi All,

From reading other posts in this forum, it seems that Provisioning now supports this, but I am having trouble getting started. Specifically...

1. PXE booting with UEFI enabled times out with no message and returns to the boot menu (I have been able to boot from media)

2. How do you create the System and MSR partitions? How big should they be? What goes on these?

3. Deploying the OS to a GPT partition using DISM produces an "Error: 5 Access Denied" error.

I'm sure that after getting past these initial stages, I will have more questions. Any help will be appreciated.

We are running LD 9.5 SP2 with the 2014-0417 component patch. PXE Reps have been updated.

Thanks.

Pete

I have a few questions about your product in regards to
capturing a Windows 7 image using the steps “How to Capture a Windows 7
image with OSD using Imagew.exe v2 in 9.0 SP2 & SP3 and 9.5” which can be found at this link How to Capture a Windows 7 image with OSD in LANDesk® Management Suite 9.5, 9.0 SP2 and SP3. I added the link that I used so that you can see what I have already
completed and the step that I’m getting stuck on and perhaps you can give me a
solution to this issue.

So the step that I’m having trouble with is the last step on
this document. Once I select the “OSD capture script
(Capture_Windows_7_Imagew)” at the end of this document I’m not seeing the
process that the last page shows (which is the progress of Creating Image).
Instead I see two or three command prompt windows that appear and disappear and
then I just see the LANDesk background only. I do not see the image in the last
step of this document. Any ideas what this could be from?

I have tried the different options for running SYSPREP.EXE
for the Image Capturing and still have had no luck.

So I am trying to capture a simple image and deploy it to a computer.  I have followed the instructions outlined here:  How to Capture a Windows 7 image with OSD in LANDesk® Management Suite 9.5, 9.0 SP2 and SP3.  Please do NOT tell me to use provisioning "Because OSD is hard to troubleshoot and going away" considering the very FIRST step outlined in the document here: How to get started with Provisioning for Windows 7 in LANDESK® Management Suite 9.5 is to create and image using OSD and it points back to the first document. 

I went through the first document.  It would pop up DOS windows and then hang and the process would show as "Failed" in scheduled tasks (I am dragging the device identified via MAC in WinPE managed mode.  Found out this can be fixed by manually change the I: and the H: drive to Z: and Y:.  After that changed at least the imaging tool RAN.  When it failed you could see the I and H drives were mapped, the paths were correct but the log showed: 

"4439C4535C03","ERR_Fail",-1917190229,0:02:01,29/07/2014 3:37:49 PM,29/07/2014 3:39:50 PM,"ldrun drvmap.exe <domain>\ServiceLANDesk <passwd Hash Removed> I: """\\<FQDN>\legacy$""", STATUS FACILITY=3513"

When you tried to run the command: "ldrun drvmap.exe <domain>\ServiceLANDesk <passwd Hash Removed> I: """\\<FQDN>\legacy$""", STATUS FACILITY=3513" what you got back was a BAD SYNTAX error.  Running Imagew command manually was able to create an image, but I have been unable to get that image to actually boot once deployed.  Once I changed the drive letters, the ImageW tool ran, but then created a file 4,736KB large and rebooted the computer no matter what partition you choose. 

Beyond that, the unattended.XML file is never created by landesk so the options selected in Deploy simply don't get applied.  I had to change the H and I drives again in order to get the deploy to run as well. 

Could someone please give me a hand with this.  I would just like it if the instructions actually worked so that I can do this most basic of tasks.

Thanks