HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
I guess you mean the HCL Notes 12.0 Multilingual User Interface - Installer.
Can that package be installed silently with different MSI parameters per sub package?
I think this is exactly what the customers need!
Currently it's only a compressed .exe file with a very simple .vbs file inside, which opens one installer after the other and only in UI mode (see screenshot). This cannot be used silently with a software deployment system, like SCCM, LanDesk, MarvelClient Upgrade, etc.
The question is, which customer installs the Notes client in foreground and manually?
This was shipped in Notes 12.0 - where we have provided one package that contains all the languages in one installer.
Also add the option to add all dictionaries in one package ! I´ts a mess for admin to repack permanently the clients to get all deployed ! We need a real multi language client !
This should be the default.
Toni Feric, Belsoft Collaboration
We need this!
Although it is already possible today to combine all kinds of languages with the existing separate MUI installers into one single installation package, I support the idea.
My experience with various customers is that there is the need for an easy/easier to deploy/install package.
Including all languages in one single installation package will help most customers to achieve this.
A > 1 GB size installation package is not uncommon nowadays, and with contemporary techniques like pre install caching and peer to peer deployment, the size of an installation packages is only a problem in very distinct use cases.
Makes a lot of sense!
Maybe have one pack for English only with all the dictornaries and than ship all other languages as one pack!
And allow admins to decide which langauges to add.
There is much more effort to have separate kits.
And on the other side for us to find the right kit to install!
[ Daniel Nashed / http://blog.nashcom.de ]
And at the installation stage to be able to select the desired languages.