The storage control blocks were destroyed installing HP Graphics drivers

[Tinribs]

HI All,

Just got a load of new computers to replace an ageing inventory.

Got an image working in SCCM and built 140 of them before we noticed that the graphics driver included in the HP Softpaq that we used to create the driver package was the wrong one. This has been resolved in the image now so any newly built machines will work. However we now have 100+ machines with the base MS graphics installed.

I have created an application using the Intel driver setup with -s (for a silent install) and deployed it to all the machines. Not going that well. As of nine this morning 75 have failed with the same error 0x7 "The storage control blocks were destroyed". The problem is that one of the machines has worked. So there are 83 machines that have attempted the installation - 7 already had the driver installed (manually once we discovered the issue) 75 failed and 1 success. All machines are identical (HP ProOne G400 4) and have exactly the same image installed and the same level of BIOS.

If you run the installation manually it works fine. If you run it manually from the downloaded application in the CCMCache folder it works fine. There is nothing in any event log and the CCM logs just report the same error as on the SCCM console.

If one hadn't worked I would just assume that this cannot be done over SCCM and settled for having to do the job manually (at ten minutes per computer a lot of time) but as one has worked I need to know why 75 have failed!!

 

OS is 64 bit Win 10

If anyone can help please let me know - I can post logs if required...

TIA

[pete]

I assume you've checked antivirus isn't interfering?

 

If you trigger the install remotely from the CCMCache folder using PSTools / Powershell, does it work?

[Tinribs]

I assume you've checked antivirus isn't interfering?

 

If you trigger the install remotely from the CCMCache folder using PSTools / Powershell, does it work?

 

Thanks for the reply Pete,

All the machines have the same AV software so that wouldn't explain why one worked and the others didn't and I suspect the AV would cause issues if we ran it manually which we know works.

Haven't tried the PS remote thing but that's because I wouldn't know how so if you could advised I will give it a go.

[pete]

Using PSTools (remote powershell would work too) from SysInternals (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec), try something like:

 

psexec \\computername -s -i "\\path\to\installer.exe /S"

 

replacing the path and install switches with the location of the installer/package in the CCMCache (or a file share). If that succeeds, look at the switches (documented in the above URL) for detaching the process and feeding a list of computers to psexec.

 

You're testing "is this package generally unreliable for unattended / remote deployment or is it just unreliable if pushed via SCCM?"

[Tinribs]

Using PSTools (remote powershell would work too) from SysInternals (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec), try something like:

 

psexec \\computername -s -i "\\path\to\installer.exe /S"

 

replacing the path and install switches with the location of the installer/package in the CCMCache (or a file share). If that succeeds, look at the switches (documented in the above URL) for detaching the process and feeding a list of computers to psexec.

 

You're testing "is this package generally unreliable for unattended / remote deployment or is it just unreliable if pushed via SCCM?"

 

OK - so that gives the same error. Nothing in any event logs on the client. I then tried running the app manually and silently (which I hadn't done before) locally. In this case absolutely nothing happens. Nothing appears in task manager and no errors in any logs. There's even supposed to be an HP installer log that appears in C:\windows\INF and that doesn't appear. It's looking like the drivers don't like the -s switch to run silently.

Another anomaly I've noticed (that I missed before) is that if you run the setup locally the driver prompts that the installation will replace an older version that is already installed and it lists the installed drivers as the one that I'm actually trying to install that I know AREN'T installed. Searching the registry finds nothing and none of the relevant driver files or the control panel icon are present...

Still no idea why one of the machines actually worked...

[Fazza]

There should be a switch to overwrite existing drivers so make sure you are using that.