When using SCCM powershell script detection for an application deployment type - is it possible to encypt the script/obscure such that it is unreadable to SCCM console users?
I'm trying to solve a problem caused by too many SCCM console users, who can see application detection rules/values, who then hack their workstations to avoid mandatory deployments.