Best Way to Deploy EXE Packages via Group Policy
-
I want to deploy an EXE package via Group Policy, but obviously GP wants an MSI file. That doesn't appear to be an option in this case, at least not at this time, so looking to do something else. I'm guessing that a startup script might be the place to do this? The EXE in question (It's Veeam Endpoint Protection) has a silent installer flag so that isn't a problem. Is this the right approach? Is there something better?
How would you guys handle this and approach it?
-
Have you opened the EXE with 7-Zip? Generally there will be an MSI inside of it.
-
PDQ Deploy would be my preferred method.
-
If the EXE has a silent installer flag I would run it as a startup or login task the first time. Just add a check in there to see if it has already been installed.
-
@coliver said in Best Way to Deploy EXE Packages via Group Policy:
Have you opened the EXE with 7-Zip? Generally there will be an MSI inside of it.
There is, but it's not installable.
-
@Romo said in Best Way to Deploy EXE Packages via Group Policy:
PDQ Deploy would be my preferred method.
I'm aware that that can do it and I'll look into that as well. Specifically trying to get GP working in this case, though. At least first.
-
@coliver said in Best Way to Deploy EXE Packages via Group Policy:
If the EXE has a silent installer flag I would run it as a startup or login task the first time. Just add a check in there to see if it has already been installed.
Meant to say I would put it on a share and have a startup script execute it with the silent flag. Drop a installcomplete.txt file somewhere on the local disk and query for that at startup.
-
@coliver said in Best Way to Deploy EXE Packages via Group Policy:
@coliver said in Best Way to Deploy EXE Packages via Group Policy:
If the EXE has a silent installer flag I would run it as a startup or login task the first time. Just add a check in there to see if it has already been installed.
Meant to say I would put it on a share and have a startup script execute it with the silent flag. Drop a installcomplete.txt file somewhere on the local disk and query for that at startup.
Cool, that's the direction that I was headed.
