First, open up your command XML. The best way you want to view it is in the console's Profile Migration editor. To get to it, follow these steps;

1. If you open up your Management Console, and go to Tools>Distribution>OS Deployment
2. I am going to show you how to edit the XML in the provisioning template as OSD is gone in 9.6. But the same XML can be used in either location.
3. Go into you're "my templates" section and create a new template (or edit an existing one). Create a "Capture Profile" action.
4. Once you have added the action, you can browse to add a new Command XML, or edit to edit one.
5. Hit "Edit" and select the template you want and hit "Edit" again. You can place the attached SampleProfileXML in the "...\ldlogon\uma\commandxml" folder and use it, or use one you are already working with.

Now that you are in the editor, here are some of my tips to remember when building a Profile Migration Script (Command XML);

Tips

1. I found it best to INCLUDE all and then EXCLUDE the specific Users, Files, and Folders you do not want captured. When you look at the Command XML, you’ll notice on the User Profiles, and on Files and Folders I INCLUDE each of the top directories I want, and then EXCLUDE the lower directories I do not want captured.
2. When doing either an INCLUDE or EXCLUDE, make sure to check the “Scan Sub Folders” option if it applies.
3. There are some good variables that are specific to UMA\SMA, you have to look in the Documentation to find them.
   1. http://download.lenovo.com/ibmdl/pub/pc/pccbbs/thinkvantage_en/sma60dg_en.pdf
4. I found it best to have the users logged off at time of capture and deployment, but I have seen successful captures with the user logged on as well.
5. The “My Documents” section, when you are building your script, appears to be useless, I just ignore it all together. All of you're "My Documents" can be included in the selection of "User Profiles" and in the "Files and Folders"  as shown above in rule # 1. The %Personal Directory% variable takes care of it unless the user has been added to the exclude list.
6. When in doubt, check the documentation listed in Rule # 3, it actually has a lot of information.

Attached is the sample XML script as listed above. If you open it up in the Profile Migration editor, you can see how I apply each of the above mentioned rules.

I am working with LD support but what I am curious about is after CTOS and the machines boots into Windows how long until the ldprovision fully loads? There is some version of an "agent" loading but they are telling me to build in a 10 minute wait after CTOS and once it boots into Windows.

In system config is wait your first action? If so how long is it?

So i am trying to deploy Win 7 to a Dell Optiplex 740 (amd processor) using LDMS 9 SP2. with provisioning and I am using imagex as my capturing tool. I have captured both the 100Mb system partition and the partition with my image on it into two separate .wim files. And I am attempting to deploy both images back to a freshly formatted hard drive.The problem is that after the provisioning template wipe all the volumes and partitions on the machine, it fails when trying to deploy the image. The error is this:

action index=57540 type=Deploy_image
FAILED
error:[80001803H]The action failed.
Execute result:
return:2
output:

and in the command prompt it says this:

Error setting temp path: [C:\].

The system cannot find the path specified.

the only thing i have really found that pertains to deployment and this error code is that it could be that my WinPE image doesn't have the right driver for the disk. But this is a standard (very common) WD Blue Caviar hard drive. And besides, I have run diskpart.exe from WinPE and it is seeing the drive. And my WinPE image appears to have every frickin driver in the universe on it.

I am not even sure that I am supposed to be capturing and deploying both .wim files but I have not found any solid documentation on these forums with instructions (using ImageX) to successfully capture and deploy a Win 7 image.

The attached file is the ldprovision.log file (shortened) and it looks like it is fails at "tryallwebservice." so i am not sure if this has anything to do with IIS. I am still able to deploy my XP image with no problems and nothing has changed on my core, except installing SP2. But i have successfully pushed out my XP image since installing SP2.

Any help would be appreciatied since my boss wants to know when the hell i am going to upgrade all my labs to Win7.

thanks.

jeff

Description:

When provisioning a device with an OEM license provisioning doesn't continue after the reboot into windows.

Cause:

