Is there any reason that a trial of Enterprise features would cause an MSI that is set to run in a GPO to not run correctly? Running the .MSI manually generates the desired feature (running msiexec /x "\\server\software.Msi" /norestart /passive) but pushing it out via GPO triggers some delay in startup but doesn't result in any uninstallation.
This happens because a package created with an unlicensed version of Advanced Installer shows a message during install. To test a package with GPO you can try using a "Simple" project. It's free, so it won't show any trial messages.
Can I make the Simple trial proceed to a Custom Action and run the .EXE that just got installed from a GPO? This is what I'd like to test... I haven't had any luck getting this to work any other way I've tried.
Update- I've purchased the Professional version (I noticed the 30 day money back guarantee!) and I'm still having no luck.
I've created a Custom Action to run the installed .EXE when installed via GPO Assignment to the machine. I can get the .EXE to install after a GPUPDATE /FORCE, but it seems to never run the .EXE unless one starts it manually. Any help would be greatly appreciated.
Perhaps setting the exe custom action to run asynchronously, without waiting for a return code would solve the issue. Also, you should set it to run after InstallFinalize standard action. This is at the very end of the install.
If you still can not get this to work, please send your .aip project file to support at advancedinstaller dot com so we can take a look.
FOLLOW US
Get the latest news in Application Packaging