USB 3.0 Schedule Task failing - says not enough storage available

April 17, 2014, 10:05 am

≫ Next: Re: USB 3.0 Schedule Task failing - says not enough storage available

≪ Previous: Re: PXE-E53: no boot filename received - when trying to PXE boot to upload a syspreped image -Documented fix doesn't work

Hello,

I have been using LANDesk 9.5 SP1. My workaround for USB 3.0 is to create a driver package and Assign via HII. Recently, when testing a new Distro Task (Type = Executable), the Scheduled Task fails. The driver install log on the client is OK (attached). Watching Device Manager during the task, the USB3.0 goes from Yellow Exclamation mark to being installed. However the log on the core says:

Not enough storage is available to complete this operation

Return Code 14

I've reproduced this issue on 2 models now. Each machine has over 200GB free.

Snippit from SDClient log on the client below <corename, IP>:

Thu, 17 Apr 2014 12:23:26 File (<core>\image\drivers\win7\Laptop\e6x30\USB 3.0\Intel_Chipset_7-Series_USB3_THK45_A05_SETUP_ZPE\Setup.exe) is cached locally

Thu, 17 Apr 2014 12:23:26 LSWD or Executable Client Thread

Thu, 17 Apr 2014 12:23:26 PackagePath: [<core>\image\drivers\win7\Laptop\e6x30\USB 3.0\Intel_Chipset_7-Series_USB3_THK45_A05_SETUP_ZPE\Setup.exe]

Thu, 17 Apr 2014 12:23:26 Processing generic executable

Thu, 17 Apr 2014 12:23:43 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\image\drivers\win7\Laptop\e6x30\USB 3.0\Intel_Chipset_7-Series_USB3_THK45_A05_SETUP_ZPE\Setup.exe' ('-overwrite -report c:\windows\buildInfo\E6530USB3.0Log.txt -s') result 14

Thu, 17 Apr 2014 12:23:43 Installation result 8DB5000E

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Getting post package install inventory delay setting.

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Initial delay value is '5' minutes

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Initial random delay value will be up to '15' minutes

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Actual random delay value is now '8' minutes

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Setting up local scheduler to launch inventory scanner with a delay of '13' minutes...

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Successfully created inventory scanner task.

Thu, 17 Apr 2014 12:23:43 The nostatus flag has NOT been set.

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Getting post package install inventory delay setting.

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Initial delay value is '5' minutes

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Initial random delay value will be up to '15' minutes

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Actual random delay value is now '8' minutes

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Setting up local scheduler to launch inventory scanner with a delay of '13' minutes...

Thu, 17 Apr 2014 12:23:43 PostInstallInventoryScan: Successfully created inventory scanner task.

Thu, 17 Apr 2014 12:23:43 Sending task status, cmd line -coreandip=<core>:<IP>-taskid=3012 -retcode=-1917517810 -complete -pkgid=1138

Thu, 17 Apr 2014 12:23:44 processing of package is complete, result -1917517810 (0x8db5000e - code 14)

↧

Re: USB 3.0 Schedule Task failing - says not enough storage available

April 18, 2014, 5:57 am

≫ Next: Re: Porting existing image over to landesk Provisioning

≪ Previous: USB 3.0 Schedule Task failing - says not enough storage available

Hi, I had the same error and it is not related to disk storage.

You are trying to install Intel usb3 driver and error 14 is "Setup has completed successfully but a system restart is required"

Edit your "error code template" to set code 14 as "successful"

↧

Re: Porting existing image over to landesk Provisioning

April 24, 2014, 9:22 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: USB 3.0 Schedule Task failing - says not enough storage available

I waited even longer and it did eventually move past "setup is preparing your computer for first use" and then proceeded to sysprep /oobe /generalize / reboot as is what I have set in my unattend.xml in the "audituser" pass which is based off the win7x64unattend.xml provided via the landesk pdf here on the community.

My guess is that I shouldnt be having the computer syspreppping to oobe again during the provisioning process.

I'm contemplating removing the audituser pass from my unattend and see if that works. Problem with troubleshooting imaging is that it takes awhile to re-image a machine again and go through all of the steps.

↧

Re: Provisioning template-System Config-Distribute software

April 24, 2014, 11:56 am

≫ Next: Re: Porting existing image over to landesk Provisioning

≪ Previous: Re: Porting existing image over to landesk Provisioning

Look in your Windows event logs... Is there something else installing things at the same time? Both Wsus and/or LD Patch manager can get in your way here.