With Windows 8 and Windows 8.1 Microsoft made a change to the sysprep environment  to improve the end user experience by skipping the SetupComplete.cmd section if an OEM license is detected. This allows the end user to get to the Welcome Screen faster. This is what causes provisioning to fail to start after the reboot.

To see if you are experiencing this issue look in C:\Windows\Panther\UnattendGC\Setupact.log after you have booted into windows and provisioning doesn't continue.

You should find this line.

[msoobe.exe] OEM license detected, will not run SetupComplete.cmd

Resolution:

To resolve this you need to add a First Logon Command to your unattend file. It should look like this.

<FirstLogonCommands>

                <SynchronousCommand wcm:action="add">

                    <Order>1</Order>

                    <CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>

                    <RequiresUserInput>false</RequiresUserInput>

                </SynchronousCommand>

</FirstLogonCommands>

If the SetupComplete.cmd file isn't there you can create your own file or script to inject to reference.

The file just needs to have this command.

C:\ldprovisioning\ldprovisioning.cmd

Also be sure to change the path

<CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine>

to match your new file location.

Applies to LANDesk Management Suite 9.5 SP1 and newer

Description

Hardware Independent Imaging allows drivers to be injected during the imaging process specific to the destination hardware. During hardware migration planning, driver decisions must be made.  In order to assist with that migration planning a preview option has been added to HII, enabling IT to review driver assignments prior to upgrading to a new OS.

Requirements

• The client where the preview is being run must have an agent installed.
• The client must be able to download the drivers.db3 file from the core server.

Running HIIClient

1. Copy HIIClient.exe to the client from the core. The file can be found in the %LDMS_HOME%\landesk\files directory.
2. Run HIIClient with the appropriate preview options (See below).
3. Review the logs for driver assignment and detection found in the directory where HIIClient was run.

Note: If HIIClient.exe is ran from a directory that the log is unable to be wrote to (i.e. C:\HiiClient.exe) it will write to C:\Windows\Temp\HIIClient.log

HIIClient.log

HIIPreview.log

HIIClient options

hiiclient [/?] [/uncpath] [/taskid <taskid>] [/preview | /previewall] [/os <os> /arch <architecture>]

/? - Shows standard help and syntax information

/uncpath - Specifies if HII should use unc based paths to drivers

/taskid - Specifies the <taskid> to use to ask for SWD snippet when processing packaged drivers

/preview - Specifies if HII should run in preview only mode.

/previewall - Specifies if HII should run in preview only mode with debug information.

/os - Only valid with both /preview and /arch.

          Specifies which OS the preview should be run for.

          Valid options are: winxp, win7, win8, server2003, server2008r2, server2012

          If not specified the currently detected OS will be used.

/arch - Only valid with both /preview and /os.  Specifies which architecture the preview should be run for.

          Valid options are: x86, x64.

          If not specified the currently detected Architecture will be used for the preview.

Purpose:

After making any change to the boot.wim, or after applying any major LANDESK patch on the Core Server, PXE Representatives should be redeployed.

Solution:

You have three methods to accomplish this. Your end goal is simply to replace all of the *boot*.wim files on the PXE Representatives so that they match what you have on the Core Server

Method #1: Schedule the PXE Representative Deployment Script (LDMS 9.5 or earlier) or Distribituion Package (LDMS 9.6) and target your PXE Representatives.

     1. (9.5 or earlier) In the Management Console go to Tools>Distribution>OS Deployment>All other Scripts>PXE Representative Deployment

     2. Schedule this script:

     3. Target your PXE Representatives. If you have multiple, the easiest way to identify them is to look at the "PXE Representatives" in the console.

     4. Drag all of these devices down to your scheduled task, and kick it off.

Method #2: Copy over and replace all of the boot*.wim files from your "...LANDesk\ManagementSuite\landesk\vboot" folder on your Core to the following folder on the PXE Representative:

Program Files\LANDesk\PXE\System\images\Boot

Method #3: The following script will do Method #2 for you. Script to Update the WinPE image on PXE representatives

I'm trying to move to using VMWare Workstation to maintain my image.

Here's what I plan on doing:

• Update the VM (patches, new software, new settings)
• Take a snapshot
• Sysprep it (remove LANDesk, reset Symantec, delete files/folders, and then sysprep)
• Pull the .wim
• Revert to pre-syspreped VM
• Rinse, repeat

So far I'm having issues though when imaging with that .wim. Most often it's network. Typically the network driver installs however there is no connection. (Shows up in hardware manager) If I try and go to look at the interfaces though I get a "Class not available" error.

Does anyone have any experience/guidance in this?

I've asked Mr. Google about this, but he hasn't been very helpful. 

I've created my thin base image of Win7 x64 Enterprise and generalize it before capture.  I have steps in the System Configuration phase that set the registry keys for pointing updates to our WSUS server.

I just recently noticed that updates are off after the template has finished.  A simple click of the button will turn them on, but that leaves it up to the technician to ensure that is done.

I went back to my base image vm and the updates are turned on before generalization, but when I generalize the vm, sysprep appears to be turning it off before shutting the vm down for capture.

I am running 9.5 SP2 and am planning on moving to 9.6 soon, but this doesn't seem to be a problem with LD.  Am I missing a reg key that turns them on?  Below are the registry settings that are being made in my template:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"="http://windowsupdate.WSUSServer.com"
"WUStatusServer"="http://windowsupdate.WSUSServer.com"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"AUOptions"="4"
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"NoAutoUpdate"=dword:00000000
"RescheduleWaitTime"=dword:00000001
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:0000000c
"UseWUServer"=dword:00000001
"NoAUAsDefaultShutdownOption"=dword:00000001

Hi,

Couldn't find any questions specifically for this.

We purchased some tablet devices that we would like to image using a USB ethernet adapter.

Our imaging process uses machines pre-imported into Landesk with csvimport.exe:

Machine Name, MAC, Serial

Reason for this is that we insert variables into the unattend.xml file to set the machine-name and join it onto the domain

if I use csvimport.exe and set all the MAC address' to use the same ethernet controller then when importing these, each machine in the list would overwrite each other.

My question is what is the best way to go about imaging these machines?

I'm going to import them using the wireless MAC address and report back if this worked

Description:

In LDMS 9.6 a new feature was added called Machine Mapping. This feature is found under Toolbox -> Distribution -> Machine Mapping.

This feature was created to make it easier to provision new systems more dynamically with less work by the administrator.

It was specifically built to utilize three template actions, Install Mapped Software, Launch Template, and Deploy Profile.

This document will give you an understanding of how Machine Mapping is used and how to set it up.

Configuration:

Open the Toolbox to Distribution and click on Machine Mapping.

This is a simple process.   You have a Source, Destination, and Days Valid.

To add a device to the Source or Destination simply drag it from the device list above to the desired area.

Days Valid is how long that mapping will function. This is useful if you need are provisioning many systems and need a specific time frame.

Uses:

To present how this can be used to benefit your environment I will give a few case studies.

Case Study #1

You need to provision new systems for different departments, accounting, sales, and marketing. Each of these departments requires different software. You could create three different templates with the different software but it is much more efficient to use Install Mapped Software and Machine Mapping.

To do this you just need to designate one template machine from each department. In the screenshot above you can see that Win8xTA is being used as the template machine for 3 other systems.

With this set every time a system is being provisioned and gets to this template action it will look at the Machine Mapping and then install the software that has been mapped, In other words if the template system was an Accounting system and it had Dynamics installed, the Install Mapped Software action would install Dynamics on the system being provisioned. If the system you are provisioning is mapped to the template system in Marketing and that has Photoshop installed, Photoshop will be installed on the new system when the action executes.

(Important: This will only work if you have set up Product to Package Mapping. How to Configure Product to Package Mapping and Install Mapped Software)

Case Study #2

You are migrating users to new systems and need to get their profiles and software moved over with minimal work.

To do this, first create the Machine Mapping for the old machine as the Source and the new machine as the Destination.
Example in the first screen shot WIN8-1X64 mapped to WIN81X64-3

Then create two provisioning templates.

