Managing Updates for HP Insights Windows Application

Introduction

By default, devices are set to auto-update the HP Insights Windows Application upon deployment. However, since May 2019 (version 3.19.160 onwards), users can disable auto-updates for a specified period.

This article outlines the process of managing updates for the HP Insights Windows Application, including:

• Release Classification

• Release Expiration and Auto Upgrades

• Methods to Manage Updates

Release Classification, Expiration, and Auto Upgrades

Release Classification

All releases of HP Insights Windows Application are categorized as either:

• Latest Release: Only one release is classified as the latest release, and it is the most current one. After a month of its release, the Latest Release is classified as a General Release.

• General Release: All releases before the Latest Release are classified as General Release. General Releases are supported up to seven months after releasing the next release, classified as a General Release.

For the beta release, the Latest Release and General Release are the same (that is, version 3.19.160) and are available at https://workforceexperience.hp.com/software and https://eu.workforceexperience.hp.com/software. 

HP recommends that customers who wish to disable auto updates of the HP Insights Windows Application only use the latest General Release. For example, between May 8 and June 8, 2019, HP recommends that customers use the April 9, 2019 release.

After June 8, 2019, HP recommends that customers use the May 8, 2019 release.

Release Expiration and Auto Upgrades

Each General Release of the HP Insights Windows Application has an expiration date. Customers who choose to disable automatic updates can remain on a given General Release until its expiration date, which is six months after the release of the next General Release. If the installed version of the HP Insights Windows Application on a device becomes six months old, the application enters an additional 30-day grace period. At the end of this 30-day grace period, the HP Insights Windows Application is designed to automatically upgrade to the latest General Release. The device will then remain on this latest General Release until its expiration date.

The following table illustrates the expiration date, the 30-day grace period for each release, and the auto-upgraded version applied after the grace period.

Option 1: Deployment using HP Insights and HP Insights Analytics Versions

Supported versions: The ability to manage auto updates of the HP Insights Windows Application is available only from the May 2019 release (version 3.19.160 onwards). The following describes the version of the HP Insights and HP Insights Analytics Package used for managing beta release updates.

Methods to Manage Updates (Earlier Versions)

The management of auto updates for the HP Insights Windows Application is achieved through a policy, which consists of a group of registry updates applied to the device. This auto-update policy governs the application's automatic updates and includes three key attributes. The following table outlines these attributes

Customers can choose any of the following methods to manage (enable or disable) automatic updates for the HP Insights Windows Application on HP Insights Windows devices:

• Method A: Use a batch file to manage updates

• Method B: Use a Microsoft Active Directory (AD) group policy object (GPO) to manage updates

Method A: Use a Batch File to Manage Updates

This method uses a .BAT file to manage automatic updates of HP Insights Windows Application.

Step 1: Create a batch file

1. Open Notepad.exe or any text editor

2. Copy and paste the following into the body of the file

::@echo off
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v IsVersionPolicy /t REG_DWORD /d 200 /f
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v TechpulseVersion /t REG_SZ /d %1 /f
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v HPTAVersion /t REG_SZ /d %2 /f

1. Click File > Save As, then save the file as the versionsettings-ref-import.bat. 

2. Save the versionsettings-ref-import.bat to a location accessible by all devices in the organization.

Step 2: Deploy the batch file

Customers can use a logon script or Microsoft System Center Configuration Manager (SCCM) to deploy the batch file.

Logon script

Those who have deployed the HP Insights Windows Application on a device can distribute the batch file (versionsettings-ref-import.bat) as a logon script using the following syntax.

{Path}\versionsettings-ref-import.bat TechpulseVersion HPTAVersion

For example: {Path}\versionsettings-ref-import.bat 3.19.160 and 4.1.4.2780

For devices where the HP Insights Windows Application is not yet deployed, you can combine the auto-update batch file (versionsettings-ref-import.bat) with the HP Insights Windows Application installation package into a single batch file using the following syntax.

{Path}\versionsettings-ref-import.bat  TechpulseVersionHPTAVersion && [Path]\Setup.exe /silent CPIN=[Company-PIN]

