You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: intune/intune-service/configuration/device-profile-troubleshoot.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,11 +29,11 @@ This article applies to the following policies:
29
29
30
30
## Policy refresh intervals
31
31
32
-
When a device syncs with Intune, it checks for configuration for the current user/device context, receiving any pending actions, policies and apps assigned to it.
32
+
When a device syncs with Intune, it checks for configuration for the current user or device context, and receives any pending actions, policies, and apps assigned to it.
33
33
34
34
For app protection policy refresh intervals, go to [App Protection Policy delivery timing](../apps/app-protection-policy-delivery.md).
35
35
36
-
There are 3 main types of device syncs - change-based, client initiated, and single device.
36
+
There are three main types of device syncs - change-based, client initiated, and single device.
37
37
38
38
### Change-based
39
39
@@ -48,7 +48,7 @@ An offline device, like when it's powered off, or a disconnected device, might n
48
48
49
49
> [!NOTE]
50
50
>
51
-
> - It might take additional time for Intune reports to reflect the latest status of the policy on the device in the Intune portal.
51
+
> - It can take more time for Intune reports to reflect the latest status of the policy on the device in the Intune portal.
52
52
> - To receive push notifications, devices must connect to specific network endpoints. For a list of network endpoints, see [Network endpoints for Microsoft Intune](../fundamentals/intune-endpoints.md#intune-dependencies).
@@ -57,24 +57,24 @@ An offline device, like when it's powered off, or a disconnected device, might n
57
57
58
58
### Client initiated
59
59
60
-
Thee following client syncs happen in response to a device event or state change, like when a user signs into the device or if the malware status changes:
60
+
The following client syncs happen in response to a device event or state change, like when a user signs into the device or if the malware status changes:
61
61
62
-
-**Maintenance syncs** - These syncs include a large amount of client-initiated syncs and they occur at predetermined intervals. They can be initiated by the client or service depending on the platform. The estimated check-in schedule for all platforms is about every 8 hours.
62
+
-**Maintenance syncs** - These syncs include a large number of client-initiated syncs and they occur at predetermined intervals. The client or service can initiate the sync, depending on the platform. The estimated check-in schedule for all platforms is about every 8 hours.
63
63
64
-
Independent of the client schedule, devices are only allowed 1 maintenance sync every 6.5 hours.
64
+
Independent of the client schedule, devices are only allowed one maintenance sync every 6.5 hours.
65
65
66
-
-**Newly enrolled devices** - When devices first enroll, syncs run more frequently to run configuration, compliance, and non-compliance checks. The check-ins are estimated at:
66
+
-**Newly enrolled devices** - When devices first enroll, syncs run more frequently to run configuration, compliance, and noncompliance checks. The check-ins are estimated at:
67
67
68
68
| Platform | Estimated refresh cycle|
69
69
| --- | --- |
70
70
| Android, AOSP | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours |
71
71
| iOS/iPadOS | Every 15 minutes for 1 hour, and then around every 8 hours |
72
72
| macOS | Every 15 minutes for 1 hour, and then around every 8 hours |
73
-
| Windows PCs enrolled as devices | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours |
73
+
| Windows | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours |
74
74
75
75
### Single device
76
76
77
-
These check-ins are driven by admins or end users when they run certain actions on a single device:
77
+
Admins or end users initiate these check-ins when they run certain actions on a single device:
78
78
79
79
-**End-users actions** - Includes actions made by users in the Company Portal website or app, like [checking the compliance status](../user-help/check-status-company-portal-website.md), syncing for policy or profile updates, or [installing apps](../user-help/manage-apps-cpweb.md#available-and-required-apps).
80
80
@@ -180,7 +180,7 @@ For more information on dynamic groups, go to:
180
180
181
181
On Windows devices, when trying to sync in the **Settings** app > **Accounts** > **Access work or school**, you might see a `The sync could not be initiated (0x80072f9a)` error.
182
182
183
-
If the Trusted Platform Module (TPM) was reset to factory settings, then the device must reenrolled to resume syncing. The device's Microsoft Entra identity is stored in the TPM. So, if the ID is removed, then reenrollment is the only way to reestablish the Microsoft Entra identity.
183
+
If the Trusted Platform Module (TPM) was reset to factory settings, then the device must reenroll to resume syncing. The device's Microsoft Entra identity is stored in the TPM. So, if the ID is removed, then reenrollment is the only way to reestablish the Microsoft Entra identity.
0 commit comments