Config db ntf: 20120806213000
Analyze db ntf: 20120806213000
Windows Version: 3.0.0 :: MAC OS X Version: 2.0.36 :: Linux Version: 2.0.38
Eclipse Plugin: 1.0.0


Major Improvements: NEW ECLIPSE MANAGEMENT MODULE to manage/query Eclipse settings, install/uninstall plugins, and configure Sametime communities, Fixed a bug for workspace page deletion on unstacked desktops, MassChanges can now also change location documents, References now support default values, Added a new "background" runtype, New feature to not execute onetime actions again when resaving them


General Notes

Supported IBM Lotus Notes releases: 5.x, 6.x, 7.x, 8.x, up to 8.5.3 (Administrators need at least IBM Lotus Notes 7.x on Windows or Linux)
Supported client-side operating systems: Microsoft Windows NT4 (>=SP2), 2000, XP, 2003, 2008, Vista, 7, and Citrix/WTS, Apple Intel Mac OS X Leopard & Lion, Linux
Supported server-side operating systems: any supported by IBM (operating system independent)
NOTE: Support is limited for platform and release combinations not supported by IBM
Linux & Mac OS X: Skinning, Realtime, Zip/Unzip and Attachment Blocking are not available on Linux or Mac OS X;
Citrix, Linux & Mac OS X: the MarvelClient Upgrade module is only available on Windows (=not on Citrix, Linux or Mac OS X)
MarvelClient on Mac OS X and Linux does not support the runtypes "After Login - Before Sync", "After Login - After Write" and "On first server access" - any such actions must be set to run at a different supported runtype, e.g. "After Login"
IMPORTANT NOTESThis release contains select important updates highlighted in red

Configuration Database

CHANGEChanged the order of main navigation entries in the left hand navigator; General\* no comes after MarvelClient\* and before Zip/Unzip and Attachment Blocking
CHANGE / ENHANCEMENT

The When tab has been changed and enhanced as follows:


1.) instead of selecting persistent and then "once a day" or "at every client start", the options are now consolidated into one field.
2.) except for the "Repeat?-Option" "persistent, you can now choose whether you wish to "Keep local exec. info" - if checked, an action will NOT be re-executed again when resaving the corresponding action.
NOTE that when testing ONE TIME actions, many customers rely on the action to re-execute when resaving an action; if you wish to use the "resave=re-execute" feature you must UNCHECK the "keep local exec. info" box!

ENHANCEMENTAdded a new option to masschanges to also process location documents for mailserver and/or mailfile(path) changes (requires DLL >= 2.6.1)
ENHANCEMENTAdded new options to specifiy different Zip/Unzip and Attachment Blocking settings for different databases (based on e.g. template name (pattern) and/or filepaths (patterns)) - the corresponding DLL is currently being beta-tested at selected customer sites and will be released soon.
ENHANCEMENTAdded new runtypes to various actions (run agent, run program, ini management, eclipse actions, ...)
ENHANCEMENTAdded a new Eclipse Management Menu with options to change/remove Eclipse settings, query Eclipse settings, install/uninstall plugins/widgets, and manage Sametime Communities
NOTE: this requires a valid Eclipse Configuration license

Analyze Database

ENHANCEMENT

The HW/SW inventory (Windows only) agent has been enhanced as follows:

1.) if MC_AddonColGetProductInfo is set, the HW/SW inventory agent will now also obtain all uninstall information from the Windows registry - this is then available from the following view:

The uninstall list contains a complete listing of all uninstall entries for the "all" and "current" user registry parts (for both 32 and 64 bit environments where applicable); for customers where the products inventory did not work due to WMI issues, the new uninstall list also contains product code details for possible uninstall of software: In the following example, the product code is {23170F69-40C1-2702-0920-000001000000}


2.) it now also determines the computer identifying number, serial number and asset tag; if run, the information will display on the OS / HW tab of each user's profile:


NOTE that in the Run Agent action running the HW / SW inventory you must click on "check for update" after updating the design of ýour config database so as to deploy the code changes to your MC clients.
Also note that the HW / SW inventory agent will determine manufacturer, model and version even if neither MC_AddonColGetHWDetails, nor MC_AddonColGetLogicalDriveInfo, nor MC_AddonColGetProductInfo are set;
the agent will determine these details every time it runs, even if it has nothing to do.

MarvelClient Upgrade

- No changes -- No changes -

.DLL Updates (Windows)

