Hello,

I have a Win7 x64 image which has been sysprepped (generalized and audit mode) which used to work, but for some unexplained reason it now does not finish the whole provisioning process  No errors are reported in LDMC for it.

After the WinPE process completes the machine goes through the process of installing drivers, which is normal.  However once this is done and it boots into Windows for the first time it just sits there.  The provisioning process does not complete.  I have looked around and done as much research as possible, but I have not found an actual solution to the problem at this time.  I have found after CTOS reboots that "C:\ldprovisioning" is created with two files in it - launchldprovisionasuser.exe and ldprovision.exe.  If I execute the first and then the second executables the provisioning process picks up where it left off and installs the agent and any additional packages that I have added to the template.

Has anyone else seen this or have any ideas what I can do to resolve it?

Recently Upgraded to 9.5 and so far everything is working well except for OSD tasks with our Wyse Z9os7 thin clients.  PE loads up and get all the way thru loading the driver and then it times out waiting for an IP.  just show's the loop back address.  No lights on on the eithernet jack.  I know a driver is not loading even though it says that it is.  Any Ideas would be greatly appriciated.

Another issue after upgrading to 9.5.   We are now unable to pxe boot to a provisioning template.  Well,  we are able to pxe boot to the point where we choose the template, but then nothing. It times out.  It goes to 40 and then the drop down menu appears again to choose the template.  This used to work great and was a great too for computers that we were unable to deploy the templates to within the management console.  Any body else have any experience with this?  For the record the templates did update after the upgrade and the new sections were populated. We are still able to deploy the templates from the management console and they work great...it's when pxe booting there is a problem.  Thanks.

Is there a limit to the size of profile that can be captured with a provisioning template using UMA?  It seems larger profiles sizes fail when smaller sized profiles are successful.  There is plenty of space to store the large profile.

Trying to get to the bottom of an issue I am having with the deploy profile command in my osd provisioning template using 9.5. The capture profile works fine and the profile can be manually restored or used in a template as a stand alone deploy profile command, but the deploy profile fails when used within my complete template. This seems to happen only to profiles larger than 3GB. 

I have checked the ldprovisioning logs and it indicates that the ldprovision.exe: Reporting action status:  5 to Core right before the deploy profile fails.

I have checked the deploy profile handler log and it indicates:  DeployProfileHandler.exe:Executed Command. Return value is 259. 

My question is does anybody know what these error codes indicate.  I am hitting a brick wall when it comes to being able to confidently capture and restore a users profile. 

How can I export OSD script task from a LDMS 9.5 preproduction core server to another LDMS 9.5 production core server? Is there any way to avoid manually recreating all the OSD script task in the new core server?

I have tried to use export/import menu option but it fails to complete with an error:

Any ideas on how to export this OSD scripts

Thanks!

Hello, I have a provisioning template that we were having issues with at the beginning of the week that support helped us fix and got working after patching the core with a followup to fully work with 9.5.

The machines we work with are mainly HP 8xxx series and on Tuesday we got provisioning working again without making any change to our template other than adding an action to map the prefferred server back to the core for the image tools etc.

And then Wednesday I went to provision more machines and ran into the fixwindows action failing on all 8xxx series machines, but oddly enough it ran just fine on the z420 workstations I had to do as well. I spent the better part of Wednesday trying to figure out why. Removing the fixwindows action lets the template proceed to next action of the unattend inject followed by HII, both of those tasks however fail and without a NIC driver the template is basically dead at that point even though its not failed.

Manually running fixwindows gives me the BCD not found regardless of partition forcing. LDMS shows an error of -2147479552 for fixwindows.

If I run without the fixwindows I get an error of -2147478271 for the unattend inject and an error of -2147477501 for HII.

I'd prefer to keep the fixwindows as we tend to have a hodgepodge of systems that can have multicard readers and dual dvd drives, to systems with more than a pair of hard disks.

Hi All,

I'm on LDMS 9.0 and having a random issue with OSD.

For the most part, it works fine. However every once in a while I will have a machine that just refuses to complete the process. I cannot come up with a rhyme or reason yet.