First create template with Install Mapped Software and Deploy Profile actions in System Configuration.

(Be sure to set Deploy Profile to Useautomatic naming.)

Second create another template that is configured with Capture Profile and Launch Template actions.

(Be sure to set Deploy Profile to Use automatic naming.)

Select the first template created in the Launch Template action.

Finally, schedule the second template to the source system. It will capture the profile from the old machine and then launch the first template on the destination, which will then install the software from the old system and restore the profile.

(Note: There is a slight delay between the Launch Template action and the new template starting.)

(Important: Also if there is no Machine Mapping for the system and you have a Launch Template action, it will schedule the new template to itself.)

Finally enjoy the time saved from not having to move, name, or copy files,or manually installing specific software.

Description:

Product to Package Mapping and Installed Mapped Software are powerful new components that were introduced in LDMS 9.5 SP2 and are used in LDMS 9.6.

Product to Package Mapping allows you to use a template system or a previous inventory scan for the same system and automatically install software based on the template.

This is very useful for old to new migrations and even in-place migrations. Also it saves time in customizing individuals computers whose old computer failed or those who are getting new systems when paired with machine to machine mapping and profile migration.

This document will walk you through how to set this up so you can start using it in your environment.

Configuration:

1. Configure Products in Software License Monitoring

Open Reporting/Monitoring in the Toolbox and open Software License Monitoring. (Note: You need Silverlight installed to see the webpage.)

Next select Products and Discovered.

In Discovered you will find Software discovered on your systems by LANDESK.

(Note: If you don't see the software you are expecting, you can add custom products here How to add a Custom Product to Software License Monitoring

Also if you want to set up License tracking and other options please review the following landing page as it is not covered in this document:

Software License Monitoring (SLM) Landing Page)

While in Discovered right click on the software you would like to use in Product to Package Mapping and go to Move to -> Monitored.

Once you have set all of the items you want to Monitored, click on the Monitored tab to ensure they are all there.

Close the Software License Monitoring window.

2. Set up Product to Package Mapping in Provisioning

Open the toolbox in Distribution and then OS Provisioning/OS Deployment (LDMS 9.6/9.5 SP2) and click on the Product to Package Mapping icon.

If you skipped or didn't configure Software License Monitoring this is what you'll see.

If you did configure Software License Monitoring you should see the packages you've set to Monitored.

You can now begin mapping your install packages to the software. To do this simply click in the SWD Packages box and then double click the desired Distribution Package.

