The ability to use current, up to date, Driver Packs for Windows imaging needs is clear. Official HP Driver Packs are released on a cadence that often require IT departments to update specific drivers immediately after deployment. Why not create your own, as needed?
This blog post will cover how to inventory the battery health manager setting for a collection of devices leveraging a PowerShell script to generate a .csv file. We will cover a solution for Configuration Manager and one without it.
The hybrid working environment, where users are working from home or not at a fixed desk location poses additional challenges for IT resilience. One of those areas is the recovery of a non-functional device that requires a fresh Windows image to get the end-user productive again. HP Sure Recover is built into the hardware & firmware of selected HP business devices and helps to securely install the operating system from a network location.
Configuring new devices for company use is traditionally a complicated and time-consuming process. Windows Audit mode condenses the number of steps it takes to get new devices up and running through hardware-agnostic configuration profiles that can be deployed anywhere with internet access. Devices can be sent from HP straight to users, who, once registered with Autopilot, just need to log in with their work email to get quickly provisioned and start work.
HP Image Assistant (HPIA) is a vital tool that assists IT admins to manage their fleet more efficiently with a simpler setup and execution process.In this blog post we will cover how you can setup HPIA in a Microsoft Intune environment and push it to all your client devices with a few simple steps.
In order to provide a more secure access to the BIOS, HP introduced Sure Admin on commercial systems. HP Sure admin depends on a cryptographically secure infrastructure, the Secure Platform Management (SPM), previously released in the BIOS to support features such as HP Sure Run and Sure Recover.
The combination of a remote workforce with Work From Home (WFM) needs in the age of Covid-19, and mobile users now utilizing their notebooks always plugged in, increases the likelyhood of battery damage.
HP Image Assistant can install/update drivers and other components from an offline repository that has been populated with Softpaqs for HP supported business systems. A Repository folder, if to be used by HPIA, requires to be configured correctly. Configuring can be done with HP's Client Management Software Library.
With the move to the DCHU driver model many of the typical tray applications have migrated to a Universal Windows Platform (UWP) application. These applications are typically installed from the Windows Store into a specific user profile.
Modern Standby: Why HP System Default Settings
The HP System Default Settings Softpaq was developed to optimize settings and battery utilization on HP systems. HP recommends the Softpaq be installed on all supported mobile platforms, with and without Modern Standby support.
Installing Driver Appx packages during MEMCM/OSD
The implementation of the UWP driver model by Microsoft imposes restrictions on how a complete driver package can be deployed when a PC is (re)imaged. Drivers with a control UWP application are split between the hardware-enabling driver and an appx package, typically installed with DISM.
HP Image Assistant (HPIA) has become a useful tool for IT shops helping to automate the deployment and updating of PCs in an Enterprise. HPIA can be used to (not-including capabilities such as, quick access to Readme and CVA files, Advisories and Bulletins, etc.):
HP Image Assistant (since version 4.5.4) and the HP Client Management Script Library (since version 1.4.0) can team up to deliver intelligent and efficient installation of HP drivers, bios, and other HP software in a Microsoft Endpoint Management Configuration Manager (MEMCM), or other similar management environments.
This the inaugural post in a Zombieload Special series. Here's how you can leverage the HP Client Management Script Library and a little bit of your own PowerShell magic to quickly identify whether your platform needs a softpaq mentioned in a security bulletin.