Missing drivers - Windows 10 on older HP Elitebooks

HP does not provide Windows 10 driver packs for models earlier than their G1 lineup, and Windows 10 drivers for earlier models are scarce. After a deployment you will be left with some devices with missing drivers. The following drivers are found to be working on Windows 10 x64 1511 in our enviroment. We deploy our machines with newest BIOS, and set to run in UEFI mode with Secureboot (not available on all models). You will need the newest BIOS for Secureboot to work, as the 2011 and 2012 BIOS does not contain updated keys. The SoftPaqs can be modified to install automatically with HP SSM.


HP Elitebook 2570p

sp64135.exe - JMicron Media Card Reader Driver
(PCI\VEN_197B&DEV_2391&CC_0805 & PCI\VEN_197B&DEV_2392&CC_0880)
sp71714.exe - HP 3D DriveGuard 5
(ACPI\VEN_HPQ&DEV_6000)

HP Elitebook 2560p

sp66584.exe - HP hs2340 HSPA+ Mobile Broadband Module
(USB\VID_03F0&PID_3A1D)

HP Elitebook 8460p

sp65514.exe - Intel® Management Engine Components Driver
(PCI\VEN_8086&DEV_1C3D&CC_0700)

HP Elitebook 8560p

sp64144.exe - HP 3D DriveGuard Software
(ACPI\VEN_HPQ&DEV_0004)
sp65514.exe - Intel® Management Engine Components Driver
(PCI\VEN_8086&DEV_1C3D&CC_0700)
sp64135.exe - JMicron Media Card Reader Driver
(PCI\VEN_197B&DEV_2391&CC_0805 & PCI\VEN_197B&DEV_2392&CC_0880)
sp66915.exe - Validity Fingerprint Sensor Driver
(USB\VID_138A&PID_003C)

HP Elitebook 8570p

sp71714.exe - HP 3D DriveGuard 5
(ACPI\VEN_HPQ&DEV_6000)

HP Elitebook 840 G1

sp69923.exe - Intel (R) Smart Connect Technology Device
(ACPI\VEN_INT&DEV_33A0)

Unable to compile Sql CE script file during SCCM client install or upgrade

I've had issues with the SCCM client on our internet (IBCM) server. At first it was the issue with configuration manager software not on C-drive, and client patches failing to apply. Then with SCCM 1511 and 1602 client installs on the server resultet in

MSI: Setup was unable to compile Sql CE script file F:\SMS_CCM\StateMessageStore.sqlce.
The error code is 80004005.    ccmsetup.

This is due to the old Sql CE databases still being present. 

To fix this, uninstall all SCCM client components. Find the Windows Installer Code with this Powershell command.

(Get-WmiObject -Class CCM_InstalledProduct -Namespace "root\ccm").ProductCode

Then move the following files to a backup folder. These are the old client Sql CE database files. They are located in the client install folder %windir%\CCM\ or in the SMS_CCM folder).

  • CcmStore.sdf
  • CertEnrollmentStore.sdf
  • ComplRelayStore.sdf
  • InventoryStore.sdf
  • UserAffinityStore.sdf

Abort any running ccmsetup processes by stopping any ccmsetup services running, and then run the following command from you SCCM client install folder (or %windir%\ccmsetup):

ccmsetup.exe /uninstall

Then install the client as usual with ccmsetup.exe


 

 

 

No secure connection to Plex on same subnet

I have never been able to connect to my Plex Media Server securely on my local area network so I decided to fix it today. The official troubleshooting article mentions pfSense 2.2 which I run. It tells users to configure DNS rebinding. This was not enough in my case, so I searched some more for a solution. The forums had a hint about how to solve this in a post by snm77. His suggestion is to add a host override point plex.direct to your servers local IP address. This did not work, but pointing the FQDN did! The FQDN can be found by using the inspector in your browser and reload https://app.plex.tv/web/app , in Chrome you would look at the Network tab and find connections to IP.*.plex.direct, the one with your servers IP is your FQDN.

In pfSense 2.2+ do the following:

1) Configure DNS Rebinding by going to System > Advanced > Admin Access and enter plex.direct under Alternate Hostnames.

2) Configure Host Override by going to Services > DNS Forwarder and create a new entry under Host Overrides. Enter the IP part for your FQDN in the Host field, the rest in the Domain field and enter your servers local IP in the IP address field. Like the image below:

Skjermbilde 2016-01-13 kl. 21.26.55.png

After these configurations, reload with the new DNS settings and you will have secure connections on both the internal network and on the internet!

WinPE SCCM PXE boot problem and solution

This is a writeup on how we solved this problem at my workplace. Written because there where few solutions available online for this problem.

Our SCCM 2012 install have been working great for OSD ever since we got it installed. We have been deploying Windows 7 to HP Elitebooks on the client VLAN, and WIndows 2008R2 to ProLiant BL460c G1 blades the server VLAN. But when we tried G7's and G8's the PE boot would halt. It would be slow, then crash with an error message. This buggered us for months. PXE booting from our Linux PXE server with utilities, firmware CD's etc. works. So it is something Microsoft do differently. Googling would mostly show results for the usual PXE issues like IP helpers, or be for SCCM 2007 wich does PXE differently.

​Boot failure right after boot.sdi message. Error 0xc0000001. "A required device isn't connected or can't be accessed."

After a lot of trial and error for WinPE (both 3.0 and 4.0) PXE booting from the Configuration Manager server it looked like this:

​ProLiant BL460c G1 - Embedded Internet - Server VLAN - WORKS
ProLiant BL465c G7 (same blade enclosure) - FlexFabric Embedded Ethernet - Server VLAN - FAILS
ProLiant BL465c Gen8 - HP FlexFabric 10Gb 2-port 554FLB Adapter - Server VLAN - FAILS 
VMware Workstation 9 (hw9) VM - E1000 - Client VLAN - WORKS
VMware ESXi VM (on Gen8) - vmxnet3 & E1000 - Server VLAN - FAILS

After this we ruled out drivers, and WinPE issues. It had to be something with the network. I had been monitoring the WDS processes (TFTP and the WDS server) with perfmon.exe and it looked ok. A colleague set up our test vm with a mirror port to a machine running Kali with Wireshark running. Then it became obvious what was happening. WDS uses 1456 as the packet size for its TFTP transfers. After the initial transfer of the bootloader, it hands the process to the distribution point service that then fills fills the ramdisk. Microsoft explains this in this technet article. SCCM DP requests 16384 as the packet size. Google quickly pointed us to a registry key that got things flying:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP​

Change RamDiskTFTPBlockSize from 16384 to 1456.

Note: A larger number should increase performance. 16384 is the maximum.