Rudy Ooms(@Mister_MDM):Intune Device Sync Just Changed Again. This Time, It Is IC3!!!! First, the Device Sync moved away from triggering Windows MDM only and started waking IME workloads too: Win32 apps. PowerShell scripts. Proactive Remediations. Now, when triggering the remote Device Sync, the IME request no longer arrives through a second WNS notification. It comes through the existing IC3 and Trouter connection: WNS for Windows MDM. IC3 for IME. At the same time, a new StatusSync flow is tracking the progress of those workloads. That part deserves its own blog. https://t.co/zUr9ffQfYE #MSIntune #Intune #Windows

2026.08.01 15:43

Intune Device Sync Just Changed Again. This Time, It Is IC3!!!! First, the Device Sync moved away from triggering Windows MDM only and started waking IME workloads too: Win32 apps. PowerShell scripts. Proactive Remediations. Now, when triggering the remote Device Sync, the IME request no longer arrives through a second WNS notification. It comes through the existing IC3 and Trouter connection: WNS for Windows MDM. IC3 for IME. At the same time, a new StatusSync flow is tracking the progress of those workloads. That part deserves its own blog. #MSIntune# #Intune# #Windows#

显示更多