> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting/configuration-guide_-hard-reset-troubleshooting.md). # Configuration guide: Hard reset troubleshooting ## **Introduction** To get started with this workflow, please ensure all related content is installed and configured appropriately. This page provides guidance on which content is included and how to configure it. Please keep in mind this is just a guide and represents suggested configurations. You are free to customize and edit content as you see fit based on your specific environment. ## Pre-requisites This library pack contains content from the following [expansion products](https://nexthink.gitbook.io/opd/overview/products). * [Employee Engagement - Campaigns](https://nexthink.gitbook.io/opd/user-guide/campaigns) * [Flow - Workflows](https://nexthink.gitbook.io/opd/user-guide/workflows) ## Content list and dependency This library pack contains the following content and dependencies: | Type | Name | Description | | --------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [Workflows](https://nexthink.gitbook.io/opd/user-guide/workflows) | Hard reset troubleshooting | The workflow of surveying employees, collecting technical data, and taking action to resolve unexpected hard resets. | | [Campaigns](https://nexthink.gitbook.io/opd/user-guide/campaigns) | Hard reset survey - Workflow invoke | This campaign is a survey that asks the user what happened and what caused the hard reset. | | | Disk cleanup - Invoke | Works in pair with the Disk cleanup remote action. It asks users if they want to start a disk cleanup and to choose between a light clean or a deep clean. | | | Disk cleanup - Completed | Works in pair with the Disk cleanup remote action. Inform the user about the completion of the disk cleanup | | [Remote Actions](https://nexthink.gitbook.io/opd/user-guide/remote-actions) | Get Windows Event Log entry information | It is used to interrogate the Windows Event Log and output details of any matching event found according to the event information provided in the inputs of the Remote Action. | | | Get battery status | Returns the health status of the battery installed on the laptop, in terms of capacity that it can still hold. | | | Get Dell pending BIOS firmware and driver updates | Utilizes the Dell Command Utility to perform scans on devices for any outstanding updates related to Drivers, BIOS, and Firmware. | | | Invoke install Dell pending driver updates | Automates Dell driver updates silently without user interface interruption. | | | Get HP pending BIOS firmware and driver updates | Utilizes the HP Image Assistant (HPIA) to perform scans on devices for any outstanding updates related to Drivers, BIOS, and Firmware. | | | Invoke install HP pending driver updates | Automates HP driver updates silently without user interface interruption. | | | Disk cleanup | Helps employees to maintain healthy levels of disk space. | ## Configuration guide ### Step 1) Install library pack content Go to the [Nexthink Library](https://nexthink.gitbook.io/opd/user-guide/nexthink-library) and install all required content. ### Step 2) Configure ITSM API connector credentials The configuration of connector credentials is essential for enabling API calls. Each Service/API thinklet has a dropdown field for credentials that needs to be filled out. When the workflow is installed or copied from the Library, this field will be blank as it is a local setup of each environment and is not included in the Library. See detailed information in the [documentation](https://docs.nexthink.com/latest/integrations/outbound-connectors/connector-credentials). ServiceNow actions can be created using the built-in ServiceNow connector. More information about the ServiceNow Incident Management connector can be found in the [documentation](/platform/user-guide/workflows/creating-workflows/configuring-connector-thinklet/servicenow-incident-management.md). ### Step 4) Configure remote action(s) This workflow uses the following remote actions. Make sure to install the latest versions and complete the setup as below. | Name | Trigger | Parameters to edit | | -------------------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Get Windows Event Log entry information | API trigger should be enabled so that it can be triggered from the Workflow |

The following RA input parameters will be overridden by workflow parameters and must have the Allow user to enter custom values ​​option enabled:

| | Get Dell pending BIOS firmware and driver updates. | API trigger should be enabled so that it can be triggered from the Workflow | | | Get HP pending BIOS firmware and driver updates | API trigger should be enabled so that it can be triggered from the Workflow | | | Invoke install Dell pending driver updates | API trigger should be enabled so that it can be triggered from the Workflow | | | Invoke install HP pending driver updates | API trigger should be enabled so that it can be triggered from the Workflow | | **Get Windows Event Log entry information - input parameters** This workflow uses this remote action to check and collect the latest status information for the following Windows events that are logged when the device reboots. This information is then passed into a support ticket created by the workflow to help IT troubleshoot the case: * Event ID 41 * Event ID 6008 * Event ID 1074 | Name | Value | Description | | -------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | search\_time\_period\_last\_x\_minutes | 180 | Number of minutes to recurse the event log to find the error details provided | | event\_log\_1 | System | Windows event log name | | severity\_level\_1 | Critical | Event level name | | event\_id\_1 | 41 | Windows event ID 41 is a critical error that usually indicates an unexpected shutdown or loss of power to your computer. | | event\_description\_1 | '' | Not used in this workflow | | event\_log\_2 | System | Windows event log name | | severity\_level\_2 | Error | Event level name | | event\_id\_2 | 6008 | Windows event ID 6008 is triggered if the computer was shut down forcefully using remote shutdown tool or automatically by a third-party program without the user request. | | event\_description\_2 | '' | Not used in this workflow | | event\_log\_3 | System | Windows event log name | | severity\_level\_3 | Information | Event level name | | event\_id\_3 | 1074 | Windows event ID | | event\_description\_3 | '' | Not used in this workflow | **Get HP pending BIOS firmware and driver updates** | Name | Value | Description | | --------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | install\_hpia\_tool | True | This Remote Action must have the HPIA tool in place to run. Confirm you would like the Remote Action to install it by setting this value to True. If the HPIA tool is already installed on the device we will skip the installation regardless of this value. To ensure successful usage every time we recommend to leave the value at True | | hpia\_required\_version | 5.2.1 | The required version of HP Image Assistant tool in the format MajorVersion.MinorVersion.BuildVersion. For example, 5.2.0 | | hpia\_tool\_download\_url | | Full URL to download the required version of HP Image Assistant tool | | maximum\_delay\_in\_seconds | 30 | This ensures randomization of endpoints when connecting to external resources to prevent any overloading | **Get Dell pending BIOS firmware and driver updates - input parameters** | Name | Value | Description | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | install\_DellCU\_tool | True | This Remote Action must have the Dell command update utility in place to run. Confirm you would like the Remote Action to install it by setting this value to True. If the DCU is already installed on the device we will skip the installation regardless of this value. To ensure successful usage every time we recommend to leave the value at True | | DCU\_required\_version | 5.2.0 | DCU Version to be used, will be installed if not installed,Any old versions present on the device will be uninstalled | | DCU\_64Bit\_download\_url | | DCU 64bit Setup executable download link | | DCU\_32Bit\_download\_url | | DCU 32bit Setup executable download link | | maximum\_delay\_in\_seconds | 30 | Maximum random delay set to avoid network overload. Provide number of seconds lower than 600 | **Invoke install Dell pending driver updates - input parameters** | Name | Value | Description | | --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | install\_DellCU\_tool | True | This Remote Action must have the Dell Command Update tool in place to run. Confirm you would like the Remote Action to install it by setting this value to True. If the Dell Command Update tool is already installed on the device we will skip the installation regardless of this value. To ensure successful usage every time we recommend to leave the value at True | | DCU\_required\_version | 5.2.0 | DCU Version to be used, will be installed if not installed,Any old versions present on the device will be uninstalled | | DCU\_64Bit\_download\_url | | DCU 64bit Setup executable download link | | DCU\_32Bit\_download\_url | | DCU 32bit Setup executable download link | | forced\_install\_no\_campaign\_notifications | True | If forced install is set to True the pending driver updates will be installed to the device with no user notifications | | forced\_restart\_no\_campaign\_notifications | False | When executing the remote action with forced\_install\_no\_campaign\_notifications set to True this input must be used to determine whether or not to force a restart after the forced update. Only applicable for forced\_install mode (no user interaction) | | campaign\_ask\_if\_can\_install | False | When executing the remote action with this input set to True, the remote action will prompt the user to ask if we can perform a driver update on the device. If the user selects 'no' then the driver update will not be performed and the script will exit | | campaign\_request\_user\_restart | True | When executing the remote action with this input set to True, if the user agrees to perform the driver installation, when the installation is complete they will be prompted to perform a restart. The user can choose to not restart if it is not convenient. If a restart is not required following updates we will automatically invoke the campaign only to inform the user the updates are complete | | update\_invoke\_campaign\_id | update\_drivers\_invoke | The campaign ID used to invoke the request to install updated drivers | | update\_complete\_restart\_needed\_campaign\_id | restart\_to\_update\_invoke | The campaign ID used to request a restart following installation of driver updates | | update\_complete\_no\_restart\_needed\_campaign\_id | update\_drivers\_completed | The campaign ID used to inform user we are finished following installation of driver updates, automatically invoked if no restart was needed | | maximum\_delay\_in\_seconds | 45 | Maximum random delay on seconds to avoid overloading the network | **Invoke install HP pending driver updates - input parameters** | Name | Value | Description | | --------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | install\_hpia\_tool | True | This Remote Action must have the HPIA tool in place to run. Confirm you would like the Remote Action to install it by setting this value to True. If the HPIA tool is already installed on the device we will skip the installation regardless of this value. To ensure successful usage every time we recommend to leave the value at True | | hpia\_required\_version | 5.2.1 | The required version of HP Image Assistant tool in the format MajorVersion.MinorVersion.BuildVersion. For example, 5.2.0 | | hpia\_tool\_download\_url | | Full URL to download the required version of HP Image Assistant tool | | forced\_install\_no\_campaign\_notifications | True | If forced install is set to True the pending driver updates will be installed to the device with no user notifications | | forced\_restart\_no\_campaign\_notifications | False | When executing the remote action with forced\_install\_no\_campaign\_notifications set to True this input must be used to determine whether or not to force a restart after the forced update. Only applicable for forced\_install mode (no user interaction) | | campaign\_ask\_if\_can\_install | False | When executing the remote action with this input set to True, the remote action will prompt the user to ask if we can perform a driver update on the device. If the user selects 'no' then the driver update will not be performed and the script will exit | | campaign\_request\_user\_restart | True | When executing the remote action with this input set to True, if the user agrees to perform the driver installation, when the installation is complete they will be prompted to perform a restart. The user can choose to not restart if it is not convenient. If a restart is not required following updates we will automatically invoke the campaign only to inform the user the updates are complete | | update\_invoke\_campaign\_id | update\_drivers\_invoke | The campaign ID used to invoke the request to install updated drivers | | update\_complete\_campaign\_id | restart\_to\_update\_invoke | The campaign ID used to request a restart following installation of driver updates | | update\_complete\_no\_restart\_needed\_campaign\_id | update\_drivers\_completed | The campaign ID used to inform user we are finished following installation of driver updates, automatically invoked if no restart was needed | | maximum\_delay\_in\_seconds | 45 | Maximum random delay on seconds to avoid overloading the network | ### Step 5) Configure campaigns There are three campaigns in this workflow: | Campaign name | Campaign NQL ID | Description | | ----------------------------------- | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Hard reset survey - Workflow invoke | hard\_reset\_survey\_\_workflow\_invoke | This campaign is a survey that asks the user what happened and what caused the hard reset. | | Disk cleanup - Invoke | disk\_cleanup\_invoke | Works in pair with the Disk cleanup remote action. It asks users if they want to start a disk cleanup and to choose between a light clean or a deep clean. | | Disk cleanup - Completed | disk\_cleanup\_completed | Works in pair with the Disk cleanup remote action. Inform the user about the completion of the disk cleanup. | {% hint style="info" %} **Please note:** In this workflow, 'Hard reset survey - Workflow invoke' appears as a single campaign with specific conditions based on campaign answers. Note that the workflow will trigger once the campaign has been fully completed {% endhint %} These campaigns should be modified before use to ensure that they match corporate communication guidelines. Navigate to the[ manage campaigns ](https://nexthink.gitbook.io/opd/user-guide/campaigns/managing-campaigns)administration page to review and edit your campaigns. For each installed campaign, please ensure to: * Customize the sender name and image. * Review and adjust questions. * Publish the campaign when you are ready to use it. ### Step 6) Schedule the workflow This is an event-triggered workflow, designed to run after a hardware reset punctual event has been detected using NQL. **Recommended trigger configuration** Select the Event trigger type and configure the event trigger as shown below. **NQL:** {% code title="Code" %} ``` 1 device_performance.hard_resets 2 | where device.operating_system.platform == windows 3 | list device.name ``` {% endcode %} ## **Usage guide** Your content is now configured and ready to be used. For usage overview and recommendations, you can visit the usage guide: [Usage guide: Hard reset troubleshooting](/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting/usage-guide_-hard-reset-troubleshooting.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nexthink.com/platform/library-packs/l1-support/workflow_-hard-reset-troubleshooting/configuration-guide_-hard-reset-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.