1. For the GPO installations, you will not necessarily be able to bypass this with a generic GPO.
Reason being:
- When you deploy an MSI package via a GPO, a flag is set on the system telling the server to complete the install. The flag will not be removed until the install completes, Regardless if the application is already installed on the machine
Resolution:
- Create a "deployment GPO" for the machines you want to deploy to as opposed to the ones that already have the software installed. Don't put the package in the "everyone" GPO. This could be convenient to have kicking around for future as well. You place the computers into a group in AD called "deployment" for example. Deployment is the only group in your deployment GPO. Whenever a package needs to go out, you simply add the computers/ computer groups to the deployment group and assign your package in the GPO. When thats done, you simply remove the computers from the group. Almost ensures no overlap.
2. For the installs, on machines that are unmanaged, and you have already created a Package for them... The SEP installer has "quiet" options. I can't remember exactly what they are right now, but consider /? at the end or in the documentation.
I like, and this is me personally, an application called
Purgos for installing, live apps in the background from an EXE package or MSI package... Unfortunately, it is beyond the scope of this forum, but definitely worth looking into, as it is an Open Source app...
Hope that helps.