NOTEThe documentation for DLL 2.5.17 suggested that KeyFileName must be specified for MC_SupportIDVault to work; this is incorrect, if not specified it defaults to "user.id".
FIX (2.9.4)Fixed a problem where MarvelClient would download agents (associated to a run agent actions) during afterlogin even if the afterlogin view reader was disabled
FIX (2.9.4)Fixed a bug where deleting a workspace page would result in an infinite loop on unstacked desktops
FIX / CHANGE (2.9.4)Relocator now canonicalizes flat names before checking its rulesets against the database url to be opened.
CHANGE (2.6.2)The Extended XML Export actions now also work with just MC Analyze licenses (for both keyfile details and local databases export)
CHANGE (2.6.2)Log output now reads "network directory is set to" instead of "found network directory"
CHANGE (2.9.4)The on first server access trigger server now defaults to ini:MailServer if not specified (in previous releases it defaulted to mc:configdb_server;
if ini;MailServer is not specified, the trigger server will fallback to mc:configdb_server
ENHANCEMENT (2.6.1)Mass changes can now also change location document along for server- and/or mailfile(path)-changes
ENHANCEMENT (2.6.1)By setting MC_LogToConsole=1 in notes.ini, MarvelClient will merge it's own log with IBM's console.log in the IBM_TECHNICAL_SUPPORT folder - this allows for easy (to read) client_clocking and reading of the console.log
ENHANCEMENT (2.6.2)The current local date/time is now also written to the beginning of log.xml:

format is [now: local time == UTC time]
ENHANCEMENT (2.6.2)MC now also logs the OS thread ID into log.xml
ENHANCEMENT (2.6.2)Setting
MC_SupportIDVault_Prompt=1
in notes.ini will prompt end users for a user name if not specified in conjunction with MC_SupportIDVault=1
ENHANCEMENT (2.9.4)Optimized disk access especially with regards to reading/writing actions.xml and mc_localstore; on rather slow machines this should be noticeable
ENHANCEMENT (2.9.4)Added new syntax for references: <^xxx:yyy$> will automatically escape the result as a regular expression
ENHANCEMENT (2.9.4)Added new syntax for references: <xxx:yyy=zzz> will use zzz as default if namespace or variable could not be found.
For ini: and env: it will use the default if the variable is missing (instead of setting it to "")
ENHANCEMENT (3.0)Added support for new action to set Eclipse Configuration Settings
NOTE: this requires a valid Eclipse Configuration license
ENHANCEMENT (3.0)Added support for new action to get/query Eclipse Configuration Settings
NOTE: this requires a valid Eclipse Configuration license
ENHANCEMENT (3.0)Added support for new action to configure Sametime Communities
NOTE: this requires a valid Sametime Configuration license
ENHANCEMENT (3.0)Added support for new action to install/uninstall plugins/widgets
NOTE: this requires a valid Eclipse Deployment/Undeployment license
ENHANCEMENT (3.0)Added a new runtype "background - init" for several actions to execute actions immediately after client startup (actually at the end of afterlogin, but without further blocking the client from starting) without waiting for a first server access; this is especially used for above mentioned new eclipse actions, but also available for ini management and the run agent action.
ENHANCEMENT (3.0)Added a new runtype "background" for the following actions:
1.) Run Agent
2.) Run Program
3.) ini Management
4.) Eclipse Config Set
5.) Eclipse Install/Uninstall

By default, this new runtype runs every 60 minutes after client startup. This allows to e.g. change notes.ini settings or run agents or programs or deploy/undeploy plugins whilst clients are up and running "within the next hour" (or whatever the background interval is set to).

To change the default interval, set
mc:bg_thread_interval=number of milli(!)seconds; the default being mc:bg_thread_interval=3600000

The first background run interval can be changed by setting
mc:bg_thread_firstinterval=number of milli(!)seconds; if not set, mc:bg_thread_firstinterval defaults to mc:bg_thread_interval (see above).

NOTE that the new runtype "background - init" runs immediately after "afterlogin" (but without further blocking the client), so you might want to use "background - init" instead if changing mc:bg_thread_firstinterval
ENHANCEMENT (3.0)Added a new config variable <notes:cache_path>
ENHANCEMENT (3.0)Actions now support a new flag <keep_info>; if set to true in an actions.xml (see config database updates above), an updated onetime action will not be executed again for users where the action has already been executed prior to the update/resave.

.dylib Updates (Mac OS X)

- No changes -- No changes -

.so Updates (Linux)

- No changes -- No changes -