HI,

I'm going to change my landesk infrastructure from 9.5 SP2 to 9.6 SP2.

I'm using provisoning with wait actionsthat working fine in 9.5 but not in 9.6.

My provisionning lauch a vbs script that make many actions like install software, reboots....

At the end of the vbs script i create a txt file that indicates it has finished is job.

In 9.5 the template wait for this txt file be present.

In 9.6 i've a popup with a time out, but the first reboot initiate by the vbs make the action wait to fail.

Is someone has a idea......

Regards

Hi,

Anybody have issues with HII working with a Lenovo X1 Carbon laptop? I have all my drivers set for the specific model but it does not install all of the drivers for the X1

I have test these drivers on the X1 itself and they work, but once the imaging is done i go into device manager and there still are a number of devices with no drivers.

Anybody have any ideas?

Thanks

I'm trying to use the Update registry option in the vonfiguration part of the template but it dosn't give me the option to speicify 64bit keys because instead of changing the key i want it's changing the key of the same path under the wow3264node key. unfortuanatly this has no effect..

i've tried HKLM64 and that didn't work either. 

Hello All,

Landesk Version: 9.6 SP1

I have been trying to boot a UEFI tablet to PXE following the guide at: How to Provision a UEFI Tablet using ImageW. The tablet is a Dell Venue 11 7130 VPro and curious to see if anyone has had success imaging this model.

I've followed the guide to a T but can't seem to successfully boot to PXE for capturing the OS. When I boot to the NIC, I can see that for a brief second, It finds the PXE Rep and makes some sort of attempt to boot to WinPE but then resumes to booting to the normal OS.

I know that UEFI sometimes has issues with Landesk's PXE menu prompts so I tried disabling the prompts with the guide at: How to hide PXE Boot Options on the F8 Menu. Still no luck.

My provisioning log seems to show that the process is starting correctly but never seems to complete. Here are the relevant log messages:

Provisioning Log

VERBOSE ProvisioningService  6/4/2015 10:01:25 AM  : <<GetProvisioningBootOption, BootOption=16

VERBOSE ProvisioningService  6/4/2015 10:01:29 AM  : >>GetProvisioningBootOption, clientMacAddress=F01FAFFD0B50

VERBOSE TemplateFinder  6/4/2015 10:01:29 AM  : >>GetTemplateForServer,computerIDN 634

DEBUGGING TemplateFinder  6/4/2015 10:01:29 AM  : >>GetProvisioningTaskForComputer.computerIdn 634

VERBOSE TemplateFinder  6/4/2015 10:01:29 AM  : info.taskId 180.info.templateId 27

DEBUGGING ProvisioningService  6/4/2015 10:01:29 AM  : Succeed to GetBootOption.PreBoot=WindowsPE,SectionOrder=1,clientMacAddress=F01FAFFD0B50

VERBOSE ProvisioningService  6/4/2015 10:01:29 AM  : <<GetProvisioningBootOption, BootOption=16

The capture template is cloned and locked with a status of waiting. Obviously it's waiting in vain since the OS continues to boot up as normal in the meantime.

Any suggestions would be much appreciated.

Description:

  when we create disconnected provisioning template on LDMS 9.6 sp2, we can't choose the file system to format USB drive, the default files system is FAT32,

FAT32 only support the max size of the file: 4G,  if the image file is larger than 4G, we can't create disconnected provisioning template successfully, so we need to capture image file in less than 4G chunks.

(FAT file system only support 2G , we need to capture the image file in 2G chunks if the file system is FAT)

Steps:

1. Add action to capture image in provisioning template, and click validate button, then add /max:2GiB at the tail of the Command-line:

2. Schedule this template to the client machine

3. Start the client machine to run the scheduled provisioning task

4. The image file will be captured as 2G chunks:

Here is the details for imagew.exe parameters:

https://community.landesk.com/support/docs/DOC-34515

Here is How to Manually Create Disconnected Template

How to Manually Create Disconnected Template

I want to show you how I fixed all of our HII Problems in 9.5 SP1 and dramatically speeded up the provisioning process with a few simple steps.
We working with this method for weeks now without any problems...so I wanted to share it to the community.

Benefits:

No DELL USB 3.0 Driver Problems, No more Blue Screens after StandBy Mode, No mixing of drivers because of generic Hardware IDs, massivly speeded up Provisioning Process