For example: {Path}\versionsettings-ref-import.bat  3.19.160 4.1.4.2780 && [Path]\Setup.exe /silent CPIN=[HP DaaS Company-PIN]

Note: For the beta release, use TechPulseVersion and HPTAVersion as 3.19.160 and 4.1.4.2780 respectively.

For additional assistance with an HP Insights company PIN, contact HP Proactive Management Managed Services.

Microsoft System Center Configuration Manager (SCCM)

For devices that do not have the HP Insights Windows Application deployed, combine the auto-update batch file (versionsettings-ref-import.bat) and the HP Insights Windows Application installation package into a single application package in SCCM.

1. In SCCM, navigate to Applications and create an application package to deploy the HP Insights Windows Application (for example, HP Insights Application).

2. To add the batch file to the HP Application:

   1. Right-click the HP Insights Application, and click Properties.

   2. Click the Deployment Types tab.

   3. Select HP Application and click Edit.

   4. In the Installation Program field, add the command to run the batch file (versionsettings-ref-import.bat) using the following syntax. The command will run before the HP Insights Windows Application is installed.

{Path}\versionsettings-ref-import.bat  TechpulseVersionHPTAVersion && [Path]\Setup.exe /silent CPIN=[Company-PIN]

For example: {Path}\versionsettings-ref-import.bat 3.19.160 4.1.4.2780 && [Path]\Setup.exe /silent CPIN=[HP DaaS Company-PIN]

For the beta release, use TechPulseVersion and HPTAVersion as 3.19.160 and 4.1.4.2780 respectively.

For additional assistance with an HP Insights company PIN, contact HP Proactive Management Managed Services.

Method B: Use a Microsoft Active Directory (AD) Group Policy Object (GPO) to Manage Updates

This method uses a Microsoft Active Directory (AD) Group Policy Object (GPO) to manage updates.

Step 1: Copying the ADML and ADMX files

1. Copy the sample ADML file provided by HP at https://workforceexperience.hp.com/software (Section: HP Insights -> HP insights Windows Application -> Download Policy File ) to \{FQDN}\SYSVOL\{Domain_Name}\PolicyDefinitions\en-US\HPInsights_Version_Settings.admx

2. Copy the sample ADMX file provided by HP to \{FQDN}\SYSVOL\{Domain_Name}\PolicyDefinitions\HPInsights_Version_Settings.adml

If the ADML and ADMX files are not saved to the correct locations, then the policy will not appear in the Active Directory Group Policy Object (GPO).

Step 2: Creating a new group policy object (GPO)

1. On the server, launch Group Policy Management.

2. In the Group Policy Management dialog box, navigate to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects.

3. Right-click on Group Policy Objects and select New.

4. In the New GPO dialog box, enter the following and click OK:

   1. Name: HPInsights-Version (or any name of choice)

   2. Source Starter GPO: (none)

Step 3: Associating the group policy object (GPO) to device groups

1. On the server, launch Group Policy Management.

2. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects.

   1. Double-click the HPInsights-Version to open the GPO.

3. Go to the Security Filtering section:

   1. Remove any User Groups by selecting the User Groups and clicking Remove.

   2. Click Add.

   3. In the Select User, Computer, or Group dialog box, click Object Types.

      1. In the Object Types dialog box, select only Computers and click OK.

      2. In the Select User, Computer, or Group dialog box, click Advanced.

      3. Click Find Now to search for all Device Groups and click OK.

      4. Repeat this step for all Device Groups as needed

   4. Click OK in the Select User, Computer, or Group dialog box.

4. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name}.

   1. Right-click on the {domain name} and select Link an Existing GPO from the dropdown.

   2. In the Select GPO dialog box, select the newly created Group Policy Object HPInsights-Version and click OK.

5. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects, select and right-click the newly created GPO HPInsights-Version and click Edit.

   1. In the Group Policy Management Editor dialog box, go to Computer Configuration > Policies > Administrative Templates: Policy definitions (ADMX files) retrieved from the central store > HPInsights-Version (it is automatically retrieved from the ADML/ADMX files)

   2. In the right menu, double-click HP Insights Version Configuration.

      1. In the HP Insights Version Configuration dialog box enter the following:

         • Select Enabled

         • HP Insights version: 3.19.160

         • HP Insights Analytics Client version: 4.1.4.2780

      2. Click OK

   3. Close the Group Policy Management Editor.

6. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects, select and right-click the newly created Group Policy Object HPInsights-Version and click Enforced.

Customers who leverage Microsoft System Center Configuration Manager (SCCM) to deploy HP Insights Windows Applications can create a global condition and requirement.

Step 4: Creating a global condition in SCCM

1. Launch SCCM.

2. Click Software Library > Overview > Application Management > Global Conditions.

3. Right-click on Global Conditions and select Create Global Condition.

4. In the Create Global Condition dialog box, enter the following and click OK:

   1. Name: HP DaaS Version Policy Check

   2. Device Type: Windows

   3. Condition Type: Setting

   4. Setting Type: Registry Value

   5. Data Type: String

   6. Hive Name: HKEY_LOCAL_MACHINE

   7. Key Name: SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy

   8. Value Name: TechpulseVersion

Step 5: Creating a requirement in SCCM

1. Launch SCCM.

2. Click Software Library > Overview > Application Management > Applications.

   1. In the right panel, select the name of the SCCM package used to deploy the HP Insights Windows Application (for example, HP Insights Application).

   2. Right-click the HP Insights Application, and click Properties.

   3. In the HP Insights Application Properties dialog box, click on the Deployment Types tab.

      1. Select HP Application and click Edit.

      2. In the HP Application Properties dialog box, click the Requirements tab.

         1. Click Add.

         2. In the Create Requirement dialog box, select the following:

            • Category: Custom

            • Condition: HP Version Policy Check

            • Rule type: Existential

            • Enable the option - The selected global condition must exist on client devices.

         3. Click OK in the Create Requirement dialog box.

   4. Click OK in the HP Application Properties dialog box.

3. Click OK in the HP Application Properties dialog box.

Note: With the Option 1 deployment, the deployment of HP Insights and HP Insights Analytics is controlled. However, HP Insights Plugins will automatically update to the latest versions alongside the installed HP Insights and HP Insights Analytics.

Option 2: Deployment using HP Insights, HP Insights Analytics, and HP Insights Plugins Package Versions

Supported Versions: The ability to manage auto updates of the HP Insights Windows Application is available only from the May 2019 release (version 3.19.160 onwards). The following describes the version of the HP Insights, HP Insights Analytics, and HP Insights Plugin Package used for managing beta release updates.

Additional Notes:

• Minimum Support for HP Insights Plugin Package:

  • HP Insights: 5.24.230

  • HP Insights Analytics: 4.2.2364.0

• It is required to set the above application minimum versions to support the HP Insights Plugin Package in the deployment ring. To get additional functionalities, it is mandatory to configure HP Insights Plugin Package to manage updates for HP insights Windows application.

• If the HP Insights Plugin Package is not configured and the minimum supported versions of HP Insights and HP Insights Analytics are not set, additional functionalities will not be available.

Methods to Manage Updates (New Versions)

The management of auto updates for the HP Insights Windows Application is achieved through a policy, which consists of a group of registry updates applied to the device. This auto-update policy governs the application's automatic updates and includes three key attributes. The following table outlines these attributes of the auto-update policy:

Customers can choose any of the following methods to manage (enable or disable) automatic updates for the HP Insights Windows Application on HP Insights Windows devices:

• Method A: Use a batch file to manage updates

• Method B: Use a Microsoft Active Directory (AD) group policy object (GPO) to manage updates

Method A: Use a Batch File to Manage Updates

This method uses a .BAT file to manage automatic updates of HP Insights Windows Application.

Step 1: Create a batch file

1. Open Notepad.exe or any text editor.

2. Copy and paste the following into the body of the file:

::@echo off
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v IsVersionPolicy /t REG_DWORD /d 200 /f
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v TechpulseVersion /t REG_SZ /d %1 /f
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v HPTAVersion /t REG_SZ /d %2 /fREG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy" /v PluginPackageVersion /t REG_SZ /d %3 /f