Frank

↧

Re: Porting existing image over to landesk Provisioning

April 25, 2014, 1:26 am

≫ Next: Re: Porting existing image over to landesk Provisioning

≪ Previous: Re: Provisioning template-System Config-Distribute software

Hi Ryan

What version of LANDESK are you using? One thing to make sure of is that you create C:\Windows\LDDriverStore either in your image or create it using an action within the provisioning template (I prefer the latter). This is where the HII action will copy all the drivers to. Just make sure the create directory action goes before your HII action

Also, what method are using for HII? UNC or HTTP? In your driver store, have you extracted all the files? I tend to sysprep using oobe /generalize /shutdown to capture an image as it works better when injecting the computername into the unattend.xml. Win7 does go through the 'setup is preparing your computer for first use' process a couple of times during the setup. Also you may want to add <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> to the generalize section of your unattend at the end to prevent Windows from removing all your newly detected drivers during setup.

Post your unattend.xml and your provisioning template and we can take a further look

Martyn Ayers

MarXtar Ltd/MarXtar Corporation

http://landesk.marxtar.co.uk

LANDesk Expert Solution Provider

Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based

Update - New v2.3 Now with Automated Subnet Rep Selection and Optional Maintenance of LANDESK Reps

The One-Stop Shop for LANDesk Enhancements

- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing

- State Notifier - Real-Time Device, User State and Process Monitoring. Inventory Updating, Alerting & Historical Analysis

↧

Re: Porting existing image over to landesk Provisioning

April 25, 2014, 4:57 am

≫ Next: Re: Lenovo Tablet2 provisioning

≪ Previous: Re: Porting existing image over to landesk Provisioning

Thanks for taking the time to reply Martyn. We are running 9.5 sp 1. I have not been creating the c:\windows\lddriverstore manually or through provisioning as I was assuming that the HII action was doing this. I am currently using HTTP for my drivers and have allowed the config and other file types in IIS.

I have attached my unattend.xml file to this reply. It is my understanding that the "auditsystem" and "audituser" passes of this unattend are not used at all if my image is oobe /generalized and not audit mode.

↧

Re: Lenovo Tablet2 provisioning

April 25, 2014, 8:32 am

≫ Next: Re: Porting existing image over to landesk Provisioning

≪ Previous: Re: Porting existing image over to landesk Provisioning

We just got a bunch Lenovo ThinkPad Tablet 2. CTonkin, in order to create the USB Boot Media you need this (from the PDF that Dave posted)

1.Open a Command Prompt with Administrator priviliges in either Windows 7 Pro or Windows 8 Pro

2.Insert the target USB boot media device into an available USB port

3.Type DiskPart in the command prompt

4.Type List Disk, Make note of the disk number of the target USB drive

5.Type Select Disk X, where X is the target USB drive noted in step 4

6.Type Clean

7.Type Create Partition Primary

8.Type format FS=fat32 quick

9.Type Active

10.Type Assign

11.Type list volume

12.Type Exit

I ordered the ThinkPad USB 3.0 Ethernet Adapter. I will let you know how it goes, if you have more information please share it.

Thank you

↧

Re: Porting existing image over to landesk Provisioning

April 25, 2014, 9:00 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Lenovo Tablet2 provisioning

Ryan,

There are many different ways to accomplish this.

Here is how I do it (well, the parts that pertain to what you need to get through mini setup)