Steps:

1. Create a Driver Share like this
   
   You get this Drivers from here: Dell Driver CAB files for Enterprise Client OS Deployment
2. Become familiar with the oldschool Copydrivers.exe-Tool and populate the .ini like this.
   
   
3. Edit your Provisioning Template
   Map a Network Drive to preferred Server
   
   
   Run the Copydrivers.exe with /c
   
   
   Run the Microsoft DISM-Command
   x:\windows\system32\dism.exe
   /image:c:\ /add-driver /driver:"c:\Drivers" /recurse /forceunsigned
   
4. DELETE HII from the Template (its not needed in the POST-OS Section anymore)
   

Now your Windows Installation has all drivers that are needed right for this computer model.

Kind regards,
Marco Feuerstein

Germany

Hello all,

Having an issue with Distribute Software.

Packages succeed when run as scheduled tasks, so the packages themselves look good, but they  fail when using Provisioning (whether using a template that reimages a computer, or a template that ONLY runs the software distribution). The packages reference software held on a Windows share on the core server (\\CORE\Packages\)
I suspect an issue with either IIS configuration or preferred server configuration, but I'm not really sure how to make that determination (or fix it, for that matter). Was wondering if anyone can provide any direction on this matter.

The following are logs from a workstation where I have attempted to run this task.

ldprovision.log

2015-06-05 16:21:34(3572-4008) ldProvision.exe:*********  Begin an action - Distribute_software

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Do EnvironmentCheck

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0

2015-06-05 16:21:34(3572-4008) ldProvision.exe:In Handle Action.

2015-06-05 16:21:34(3572-4008) ldProvision.exe:About to download handler.

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Need to download handler:

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Handler remote: /LdLogon/Provisioning/windows/SDClientHandler.exe

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Handler local: c:\ldprovisioning\SDClientHandler.exe

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Looking for existing file (c:\ldprovisioning\SDClientHandler.exe)

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Entering downloadbyproxy.

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "c:\ldprovisioning\SDClientHandler.exe" http://CORE/LdLogon/Provisioning/windows/SDClientHandler.exe)

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Process exit code:0

2015-06-05 16:21:34(3572-4008) ldProvision.exe:The file (c:\ldprovisioning\SDClientHandler.exe) was successfully downloaded

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Done with download handler.

2015-06-05 16:21:34(3572-4008) ldProvision.exe:Launching action handler [SDClientHandler.exe] with parameters ["]

2015-06-05 16:21:40(3572-4008) ldProvision.exe:handler launched.

2015-06-05 16:21:40(3572-4008) ldProvision.exe:Report might reboot status to core.

2015-06-05 16:21:40(3572-4008) ldProvision.exe:Call web service SetActionStatus()

2015-06-05 16:21:40(3572-4008) ldProvision.exe:Start TryallWebService Attempt:0.

2015-06-05 16:21:41(3572-4008) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2015-06-05 16:21:41(3572-4008) ldProvision.exe:Reporting action status: 5 to core

2015-06-05 16:21:41(3572-4008) ldProvision.exe:Call web service GetStatusString()

2015-06-05 16:21:41(3572-4008) ldProvision.exe:Start TryallWebService Attempt:0.

2015-06-05 16:21:41(3572-4008) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2015-06-05 16:21:41(3572-4008) ldProvision.exe:StatusString = The action failed.

2015-06-05 16:21:41(3572-4008) ldProvision.exe:Call web service SetActionStatus()

2015-06-05 16:21:41(3572-4008) ldProvision.exe:Start TryallWebService Attempt:0.

2015-06-05 16:21:41(3572-4008) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

2015-06-05 16:21:41(3572-4008) ldProvision.exe:End of action - Distribute_software

2015-06-05 16:21:41(3572-4008) ldProvision.exe:Last action failed

SDClientHandler.log

2015-06-05 16:21:34(1880-1728) SDClientHandler.exe:Starting Software Deployment.

2015-06-05 16:21:34(1880-1728) SDClientHandler.exe:Checking for SDClient Mutex.

2015-06-05 16:21:36(1880-1728) SDClientHandler.exe:Got mutex attempting distribution.

2015-06-05 16:21:36(1880-1728) SDClientHandler.exe:id=23112015-06-05 16:21:36(1880-1728) SDClientHandler.exe:Executing: C:\Program Files (x86)\LANDesk\LDClient\SDClient.exe /pkgid=2311

2015-06-05 16:21:36(1880-1728) SDClientHandler.exe:Going to execute "C:\Program Files (x86)\LANDesk\LDClient\SDClient.exe" /pkgid=2311 /disableclientqueue /taskid=2980

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:SDClient call retcode: -1918107543 (code - 105).

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:Getting returncode mapping from http://CORE/LANDesk/ManagementSuite/softwaredistribution/apmservice/PackageInfo.asmx

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:Requesting for PackageID: 2311, ReturnCode: -1918107543

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe: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><MapReturnCode xmlns="http://tempuri.org/"><iPackageId>2311</iPackageId><iRetCode>-1918107543</iRetCode></MapReturnCode></soap:Body></soap:Envelope>

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:Found httpclient.exe at C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:httpclient args:  -H"c:\ldprovisioning\headerHII.txt" -o"c:\ldprovisioning\bodyHII.xml" -f"c:\ldprovisioning\resultHII.xml" http://CORE/LANDesk/ManagementSuite/softwaredistribution/apmservice/PackageInfo.asmx

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:TryallWebService exitcode: 0

2015-06-05 16:21:40(1880-1728) SDClientHandler.exe:Failed to install package based on return code mapping, retcode: -1918107543 (code - 105).

Based on the logs and what I've seen, I'm guessing (but not totally sure) that typical scheduled tasks are using UNC, which appears to be working (screenshot below) but HTTP does not.

Hi,

We are currently have an issue with provisioning, running LDMS 9.6.

We need to deploy Lenovo (x250 series) to users with WIN7, however, when imaging using the different partitioning options, we end up with a UEFI System Partition.

This is a major issue, as we are unable to encrypt the machines with Sophos Safeguard our Encryption tool.

I found from another Community thread that 'Create Default Partitions' - Pre OS Installation task, creates  an EFI System Partition, which causing the problem. - I cannot migrate this partition either.

I have tried Auto Assign Partitions - Pre OS Installation task, however, I encounter a similar issue.

Any ideas on what can be done/should be done ?

Kind Regards

Shaquille

Hello,

I am curious if anyone might have any insight into this problem.

I am creating a USB boot drive using the LDMS console. I can use this boot drive to get into PE on any new devices (we are a Lenovo shop) with the haswell chipset and UEFI without any issue. For any older devices that do not use UEFI, these boot drives will not load into winPE. Thus, we cannot image a machine using provisioning with a USB boot drive.

Thanks in advance!

Marc

If you are provisioning computers in another office or on another floor, it's very helpful to view the WinPE environment while the provisioning template is running.  Follow these steps to use LANDESK Remote Control to view the remote computer:

1. From your core or a computer with a LDMS console installed, open a RUN command and type ISSCNTR.exe.  This launches the LDMS remote control platform.
   
2. Enter the IP address of the device in question.  The device must have booted into WinPE before it can be remote controlled.
   
   
   
   
3. If required enter credentials to connect.  Once connected, click the magnifying glass icon on your toolbar to start viewing and interacting with the remote screen.
   
   
   Please note, LANDesk remote control is a 32-bit application.  As such, it is not compatible with x64 WinPE.  If you are using the 64-bit version of WinPE, LANDesk Remote Control will not be available.

I am getting a "not enough disk space" error when attempting to deploy an image to another laptop.  The original image was captured off a 500GB drive but the image itself is only 20GB.  Golden image is just Windows updates and Office.  When I start the deployment it says it doesn't have the needed 21GB free.  Deployment is set to remove and then create all the default partitions.  Deployment is successful if deployed to the same laptop type that it was capture from.  I've scanned the logs but i'm not sure what to look for.

I have tried all of the drivers from the Lenovo site. I get an IP on the the initial pxe boot but right before it gets to the pxe menu, I don't get an IP address. It is 127.0.0.0.

Hello all,

i was wondering if anybody has seen or heard of any issues with regard to deploying OS via landesk to an encrypted hard drive, we are about to place an order for a batch to come in and we were wondering if this could be a potential problem that might prevent us from imaging them? i have done a search around this topic but nothing has come up as of yet, we are using LDMS 8.7 and the os we are looking to deploy is XP.

We are relatively new to LDMS and to date we have been testing the deployment process and building the deployment packages, however we are almost ready to venture into the world of true OS Deployment (deploy images to computers and then applications based on Provisioning templates).

I am wanting to get my head around the whole process that is required to setup our AD/DHCP server to use LDMS when booting into PXE environment.  Our environment is an Windows Active Directory 2003 and we are currently using Acronis Snap Deploy for image deployment.

Is anyone able to provide me with links or information on the steps required to setup PXE to work with LDMS.  If there are any guides or BKM's that would be great.

Also, is there any way of using Acronis after we have migrated over to LDMS for PXE?  Even though our intention is to stop using Acronis, we may still require it for some deployments while we are still setting up LDMS so if we could use LDMS for PXE that would be great, if not then we will just make the cutover when we are completely setup and ready to go.

My apologies if this has already been answered else where in the forums, I have done some searching and havent been able to find much that would assist us in setting up the environment.

Thanks,

Matt

I am having an issue trying to get a new template to run.  It seems to fail at "Inject Script", and it looks like that is due to there being no C:\ to move the file to.  I'm not sure why it's not working, but I did copy the following logs : ldProvisioning.log - InjectScript.log, and diskpart.txt.  The thing that really baffles me is that it works sometimes.  I had the template working, then I pointed it to a test TBI and it failed.  So I then reverted the template back the original TBI that worked, and now that is failing as well, all with the same error! 

We currently have multiple templates that work fine, and I originally was making a private copy of of one of them, and then removing most of the System Configuration steps, leaving just a basic provisioning of the image, the LD agent, patches, and a reboot.  That is when it started failing.  So I decided to try and build a brand new template to avoid any clone issues, and at first it worked...but then once I pointed to a different TBI, it failed, and keeps failing if I revert back.  I know pointing to a different template is not the cause, as that is how we update our base image.  Once testing is completed, we simply replace the TBI in our production folder, and we never see that error.

Thanks

-RickS

Landesk 9.5 SP3

I have searched everywhere and cannot find a document explaining Templates thoroughly.

My questions are?

1. In all Public Templates there are no little black arrows showing. In the Public folder we made groups containing Templates and they all show a little black arrow?

2. Many of the Templates in the All public Template folder have duplicates (with some additional dates added on) And Locked has a YES there, what does this mean?

3. What is the proper procedure for copying a basic template made in the All Public templates folder and putting it into my groups in my Public folder, copy and paste or clone and copy to?

I am looking for a driver that works in WinPE. We are using Management Suite Version 9.50.2.6 without SP. For that version LD wrote:

LANDESK Management Suite 9.0 SP3 - LANDESK Management Suite 9.5 without Service Pack

• The WinPE version is updated to 3.1.
• WinPE 3.1 requires Windows 7 drivers (NDIS 6.2).

So we searched for NDIS 6.2 drivers (Win7x86). Network adapter in the Lenovo T450s is "Intel Ethernet Connection I218-LM"

But all didn't work! Any help in which *.inf files are needed would be great!?

I successfully captured an image and was attempting to re-deploy to the laptop to test the image.  Unfortunately it gets nearly to the end of the deploying the image phase and I get an error "Image Stream Corrupt"

I check the logs and it exits the deploy image task with an exit code of 205 and internal status of -2147477501.  I'm deploying Win 7 64 to a HP Elitebook Folio 9470m.

Thoughts?

It is taking about 20 minutes, sometimes more, to get through the HII step in Provisioning.  It hasn't always been that way, but as we've added more and more hardware models (currently 42) to our driver database it has slowed down the process significantly. 

I am wondering what the best practices are for uploading drivers into the drivers folder.  Currently when we notice that a driver is missing after imaging it, we download it from HP, extract the SPxxxxx.exe and upload the entire contents of that extraction into our Drivers folder, organized by model.  Those extracted folders can be very large, which is probably at least part of the reason why HII is so slow. 

The hope is that we could just grab the .inf, .ini, .cat, or .sys files and exclude the rest.  Is that possible, and how do I know which files are necessary?  What is the best way to go about cleaning up an existing driver library?

Thanks!