Loading
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

  • Dynamox,

     

    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.
    Expand Post
  • By "mini setup" I assume that you meant Self-Healing. If you are assigning an msi and it requires current user settings to function, the package will self-heal when run the first time by the user.

     

    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.
    Expand Post
  • Thank you for your input guys. We assign our applications. For example let's take Office 2000. I use data1.msi , which is the original msi from Microsoft. I create a GPO, select this msi and select assign. My computer joins active directory, the applications gets loaded. I login as Administrator and run ..let's say Microsoft Word, windows installer windows appears and runs for about 15-20 seconds, then Word opens up. After then if i click on Excel or PowerPoint they open up right away. Another application from Cognos Impormtu, when assigned and deploy the same way, does not go through this mini setup/self healing process. It jsut opens.

     

    Thanks for your help guys.
    Expand Post
  • That is correct, Office does require certain user settings and they get loaded by virtue of the installer service recognizing that the key path or key file is missing from a component. That component being part of the user profile (registry/directory). If you look in the application log, you will find warnings or errors under the msiinstaller source.
  • Thank you for this info nicholas_ong. My application does not install any user profile related settings/registry entries. Am i understanding you correctly that each component in my msi should have at least one key file? If i run my msi after AD GPO install and look in the even view i should see the error message about the component that was missing key path, so i would basically set a key in that component?

     

    Thank you for being very helpful and patient :)
    Expand Post
  • Generally, each component contains a key file or key path(registry). If a self-healing were to occur, the event viewer will show the component that is missing from the feature you are trying to invoke.

     

    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.
    Expand Post
  • I've tried deploying the msi and then checking the Event View for the error about components missing, but strangly enough i only saw one message that read something like this Product: -- Installation operation completed successfully. Installation went through the mini-setup, so i expected to see some error about components missing. Very strange, any ideas?
  • so this is what you're saying:

     

    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?
    Expand Post
  • Hey Nicholas. You are correct

     

    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.
    Expand Post
  • Ok there's got to be something we're missing here. Does the self-healing initiate only when the application is launched through the shortcut? Have you tried drilling down to the executable?

     

    What application are we talking about here?
10 of 17

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


Loading
msi properties and AD GPO deployment