Allow Windows Service feature to Grant user access to service on remote machine
To get around concerns for security, one option would be to have checkbox (default unchecked) that would be displayed when choosing Custom User that would say something along the lines of "Grant logon as a service rights if new user". Therefore it's still up to the user to decide whether it's needed or not.
David Keaveny commented
Happy new 2020, and where is this feature?!
George Tsiokos commented
This pre-deployment script solves the problem:
Mark Lamprecht commented
Powershell is all fine and well as a temporary workaround but it quickly becomes a pain in the proverbial when we've got 10's of projects to administer, so the question is: when will this be implemented? :-)
Douglas Spooner commented
Is this implemented yet?
David White commented
+1 Is this implemented yet?
+1 The ideal solution (group policy) takes months in some places :).
Any timeline on when this will be implemented? It is currently very difficult to deploy Windows Services to multiple machines, when you have to manually grant permissions to the user on each machine (think about doing that for 20 servers, it is a pain).
Sure, Group Policy comes to mind, but then we have to involve the IT Infrastructure guys and we just loose one of the most value-add reasons to have Octopus in the first place - which is to be more independent