In Windows, how does a per-user install happen for users who lack install privileges?

user_3112829 0
Viewed 3167

My users typically work on locked-down workstations. They lack administrator privileges and cannot install software for themselves. In the past, I've designed my applications to be installed per-machine, not per-user. An administrator installs my application on a workstation, and everyone using that workstation can then use the application.

Now I'm considering switching to a per-user install, but I don't know how that would work in my user environment. Is there a way for an administrator to say "Use my privileges to install this application not for me, but for user X?" Does the administrator have to do one user install at a time, or is there a way to do a batch of installs all at once? In a nutshell, am I making things easier, harder, or impossible for the IT staff? Does any of this depend on my installer? (I'm using Windows Installer.)

installation windows-installer windows
2 Answers

Per user installs was a mistake. It should be an option, not the default as we see more and more malicious apps and unwanted apps under user directories. This is not the way cybersecurity works by putting applications in the hands of untrained and cyber rejected users. Users want easy and cybersecurity is neither easy or agile. Simple put, DevSecOps is how security works and agile does not say anything about security. In fact, the IBM/Ponemon Cost of a Data Breach continue to state that DevSecOps is a breach mitigator and those practicing it have a much less chance of being breached.

Further, agile signatory and one of the original agile authors Robert C. Martin states in his new book

"Agile is a set of principles, practices, and disciplines that help small teams build small software projects.

Agile is a small idea about the small problem of small programming teams doing small things. Agile is not a big idea about the big problem of big programming teams doing big things."

user_199619310
Related