Hi Mathieu,
Yes, you can build an MSI with a beautiful GUI and UX that can also be deployed through Active Directory/GPO.
To make sure your MSI can be deployed successfully through GPO you must follow these rules:
- Do not include in the Wizard Dialogs Stage custom actions that change the system. Changing the system should be done only by deferred custom actions from Install Execution Stage.
- If your MSI contains custom dialogs for capturing input, like a license key for example, document this nicely with examples on your website, so that admins can find out how to deploy it. It will save you lots of time on customer support calls.
- Do not ask for unique user information during installation, eg. user account password or customer ID. This information should be requested upon launching the application, after it was installed. This is because admins deploy the packages over the network with a command line that must work on all machines, so if you are asking for a password, which is unique for every user, you are practically not allowing the admins to automatically deploy your application in their intranet.
- It is recommended to have the package install per-machine. This makes tracking/audit easier for the admins and also eases their jobs on deploying upgrades.
The following article I wrote about
enterprise deployment for Windows applications contains more details. You should also take a closer look at the last section, about user data, I've seen a lot of applications incorrectly designed in this part.
Regarding what you can do in the GUI, basically anything that Advanced Installer allows you to, as long as you don't cross one of the above recommendations or try to add a custom dialog control
which requires you to activate our support for
Enhanced User Interface from Themes page. This(
the latter) means you will get a bootstrapper EXE, that bundles your MSI, to obtain the nicer GUI and you don't want that.
Of course, you need to have at least an Enterprise project, respectively license, to get access to our Dialogs Editor, for full editor capabilities(drag and drop controls, custom texts, trigger events, etc...).
When you will double click your MSI it will run by default with full UI (do not enable the option "Limit to basic UI"). When admins want to deploy it they will specify this command line in their consoles:
This will make the MSI run with silent UI, which is what they need. In that command line they can
append additional parameters to customize the installation, depending on what you allow them to do. i.e. a custom install path, enter a serial number (that can be used on all machines), etc...
Regards,
Bogdan
FOLLOW US
Get the latest news in Application Packaging