Thanks for doing this.
We use the Admin install extensively in the Enterprise environment where the users do not know the values for the properties needed to install the application - but the admin does. For example, the name of the database, the server it's installed on, the db platform (Oracle, MSSQL,..), what modules they are licensed for any many other settings to properly setup the app. In this scenario, the "Admin" run msiexec /a and answers all the questions needed for their environment. When the admin clicks "Finish", another MSI is generated and placed on a shared folder for all users to run with only a progress bar showing.
What is the timeframe for the next release?
We use the Admin install extensively in the Enterprise environment where the users do not know the values for the properties needed to install the application - but the admin does. For example, the name of the database, the server it's installed on, the db platform (Oracle, MSSQL,..), what modules they are licensed for any many other settings to properly setup the app. In this scenario, the "Admin" run msiexec /a and answers all the questions needed for their environment. When the admin clicks "Finish", another MSI is generated and placed on a shared folder for all users to run with only a progress bar showing.
What is the timeframe for the next release?