Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Old Version 1

changes.mady.by.user panagenda Expert

Saved on

compared with

New Version 2

changes.mady.by.user panagenda Expert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
This component release is part of MarvelClient 14.0

Config DB - General

CHANGE / ENHANCEMENT

The Eclipse Sidebar action now has three options for the initial state of the sidebar: Open, Thin, and Closed.

Previously there were only two options (Open and Closed), and the old "Closed" option now maps to the new "Thin" option to match the naming convention used by the Notes client.

FIXFixed an error in the MultiTenant Action: MARVELCLIENTACTIONDISTRIBUTION.LOADDEPENDENCIES 13 in Line 804: Type mismatch

Config DB - MC Upgrade UI

NEW

Added a new feature to "predict" machine candidates for one or multiple upgrade configurations.

Prerequisites:

  • Upload documents in the Analyze database from as many users as possible
  • Automailer needs to be configured and enabled. This feature synchronizes information from the public addressbook and the analyze database, to e.g., carry over last used machine, platforms and release details from person documents, and identify users who have not yet uploaded into the analyze database. The sending of install mails can be disabled (aka set to requiring approval).
  • A full license of SecurityInsider to resolve group members used via Who tab restrictions and excludes

New view actions in the MarvelClient Upgrade\Configuration(s)  view allow to then "predict" upgrade candidates:

Image Added


When run, the functionality does the following:

  • If applicable (=if access definitions or direct restrict and/or exclude settings are specified on the Who tab), builds a list of all users who are supposed to receive an upgrade. This requires a full license of panagenda SecurityInsider (SI). The path to the SI database is specified under Advanced\SecurityInsider Sync - for the upgrade prediction functionality, actual synching is not required (neither manual, nor in background).
  • Next, all automailer documents are investigated in the Analyze database. The path to the Analyze database is specified in Online Update configuration. In case multiple analyze paths are specified therein, the first one is used. From the automailer documents, a list of all machine names is built from for which usernames match the readers identified in the previous step and where information was updated in the last 90 days in the public address book.
  • Next, the list of machine names is extended with all upload documents from the last 90 days for which readers match.
  • All machine names are then checked for whether they match the conditions specified on the Conditions tab of the upgrade configration - e.g., does bitness match, client type, disk space, memory etc.
  • If "Print Info" was selected, the number of resulting machines is printed to the status bar.
  • If "Create Candidate Documents" was selected, Upgrade Candidate documents are created in the Analyze database under MarvelClient Upgrade\Upgrades by Result. This allows customers to predict which machines are most likely to receive an upgrade and thereby track how many users (or more so machines) have not yet/already performed an upgrade.
CHANGEWhen publishing a static configuration, the MCUpgrade Config Wizard now treats the old client folders as optional (previously, they were mandatory). The long built-in auto-detection of a pre-installed client will automatically fill in the folders at the beginning of an upgrade/installation.
FIXFixed an issue where VersionInfo was not extracted from the installer for 14.0FP2 due to it including an additional msi file
FIXMCUpgrade Config Wizard: Fixed an issue where validation of latest and archive folder always wrongly prompted that the archive folder must not be the same or underneath the latest folder, even if both were different
FIXAdded support for the version >= 14 install parameters PROGDIRW64 and DATADIRW64, which are required when deviating from best practice installations AND when upgrading a client from 32bit to 64bit (but not when upgrading a 64bit client). In case (DATADIR and DATADIRW64) or (PROGDIR and PROGDIRW64) are specified, the non-W64 settings win with regards to the MCUpgrade Configuration. Note: Different folders for (DATADIR and DATADIRW64) and (PROGDIR and PROGDIRW64) are neither supported nor advisable. For further details see HCL technote KB0114991: Upgrading Notes client, program directory and data directory path get changed or moved.
FIXFixed an issue where the publishing settings were hidden in read mode