Event banner
Windows Office Hours: September 19, 2024
Event Ended
Thursday, Sep 19, 2024, 08:00 AM PDTEvent details
Get answers to your questions about adopting Windows 11 and managing the Windows devices used by remote, onsite, and hybrid workers across your organization. Get tips on keeping devices up to date ef...
Heather_Poulsen
Updated Nov 19, 2024
VNJoe
Sep 19, 2024Iron Contributor
Are there plans to improve the times for Intune? 24 hour cycles aren't nearly enough for business standards, and recently, there have been more issues with extended install times. Will you be bolstering the infrastructure to support more efficient endpoint processing?
- Paul_WoodwardSep 19, 2024Iron Contributoroofhours.com has an article about triggering some Intune tasks - IIRC it was 'device sync' - they are actually just tasks in the task scheduler. After the initial hour after boot, the Intune client gets a lot less chatty with the backend service, so some changes to policy etc might take longer to be picked up. You might find out a way to get whatever it is done a bit faster, take a look.
- EricMoeSep 19, 2024
Microsoft
The policy refresh intervals are defined here, https://learn.microsoft.com/en-us/mem/intune/configuration/device-profile-troubleshoot, all of which are shorter than 24 hours. Is there a particular 24-hour cycle that you are experiencing that you want to call out?- VNJoeSep 19, 2024Iron ContributorI'd say that if there were a mechanism that resets the check-in cycling, that'd help. 8 hours generally means one change per operator shift, and they're hard pressed to modify it if it's not a correct policy. It's mostly in regards to troubleshooting where it becomes cumbersome. Additionally, Autopilot installs have become extremely slow and/or drawn out where it's starting to take days to install the same software that usually was deployed within hours. Just some recent observations
- Jason_SandysSep 19, 2024
Microsoft
Hi Joe, Keep in mind that the 8 hour polling interval/cycle is mainly a "catch-up" for devices that were not online at the time a policy change was made or where the policy change hasn't made it to the device for whatever reason. All policy changes are sent to devices at the time they are made. Because of the scale of the service though, this is subject to some limiting and throttling (some of which is outside the control of Intune). If a policy change is targeted at a small number of devices, those changes should happen in more or less real-time. Arguably, if a change impacts a large number of devices, you wouldn't want that to instantly impact those devices anyway.