3. Click File > Save As, then save the file as the versionsettings-ref-import.bat.

4. Save the versionsettings-ref-import.bat to a location accessible by all devices in the organization.

Step 2: Deploy the batch file

Customers can use a logon script or Microsoft System Center Configuration Manager (SCCM) to deploy the batch file.

Logon script

Those who have deployed the HP Insights Windows Application on a device can distribute the batch file (versionsettings-ref-import.bat) as a logon script using the following syntax.

{Path}\versionsettings-ref-import.bat TechpulseVersion HPTAVersion PluginPackageVersion

For example:

{Path}\versionsettings-ref-import.bat 5.24.230 4.2.2364.0 1.0.1.0

For the beta release, use TechPulseVersion and HPTAVersion as 5.24.230 and 4.2.2364.0 respectively and additionally 1.0.1.0 for the plugin package.

For devices where the HP Insights Windows Application is not yet deployed, you can combine the auto-update batch file (versionsettings-ref-import.bat) with the HP Insights Windows Application installation package into a single batch file using the following syntax.

{Path}\versionsettings-ref-import.bat TechpulseVersion HPTAVersion PluginPackageVersion && [Path]\Setup.exe /silent CPIN=[Company-PIN]

For example:

{Path}\versionsettings-ref-import.bat 5.24.230 4.2.2364.0 1.0.1.0 && [Path]\Setup.exe /silent CPIN=[HP DaaS Company-PIN]

For the beta release, use TechPulseVersion and HPTAVersion as 5.24.230 and 4.2.2364.0 respectively and additionally 1.0.1.0 for Plugin Package. For additional assistance with an HP Insights company PIN, contact HP Proactive Management Managed Services.

Microsoft System Center Configuration Manager (SCCM)

For devices that do not have the HP Insights Windows Application deployed, combine the auto-update batch file (versionsettings-ref-import.bat) and the HP Insights Windows Application installation package into a single application package in SCCM.

1. In SCCM, navigate to Applications and create an application package to deploy the HP Insights Windows Application (for example, HP Insights Application).

2. To add the batch file to the HP Application:

   1. Right-click the HP Insights Application, and click Properties.

   2. Click the Deployment Types tab.

   3. Select HP Application and click Edit.

   4. In the Installation Program field, add the command to run the batch file (versionsettings-ref-import.bat) using the following syntax. The command will run before the HP Insights Windows Application is installed.

{Path}\versionsettings-ref-import.bat TechpulseVersion HPTAVersion PluginPackageVersion && [Path]\Setup.exe /silent CPIN=[Company-PIN]

For example:

{Path}\versionsettings-ref-import.bat 5.24.230 4.2.2364.0 1.0.1.0 && [Path]\Setup.exe /silent CPIN=[HP DaaS Company-PIN]

For the beta release, please use TechPulseVersion and HPTAVersion as 5.24.230 and 4.2.2364.0 respectively and additionally 1.0.1.0 for Plugin Package.

For additional assistance with an HP Insights company PIN, contact HP Proactive Management Managed Services.

Method B: Use a Microsoft Active Directory (AD) Group Policy Object (GPO) to Manage Updates

This method uses a Microsoft Active Directory (AD) Group Policy Object (GPO) to manage updates.

Step 1: Copying the ADML and ADMX files

1. Copy the sample ADML file provided by HP at https://workforceexperience.hp.com/software (Section: HP Insights -> HP insights Windows Application -> Download Policy File ) to \{FQDN}\SYSVOL\{Domain_Name}\PolicyDefinitions\en-US\HPInsights_Version_Settings.admx

2. Copy the sample ADMX file provided by HP to \{FQDN}\SYSVOL\{Domain_Name}\PolicyDefinitions\HPInsights_Version_Settings.adml

If the ADML and ADMX files are not saved to the correct locations, then the policy will not appear in the Active Directory Group Policy Object (GPO).

Step 2: Creating a new group policy object (GPO)

1. On the server, launch Group Policy Management.

