HP Client Management Script Library 1.5 released
We've released version 1.5 of HP Client Management Script Library, and it's now available for download. Due to a technical issue,the release to the Powershell
Gallery is lagging a bit.
Please start evaluating migrating to this new vers, and let us know in the forums of any issues you may encounter.
In this version, we introduce two modules and a number of feature enhancements.
Retail module
This module is of interest to our retail customers who own HP Engage Go platforms, and allows controlling the table lock modes (including whether a PIN is required). If you don't own one of these devices, you can skip this section.
To get the currently configured mode, use the Get-HPRetailSmartDockConfiguration function in an elevated command line. You can also specify the -ShowPin if you currently have a PIN configured and want it displayed.
c:\PS> Get-HPRetailSmartDockConfiguration -ShowPin Name Value ---- ----- RetailSmartDockSupported True RetailSmartDockMode FastReleaseAndPIN RetailSmartDockTimeoutSeconds 15 RetailSmartDockState Docked RetailSmartDockHub AdvancedConnectivityBase RetailSmartDockDockCounter 19 RetailSmartDockBaseLockoutS... 111 RetailSmartDockRelockSeconds 201 PinIsSet True ActivePIN 3131
You can now switch between the four available modes (FastRelease, FastReleaseAndPIN, Privleged, and PrivilegedAndPIN) by using the
Set-HPRetailSmartDockConfiguration function:
c:\PS> Set-HPRetailSmartDockConfiguration -Mode PrivilegedAndPin -PIN 1234
Note that a new PIN must be between 4 and 10 characters in length, and is required for FastReleaseAndPIN amd PrivilegedAndPIN modes.
Consent Module
This second module adds support for managing HP Analytics consent from powershell. This is further documented in this whitepaper, and you can also
use that document to roll your own version in lieu of using HP CMSL.
To view the current configuration, use Get-HPAnalyticsConsentConfiguration:
C:\PS> Get-HPAnalyticsConsentConfiguration
Name Value
---- -----
ManagedBy User
AllowedCollectionPurposes {}
TenantID Individual
ManagedBy indicates if this is a user-managed device or organization managed device, and AllowedCollectionPurposes indicates the purposes you permit HP to use
collected information, which may be one or more of the purpose flags (Marketing, Support, or ProductEnhancement). For more information, please consult the whitepaper linked above.
To configure your preferences, use the Set-HPAnalyticsConsentAllowedPurposes function:
Set-HPAnalyticsConsentAllowedPurposes -AllowedPurpose Marketing,Support,ProductEnhancement.
To clear all purposes replace -AllowedPurposes [purposes] with -None.
New in repository module
The repository module gets a few enhancements. Primaly it now has a filter for UWP softpaqs.
Also, you can now use NewRepositoryReport to get a detailed listing of what's in your repository, in various formats (except HTML, we left that as an exercise to the
user, since we are still considering what the HTML report should look like). Here's a clipped example, when executed in my repository:
PS C:\ps> New-RepositoryReport | ft Softpaq Vendor Title Type Version ------- ------ ----- ---- ------- SP100002 Intel Intel Video Driver and Control Panel Driver 100.7324... SP100032 Crossmatch HP Client Security Manager Software 9.4.4.28... SP100099 Synaptics HP Ultraslim Docking Station DisplayPort (DP) Hub Firmware Firmware 2.33.004...
Finally, repository logs can now be written in CMTrace format rather than the previously defined, arbitray format. You can control this format via Set-HPCMSLLogFormat, or by setting the HPCMSL_LOG_FORMAT environment variable. This will direct the Write-HPLogInfo, Write-HPLogWarning, and Write-HPLogError functions to use the apropriate format.
Note that if you are switching logs, you probably want to start a new log file, otherwise you will end up with mixed formats in the same file.
We hope you enjoy this release, let us know your thoughts, issues, or suggestions in the forums.
Image Credits Jonas Ferlin, Brazil, via Pexels.com.