



Pros and cons: first option gives the user too much power, but he may install whatever he needs to second option gives no power to the user, but you'll have to do extra work to publish any software he needs. You can use a GPO to "Publish software": opposed to "Assign software", which will force an installation of a given software to the computers affected by that GPO, "Publish software" will allow any user logged on a computer affected by the GPO to install the software you've, well, published in that GPO: But the good news is you can do that with a GPO, using Restricted groups: install, upgrade, and run client applications without administrator privileges. You've to be local administrator to install software, there's no "Installing software delegation". For Windows endpoints you run the Pulse Client installation program by.
