Configuration guide: Intune client continuity

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.

• Flow - Workflows

Content list and dependency

This library pack contains the following content and dependencies:

Type	Name	Description
Workflows	Hard reset troubleshooting	The workflow of surveying employees, collecting technical data, and taking action to resolve unexpected hard resets.
Remote Actions	Get Intune synchronization status	Helps to identify any issues with policy synchronization or problems applying policy.
	Get Intune device status	Helps to understand the health of Intune-managed devices, and identify any issues with device enrollment.
	Set service information	Changes the status and startup type of one or multiple services, which are provided as input.
	Restart service	Restarts the service except if it is in the blacklist.
	Invoke Intune policy synchronization	Searches for the "PushLaunch" scheduled task created automatically by Intune and forces the start of the task forcing the policy synchronization.
	Get Intune client disgnostics	Creates a copy of the MDM logs within the folder "c:\users\public\documents" on a local device.

Configuration guide

Step 1) Install library pack content

Go to the 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.

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.

Step 3) 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
Set service information	API trigger should be enabled so that it can be triggered from the Workflow	The following RA input parameters must be configured: ServiceName: IntuneManagementExtension StatusChange: start SetSrartTypeTo: auto
Restart service		ServiceName: DmWapPushService

Step 4) 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 Scheduled trigger type and configure the event trigger as shown below.

NQL:

Code

1 devices during past 7d
2 | where operating_system.platform == Windows and operating_system.name !in ["*server*"]

Recurrence: Weekly - select at least one day.

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: Intune client continuity

---

RELATED TOPICS

• Manage Workflows

• Manage Remote Actions