Thanks for the suggestion. Indeed it’s something that we have considered, but there are some significant concerns that it raises with regard to permissions and security, so I don’t know if it’s something that we will implement in the future or not. There likely isn’t a “safe” way to do it, as the executing user will still ultimately have local admin permission on all target computers.
From my perspective, I don’t mind that the executing user will have local admin permission on all target computers.
What I don’t want is for them to mess up or change any of my deployments, queues, and settings on BatchPatch. Or create new ones for that matter…
Basically, I would want them to have read-only access to the BatchPatch application.