The default list of Old Notes Data excludes now also includes the following two entries when creating new upgrade configurations:

network:workspace\logs*
network:(IBM|HCL)_TECHNICAL_SUPPORT*

Note that this does not affect existing upgrade configurations.

The Mail Template Replace Design feature can now accept multiple target configurations for the same template.

There is also a new option: "Restrict to major Notes version"

If the Cleanup agent encounters the error "Error in CLEANUP_NOTESRENAMES in line 37: Object variable not set - Function aborted" it now continues processing the next document instead of stopping

Changed the "Roam latest backup" example actions so they default to a runtime of Before Login instead of BL Init.

Also changed the title of the "Set mc:DXL Export/Import Roaming" example action to suggest that the DXLRawImport agent should use a runtime of "After Write".

The Roaming Cleanup action now supports a runtype of Background Init.

The "ROAMING: Exclude ini-Entries Directory, SharedDataDirectory and more" example INI Filter action now also excludes the following entries: EXTMGR_ADDINS, AddinMenus, and NSF_HOOKS

Several changes to allow various pieces of code to work properly with the 64-bit 12.0.2 FP2 client, including:

• Online Update using the LotusScript connect option
• Reading the clipboard (Application/Mailfile action, Profile document action)
• Getting the list of servers (Agent action, Recent Apps action)
• Reading the low-resolution database icon (Application/Mailfile action)

Note that these things worked properly on previous 64-bit clients, but changes were required with 12.0.2 FP2. These will also be needed for Notes 14.

Release notes URL generation code has been updated to properly detect templates tagged as Notes 14.

Fixed a problem where Online Update using a Java connection option and proxy server settings would fail on Notes 14.

Fixed a problem where the GetLicenseInfo.xml file generated by Online Update is sometimes empty after a failed connection, and cannot be deleted or modified until the Notes client restarts.

Fixed a problem on the Application/Mailfile action form where the validation display shows the wrong text if 'Variable' is selected as a Local Replica option and the 'Variable' field is empty.

In the MarvelClient Upgrade Configuration Wizard, previous versions allowed you to disable "Install Service" in combination with "Use Service exclusively" - which makes no sense, since the service cannot be used unless it's already installed.

Now, "Install service" can no longer be disabled if "use service exclusively" is selected.

To avoid potential client crashes, the Compact Templates option can no longer be enabled when selecting a full client package >= 12.0.2

Fixed a class conflict error for the "Image" class in the Windows 64-bit client

Fixed an issue where after clicking on "Launch KeyfileEditor" and closing the KeyfileEditor, Notes would run into a "subscript out of range" error in the latest template. 

Automailer now allows the use of non-email Notes accounts.

Previously it excluded any person documents where MailSystem was different from "1" (Notes), or MailServer or MailFile were empty. These can now be optionally included. If this option is enabled (default is disabled), and Automailer is processed on each mail server, a new field is displayed to choose on which mail server to include the non-email accounts.

Fixed a problem where the HW/SW Inventory agent would be missing data if Online Update had been performed using a 32-bit client, but the agent was run on a 64-bit client (or vice versa)

Changed the text on the Mailbased Installer form to say "Windows/Notes 64 Bit" instead of "Windows 64 Bit" to better indicate that this refers to a 64-bit Notes client, not a 64-bit version of Windows

MarvelClient now offers two ways to automate replacing the design of a user’s mail database if the mail template version is not up to date:

1. With MarvelClient Upgrade you can initiate replacing the design of the user’s mail database immediately after a Notes client is upgraded, using the "success" email generated by the upgrade process.
2. Based on user data (Notes version and current mail template name) in the MarvelClient Analyze database, you can replace the design of a user’s mail database using a scheduled agent.

This can be useful for updating a user's mail template to the latest version after the Notes client is upgraded to a new client version. It can also be used to deploy a customized mail template to specific users.

The Users by State & Upload Key view now has a "(64)" suffix in the MarvelClient version column if the client is using a 64-bit version of MarvelClient

The Notes by Notes & MC Release view now has a "(64bit)" suffix in the subcategory groupings of the following categories if the client is using a 64-bit version of MarvelClient:

• MarvelClient
• Notes Releases

Added a "Windows/64" option for Mailbased Install/Mailbox PostopenScript

New options and fixes for the Windows 64-bit client:

• MCUpgrade now includes nice64
• Fixed problems publishing an upgrade or importing installers when using a 64-bit client
• Cinema Slide conversion to HTML now works with 64-bit clients

Added new views for Nomad Roaming backups, by Nomad Client, and by Nomad Device.

Nomad Web clients 1.0.6 and higher will also now report the browser and OS version in the Analyze DB.

This allows you to backup and restore your Recent Apps and workspace settings across some or all of your Nomad clients. Please see the Nomad Roaming Overview and related documents in the knowledgebase for more information.

This allows you to prevent Nomad Web users from accessing, replicating, or deleting specific databases either locally or on a server. The most common use-case is if you have databases on your server that you don't want Nomad Web users to open (maybe because they use Java or clientside XPages), you can easily prevent them from being used by Nomad Web users with a simple MarvelClient action.

Beginning with HCL Nomad Web 1.0.4, select MarvelClient actions can run in the background after the client has started.

This can be used to optimize the startup time for Nomad Web, potentially reducing the amount of time between when a user logs in and when their workspace is ready to use.

The "Advanced" section on the Nomad Web Migration Roaming action has been removed.

Made formulas in the web migration lookup view more efficient.

Nomad Web Migration action. This action can be used to enable a one-time desktop migration on a first-time setup of Nomad Web.

Requires HCL Nomad Web 1.0.2 or higher (available in December 2021).

Platform selector on Generic action form now enabled for all platforms

New view for notes.ini Preferences by User. This also allowed us to add a new Preferences tab to the user upload doc.

The Devices and Platform selector now supports the selection of Nomad Web. The selector for Linux has been removed.

Except for Location and Connection actions, any existing non-restricted action will automatically run on HCL Nomad Web, too.

Any existing Location and Connection actions, and any existing actions that are restricted to any number of devices and/or platforms, must be specifically edited and enabled for Nomad Web.

NOTE: You are advised to not enable existing Location and Connection actions for Nomad Web, but to create new, dedicated actions for Nomad Web. The simple reason is that Nomad Web requires the WSS port, whereas rich clients usually make use of the TCP(IP) port. See below for details regarding the new Nomad Location action.

A new "Nomad Location" action is now available. This should be used for management of the Location document on Nomad clients instead of the standard Location action.

Note that existing Location actions will not run on the latest Nomad client builds unless you explicitly resave them and specify the Nomad clients they should run on. We strongly encourage you to use the new Nomad Location action instead of activating old Location actions for Nomad.

Nomad App Restrictions also run on Nomad Web.

The Nomad Web platform only supports a specific subset of App Restrictions. The action form in the Config DB has icons that indicate which App Restrictions are available on the different Nomad platforms.

Online Update no longer checks for new versions automatically on Mac. This avoids problems where LotusScript-to-Java calls don't always work properly on MacOS.

MCUpgrade\by Summary Latest view was not sorted properly.

The config file XSLT document did not include config_user_* values for GreenLight customers.

When downloading the MCUpgradeService files from the upgrade config wizard (Elevation tab with Service type upgrade selected), customers had to merge their public key file into the zip file manually.
Downloading now prompts for a public key file and merges it into the resulting zip file automatically.

New languages available! Our templates now have translations for these additional languages:

• Spanish
• French
• Italian
• Dutch
• Russian
• Japanese

After you run OnlineUpdate to upgrade to the latest template, you can close and reopen the database and run OnlineUpdate again to download one, some, or all of the new languages.

New languages available! Our templates now have translations for these additional languages:

• Spanish
• French
• Italian
• Dutch
• Russian
• Japanese

You will need to run OnlineUpdate in your Config DB to select and download the new languages.

Improvements to the Upgrade Wizard:

• Now allows for filepaths with spaces
• Easier shortcut icon selection
• Deploying MarvelClient Essentials will now consistently use pmc.dll as the deployed filename

Workaround for a problem where the Audit agent would not fully process large batches of upload documents, but it would set all the upload documents to processed anyway. This is due to a Java bug specific to Domino 11.0.1FP3 and Domino 12. Some details are in this HCL technote: https://support.hcltechsw.com/csm?id=kb_article_view&sys_kb_id=a614d6191bf0f010a67e9759bc4bcbe6 

Better processing of documents in the Cleanup handler, to avoid problems where usernames have been modified by the Admin process. This includes:

• new option to remove documents that have been renamed by the Admin process and now have obsolete upload keys
• new option to remove documents that are not the latest version of Notes on that computer (i.e. if there are multiple upload documents for a single machine representing multiple Notes client versions, only keep the upload document for the highest version found)
• fixed a problem where Cleanup didn't work properly for users who had multiple shortnames defined