You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should use different principals for the scheduled task and running the game.
The scheduled task needs write access over steamcmd for autoupdate and allow login as batch job.
This could run under the current user's principal unless another account is specified (it should not be LocalService).
It also needs:
Read access to the server configuration file, pid files, and the STEAM_USERNAME environment variable
Write access to workshop content, master, config and transcript logs
The game should run as LocalService with as few privileges as possible. It needs:
Read access to workshop content, master, config
Write acess to pid files and profile directory
As a consequence, pid fils should not go in the config directory, and transcripts should not go in the profile path.
Usage of
Register-ArmaServerTask
with-UserId xxx
is not working.For details, see: https://stackoverflow.com/a/70793765/6092856
The text was updated successfully, but these errors were encountered: