Product Updates & Alerts
IMM’s flagship eSignature platform (formerly known as TotaleAtlas) is used to power millions of “end-to end” eTransactions every month. Integrating with virtually any business application, our advanced eSignature technology provides an easy-to-use, eSignature experience for consumers, while significantly transforming internal business processes and the way transactions flow across your organization.
Adobe Reader Compatibility Updates
June 6, 2018
IMM has recently tested the most currently available versions of Adobe Reader for compatibility and is pleased to make our new compatibility matrix available to our clients. You may download the new version of the compatibility matrix by click on the “Download Compatibility Matrix” link below.
Download Compatibility Matrix >
We hope you will find this information to be helpful. If you have questions about Adobe Reader version compatibility, please contact our customer support center.
TLS 1.2 Mandatory Update Advisory
November 27, 2017
Overview
In July of 2016, IMM provided notification to all eSign and eSign remote clients recommending the updating of TLS to version 1.2 in order to reduce identified security vulnerabilities in TLS 1.0 and 1.1.
Due to the importance Adobe places on security practices and policies, as of January 16, 2018 – Adobe will only accept transactions submitted using TLS 1.2 protocol. Any transactions submitted via 1.0 and 1.1 will be rejected and will not be processed. This mandate applies to both remote eSign transactions submitted by IMM eSign (TotaleAtlas) as well as transactions performed directly via the Adobe Sign portal – what we refer to as “ad-hoc” transactions.
In addition, RC4 cipher will need to be disabled.
Description
Due to an identified security vulnerability with TLS 1.0 and 1.1, IMM advised clients in July 2016 to determine if either TLS 1.0 and/or 1.1 protocol was running on your IMM eSign (TotaleAtlas) Server. If in fact it was in use, IMM’s recommended action at that time to resolve the vulnerability was to implement TLS 1.2.
Now Adobe is mandating that any IMM eSign Remote transactions (formerly known as Document Exchange) will require TLS 1.2. RC4 cipher will also need to be disabled.
If you have not updated your TLS protocols to 1.2 or have disabled RC4 cipher, please be advised that your IMM eSign remote transaction submissions; ad-hoc submissions, or; the IMM eSign download service will be at risk for operational disruption.
Action Required
In 2015 Microsoft released an update to support TLS 1.2. If these updates are applied to the IMM eSign (TotaleAtlas), and SQL servers in use by IMM eSign, the application will continue to function properly. Disabling TLS 1.0 & TLS 1.1 and not implementing the TLS 1.2 update will cause both servers to not run properly and in turn will not allow IMM eSign to operate normally. We have included the links below that pertain to the various updates that you may need to be able to download Microsoft’s patch for TLS 1.2.
- TLS 1.2 needs to be enabled on the following:
- eSign server
- Standalone SQL server (Please refer to this page to determine which potential update you might require)
- Workstations that process ad hoc remote sessions, widgets and have access to the Adobe portal.
- Any server that runs the ad hoc downloader separately from the eSign server
- RC4 cipher needs to be disabled on the following (Please refer to this page for further details on RC4 disablement)
- eSign server
- Workstations that process ad hoc remote sessions and widgets.
- Any server that runs the ad hoc downloader separately from the eSign server
We hope you will find this information to be of value. If you have further questions about TLS version updates, older version vulnerabilities, and the associated Adobe TLS 1.2 requirements, please contact our customer support center.
In July of 2016, IMM provided notification to all eSign and eSign remote clients recommending the updating of TLS to version 1.2 in order to reduce identified security vulnerabilities in TLS 1.0 and 1.1.
Due to an identified security vulnerability with TLS 1.0 and 1.1, IMM advised clients in July 2016 to determine if either TLS 1.0 and/or 1.1 protocol was running on your IMM eSign (TotaleAtlas) Server. If in fact it was in use, IMM’s recommended action at that time to resolve the vulnerability was to implement TLS 1.2.
In 2015 Microsoft released an update to support TLS 1.2. If these updates are applied to the IMM eSign (TotaleAtlas), and SQL servers in use by IMM eSign, the application will continue to function properly. Disabling TLS 1.0 & TLS 1.1 and not implementing the TLS 1.2 update will cause both servers to not run properly and in turn will not allow IMM eSign to operate normally. We have included the links below that pertain to the various updates that you may need to be able to download Microsoft’s patch for TLS 1.2.
- eSign server
- Standalone SQL server (Please refer to this page to determine which potential update you might require)
- Workstations that process ad hoc remote sessions, widgets and have access to the Adobe portal.
- Any server that runs the ad hoc downloader separately from the eSign server
- eSign server
- Workstations that process ad hoc remote sessions and widgets.
- Any server that runs the ad hoc downloader separately from the eSign server
Change to Product Upgrades Installation Policies
August 11, 2017
In order to enhance and streamline installed product upgrades, IMM is announcing a change in our upgrade support policy effective immediately. If you should have any questions regarding the updated policy, please contact our technical support center.
The below changed policy language has also been updated in our published Support Policies Document.
NOTE: At this time, our new upgrade installation policy is not applicable to our workflow-based solutions.
Upgrades
Product upgrades are provided via our “Express” model as part of your annual maintenance. Non- standard Custom installations are billable and not included in AM.
Express Installation
Express installs are delivered via a virtual server download in an OVA file, to be imported by you into your VMware or Microsoft virtual server platform (other virtual server platforms are not supported for installation).
Once you import the server into your environment, IMM installer(s) will make product configurations (settings) to enable the product to work for you. All Express installation work is performed during IMM business hours.
Custom Installation
If you choose to not use the standard Express model for installation of your IMM product, you fall under the Custom Installation model and installation time is billable. Examples of non-Express installs are (but are not limited to) Physical server installation, Manual installation in the FI environment, Changes to (other than settings) the software installation like moving the database to another server or requiring different versions of infrastructure components to be installed.
To understand why this change in our policy was made, and how it benefits our valued clients, you can learn more here.
Product upgrades are provided via our “Express” model as part of your annual maintenance. Non- standard Custom installations are billable and not included in AM.
Express installs are delivered via a virtual server download in an OVA file, to be imported by you into your VMware or Microsoft virtual server platform (other virtual server platforms are not supported for installation).
If you choose to not use the standard Express model for installation of your IMM product, you fall under the Custom Installation model and installation time is billable. Examples of non-Express installs are (but are not limited to) Physical server installation, Manual installation in the FI environment, Changes to (other than settings) the software installation like moving the database to another server or requiring different versions of infrastructure components to be installed.
IMM eTeller Check21 (formerly Teller Item Capture)
May 26, 2017
Canon has announced changes to their check scanner product lines and have discontinued several units previously used by IMM clients. We have been advised of the following sunset dates for the products listed below. Please incorporate this information into your product replacement and future budgeting plans.
IMM Statement on Recent Security Events
May 22, 2017
IMM considers the protection and security of our systems along with the information processed by our technology a very serious matter. In light of recent security incidents that have been reported in the media, we’d like to take a moment to share information that may be of interest to our clients.
IMM’s internal systems have not been impacted by the recent “WannaCry” malware/ransomware scenario. The most proactive protection that can be taken for this and other malicious software is to maintain current release levels and patches of all internal software including but not limited to desktop operating systems, network operating systems, database systems, virus protection and intrusion detection programs.
IMM has internal policies combined with security protocol in place that keeps our systems up to date with the most current security patches and release levels to protect our systems. We highly recommend that our clients check to make sure that their software is up-to-date, and that appropriate security, virus and malware detection programs are maintained to protect systems and the data that resides within them.
If you have any questions regarding information security policies, please feel free to contact our client support center.
Support for Older Topaz Signature Pads
April 5, 2017
Due to enhanced features and functionality that we are adding to the IMM eSign platform going forward, you may find that older models of Topaz Signature Pads may not fully support the new functionality. Specifically, models T-LBK766, and T-LBK57GC series LCD display pads will need to be evaluated. In some cases, Topaz can provide firmware updates that will allow these older devices to operate with the new releases of IMM eSign.
If you have these devices, please contact the Topaz Technical Support team by calling 805-520-8286 and see if your device will support a firmware update.
As always, if you should have any questions about this technical update, please contact our customer support center.
Support Sunset for Older IMM Product Versions
March 30, 2017
To maintain the quality of our customer support and overall customer satisfaction, we are announcing the formal support sunset date of September 30, 2017 for the IMM products and versions listed below:
1. TotaleAtlas 5.3x (all variants of 5.3) and below
– Note: Does not apply to TotaleAtlas Workflow clients
2. Teller Item Capture Server 4.2 and below
– Client 3.0.9 and below
3. TotaleReceipts Server 6.3.2 and below
– Client 6.3.1 and below
All customers affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to a supported product version before September 30, 2017. After this date, IMM will no longer provide any form of technical or product support for the product versions listed above.
Please be aware that all labor for product support or services by IMM on an unsupported product version is not included in your annual maintenance, and is therefore a billable service as documented in our support guidelines. This also includes any support related to product upgrades. Additionally, if a support request requires a software modification, changes can only be applied to a currently supported version. Therefore, it is highly suggested that you upgrade to a supported version as soon as possible to avoid further complications.
As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions. Please ensure you schedule your upgrade early to ensure you avoid the complications, risk and cost of running an unsupported product.
You can initiate your upgrade migration by:
1. Contacting IMM’s Client Support Center; or
2. Completing the TotaleAtlas 2015 upgrade request form (only used for TotaleAtlas upgrades) on our website by using the button below; or
3. Emailing your upgrade request to: projects@immonline.com.
For any questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.
– Note: Does not apply to TotaleAtlas Workflow clients
– Client 3.0.9 and below
– Client 6.3.1 and below
Product Name Change
March 29, 2017
As a part of our on-going efforts to enhance our messaging and description of our solutions to the market, IMM announced a product re-branding initiative in the fall of 2016. All IMM products are the process of undergoing a name change, first in the sales and marketing areas (website, product brochures, etc.) to be followed in the physical product itself. The new names listed below will be present in all new product releases going forward. The product brand name changes does not impact the feature or functionality included today or in the future of each product, but rather is only a name change.
Old Product Name-> New IMM Product Brand
TotaleAtlas -> IMM eSign
TotaleAtlas Workflow -> IMM eSign plus
Document Exchange -> IMM eSign (Remote eSignatures)
TotaleReceipts -> IMM eReceipts
Teller Item Capture -> IMM eTeller Check21
TotaleChecks -> IMM eChecks
If you should have any questions, please contact your IMM Client Success Manager, or our Client Support Center.
Old Product Name-> New IMM Product Brand
Adobe Sign Update
March 10, 2017
Adobe Sign is expanding their North American data center and will undergo a period of planned maintenance that will result in expected system downtimes during the expansion procedure. This action is being performed to enhance the data center and is expected to result in improvements to service reliability, durability, scalability and automation.
When is the Planned Maintenance Operations?
The expansion will occur in 2 separate project phases on the dates and times listed below. The Adobe Sign services are expected to be unavailable for usage during these maintenance periods.
#1: Sat. March 11 @ 8pm ET – Sunday, March 12 @ 5am ET
#2: Sat. April 8 @ 8pm ET to Sunday, April 9 @ 2am ET
What Action Should You take?
Simply be aware that consumers will not be able to sign documents or complete transactions during these periods. However, all transactions in flight prior to the outage will be preserved and available for completion upon service restoration.
New IP Address Ranges
As a part of the data center expansion, new IP address ranges are being made available for the service. Please check with your IT Department to see if your institution needs to add the new IP address ranges to your existing range settings. The new IP address ranges can be obtained by contacting our Technical Support Center.
For any questions or clarifications on this announcement and the upcoming maintenance periods, please contact our Client Support Center or your Regional Client Success Manager.
The expansion will occur in 2 separate project phases on the dates and times listed below. The Adobe Sign services are expected to be unavailable for usage during these maintenance periods.
#2: Sat. April 8 @ 8pm ET to Sunday, April 9 @ 2am ET
Simply be aware that consumers will not be able to sign documents or complete transactions during these periods. However, all transactions in flight prior to the outage will be preserved and available for completion upon service restoration.
As a part of the data center expansion, new IP address ranges are being made available for the service. Please check with your IT Department to see if your institution needs to add the new IP address ranges to your existing range settings. The new IP address ranges can be obtained by contacting our Technical Support Center.
TLS Vulnerability Advisory
July 18, 2016
Overview
IMM is providing notification to our clients of a potential issue that could impact the security of your IMM TotaleAtlas solution due to identified TLS vulnerabilities. Please take a few moments to carefully review this information and determine if you need to take any corrective action to properly secure your operation. If you have any questions, please do not hesitate to contact our customer support center for assistance.
Description
Due to an identified security vulnerability with TLS 1.0 and 1.1, IMM is advising each customer to determine if either TLS 1.0 and/or 1.1 protocol is running on your IMM TotaleAtlas Server. If in fact it is, IMM’s recommended action to resolve the vulnerability is to implement TLS 1.2.
Please take note that If you disable TLS 1.0 and 1.1, you must ensure that TLS 1.2 is installed both on the TotaleAtlas and the SQL Server. TotaleAtlas uses SQL Server internally (by default IMM uses SQL express unless you have a licensed SQL standard version).
Microsoft released an update to support TLS 1.2. If these updates are applied to the SQL server in use by TotaleAtlas, the application will function properly. Disabling TLS 1.0 & TLS 1.1 and not implementing the TLS 1.2 update will cause SQL service to not run and in turn will not allow TotaleAtlas to operate normally. We have included the link to be able to download Microsoft’s patch for TLS 1.2 here
We hope you will find this information to be of value. If you have further questions about TLS version vulnerabilities and the associated security impact on TotaleAtlas, please contact our customer support center.
IMM is providing notification to our clients of a potential issue that could impact the security of your IMM TotaleAtlas solution due to identified TLS vulnerabilities. Please take a few moments to carefully review this information and determine if you need to take any corrective action to properly secure your operation. If you have any questions, please do not hesitate to contact our customer support center for assistance.
Description
Please take note that If you disable TLS 1.0 and 1.1, you must ensure that TLS 1.2 is installed both on the TotaleAtlas and the SQL Server. TotaleAtlas uses SQL Server internally (by default IMM uses SQL express unless you have a licensed SQL standard version).
Microsoft released an update to support TLS 1.2. If these updates are applied to the SQL server in use by TotaleAtlas, the application will function properly. Disabling TLS 1.0 & TLS 1.1 and not implementing the TLS 1.2 update will cause SQL service to not run and in turn will not allow TotaleAtlas to operate normally. We have included the link to be able to download Microsoft’s patch for TLS 1.2 here
We hope you will find this information to be of value. If you have further questions about TLS version vulnerabilities and the associated security impact on TotaleAtlas, please contact our customer support center.
Reminder of Support Sunset for Older Versions of TotaleAtlas
February 8, 2016
This is a reminder notice for all of our TotaleAtlas customers. In October of 2015, IMM formally distributed a sunset announcement for older versions of TotaleAtlas. We are re-distributing this to all clients today as a courtesy reminder of the official sunset of older TotaleAtlas versions prior to version 5.3. This sunset is effective April 1, 2016.
We’ve included the original email content below for your convenience. If you should have any questions or concerns, please contact our customer support center today and we will be happy to assist you.
In July of 2015, IMM announced the next-generation of TotaleAtlas, called TotaleAtlas 2015. This new release of TotaleAtlas provides many attractive product updates and new functionality – and is designed to align with current technology standards.
In order to maintain the quality of our customer support and overall customer satisfaction, IMM is announcing the formal sunset date for support of some of the older versions of TotaleAtlas. Please read the information below carefully in order that you may plan accordingly to avoid any disruption in the support of your TotaleAtlas implementation.
IMM is formally announcing the sunset of support for the following prior versions of TotaleAtlas, effective March 31, 2016.
Older Release Versions Scheduled for Support Sunset:
TotaleAtlas 4.x
TotaleAtlas 5.1
TotaleAtlas 5.2
Beginning April 1, 2016, all clients must have either TotaleAtlas 5.3 or TotaleAtlas 2015 installed and operational in order to maintain support of their TotaleAtlas implementation.
All TotaleAtlas clients affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to either TotaleAtlas 5.3 or TotaleAtlas 2015. After March 31, 2016, IMM will no longer provide any form of technical or product support for the prior versions of TotaleAtlas listed above. As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions.
Customers may contact IMM’s support center or the upgrade migration team by either completing the TotaleAtlas 2015 upgrade request form, or by emailing their upgrade request to: projects@immonline.com.
For any questions or clarifications on this sunset announcement, please contact either our technical support center or your regional IMM Client Success Manager.
TotaleAtlas 4.x
TotaleAtlas 5.1
TotaleAtlas 5.2
Document Exchange Product Update Announcement
November 26, 2015
Overview
On December 1, 2015, Adobe will implement a modification to the Document Exchange service. This modification will not impact the consumer or the employee experience while using the service. However, it will result in a noted visual difference in the appearance of the signed documents processed by the service.
Current Product Behavior
Once a document has been signed and processed through the Document Exchange service, a visible blue border is placed around the document contents. The document integrity validation indicator (green check mark), along with the Adobe transaction ID are displayed within the bottom section of the blue border.
New Change in Product Behavior
On December 1, 2015, Adobe will discontinue the use of the blue border and it will no longer visually appear on the signed documents. This modification is being made in order to maintain the original quality and integrity of the document contents as it appeared before, during, and after the signing event.
Replacement for Blue Border
While the blue border will no longer visually appear on the document, the tamper evident validation and certification of document integrity is still being performed. Indication of document integrity status will now be visually portrayed with the following behavior as the document is viewed in Adobe Reader (or compatible PDF viewer):
a. Document Integrity Validated: A blue banner is displayed at the top of the document viewing window with corresponding language that confirms the document has been certified by Adobe. This certification behavior has actually been in operation for a period of time now. (See example below)
b. Document Integrity Not Validated: A red banner is displayed at the top of the document viewing window with corresponding language indicating that the document has not passed certification. This will be an indicator that the document integrity is suspect and should require immediate research and attention.
Transaction ID/Audit Trail Access
With this new behavior the transaction ID and the Audit Trail can be accessed simply by clicking on the signature area of the document while it is being viewed in Adobe Reader. This will take the user to the Adobe Document Cloud eSign Services portal where the transaction ID is verified and the audit trail can be accessed.
We hope that you will find this information helpful. Should you have questions or require further information regarding this change to the Document Exchange service, please contact IMM’s Support Center.
Once a document has been signed and processed through the Document Exchange service, a visible blue border is placed around the document contents. The document integrity validation indicator (green check mark), along with the Adobe transaction ID are displayed within the bottom section of the blue border.
On December 1, 2015, Adobe will discontinue the use of the blue border and it will no longer visually appear on the signed documents. This modification is being made in order to maintain the original quality and integrity of the document contents as it appeared before, during, and after the signing event.
While the blue border will no longer visually appear on the document, the tamper evident validation and certification of document integrity is still being performed. Indication of document integrity status will now be visually portrayed with the following behavior as the document is viewed in Adobe Reader (or compatible PDF viewer):
With this new behavior the transaction ID and the Audit Trail can be accessed simply by clicking on the signature area of the document while it is being viewed in Adobe Reader. This will take the user to the Adobe Document Cloud eSign Services portal where the transaction ID is verified and the audit trail can be accessed.
iSign and iOS 9.x
November 17, 2015
Recently we advised our clients that in the initial qualification of iOS 9.x, our testing revealed unexpected behavior. We asked that you not update any iSign iPads to the new release until notification from IMM that the unexpected behavior was resolved.
We are pleased to share that we have released IMM iSign v209 which fully supports iOS 9.x. iSign customers may now proceed to update iPads to Apple’s new iOS release knowing that it is compatible and supported with IMM’s iSign solution. Also be sure to download and install the new iSign app from the App Store.
If you should have any questions or would like further information, please do not hesitate to contact our customer support center.
Support Sunset for Older Versions of TotaleAtlas
October 7, 2015
In July of 2015, IMM announced the next-generation of TotaleAtlas, called TotaleAtlas 2015. This new release of TotaleAtlas provides many attractive product updates and new functionality – and is designed to align with current technology standards.
In order to maintain the quality of our customer support and overall customer satisfaction, IMM is announcing the formal sunset date for support of some of the older versions of TotaleAtlas. Please read the information below carefully in order that you may plan accordingly to avoid any disruption in the support of your TotaleAtlas implementation.
IMM is formally announcing the sunset of support for the following prior versions of TotaleAtlas, effective March 31, 2016.
Older Release Versions Scheduled for Support Sunset:
TotaleAtlas 4.x
TotaleAtlas 5.1
TotaleAtlas 5.2
Beginning April 1, 2016, all clients must have either TotaleAtlas 5.3 or TotaleAtlas 2015 installed and operational in order to maintain support of their TotaleAtlas implementation.
All TotaleAtlas clients affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to either TotaleAtlas 5.3 or TotaleAtlas 2015. After March 31, 2016, IMM will no longer provide any form of technical or product support for the prior versions of TotaleAtlas listed above. As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions.
Customers may contact IMM’s support center or the upgrade migration team by either completing the TotaleAtlas 2015 upgrade request form, or by emailing their upgrade request to: projects@immonline.com.
For any questions or clarifications on this sunset announcement, please contact either our technical support center or your regional IMM sales manager.
TotaleAtlas 4.x
TotaleAtlas 5.1
TotaleAtlas 5.2
