Option to change Windows Service-Account of Gateway Service
Hi!
It's not even about isolating permissions. The problem is, that I was not able to access the SMB share (non domain-joined NAS) from Windows Server 2025 without username/password. I was following various guides how it could work in theory but ultimately it only worked the classic way where you create identical username and password on both sides.
Kind Regards,
Stefan
Option to change Windows Service-Account of Gateway Service
Hi!
I can confirm that when just changing config the account does NOT change. So its only happening when updating as you mentioned!
The account is a regular local Windows account (server is not domain joined). This is required for SMB-Access to work because only with a windows account I can set username and password accordingly.
Kind Regards,
Stefan
Option to change Windows Service-Account of Gateway Service
Hi!
Regarding Installation on a Windows Server it would be good to have a supported option to define another gateway service account than NETWORK SERVICE.
For example - session recording to SMB-Share requires authentication. It is actually possible to access a share and use it for session recording when changing the gateway service account to one that has access to that share.
But there are caveats:
you need to manually adept NTFS permissions for the gateway folder within "Program Data" for the new service user
triggering gateway update from devolutions server/RDM fails (ERROR listener{port=7171}:https{client=xx.xx.x.xxx:61728}:request{method=POST path=/jet/update}: devolutions_gateway::http: error=500 Internal Server Error at devolutions-gateway\src\api\update.rs:68:9: failed to write the new `update.json` manifest on disk [source: Access is denied. (os error 5)]))
everytime you modify the gateway-configuration from the server console (companion tab), the service-account automatically changes back to NETWORK SERVICE
BR