Install base image, customize, patch and leave in Audit mode. (I don't run sysprep to enter audit mode, I use ctrl+shift+F3 after new install)

(I don't pre-create and drivers directories or anything. Pretty much install, patch and customize settings)

run sysprep /oobe /generalize /shutdown (I don't point to an xml here)

capture the image after it shuts down being careful to not let it boot up before capture

Deploy the image with your template and include an "inject script" action for your unattend (to create c:\windows\panther\unattend.xml)

Add an HII operation to enumerate hardware and inject drivers. The c:\windows\lddriverstore folder will be created automatically.

That should be enough to get the machine through sysprep (drivers and unattend.xml) Once you have that part working, you can start adding more template actions to meet your end goal.

If you still have hangs/"bluescreen of death", boot back into WinPE and see what drivers were copied to c:\windows\lddriverstore and make sure the appropriate driver(s) were injected.

I'm not sure if you need all that stuff you have in the Audit pass

I have attached my xml if you want to see if it works for you

-Tracy

↧

Re: Provisioning template-System Config-Distribute software

April 25, 2014, 9:53 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Porting existing image over to landesk Provisioning

It could be as simple as the agent configuration. Is "Software Distribution" included with the agent that you are using for provisioning? I just had a similar issue, because I got the bright idea to turn it off in my provsioning agent.

Thanks,

Scott

↧

Re: Provisioning template-System Config-Distribute software

April 25, 2014, 9:57 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Provisioning template-System Config-Distribute software

Yes, software distribution is turned on from what I can tell. Would anyone be willing to share what their provisioning agent is setup like? I'm thinking I missed something dumb and probably would have an a HA moment when I see a correct working one. Thanks

↧

Re: Provisioning template-System Config-Distribute software

April 25, 2014, 11:42 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Provisioning template-System Config-Distribute software

I am still trying to nail down my settings, but I used this link, http://community.landesk.com/support/docs/DOC-9526, as a reference.

Pay close attention to the first image, as this is the area that I was referencing earlier.

I only showed what I focused on in setting it up. The post still looks like it is valid, although at the beginning it shows as deprecated with 9.0 SP3.

Hope this helps,

Scott

↧

Re: Provisioning template-System Config-Distribute software

April 25, 2014, 11:56 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Provisioning template-System Config-Distribute software

Scott, this is very similar to what I have. I will dig deeper and continue to test. Thanks for the input

↧

Re: Provisioning template-System Config-Distribute software

April 28, 2014, 3:30 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Provisioning template-System Config-Distribute software

Can you check the application event log for any errors / crashes of the sdclienthalnder.exe process on the client PC like below?

Description:

Faulting application name: SDClientHandler.exe, version: 9.50.2.16, time stamp: 0x515982df

If yes then I have 2 environments with a similar problem and an open case with LANDesk for this but no resolution at present.

↧

Re: Provisioning template-System Config-Distribute software

April 28, 2014, 4:26 am

≫ Next: Re: Provisioning template-System Config-Distribute software

≪ Previous: Re: Provisioning template-System Config-Distribute software

Also, I know we did have an issue with the Software Distribution action that was resolved in one of the later component patches for LDMS 9.5 SP2.

The issue there was for example, if you had 10 packages to install, on various computers a random amount of those 10 packages would get installed.

If you looked at a computer that only got 5 out of 10 packages installed, it would show successful for all 10 packages, however if you dug into the details you would see that it installed 5 of the 10 packages twice, not all 10 packages.

Not sure how else to explain the issue.

At any rate, the BASE component patch that is available under LANDESK Updates in Patch Manager resolves that issue.

↧

Re: Provisioning template-System Config-Distribute software

April 28, 2014, 4:29 am

≫ Next: Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

≪ Previous: Re: Provisioning template-System Config-Distribute software

Thanks Dave, I'll give this a shot!

↧

Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

April 28, 2014, 5:51 am

≫ Next: Upgrading Landesk 9.0.3 to 9.5sp2

≪ Previous: Re: Provisioning template-System Config-Distribute software

You may want to try SP2 and the latest component patches.

The latest component patches are now available in content in the Patch and Compliance tool.

There have been some enhancements to HII, including what it can do within windows for difficult to install drivers such as USB 3.0.

Basically after upgrading you will want to do an HII pass within PE, and also one more HII pass within windows.

↧

Upgrading Landesk 9.0.3 to 9.5sp2

April 28, 2014, 10:45 am

≫ Next: Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

≪ Previous: Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

Is it possible to upgrade the 9.0.3 client to 9.5.2, without installing the 9.5 client, then the 9.5 sp1 client and then the 9.5 sp2 client?

↧

Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

April 28, 2014, 11:45 am

≫ Next: Re: Upgrading Landesk 9.0.3 to 9.5sp2

≪ Previous: Upgrading Landesk 9.0.3 to 9.5sp2

Dave, alas, the SP2 upgrade is probably not on our roadmap for a while. We just put in a ton of time upgrading from 9.0 SP3 to 9.5 SP1. I will open a support case soon...

↧

Re: Upgrading Landesk 9.0.3 to 9.5sp2

April 28, 2014, 12:09 pm

≫ Next: Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

≪ Previous: Re: 9.5 SP1 HII Assigned Driver Package fails return code 1

No, you need to re-deploy the 9.5 agent, there is not really upgrade path for the agent. But, if your Core is on 9.5 Sp2 and you deploy your new agents, they are automatically on SP2 also.

Hope this helps.

Frank

↧