2. In the Group Policy Management dialog box, navigate to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects.

3. Right-click on Group Policy Objects and select New.

4. In the New GPO dialog box, enter the following and click OK:

   1. Name: HPInsights-Version (or any name of choice)

   2. Source Starter GPO: (none)

Step 3: Associating the group policy object (GPO) to device groups

1. On the server, launch Group Policy Management.

2. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects.

   1. Double-click the HPInsights-Version to open the GPO.

3. go to the Security Filtering section:

   1. Remove any User Groups by selecting the User Groups and clicking Remove.

   2. Click Add.

   3. In the Select User, Computer, or Group dialog box, click Object Types.

      1. In the Object Types dialog box, select only Computers and click OK.

      2. In the Select User, Computer, or Group dialog box, click Advanced.

      3. Click Find Now to search for all Device Groups and click OK.

      4. Repeat this step for all Device Groups as needed

   4. Click OK in the Select User, Computer, or Group dialog box.

4. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name}.

   1. Right-click on the {domain name} and select Link an Existing GPO from the dropdown.

   2. In the Select GPO dialog box, select the newly created Group Policy Object HPInsights-Version and click OK.

5. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects, select and right-click the newly created GPO HPInsights-Version and click Edit.

   1. In the Group Policy Management Editor dialog box, go to Computer Configuration > Policies > Administrative Templates: Policy definitions (ADMX files) retrieved from the central store > HPInsights-Version (it is automatically retrieved from the ADML/ADMX files)

   2. In the right menu, double-click HP Insights Version Configuration.

      1. In the HP Insights Version Configuration dialog box enter the following:

         • Select Enabled

         • HP Insights version: 3.19.160

         • HP Insights Analytics Client version: 4.1.4.2780

         • HP Insights Plugin Package version: 1.0.1.0

      2. Click OK.

   3. Close the Group Policy Management Editor.

6. In the Group Policy Management dialog box, go to Group Policy Management > {forest name} > Domains -> {domain name} > Group Policy Objects, select and right-click the newly created Group Policy Object HPInsights-Version and click Enforced.

Customers who leverage Microsoft System Center Configuration Manager (SCCM) to deploy HP Insights Windows Applications can create a global condition and requirement.

Step 4: Creating a global condition in SCCM

1. Launch SCCM.

2. Click Software Library > Overview > Application Management > Global Conditions.

3. Right-click on Global Conditions and select Create Global Condition.

4. In the Create Global Condition dialog box, enter the following and click OK:

   1. Name: HP DaaS Version Policy Check

   2. Device Type: Windows

   3. Condition Type: Setting

   4. Setting Type: Registry Value

   5. Data Type: String

   6. Hive Name: HKEY_LOCAL_MACHINE

   7. Key Name: SOFTWARE\Policies\Hewlett-Packard\HPTechPulse\GPO\TechPulseVersionPolicy

   8. Value Name: TechpulseVersion

Step 5: Creating a requirement in SCCM

1. Launch SCCM.

2. Click Software Library > Overview > Application Management > Applications.

   1. In the right panel, select the name of the SCCM package used to deploy the HP Insights Windows Application (for example, HP Insights Application).

   2. Right-click the HP Insights Application, and click Properties.

   3. In the HP Insights Application Properties dialog box, click on the Deployment Types tab.

      1. Select HP Application and click Edit.

      2. In the HP Application Properties dialog box, click the Requirements tab.

         1. Click Add.

         2. In the Create Requirement dialog box, select the following:

            • Category: Custom

            • Condition: HP Version Policy Check

            • Rule type: Existential

            • Enable the option - The selected global condition must exist on client devices.

         3. Click OK in the Create Requirement dialog box.

   4. Click OK in the HP Application Properties dialog box.

3. Click OK in the HP Application Properties dialog box.

Related Resources

For additional information on Minimum supported HP Insights Plugin Package, its dependencies on HP Insights and HP Insights Analytics packages as well as the content and functionality of packages, refer to:

• Plugin Package in HP Insights Application

• HP Insights Plugins Catalog

Contact Us

For any assistance, create a support case or email [email protected]