Why Intune PowerShell Scripts are Not Executed Immediately
You deploy a PowerShell script in Intune and expect it to run immediately. That assumption makes sense, but that is not really how it works.
Hours later, it suddenly executes the moment the user signs in. The Funny thing? That is not random. It is by design.
In this blog, we will break down what actually triggers the Intune Management Extension, where the eight-hour interval really comes from, and why pressing Sync will never wake the PowerShell workload. If you think script execution is push-driven, this will change that.
https://t.co/hAKd25UaQF
#Intune #MSIntune #Windows #Windows11
⚠️ Heads up! The "Run script as 32-bit process on 64-bit clients" toggle doesn't seem to have any effect when using the PowerShell script installer for Win32 apps in Microsoft Intune. Scripts always run as a 32-bit process.
I added some logging to confirm:
• [Environment]::Is64BitProcess consistently reports False
• [Environment]::Is64BitOperatingSystem reports True
• Result: "Process: 32-bit, OS: 64-bit" with the toggle both on and off
The practical impact is that any HKLM:\SOFTWARE writes silently land in HKLM:\SOFTWARE\WOW6432Node due to WOW64 registry redirection.
Has anyone else noticed this?
#msintune #intune #microsoft #powershell