Version notes
These release notes contain information about new features and functions in Saperion ELM version 6.3, as well as any known issues, and update notes.
For more details about feature functionality, refer to the ELM documentation in the Saperion documentation portal. In addition, for further information regarding the system itself, refer to the current Saperion technical specification.
About compatibility
Saperion ELM Server Exchange Edition Version 6.3 is compatible with Saperion ECM versions 7.5.3 and higher.
New features and improvements
Management of user permissions and roles
With Saperion ELM version 6.3, the user permissions and role management were moved from Archive Web to the ELM Enterprise Manager. If you already have configured permissions/roles, these are migrated to the centralized database when you first log in to Archive Web.
ELM MailApp
The ELM MailApp now supports ELM server installations archiving from cloud platforms such as Office 365. ELM MailApp is no longer part of the ELM_64bit_Extensions optional features installer; instead, it has its own installer.
ELM server installations
With Saperion ELM version 6.3, an ELM server using EWS Connector can now work with Microsoft Messaging API and Collaboration Data Objects (MAPI CDO). Thus, Outlook is no longer a requirement for ELM server installations.
Signed emails
Support for signed emails was extended to included support for embedded messages. More information about signed emails can be found in the ELM "Optional Features" manual.
Store Access component
The Store Access component has been updated. It now supports the following:
- Saperion version 7.5 SP3
- Standard ACLs in the Saperion Classic Connector configuration
The Store Access component is described in more detail in the ELM Installation manual.
Known issues
Kerberos and PowerShell
The ELM installation package uses Kerberos authentication when running remote PowerShell cmdlets. Kerberos authentication must be enabled on the PowerShell web service installed by the MS Exchange server.
MAPI CDO
When MAPI CDO is used as the MAPI subsystem, Unicode string properties, such as "From", "CC", "BCC" and "Subject" are not supported by post-processing plugins, nor on retrieve. In both cases, Unicode characters are replaced with the "?" character.
ELM MailApp
The ELM MailApp cannot be used for archiving mails from personal archive mailboxes.
Web Service configuration
The web service configuration on MS Windows 2003 x64 does not work properly when IIS is configured to run in x86 mode.
About Updating
- Permissions defined in Archive Web must be migrated to the centralized permissions database when updating to ELM 6.3. The migration occurs automatically with the first login to the Archive Web application. We recommend logging in right after the ELM server was updated on each web server hosting the Archive Web application.
- With ELM version 6.2, Public Folder access must be configured again for each imported MS Exchange server, as the global public folder owner settings were moved to server level when updating from versions before 6.2.
- Scheduler configuration for public folders must be updated with the update tool included in the ELM server setup. It is crucial to perform the update with the application. Refer to the manual when updating from versions before 6.2.
- When updating to version 6.0, make sure that .NET 2.0 SP2 and .NET 4.0 are installed.
- After updating to 5.5 or higher, make sure that your ELM DDC contains a SYSROWID
column with a value. Without this column, there may be problems when
reading/writing using the Saperion Classic Connector.Use the SQL statement
appropriate for your server:
- SQL ServerUPDATE ELM SET SYSROWID = Replace(NEWID(),'-'")+'000000000000' WHERE SYSROWID IS NULL
- OracleUPDATE ELM SET SYSROWID = SYSGUID() || '000000000000' WHERE
SYSROWID IS NULL Note: Depending on the number of records in your database, the SQL command may need several minutes to run.
- When multiple ELM products are present on the same server, or use the same components in a distributed architecture, all products have to be updated to the same version number (version 6.0 and higher).
- If you are installing ELM on a computer with Microsoft SharePoint installed (any version), the ELM web applications will be installed to different ports (9981 for web services, 7781 for Archive Web). Include the port number when you configure access to the archive and retrieve servers.
- If you are installing ELM on a computer with a BlackBerry server installed (any version), note that ELM requires Outlook, while BlackBerry requires Exchange MAPI. These components cannot coexist on the same computer. Contact Saperion support regarding update possibilities.
- After installation, ensure that the MCSWS handler mapping is configured as follows:> Apply to ‘*.*’> Apply to files and folders.> On IIS 7, the application pool must be set to “Integrated” Managed Pipeline Mode.More details are included in the documentation.
- On IIS 7: make sure that the ISAPI and CGI restrictions allow ASP .NET v4 for both x86 and x64 platforms.
Update from version 5.x
A direct update to 6.0 is possible once all software prerequisites are fulfilled.
Update from older versions
Refer to the ELM v5.5 Release Notes (Saperion v7.1) for information on how to update ELM from earlier versions.