For instanc, I imaged a Lenovo T410 this morning with no issues. However now I am trying to image a lenvo T400 and am running into the problem descibed below.

I am able to pxe into OSD without issue, PE loads and I am able to select my OS options to be deployed. Once options are selected, i hit continue and I sit an stare at the blue LD splash screen forever, the Ghost application never launches.

Here is the Log from my recent OSD attempts, I was hoping someone might be able to help me figure this out.

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

"0018FE6E777C","OK",0,0:00:01,6/13/2013 10:37:21 AM,6/13/2013 10:37:22 AM,"WINPE, TIMEOUT=1800"

"0018FE6E777C","OK",230227968,0:00:00,6/13/2013 10:37:23 AM,6/13/2013 10:37:23 AM,"ldrun drvmap.exe qsamericas\landesk 20C79AAC164080432A952F00B73ADB9F7FB6D026801 I: """\\qshbld03\appdeploy$""", STATUS FACILITY=3513"

"0018FE6E777C","OK",230227968,0:00:01,6/13/2013 10:37:24 AM,6/13/2013 10:37:25 AM,"ldrun drvmap.exe qsamericas\landesk 20C79AAC164080432A952F00B73ADB9F7FB6D026801 H: """\\qshbld03\ldmain""", STATUS FACILITY=3513"

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:37:26 AM,6/13/2013 10:37:28 AM,"ldrun sdclient /f /o /dest="X:\LDClient\LDPathExist.exe" /p="http://172.16.15.237/landesk/files/LDPathExist.exe", STATUS"

"0018FE6E777C","OK",0,0:00:00,6/13/2013 10:37:29 AM,6/13/2013 10:37:29 AM,"ldrun LDPathExist.exe """I:\Images\Ghost\HP\DX5150\DX5150W7BASE.GHO""", STATUS"

"0018FE6E777C","OK",0,0:00:01,6/13/2013 10:37:30 AM,6/13/2013 10:37:31 AM,"ldrun LDPathExist.exe """H:\osd\Ghost\GHOST\GHOST32.EXE""", STATUS"

"0018FE6E777C","OK",-2147024809,0:00:00,6/13/2013 10:37:32 AM,6/13/2013 10:37:32 AM,"diskpart /s X:\LDClient\rmvol.txt"

"0018FE6E777C","OK",0,0:00:01,6/13/2013 10:37:33 AM,6/13/2013 10:37:34 AM,"diskpart /s X:\LDClient\wipeDisk0.txt"

"0018FE6E777C","OK",0,0:00:09,6/13/2013 10:37:35 AM,6/13/2013 10:37:44 AM,"cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:"

"0018FE6E777C","OK",230096896,0:08:48,6/13/2013 10:37:45 AM,6/13/2013 10:46:33 AM,""ldrun RunBatch -1 h:\osd\Ghost\GHOST GHOST32.EXE -clone,mode=load,src=i:\Images\Ghost\HP\DX5150\DX5150~1.GHO,dst=1 -sure -auto", STATUS FACILITY=3511"

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:34 AM,6/13/2013 10:46:36 AM,"ldrun sdclient /f /o /dest="X:\LDClient\diskinfo.exe" /p="http://172.16.15.237/landesk/files/diskinfo.exe", STATUS"

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:37 AM,6/13/2013 10:46:39 AM,"ldrun sdclient /f /o /dest="X:\LDClient\assvol2.txt" /p="http://172.16.15.237/landesk/files/assvol.txt", STATUS"

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:40 AM,6/13/2013 10:46:42 AM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\RMVOLLETTER.TXT" /p="http://172.16.15.237/landesk/files/RMVOLLETTER.TXT""

"0018FE6E777C","OK",0,0:00:01,6/13/2013 10:46:43 AM,6/13/2013 10:46:44 AM,"ldrun tokreplw X:\LDClient\assvol2.txt partition=1"

"0018FE6E777C","OK",-2147024809,0:00:02,6/13/2013 10:46:45 AM,6/13/2013 10:46:47 AM,"diskpart /s X:\LDClient\RMVOLLETTER.TXT"

"0018FE6E777C","OK",0,0:00:00,6/13/2013 10:46:48 AM,6/13/2013 10:46:48 AM,"diskpart /s X:\LDClient\assvol2.txt"

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:49 AM,6/13/2013 10:46:51 AM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\fixvista.bat" /p="http://172.16.15.237/landesk/files/FixVista.bat""

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:52 AM,6/13/2013 10:46:54 AM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://172.16.15.237/landesk/files/fixntfs.exe""

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:55 AM,6/13/2013 10:46:57 AM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://172.16.15.237/landesk/files/bcdedit.exe""

"0018FE6E777C","OK",0,0:00:02,6/13/2013 10:46:58 AM,6/13/2013 10:47:00 AM,"ldrun sdclient.exe /f /o /dest="x:\cba8\FixWindows.exe" /p="http://172.16.15.237/landesk/files/FixWindows.exe""

"0018FE6E777C","OK",-2147481750,0:08:13,6/13/2013 10:47:01 AM,6/13/2013 10:55:14 AM,"ldrun x:\cba8\FixWindows.exe 1"

"0018FE6E777C","ERR_TimeOut",0,0:06:52,6/13/2013 10:55:15 AM,6/13/2013 11:02:07 AM,"cmd /c copy /y X:\LDClient\guid.pds C:\LDISCAN.CFG"

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

Much appreciated!

Hello,

we are new to LanDesk, now the core server is 9.0 SP3. We are testing the UMA profile migration tool. It looks like working properly, except for... the Internet Explorer Favorites. The whole profile is exported and imported (documents, desktop, wallpaper, color, and so on) and not the "ordinary" favorites! Our OS is Italian, don't know if it matters (and shouldn't...). Thank you!

Hallo,

wir haben dieses Jahr die LANDesk Management Suite bei uns im Unternehmen eingeführt. Wir haben unsere bisherigen Geräte immer mit OTRS inventarisiert und verwenden als Hostnamen, die Inventarnummern die mit OTRS erzeugt worden sind.

Da wir bald mit Data Analytics die Inventarisierung durchführen möchten, möchte ich wissen wie man LANDesk so einstellen kann, dass die Konsole jedem neuen Gerät, welches sich per PXE beim ersten Mal inventarisiert eine neue Inventarnummer erzeugt wird, die dann auch gleichzeitig als Variable "ldHostname" dem Gerät zugewiesen wird.

Hat damit jemand schon Erfahrungen gesammelt?

Has anyone been using Profile Migration in LDMS 9.0 sp3?

I need to do a ton of hardware refresh and I currently have something that works, migrates all user profiles. However, I'm looking for the different variables that you can use to also backup the Pictures, Movies etc..

Let me know if anyone is successfully using it.

Thanks

Jose Cruz

Create Partition

To reduce the number of actions needed in a template additional options have been included with the create partition action handler. They include the ability to mount the newly created parittion, format the partition, and make the partition bootable. The ability to create GPT partitions has also been added.

Hardware Independent Imaging (HII)

HII can now be run in both the Post-OS configuration (WinPE) section of provisioning as well as the System configuration section (Client OS). During the Post-OS configuration HII will only apply driver files. Driver setup packages are ignored. During the System configuration HII will apply assigned driver setup packages. Driver INF files are ignored as they should already have been applied in the Post-Os configuration.

Patch System

The option to select the scan and repair settings that will be used has been added.

Template Options

Template options have been added to allow provisioning to run silently, control how long the client GUI is visible after completing and to retain the provisioning folder when the template has completed.

Windows Refresh

Support for Windows 8 refresh and reset have been added. Note that recovery media from your manufacturer may be required. Options for using the local WIM or specifying a WIM are available.

Reset: Deletes all personal files and settings. By default will quick delete files meaning files could be recovered using special software. Checking the option to fully clean the drive will erase data thoroughly making  recovering deleted files far less likely.

Refresh: Does not affect user data or settings.

Create and assing local WIM: Creates and image of the device in the current statue and assigns it as the local refresh/reset wim.

Assign specified image as local WIM: Assigns a new WIM as the local WIM on the device.

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.
   1. HIIClient.log
   2. 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.

Hi

I am using LANDesk Management Suite 9.5 and we do OSD. We have a problem with the template action "Map drive to preferred server". I don't know if our configuration of the action is wrong because the client fails always at this step. I uploaded a screenshot in the attachement.

Thanks

HI

I Encountered an error When use  OSD of 9.5

System image  is win7 , through the Sysprep forpackage，

Deployment when face the following error：

"Windows encountered an internal error setup is loading or search no answer file"

But when I use the same image packets are deployed on 9.0sp3 is successful.

Thankyou！

Applies to LANDesk Management Suite 8.8 and newer.

Description

This document is intended to show the versions of WinPE used in each version of LANDesk Management Suite. The goal is to facilitate getting the correct drivers for the WinPE version being used.

Note: In LANDesk Management Suite 9.5, the 64-bit version of WinPE is included to add support for UEFI devices.

Resolution

LANDesk Management Suite 9.5 (with HP ElitePad Integration Update and/or the BASE 0228A patch) - 9.5 SP1

• The WinPE version is updated to 4.0.
• WinPE 4.0 requires Windows 8 drivers (NDIS 6.3).
• WinPE 4.0 does include a generic NDIS driver so a specific NIC driver may not be required.
• For additional information on managing drivers in LANDesk Management Suite 9.5 please see How to Add Drivers to WinPE for LANDesk 9.5.
• Client devices must have processor support for PAE/NX/SSE2 in order to boot into WinPE 4.0.

LANDesk Management Suite 9.0 SP3 - LANDesk Management Suite 9.5

• The WinPE version is updated to 3.1.
• WinPE 3.1 requires Windows 7 drivers (NDIS 6.2).
• For additional information on managing drivers in LANDesk Management Suite 9.5 please see How to Add Drivers to WinPE for LANDesk 9.5
• For additional information on managing drivers in LANDesk Management Suite 9.0 please see How to add drivers to WinPE for LANDesk 9

LANDesk Management Suite 9.0 - LANDesk Management Suite 9.0 SP2

• The WinPE version is updated to 2.0.
• WinPE 2.0 requires Windows Vista drivers (NDIS 6.1).
• For additional information on managing drivers in LANDesk Management Suite 9.0 please see How to add drivers to WinPE for LANDesk 9

LANDesk Management Suite 8.8

• The WinPE version is 1.5.
• WinPE 1.5 requires Windows XP drivers (NDIS 5.1).
• For additional information on managing drivers in LANDesk Management Suite 8.8 please see How to add drivers to the WinPE Image (formerly KB #3469)

Provisioning for LANDesk Management Suite

• This is a list of highly recommended documents for increasing overall knowledge of this component.
• The article's listed below are applicable to LANDesk Management Suite 9.5 and 9.0. They may also apply to 8.8.
• If you want to review additional content regarding this component, please use the Provisioning Discussion Tab or Provisioning Documents Tab

Changes with 9.5 SP1

• Changes to Provisioning Action Handlers in 9.5 SP1
• Hardware Independent Imaging (HII) Preview
• WinPE Version Information by LANDesk Management Suite Version

Changes with 9.5

• In order to support UEFI a new WinPE 64-bit image has been added. To manage drivers please see How to Add Drivers to WinPE for LANDesk 9.5
• Changes to Provisioning Action Handlers in 9.5

Initial Install and Configuration

• Getting Started with Provisioning for Windows 7 in LANDesk Management Suite 9.0 SP2
• Best Known Method for Deploying Windows 7
• Create and use a "provisioning agent" for end to end provisioning
• Scripted install of 64-bit Windows using LANDesk
• LDMS Version 9 HII Quick Start Guide

Additional Options and Information

• Detect and Install Patches within Provisioning
• Importing/Injecting Scripts in Provisioning
• XP to 7 Migration - Choose your own adventure!

Troubleshooting this Component

• How to enable additional provisioning logging on the 8.8 Core Server
• Troubleshooting Configure Target OS action in Provisioning template

Sample Provisioning Templates

• Sample Provisioning Templates for Scripted and image install Windows XP
• Sample Provisioning Templates for Windows 7
• Profile Migration Templates for Provisioning in LANDesk 9.0
• Sample unattended installation of a Dell pe830 using landesk provisioning
• Provisioning a Dell Server with a BMC and DRAC with sample scripts
• LDMS 9.0 Provisioning - Vboot Sample Template

NOTE:This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Provisioning if this page hasn't helped.

How to Manage Drivers in WinPE for LANDesk 9.5

Applies to LANDesk Management Suite version 9.5, 9.5 SP1 and newer.

Description

In order to perform imaging in the LANDesk Management Suite the WinPE image used during the imaging process must contain drivers for devices such as the network adapter or hard drive controller.

In 9.5 additional drivers for Intel NICs, Intel hard drive controllers, and Intel USB3 have been included in the WinPE image for convenience.

The drivers for the WinPE image should match the version of the image file being used (32-bit for boot.wim and 64-bit for boot_x64.wim), not the OS being deployed.

For adding drivers in LANDesk Management Suite 9.0 please see How to add drivers to WinPE for LANDesk 9

For adding drivers in LANDesk Management Suite 8.8 please see How to add drivers to the WinPE Image (formerly KB #3469)

Additional information about the WinPE version and required driver versions for each version of LANDesk Management Suite can be found at WinPE Version Information by LANDesk Management Suite Version

Resolution

To manage drivers to the WinPE image for 9.5 use the following steps.

1. From the console go to Tools > Distribution > OS Deployment.

2. On the Operating System Deployment screen select “Manage the drivers in the WinPE Image.

3. Select the WinPE Image that you want to manage drivers in. The default selection (boot.wim) is the WinPE image used for 32-bit vBoot and PXE.

4. To manage drivers in the 64-bit WinPE image select "Others (For user specific image)" option. Browse and select the boot_x64.wim in the vboot directory where the default boot.wim is located.

5. The image file will be processed to open the WinPE image and gather the list of drivers currently in the WinPE image file.

6. Select add or remove to manage drivers.  Note: Drivers that we included by Microsoft in the WinPE image cannot be removed. If the driver list is blank it indicates that the image file is mounted by another process and must be unmounted before drivers can be added.

7. When adding a driver a driver name must be provided. Using a name that easily identifies the driver and hardware is recommended for ease of use as additional drivers are added and removed. Browse to the location of the INF for the driver. Note: The driver must match version of the OS in the WinPE image, not the OS being deployed. The driver for the boot.wim must be a Windows 7 32-bit driver. The driver for the boot_x64.wim must be a Windows 64-bit driver.

     a. Note: If you have applied the HP ElitePad Integration update the version of WinPE has been updated to 4.0. This requires Windows 8 drivers to be used in the WinPE. For additional information please see doc???

8. After the necessary drivers have been added, select Finish and the drivers will be injected to the image.

9. After the image has completed processing it is necessary to update existing PXE representatives. Instructions on updating PXE representatives can be found at Updating the WinPE image on PXE representatives

Hi all,

We have run into an issue which we didn't come accross in the previous years. We have multiple Images on a SAN that we need to deploy to computer labs. Each lab has 25-20 computers. Nearly all have a gigabit link back to the switches. The image is NOT just the OS. It is a full blown image. The OS, all of the software needed and configured to our needs. This is how we've done it in the past as well.

Typically, OSD would take about 2 hours, which was fine. All of a sudden, it's now taking near 7 hours (after upgrading to SP3)! Any thoughts?

I know our guys are NOT using multi-cast but rather a direct download. The entire image after captured with LANDesk is 87GB. Any thought on what we can do to improve this time or make this process more efficient?

Hello, I've installed the SP1 Update to our 9.5 server but when trying to provision HII fails because the drivers are unsigned. This behavior did not existed on 9.0 or 9.5.

DISM return code 50

is there a way to modify HII to use the /forceunsigned ?

anyone else has this issue?

Thanks