(Note: If you don't have any distribution packages please start here. Software Distribution .)

(Important: You don't have to map Chrome -> Chrome or 7-zip -> 7-zip. As you can see in the screenshot you can map the install packages to anything. I mapped Office 2013 to 2003, 2007, and 2013 because I want any old systems that had an inventory of of 2003 or 2007 to get the new 2013. This is extremely useful in old to new migrations or system replacements. I have also mapped Silverlight to install on all of my virtual machines with VMware tools and I want Firefox on everything that has Microsoft Visual C++).

Once you have finished mapping click Assign and Close.

3. Add Provisioning Action Template Install Mapped Software

Everything has been configured, the final piece to get this working is to add the Install Mapped Software template action to your provisioning template.

(9.6 users, this action is added automatically if you create your template with the provisioning wizard.)

Final Notes

This feature is mostly to be used in conjunction with Machine to Machine Mapping in LDMS 9.6 How to use Machine Mapping in LDMS 9.6

In LDMS 9.5 SP2 and later it still works for in place migrations. (I.E. XP to Windows 7 or Windows 7 to Windows 8 on the same system.)

Hi All,

So let me explain my situation and then one of you hero's hopefully can help me out!

We have several remote sites which are slow links, the machines on these sites are XP so the mission was to get them upgraded in place to Windows 7. My plan was to build a PXE rep and Preferred server (on the same host), Take them to site, set of the upgrade. Now in testing on core sites the templates fine no issue HOWEVER, on the slow link sites it fails as it times out rebooting the client into the PE environment from Windows. I have attached what the template is doing but the long and short of it is:

The template starts within the OS and performs USMT (works fine) it then goes to reboot into the PE environment, to do this it copies down files including the boot.wim. Now for some reason as can see from the logs its not getting this boot.wim and other files from the PXE host, its going back to the core which is over a slow link which is why its all timing out. Now I can lower the boot.wim size but its still going to be touch and go as I have slower links yet to do.

Now this behaviour is crazy considering if you boot the machine to PE normally it will get the boot.wim and other files from the PXE server. So I need to force the clients to go to the PXE for the required files OR increase the time out.

This must have happened previously to people so there must be a solution out there. I have spoken to LANDesk but they seem to have no solution..... Can anyone help?

hello,

I can't use HTTP on PreferredServer.

so when i use provissioning with a device who have agent, Landesk want download WIM ... with http on core server on WAN. ....

how to use landesk with UNC for complete provisionning

thanks a lot

Environment:

LDMS 9.6 (Confirmed)

May apply to earlier versions using ImageW.

Review Date:

10/24/2014

Problem:

When provisioning using ImageW, provisioning uses all drive space instead of the original size of the image. 

For example:  You have a captured Windows 8 image that had a 60 GB system partition when captured.  When you deploy this image to a desktop that has a 500 GB hard drive, the system partition is expanded to 500 GB, leaving no unallocated space for other purposes.

Cause:

By default, ImageW uses scaling that automatically increases the captured partitions to the size of the physical drive it is deployed to.  This is controlled by the /x command in the "Deploy Image" action in provisioning templates.

Solution / Workaround:

Solution 1:

Remove the /x command from the "Command-line parameters" in your Deploy Image task.

Solution 2:

Add /nos:size to your "Deploy Image" task in a provisioning template.  If you don't want scaling to happen at all, use solution 1 or use a large number such as 1000g.

    Example: /nos:100g will not allow a partition that is smaller than 100 GB to scale.  If you have a partition captured that is 120 GB, it will scale.

Before:

After:

Other Information:

Consult the ImageW manual: http://www.terabyteunlimited.com/downloads/ifw_en_manual.pdf

Note: This is customer submitted information.   This is not officially supported by LANDESK Software.

Description

When PXE booting using LANDESK PXE boot, a DHCP server is necessary to provide an IP Address. However, there are 4 scope options in DHCP that are related to PXE. This article summarizes them and their settings.

DHCP Scope Options

There are 4 DHCP Scope options related to PXE that can work in 2 sets of 2:

• 43 and 60
• 66 and 67

When a PXE client boots, it sends out a DHCP request. This DHCP request contains option 60 to identify it as coming from a PXE client and not an OS.

A normal (Microsoft) DHCP server will reply with a DHCP provided IP address but, when neither option 60 nor option 43 is set in the DHCP Scope options, the PXE clients will still have no clue where the PXE server is and will therefore wait until a PXE server contacts them. In this way, the PXE server must listen to DHCP discovery packets containing option 60 sent by PXE clients and answer at the same time as the DHCP server does. This is the default method and also the reason why you might need to add IP Helper addresses of the IP of your PXE Representative to your VLAN configuration in the same way you would for a DHCP server when the clients and your DHCP/PXE are in seperate VLANS.

However, a DHCP Server that also has the PXE representative installed will send out only 1 reply, so we need option 60 set in DHCP. When option 60 is set to 'PXEClient', it means that the DHCP server knows where the PXE server is. If option 43 is not set, it means the PXE server is on the same computer as the DHCP server (same IP address). If option 43 is set, PXE clients must decode option 43 to know how to reach the PXE server.

Option 60 is not normally available in DHCP, but can be created and set automatically by running the following commands:

netsh dhcp server add optiondef 60 PXEClient String 0 comment=PXE support

netsh dhcp server set optionvalue 60 STRING PXEClient

After the client receives the PXE answer it needs to go to the next step, which is to download a boot environment. This is where DHCP options 66 and 67 come in. Option 66 tells the PXE booted client what the Bootserver is and option 67 the Bootfile that needs to be loaded.

These 2 options (66 and 67) don't work with LANDESK PXE representatives and should always be left unconfigured.

The LANDESK PXE makes use of an extra layer in the bootprocess, the LANDESK PXE menu, which includes options for Local Boot, WinPE menu, WinPE Provisioning etc. Configuring the DHCP option 66 and 67 means a PXE Boot will equal a boot to a boot environment like WinPE, which presents no flexibility.

Summary:

• Set Option 60 if the PXE representative is installed on a DHCP Server, leave option 43 unconfigured.
• Set Option 60 in combination with option 43 if the PXE representative is not on the DHCP server, but also not in the broadcast range of the client
• Options 66 and 67 should NOT be set.

working on trying to capture the image with Provisioning in 9.5 with the elitepad integration patch.

I have thrown practically every NIC I can think of into my boot.wim & still can't get it to pick up a valid IP address.

I have the HP docking station with the LAN9512-LAN9514 USB 2.0 to Ethernet 10-100 Adapter driver, along with several PROWIN64 drivers. Can anyone point me to the correct driver that needs to be loaded?

I have a scheduled task set up that boots to PE fine & also have a USB boot stick that also loads PE fine, but it keeps bombing on finding the ip address...  PXE reps have also been re-deployed btw.

Thanks!

-Dave

Hello,

I'm trying to capture a computer with Landesk 9.6.

Proccess :

I create a capture template (Capture W7) with the new creation system.

I start the computer using the network.

Select F8 - Windows provisionning.

I enter the credentials for the template.

I choose the template created (Capture W7).

As I saw in a another thread, I look at the Captureimagehandler.log and maptopreferredhandler.log.

It seems to be a credentials issue but can't find where.

When I create the preferred server, I only enter the name and the read only credential.

Is there something else to do?

Here is the maptopreferredhandler.log :

Downloader/Multicast using config file located here: X:\ProgramData\LANDesk\TMCDownload\downloadermulticastconf.xml

2014-10-30 23:19:49(1180-908) maptopreferredhandler.exe:******Mapping to: \\10.0.0.62\images\W7

2014-10-30 23:19:49(1180-908) maptopreferredhandler.exe:Drive letter = e

2014-10-30 23:19:49(1180-908) maptopreferredhandler.exe:Mode - Require Direct, no preferred server.

2014-10-30 23:19:50(1180-908) maptopreferredhandler.exe:Could not get credentials for preferred server.

2014-10-30 23:19:50(1180-908) maptopreferredhandler.exe:End of Map Drive.  Path used: - \\10.0.0.62\images\W7\.

Downloader/Multicast using config file located here: X:\ProgramData\LANDesk\TMCDownload\downloadermulticastconf.xml

2014-10-30 23:19:50(1000-788) maptopreferredhandler.exe:******UnMapping Drive

2014-10-30 23:19:50(1000-788) maptopreferredhandler.exe:Drive letter = e

2014-10-30 23:19:50(1000-788) maptopreferredhandler.exe:Could not map or unmap drive. Error code: 2250

2014-10-30 23:19:50(1000-788) maptopreferredhandler.exe:End of UnMap Drive.

Best regards

Pascal Descamps

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.

Hi,

I have read a lot of articles here in the community very similar to my problem however it did not solve it.

I just build a new 9.5 server with Sp3 (problem appear before upgrade also)

The problem when I do capture it is stuck more than usual on Diskpart command, and then the screen disappear and nothing happened. from the below log you can see that the diskpart command was executed fine, but I doubt that.

As some other people here suggested to change the drive map to Z and Y instead of I and H, I did this also with no luck.

I have tried with both methods, running manuly by selecting the image, or by schedule task.

all the landesk services are up and running, and I even restarted the server couple of times.

Is this problem might be related to .Netframe work? because I got error that it is not installed on my server and I downloaded form the internet, maybe was a wrong version i don't know but it is 4.0.3

Please guys I am seeking for your kind of support as this is an urgent matter for me.

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

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:07 PM,11/1/2014 11:04:11 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/bootfile.exe" /disableclientqueue"

"AGENT01","OK",0,0:00:03,11/1/2014 11:04:12 PM,11/1/2014 11:04:15 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/tlibr16.dll" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:16 PM,11/1/2014 11:04:20 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/tlibr32.dll" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:21 PM,11/1/2014 11:04:25 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/lddefrag.exe" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:26 PM,11/1/2014 11:04:30 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/FlushBuffer.exe" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:31 PM,11/1/2014 11:04:35 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/cicfgmgr.vxd" /disableclientqueue"

"AGENT01","OK",0,0:00:03,11/1/2014 11:04:36 PM,11/1/2014 11:04:39 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/cindis.vxd" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:40 PM,11/1/2014 11:04:44 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/copyfile.exe" /disableclientqueue"

"AGENT01","OK",0,0:00:05,11/1/2014 11:04:45 PM,11/1/2014 11:04:50 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/boot.img" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:04:51 PM,11/1/2014 11:04:55 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/vboot/ChangeBCD.exe" /disableclientqueue"

"AGENT01","OK",0,0:00:03,11/1/2014 11:04:56 PM,11/1/2014 11:04:59 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /dest="C:\Program Files\LANDesk\LDClient\BCD" /p="http://10.5.5.209/landesk/vboot/BCD.dat" /disableclientqueue"

"AGENT01","OK",0,0:00:04,11/1/2014 11:05:00 PM,11/1/2014 11:05:04 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.5.5.209/landesk/files/bcdedit.exe" /disableclientqueue"

"AGENT01","OK",0,0:00:01,11/1/2014 11:05:05 PM,11/1/2014 11:05:06 PM,"<qt/>C:\Program Files\LANDesk\LDClient\ChangeBCD<qt/> <qt/>C:\Program Files\LANDesk\LDClient\bcdedit.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\BCD<qt/>"

"AGENT01","OK",0,0:00:23,11/1/2014 11:05:07 PM,11/1/2014 11:05:30 PM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /dest="C:\boot.wim" /p="http://10.5.5.209/landesk/vboot/boot.wim" /disableclientqueue"

"AGENT01","OK",0,0:00:00,11/1/2014 11:05:31 PM,11/1/2014 11:05:31 PM,"<qt/>C:\Program Files\LANDesk\LDClient\copyfile.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\boot.img<qt/> <qt/>C:\Program Files\LANDesk\LDClient\BCD<qt/> \boot\BCD"

"AGENT01","OK",0,0:00:26,11/1/2014 11:05:32 PM,11/1/2014 11:05:58 PM,"<qt/>C:\Program Files\LANDesk\LDClient\lddefrag.exe<qt/> <qt/>C:\Program Files\LANDesk\LDClient\boot.img<qt/>, STATUS"

"AGENT01","OK",0,0:00:09,11/1/2014 11:05:59 PM,11/1/2014 11:06:08 PM,"<qt/>C:\Program Files\LANDesk\LDClient\FlushBuffer.exe<qt/>, STATUS"

"AGENT01","OK",0,0:00:00,11/1/2014 11:06:09 PM,11/1/2014 11:06:09 PM,"<qt/>C:\Program Files\LANDesk\LDClient\bootfile.exe<qt/> C:\Program Files\LANDesk\LDClient\boot.img /keep /bootunsafe, ASYNC"

"AGENT01","OK",0,0:02:11,11/1/2014 11:06:11 PM,11/1/2014 11:08:22 PM,"WINPE, TIMEOUT=1800"

"AGENT01","OK",-2147024809,0:00:02,11/1/2014 11:08:23 PM,11/1/2014 11:08:25 PM,"diskpart /s X:\LDClient\rmvol.txt"

"AGENT01","ERR_Fail",-1917190197,0:02:24,11/1/2014 11:08:26 PM,11/1/2014 11:10:50 PM,"ldrun drvmap.exe BISDC01\administrator 20973FB2DDB14CE04AA0A52B453F1DB86A1546C741B I: """\\BISDC01.Ava.com\Images""", STATUS FACILITY=3513"

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