Run as local system in interactive mode?

Comments

2 comments

  • Ryan Joachim

    Someone can correct me if needed, but I'm fairly certain that while in the past you used to be able to force an interactive session as "system", that isn't the case anymore (past Windows 7 and Server 2008) due to changes in how sessions are handled. PDQ's Local System run-as option is non-interactive by default, which follows native restrictions in Windows.

    You could use something like PSTools from Sysinternals to do it (psexec -i -s cmd.exe), but you'd have to build your scripts around it and even then I'm not sure if it still works in the Windows 10 world.

    I'd be interested in hearing what you end up finding that works for you.

    1
    Comment actions Permalink
  • Chris

    Thanks for your suggestion.

    I use a function in my PowerShell scripts "Get-LoggedOnUser" if session 0 is not detected. So the package runs in Deploy User (Interactive)-Mode.
    The function gives me the first active logged on user account.

    Now I can do some work in LoggedOn User context:

    I haven´t found another solution yet, but this works without the need of implementing other things like sysinternals etc. in my scripts.

    1
    Comment actions Permalink

Please sign in to leave a comment.