Running PowerShell as the Logged-On User from SYSTEM Context

If you have ever deployed a PowerShell script through Intune, a RMM agent, or Task Scheduler running as SYSTEM, you have hit this wall at least once: the script works perfectly when you run it interactively, but returns nothing — or the wrong thing — when deployed at scale. The reason is almost always the same. The script is collecting user-specific data. And SYSTEM is not the user. The Problem: SYSTEM and the User Are Not the Same Session When Intune or your RMM agent executes a PowerShell script, it runs in the SYSTEM context. SYSTEM is a highly privileged account, but it is completely isolated from the interactive user session happening on the same machine at the same time.