Windows Autopilot Settings Test

Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. When the Microsoft Intune is integrated with Windows Autopilot service, it eliminates the wait time for enrolled devices to get custom-imaged instead using the OEM-provided image. Autopilot settings ensure that devices are tenant-registered and properly set up, thus facilitating immediate use upon receipt. Enrolling devices in Intune using Windows Autopilot provides the following benefits:

enrolled devices are configured automatically out-of-the-box (OOBE) without manual effort.
Autopilot applies pre-defined settings, configurations, and applications during initial setup.
users can start working immediately without assistance from administrators.
Autopilot enforces uniform policies, security baselines, and configurations across all devices.
only enrolled devices are allowed to access corporate resources in a secure way.
simplifies the device provisioning, management, and user on-boarding process.

When the devices are enrolled using Windows Autopilot service, deployment profiles assigned to the enrolled devices in Microsoft Intune are correctly associated with the devices. Synchronization between the enrolled devices and their configuration profiles in the Autopilot service within the Microsoft Intune are updated, properly applied, and accurately reflected within Intune. The devices enrolled using Sync ensures that all devices added or removed in the Windows Autopilot service are reflected in Intune.

Syncs Deployment Profiles: The profiles assigned to devices in Intune (e.g., User-Driven or Self-Deploying mode) are correctly associated with devices.

Checks Hardware Details: Confirms that devices have the correct hardware information uploaded, such as serial numbers and hardware hashes.

Windows Autopilot, coupled with Intune, delivers a highly efficient, scalable, and user-friendly solution for modern device management. It minimizes IT workload, enhances user satisfaction, and ensures devices remain secure and compliant. To ensure smooth, secure, and consistent deployment of Windows devices across the organization, administrators should monitor Autopilot settings on Intune continuously. By monitoring Autopilot settings, administrators can verify that devices are properly registered, deployment profiles are applied correctly, and no devices are stuck in failed, blocked, or unknown states. This helps them detect configuration or connectivity issues at the earliest, reduces onboarding delays, and ensures new devices comply with organizational policies and security requirements.

To help administrators in this regard, the Windows Autopilot Settings test tracking devices in various states such as unknown, failed, pending reset, blocked, or not contacted and reveals the count of devices in each state. This way, administrators can quickly identify where exactly more number of devices are stuck, thus detecting delayed or disrupt automated provisioning.

Target of the Test: Microsoft Intune

Agent deploying the test: A remote agent

Output of the test: One set of results for the Intune being monitored

Configurable parameters for the test
Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Tenant ID	Specify the Directory ID of the Azure AD tenant to which the target subscription belongs. To know how to determine the Directory ID, refer to Configuring the eG Agent to Monitor Microsoft Azure Intune Using Intune REST API.
Client ID, Client Password, and Confirm Password	To connect to the target subscription, the eG agent requires an Access token in the form of an Application ID and the client secret value. For this purpose, you should register a new application with the Azure AD tenant. To know how to create such an application and determine its Application ID and client secret, refer to Configuring the eG Agent to Monitor Microsoft Azure Intune Using Intune REST API. Specify the Application ID of the created Application in the Client ID text box and the client secret value in the Client Password text box. Confirm the Client Password by retyping it in the Confirm Password text box.
ProxyHost and ProxyPort	In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the ProxyHost and ProxyPort parameters. By default, these parameters are set to none, indicating that the eG agent is not configured to communicate via a proxy, by default.
ProxyUsername, ProxyPassword, Confirm Password	If the proxy server requires authentication, then, specify a valid proxy user name and password in the Proxy Username and Proxy Password parameters, respectively. Then, confirm the password by retyping it in the Confirm Password text box. If no proxy server is used, or if the proxy server used does not require authentication, then the default setting - none - of these parameters, need not be changed.
Is DD Required for Enrolled Devices	By default, this flag is set to No. This implies that by default, detailed metrics will not be available for the Enrolled devices measure of this test. To enable detailed diagnosis for this measure, you can set this flag to Yes. In this case, you will be able to view the complete details of all Windows 365 devices that are enrolled using Windows Autopilot service, as part of detailed diagnostics.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements reported by the test

Measurement

Description

Measurement Unit

Interpretation

Autopilot sync status

Indicates the current status of synchronization between the enrolled devices and their configuration profiles in the Autopilot service within the Microsoft Intune portal.

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value	Numeric Value
Sync completed	0
Sync is in progress	1
Unknown sync status	2
Sync failed	3

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the sync state. The graph of this measure however, is represented using the numeric equivalents only - 0 to 3.

The detailed diagnosis of this measure the date and time at which the synchronization was last performed and the date and time at which the synchronization was manually triggered last.

Enrolled devices

Indicates the number of devices enrolled using Windows Autopilot service.

Number

The detailed diagnosis of this measure lists the serial number and manufacture model of each device, the time stamp at which each device contacted Intune, principle name of the user, Azure AD device ID and managed device ID and the current remediation state of the device.

Unknown devices

Indicates the number of devices whose Autopilot deployment status is unknown.

Number

Pending reset devices

Indicates the number of devices that are marked for a reset but the reset process has not yet completed.

Number

Failed devices

Indicates the number of devices where the Autopilot deployment has failed.

Number

Not contacted devices

Indicates the number of devices that have not yet connected to the Autopilot service or Intune for deployment.

Number

Blocked devices

Indicates the number of devices blocked from Autopilot deployment by policy or due to non-compliance.

Number