When a policy is assigned and applied, how long does the device take to report to the WXP console?
Duration to apply the update: When a policy is assigned, the HP Insights Agent may take up to 15 minutes to deploy the policy and synchronize with the Workforce Experience Platform (WXP). For BIOS updates, the platform uses SoftPaq (based on platform or model) or Windows Update BIOS capsules and stage the script for a shutdown and then suspend BitLocker before the subsequent restart. User must initiate the reboot. The actual installation time varies based on the device hardware and update size. Administrators can monitor the deployment status in real time from the Activity section of the console. The Activity status shows Completed if the BIOS update was successfully pushed. However, the Hardware and Software Inventory may not show the "updated" BIOS version if the end user does not initiate the reboot.
Reporting time to the WXP console: After an update is completed (after a reboot, if required), then the Windows Agent reports changes to hardware and software inventory. If a reboot is not required, then it will be reported near real time (15 minutes). As a result:
Inventory updates may appear within 15 minutes
Some dashboard charts and reports may take up to 1-2 hours to fully reflect the updated status.
HP Active Care and Wolf Protect and Trace do not collect BIOS and SoftPaq update information in real time yet.
BIOS/Driver update behavior, if a device is offline or has errors: When a device comes back online, it will retrieve the pending jobs for any active assignments, until the assignment is canceled. For the BIOS policy, the job runs every 24 hours. For Drivers, it is controlled or scheduled by the admin.
When the BIOS is downloaded, is it downloaded to a specific path and then deleted?
For BIOS SoftPaq Updates, it is downloaded to "$($Env:SystemDrive)\\SWSetup" and not deleted. However, if it's already downloaded on the BIOS update policy, it will not be downloaded again.
For BIOS WU, it is downloaded to "C:\Windows\SystemTemp\hp\" and it is deleted after a restart.
For Drivers, it is downloaded to "$($Env:SystemDrive)\\SWSetup" and it is not deleted. The file is downloaded again if the latest driver version is not installed on the device.
What is the Bandwidth Consumption on the Agent Side (Initial and Recurring Data Transmission)?
Bandwidth usage depends on the number and size of updates required on the device.
If there is an update to the HP Insights Agent, is it considered a driver so it can be updated through the console?
The HP Insights Agent is updated automatically. However, if the tenant is part of a Ring policy, update control may be available depending on the configuration.
Why do HP and WXP not always have the latest driver version available on an IHV (Independent Hardware Vendor) website, such as Intel?
HP does not include every driver version released by IHV partners. Some releases may contain minor fixes that are specific to a particular environment and are not required for most customers. We also performs additional validation to ensure that drivers work reliably with other system components and drivers. As a result, some driver versions may not be released if they do not meet HP’s quality and compatibility standards. We work closely with our partners to determine which driver updates are important to publish in a SoftPaq.
At what time does a policy run?
BIOS Update Policies: BIOS policies do not run at a fixed user-defined time.
When a policy is created, it is automatically scheduled for current time + ~15 minutes.
The schedule is stored and managed in UTC, and the agent executes it based on the device’s local time.
The server sends the job with UTC start details, and the agent aligns execution accordingly.
After initial execution, the policy is re-evaluated approximately every 24 hours until completion.
Driver Update Policies: Driver policies support scheduled execution with a start time.
Admins can specify a start date and time.
The selected time (based on the user’s profile time zone) is converted to UTC before being sent to the server.
The agent stores the schedule in UTC and executes the policy based on the device’s local time.
Is it possible to schedule policies?
BIOS Update Policies: No, BIOS policies cannot be explicitly scheduled. They are automatically triggered shortly after creation (~15 minutes) and managed through recurring evaluation cycles.
Driver Update Policies: Yes, partially.
Admins can define a start time for when the policy begins execution.
End times or maintenance window scheduling are not yet supported.
What happens if a device is offline when the policy is scheduled?
If a device comes online within the valid schedule window, the policy will still execute.
After the device reconnects, there is typically a 5–10 minute delay while the agent initializes services, loads plugins, and fetches scheduled policies.
Once initialization is complete, the policy is executed according to its schedule.
Contact Us
For any assistance, create a support case or email support@wxp.hp.com.