Thanks for recommend the CTA channel. I'll go to that next time. @Yan Wang thank you for your time, my request is to allow actions to be ran as system account. As we start to lock things down for users in images more and more in today's security standards, it can impact WEM actions or anything that runs in a users context for that matter. Security Complaince such as STIGS, CIS for example. It was brought to my anntetion that competitor UEM tool does this and I was asked why WEM can't. I can't answer this, other than explaining that the WEM continues to make great enhancements and as time goes on newer features are released. So I was curious about see if this is an option in the near future. The idea is to have options to run actions or really anything that applies to a user from a system side instead from a user side, allowing WEM to still do what it can do but not being blocked. Examples of many hardening parts I am requested to do are blocking cmd, regedit,preventing UNC access(locking the image down for example) impacts WEM from doing things. I don't see a way to do this now, and if there is please forgive my ignorance.