
kiev971.5524939900321443E12 asked a question.
msi properties and AD GPO deployment
Hello guys/girls. I have a question. We have a few Msi's that when deployed via GPO do not require to run the mini setup when run for the first time, other msi's have to go through the mini setup first and only then the applications open. Is it an option that can be set in my Basic msi project?
Another question is just cosmetic, is it possible to change the color of the progress bar during the install?
Thanks
Thank you for your question regarding GPOs and setups. You can use InstallShield Tuner to determine if your application is published or assigned, but you may also use the Group Policy Editor to make changes to the GPO directly.
Regarding the progress bar, I found a couple of items that might get you started. From the InstallShield knowledge base, article Q105794 discusses using a custom DLL or VB Script to do the job. I also found this link:
http://www.installshield.com/downloads/isd/tm/ISDevCh7.pdf
Hope this helps.
If you are publishing the msi to the users and the application self-heals, this may be a sign of a broken component somewhere in the msi package.
In either cases, look in the application log in the event viewer for error logs. They will give you a detailed description of the components that were missing during run-time.
Thanks for your help guys.
Thank you for being very helpful and patient :)
Search for that component code in your table editor to find the component that is self-healing. That will give you a better idea of what your application is doing.
1. application is assigned to the workstation
2. log in as a regular user and you get the self-healing process
3. the application launches and everything functions
4. check the application log in the event viewer and there are no warnings or errors indicating the self-healing process
5. log off the workstation and then log back on as the same user
6. application self-heals again?
1. Application is assigned to the OU in AD
2. Computer joins the OU.
3. Application gets loaded.
4. I login as Administrator and run the app.
5. Application goes through the "self-healing" and opens up.
6. I log off and log back on as Administrator.
7. Run the app, it opens right up, no self-healing.
8. Check Event viewer, Application Log, nothing but
Installation operation completed successfully.
What application are we talking about here?