Product Updates & Alerts

Product Updates & Alerts

June 10, 2022

IMM Suite of products, Supported Web Browsers, Windows 11 and Edge with IE Mode

We wanted to offer a friendly reminder that the following web browsers are supported in IMM eSign v.2020 and greater:

  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge
  1. If you are already running IMM eSign v.2020 or greater and are moving from Internet Explorer to any of the above browsers, please be sure to test that these browsers are operating as expected with IMM eSign. 
    If you need assistance using v.2020 with the above browsers, please contact our support center.
  2. If you are running a version of IMM eSign below v.2020 and wish to use any of the above browsers, you will need to upgrade to v.2020.  You may initiate your upgrade project with IMM by submitting an Upgrade Request Form.
  3. For IMM eSign Cloud service clients, you are already on the latest version of eSign v.2020, which is compatible with Chrome, Firefox, Edge and Internet Explorer.

NOTE 1  
The Signature Pad Messaging function within IMM eSign is not currently supported in Edge, Chrome or Firefox. 
We are currently working with Topaz to offer this functionality in a future release of IMM eSign, expected late this year.

NOTE 2  

Edge contains the ability to operate in an Internet Explorer emulation mode.  This is referred to as “IE Mode”.  IMM eSign v.2017 and higher does support using Edge in IE Mode.  This delivers standard eSign functionality, including the Signature Pad Messaging function.  If you wish to run IMM eSign in “IE mode”, you can follow Microsoft’s configuration instructions (links below). 

While we have certified IMM eSign v.2017 and higher with Edge operating in IE Mode, it is clients responsibility to be able to configure and manage IE Mode within their Edge Browser environments.

Getting Started Guide

Enterprise Mode and the Enterprise Mode Site List

Configure Local Site List for Internet Explorer (IE) Mode

 

NOTE 3

The default web browser that ships with Microsoft Windows 11 is Edge. 
Please DO NOT install Windows 11 on machines where you operate IMM eSign if you are running a version of IMM eSign below v.2020 unless you intend to operate Edge in IE Mode. As mentioned above, the Signature Pad Messaging function should continue to behave as expected in IE Mode. 

If you have any further questions, feel free to reach out to your Client Success Manager. Thank you for being a valued IMM client!

April 5, 2022

Supported Web Browsers

We wanted to send you a friendly reminder that the following web browsers are supported in versions 2020 and greater of IMM eSign:

  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge

If you intend to use any of those browsers with IMM eSign, please ensure that your version of IMM eSign supports your browser of choice.

We are aware that certain core hosts and business systems may require Internet Explorer. If you wish to install Windows 11 and/or run a browser other than Internet Explorer, please make sure your IMM eSign version is compatible, and that your business applications do not require Internet Explorer.

Please note that if you are running IMM eSign in the IMM cloud, you are already on the latest version of IMM eSign, which is compatible with Chrome, Firefox, Edge and IE.

If you have any further questions, feel free to reach out to your Client Success Manager. Thank you for being a valued IMM client!

March 31, 2022

Adobe Sign Branding Change

During the week of April 4, Adobe will begin rolling out a branding change to the Adobe Sign service. The new name will be referred to as “Adobe Acrobat Sign”. There will also be logo changes as we are being told.

IMM clients should observe these changes being rolled out in different variations over time. None of the URL’s or domain names being used by the service will change – and your eSign/Adobe services will continue as normal.

If you should have any questions, please contact our technical support center or your IMM representative.

March 11, 2022

Log4Net Vulnerability

IMM is aware of the Log4Net vulnerability, officially known as CVE-2018-1285, and we have determined that certain components within IMM eSign utilize the affected software and are vulnerable to this exploit.

In response, IMM has created a client and server patch that eliminates the vulnerability caused by CVE-2018-1285. Please contact our Support Team so that an evaluation can be performed to determine which patch(s) are necessary for your particular version of IMM eSign.

Here are the ways you can contact the Support Team:

March 1, 2022

Ukraine/Russia Situation Statement

IMM is monitoring the Ukraine/Russia situation closely to pro-actively manage any risk. Our delivery model depends on world-class partners, such as Microsoft and Adobe, who have the resources and sophistication to help prevent, detect, and respond to potential security incidents quickly. Our vendor risk management program evaluates all our key service providers, and considers their ability to provide continuity of operations before we partner with them. We also have a business continuity program in place to respond to a wide range of disruptions, including cyberattack. We will issue further communications as events warrant.

December 29, 2021

Log4Shell/LogJam Exploitation Statement

IMM is aware of the recently announced Log4Shell / LogJam vulnerability, officially known as CVE-2021-44228. We have completed our initial review and investigation and have determined that IMM eSign (including Adobe Sign components), IMM eSignPlus, IMM eReceipts and IMM eChecks do not utilize the affected software and are NOT vulnerable to this exploit.

For our IMM eTeller Check21 solution, we are currently working with our third-party partner on remediation solutions.  Until such remediation is available, IMM recommends our clients block the Teller Item Capture server from any non-required internet URL’s as an immediate solution.  If you should have any questions, please contact our IMM technical support center.

We will be updating this statement in the future as appropriate.

August 3, 2021

Sunset Offline eCheck/Starter Check Module

To maintain the highest quality of customer service and satisfaction, we are announcing the formal support sunset of our Offline eChecks/Starter Check Module effective June 30, 2022. You will not be required to uninstall or delete the product but after this date, IMM will no longer provide any form of technical or product support for this module.

Please be advised the module will be prorated through June 30, 2022 on your October 1st annual maintenance invoice. If you have additional questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

July 7, 2021

Microsoft Print Spooler Vulnerability

As you may already be aware, Microsoft has recently announced two severe vulnerabilities in its Windows Print Spooler service. While not directly affected by these vulnerabilities, IMM does have two products that rely on this service:

  • IMM eSign (RTS Edition) has a Virtual Printer on each workstation, which uses the Print Spooler. This Virtual Printer allows a 3rd party system to print documents to the IMM Virtual Printer, and sends the print files to IMM eSign for document signing.
  • IMM eChecks: This is installed on the Server and prints official paper checks to any printer designated on the network, also using the Print Spooler service.

 

As there is no patch yet for these vulnerabilities, both Microsoft and the Cybersecurity and Infrastructure Security Agency (CISA) are encouraging administrators to disable the Windows Print spooler service in domain controllers, and in any systems not used for printing. Please note: Take care if you disable print spooler services to not impact IMM eSign operations or functionality.

 

A helpful summary can be found here: https://www.techrepublic.com/article/critical-flaws-in-windows-print-spooler-service-could-allow-for-remote-attacks/

If you have any questions, please contact IMM Customer Support at [email protected].

March 15, 2021

Microsoft Exchange Exploits

On March 2, 2021 Microsoft released information regarding the HAFNIUM Exchange exploits that is targeting MS Exchange Servers. IMM is pleased to report to those making inquiry that our version of Microsoft Exchange was not affected by this particular report. Our internal exchange systems were unaffected and our operations continue as normal.

December 17, 2020

SolarWinds Exploitation

We wanted to notify any party making inquiry that it has been deemed at this time that neither IMM or our software and/or services utilize SolarWinds software; therefore; there is no impact nor further action required to remediate this industry software incident. Our teams are continuing to perform in-depth analysis and due diligence. If any future determinations alter the above information, we will make notice of the finding and the resulting remediation plans here.

November 24, 2020

Please Ignore any Echosign.com to Adobesign.com URL Migration Information you Receive from Adobe Sign

Adobe has distributed information regarding a modification to their product domain (URL) that would adversely impact your IMM eSign operation if followed. Please ignore this message from Adobe and take no action until further direction from IMM.

 

Specifically, Adobe is migrating from echosign.com to adobesign.com and is suggesting to customers that they can select the option – now available in the account settings for your institution – to migrate your institution to the new domain/URL.

 

This is information that should be ignored by all IMM clients as modifications have to be made programmatically to IMM eSign to function with the new domain/URL.

 

When IMM has made programmatic accommodations in IMM eSign (anticipated in 2021) we will provide you with instructions and directions on how to implement and proceed with the domain/URL migration. Once again, until that time – do not take any action on the information you may see from Adobe.

 

If you should have any questions or concerns, please contact our customer support center for further information.

March 10, 2020

Coming Soon: Expanded IMM eSign Browser Support

As IMM is aware of a number of financial application systems that are moving browser requirements to Chrome and/or Firefox, we wanted to take a moment and share how IMM will be able to support browser migrations as they become desired or necessary:

 

  1. IMM eSign release level 2020.1 is currently projected to be available for customers at the end of summer 2020.
  2. IMM eSign 2020.1 will include support for the following:
    1. Support for both Chrome and Firefox browsers
    2. Adobe Reader will no longer be required
    3. Signature pads will be supported for in-person signing with both Chrome and Firefox.  Fill-from screen will also be supported in both browsers.
    4. For IMM eSign for Credit Unions “XML Edition” – document redesigns will not be necessary.  Generic IMM eSign javascript will be supported – however if your institution leverages custom javascript, this may need to be reviewed.
    5. For IMM eSign for Credit Unions “RTS Edition” – fill-from screen will be supported in both browsers.
    6. For IMM eSign for Banks – fill-from screen will be supported in both browsers.
  3. IMM eSign 2020.1 will have many other new features as well.  A comprehensive release overview will be made available by the end of Q2 2020.  Stay tuned for more information as it becomes available.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

August 19, 2022

Recent Adobe Sign Emails Sent to Adobe Acrobat Sign Account Administrators

Your Financial Institution’s Adobe Administrator may have received emails from Adobe Sign asking if you would like to move users from one Adobe Sign account to another. The verbiage is like the below:

“As an administrator of the Adobe Acrobat Sign account [your financial institution name], this is to inform you that a different Adobe Acrobat Sign account [your financial institution name] has requested to add your user [named user] with email address [named user’s email address] to their account. If you approve of this request to remove this user from your existing Adobe Acrobat Sign account, so that this user can be added to this new Adobe Acrobat Sign account, please click the “Remove User” button below. If you have any questions, please contact Adobe Support by signing into the Adobe Acrobat Sign application and then selecting the “?” in the top right corner.”

Adobe has confirmed that these emails are legitimate and originate from them. We also understand that if the “Remove” procedure is followed, by clicking the “Remove Button”, the user will no longer be able to send documents for remote signatures through IMM eSign.

 

We therefore strongly recommend that the user is not removed, as this will have significant consequences to your organization’s ability to capture signatures remotely through IMM eSign.

Adobe has provided the information below to help us better understand the reasons for these emails. We, in turn, are passing this on to you.

 

What are the triggers causing this email to be sent?

  • Company is migrating contract from a standalone product, pilot, or Adobe Sign/EchoSign to VIP with an Acrobat Sign entitlement.
  • Company is migrating contract from ETLA, Acrobat, Acrobat Pro to VIP with an Acrobat Sign entitlement.
  • Company has accepted new terms associated with price increase for Acrobat, Acrobat DC, or Acrobat DCE.
  • An account admin has initiated migration to Adobe Admin Console and set up identity such as SSO/SAML/AD
  • An Adobe Console admin has added a claimed domain & provided CA for domain ownership + has initiated migration of all existing users that have Adobe services OR has initiated migration of user management to Console.

 

Was the customer notified/informed/aware of these changes?

Yes, directly through email and migration guide/steps:

  • As part of contract migration or self-initiated migration to Adobe Console, the person that has been listed as the company administrator during contracting did receive notice and next steps overview. (Example: Getting Started Flier)
    • Additionally, customers that meet certain revenue tiers are assigned an implementation advisor to guide the customer through this process.

Yes, through instructions & help page guidance when deploying:

  • As part of a domain claim, through initiating migration for existing users, or user management to Adobe Admin Console.

NOTE: Adobe Admin Console administrators may be different contacts than admins for any standalone Adobe service. An admin for Acrobat Sign doesn’t transfer admin rights to Admin Console.

 

What should I do if a user was moved or user is identified as a “Duplicate Acrobat Sign user(s)” (previously called “entitlement conflict.”)

Customers who have Acrobat DC, CCT, or CCE all apps will experience this issue. How to resolve:

  • If they are enterprise customers for Acrobat DC or CCE all apps, Step 1 in the Acrobat Sign Getting Started Flier will show them how to resolve the issue.
  • If they are a teams customer for Acrobat DC or CCT all apps, use Acrobat Sign Onboarding Guide page 10 to resolve the issue.
  • If user was previously had a trial, free, canceled, or pending account follow steps in this guide.

 

If you have any further questions about these notices from Adobe, please contact your Adobe account representative.

November 17, 2021

Information about the Upcoming Adobe Sign Release

Adobe is currently targeting to implement the next release of Adobe Sign on or around December 1, 2021. As a matter of standard practice, Adobe always reserves the right to modify that date or move it during final release qualification and testing.

There are 2 (two) key elements in this release that we wanted to highlight for you:

1. Adobe Sign Partnership with Notarize for Remote Online Notary (RON)

Adobe announced last year that they had partnered with a company named Notarize to bring remote online notary services to the Adobe Sign platform and client base. The first planned roll-out for this new functionality is scheduled to be a part of the December release. We wanted to alert you to the fact that his functionality will not be available to the IMM eSign client base. Please ignore any information that you might see as it will not be applicable to the IMM client base.

IMM has also recently signed a partnership agreement with Notarize to make remote online notary services (RON) available to the IMM client base. The partnership is presently being formalized and further announcements and information will be coming during the early part of December 2021. Please stay tuned for further information.

2. Adobe Sign Console and Internet Explorer

If you are presently using Internet Explorer and you have accessed the Adobe Sign console, you most likely have received a message suggesting that Internet Explorer is no longer a supported browser and that you should utilize another modern browser. Adobe has suggested to us that Internet Explorer should continue to function after the December release – however new features or functions will not be tested with IE, so Adobe cannot make representation as to the expected results when using IE with their console. Please note that for the optimum experience and reliability in performance, non-IE browsers are highly recommended for your employees to use with the Adobe Sign console.

We hope that you will find this information to be useful. If you should have any questions or concerns, please contact our technical support center – or your IMM representative for further details.

July 7, 2021

Microsoft Print Spooler Vulnerability

As you may already be aware, Microsoft has recently announced two severe vulnerabilities in its Windows Print Spooler service. While not directly affected by these vulnerabilities, IMM does have two products that rely on this service:

  • IMM eSign (RTS Edition) has a Virtual Printer on each workstation, which uses the Print Spooler. This Virtual Printer allows a 3rd party system to print documents to the IMM Virtual Printer, and sends the print files to IMM eSign for document signing.
  • IMM eChecks: This is installed on the Server and prints official paper checks to any printer designated on the network, also using the Print Spooler service.

 

As there is no patch yet for these vulnerabilities, both Microsoft and the Cybersecurity and Infrastructure Security Agency (CISA) are encouraging administrators to disable the Windows Print spooler service in domain controllers, and in any systems not used for printing. Please note: Take care if you disable print spooler services to not impact IMM eSign operations or functionality.

 

A helpful summary can be found here: https://www.techrepublic.com/article/critical-flaws-in-windows-print-spooler-service-could-allow-for-remote-attacks/

If you have any questions, please contact IMM Customer Support at [email protected].

April 16, 2021

Sunset of Support for IMM eSign & eSignPlus v2015 & v2017

To maintain the quality of our customer support and overall customer satisfaction, we are announcing the formal support sunset date of March 1, 2022, for IMM eSign and eSignPlus v2015 and v2017.

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 March 1, 2022. After this date, IMM will no longer provide any form of technical or product support for versions 2017, 2015, and older.

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 or subscription service, 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. Emailing your upgrade request to [email protected]; or
3. Click “Upgrade Request” and complete the form

For any questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

December 20, 2020

Service Enhancement Update Completed

This is to notify our eSign Cloud Service clients that the service update scheduled for Dec 20, 2020, has been completed and the service is available for normal operations. If you have any unusual behavior or any questions concerning the update, please contact our customer support center.

March 10, 2020

IMM eSign Remote Signature Update

Adobe has advised us that they are planning to implement an updated release of Adobe Sign the second week of March. This release is not scheduled to result in any downtime of the Adobe Sign/IMM eSign Remote services. The release is currently projected to have minimal changes – mostly surrounding the Adobe portal user interface. We wanted to make you aware of this upcoming release so if you notice any changes, you will know where and why they are there.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

March 10, 2020

Coming Soon: Expanded IMM eSign Browser Support

As IMM is aware of a number of financial application systems that are moving browser requirements to Chrome and/or Firefox, we wanted to take a moment and share how IMM will be able to support browser migrations as they become desired or necessary:

 

  1. IMM eSign release level 2020.1 is currently projected to be available for customers at the end of summer 2020.
  2. IMM eSign 2020.1 will include support for the following:
    1. Support for both Chrome and Firefox browsers
    2. Adobe Reader will no longer be required
    3. Signature pads will be supported for in-person signing with both Chrome and Firefox.  Fill-from screen will also be supported in both browsers.
    4. For IMM eSign for Credit Unions “XML Edition” – document redesigns will not be necessary.  Generic IMM eSign javascript will be supported – however if your institution leverages custom javascript, this may need to be reviewed.
    5. For IMM eSign for Credit Unions “RTS Edition” – fill-from screen will be supported in both browsers.
    6. For IMM eSign for Banks – fill-from screen will be supported in both browsers.
  3. IMM eSign 2020.1 will have many other new features as well.  A comprehensive release overview will be made available by the end of Q2 2020.  Stay tuned for more information as it becomes available.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

February 24, 2020

IMM eSign Cloud Service Update Complete

We are pleased to notify you that this weekend’s scheduled maintenance to update the IMMeSign Cloud Service is now complete. All services have been fully restored and the system is operational and available.

 

If you should encounter any unexpected behavior or have any questions about IMMeSign Cloud Services – please contact our technical support center.

 

Thank you for being a valued IMM client. We appreciate your business.

February 20, 2020

IMM eSign Cloud Service Update

We are notifying all relevant customers of an upcoming maintenance window scheduled for our IMM eSIgn Cloud service on Sunday, February 23. During this maintenance window – IMM eSign will not be available for normal operational services. However, signing parties who have already been sent documents for remote signing will be able to view and sign their documents during the maintenance window. Please note, this service window is only for our IMM eSign Cloud customers – premise-based eSign customers are not impacted by this service window.

 

We will send out an email notification to all Cloud Service customers once the maintenance has been completed and the service is restored to normal operations.

 

If you should have any questions, please contact our IMM customer support center or your IMM client success or regional manager.

February 10, 2020

Attention: Action Required for IMM eSign Remote Signing Users

Adobe will be sun-setting all “SOAP” API’s and utilizing solely “REST” API’s effective June 30, 2020. This will have an impact for IMM eSign clients with the below two scenarios – as the Adobe API’s are the method used for IMM eSign to communicate remote signature transactions to the Adobe Cloud:

 

  1. Your IMM eSign version is version 5.3, 6.8, 6.9, 2015.1, 2015.2 or 2016.1. All IMM eSign clients running these versions will need to upgrade to a current version of our software which does not utilize the API’s being sunset by Adobe.
  2. If your financial institution utilizes the native Adobe Sign portal to perform “Ad-Hoc” transactions (send documents directly from Adobe for eSignature and bring these documents back via our Ad-Hoc downloader) – then you will need to upgrade to a current version of our software which does not utilize the API’s being sunset by Adobe.

 

ACTION REQUIRED

If you fall into either #1 or #2 as described above. Please check your production version(s) of IMM eSign and the Ad-Hoc downloader and report back to IMM Support using the link below.

 

Please click here to Report Back to IMM Support ➜

 

If it is determined that your organization does require an upgrade, we will place you in our deployment queue and an IMM project manager will contact you to schedule a patch to avoid issues.

 

If you are affected by this product alert, the resulting upgrade to IMM’s current software version must be completed and in production by June 30, 2020 in order to avoid potential service disruption.

 

If you have any questions regarding the above, please contact IMM Support at 800.836.4750 Option 3 or [email protected].

August 19, 2022

Recent Adobe Sign Emails Sent to Adobe Acrobat Sign Account Administrators

Your Financial Institution’s Adobe Administrator may have received emails from Adobe Sign asking if you would like to move users from one Adobe Sign account to another. The verbiage is like the below:

“As an administrator of the Adobe Acrobat Sign account [your financial institution name], this is to inform you that a different Adobe Acrobat Sign account [your financial institution name] has requested to add your user [named user] with email address [named user’s email address] to their account. If you approve of this request to remove this user from your existing Adobe Acrobat Sign account, so that this user can be added to this new Adobe Acrobat Sign account, please click the “Remove User” button below. If you have any questions, please contact Adobe Support by signing into the Adobe Acrobat Sign application and then selecting the “?” in the top right corner.”

Adobe has confirmed that these emails are legitimate and originate from them. We also understand that if the “Remove” procedure is followed, by clicking the “Remove Button”, the user will no longer be able to send documents for remote signatures through IMM eSign.

 

We therefore strongly recommend that the user is not removed, as this will have significant consequences to your organization’s ability to capture signatures remotely through IMM eSign.

Adobe has provided the information below to help us better understand the reasons for these emails. We, in turn, are passing this on to you.

 

What are the triggers causing this email to be sent?

  • Company is migrating contract from a standalone product, pilot, or Adobe Sign/EchoSign to VIP with an Acrobat Sign entitlement.
  • Company is migrating contract from ETLA, Acrobat, Acrobat Pro to VIP with an Acrobat Sign entitlement.
  • Company has accepted new terms associated with price increase for Acrobat, Acrobat DC, or Acrobat DCE.
  • An account admin has initiated migration to Adobe Admin Console and set up identity such as SSO/SAML/AD
  • An Adobe Console admin has added a claimed domain & provided CA for domain ownership + has initiated migration of all existing users that have Adobe services OR has initiated migration of user management to Console.

 

Was the customer notified/informed/aware of these changes?

Yes, directly through email and migration guide/steps:

  • As part of contract migration or self-initiated migration to Adobe Console, the person that has been listed as the company administrator during contracting did receive notice and next steps overview. (Example: Getting Started Flier)
    • Additionally, customers that meet certain revenue tiers are assigned an implementation advisor to guide the customer through this process.

Yes, through instructions & help page guidance when deploying:

  • As part of a domain claim, through initiating migration for existing users, or user management to Adobe Admin Console.

NOTE: Adobe Admin Console administrators may be different contacts than admins for any standalone Adobe service. An admin for Acrobat Sign doesn’t transfer admin rights to Admin Console.

 

What should I do if a user was moved or user is identified as a “Duplicate Acrobat Sign user(s)” (previously called “entitlement conflict.”)

Customers who have Acrobat DC, CCT, or CCE all apps will experience this issue. How to resolve:

  • If they are enterprise customers for Acrobat DC or CCE all apps, Step 1 in the Acrobat Sign Getting Started Flier will show them how to resolve the issue.
  • If they are a teams customer for Acrobat DC or CCT all apps, use Acrobat Sign Onboarding Guide page 10 to resolve the issue.
  • If user was previously had a trial, free, canceled, or pending account follow steps in this guide.

 

If you have any further questions about these notices from Adobe, please contact your Adobe account representative.

November 17, 2021

Information about the Upcoming Adobe Sign Release

Adobe is currently targeting to implement the next release of Adobe Sign on or around December 1, 2021. As a matter of standard practice, Adobe always reserves the right to modify that date or move it during final release qualification and testing.

There are 2 (two) key elements in this release that we wanted to highlight for you:

1. Adobe Sign Partnership with Notarize for Remote Online Notary (RON)

Adobe announced last year that they had partnered with a company named Notarize to bring remote online notary services to the Adobe Sign platform and client base. The first planned roll-out for this new functionality is scheduled to be a part of the December release. We wanted to alert you to the fact that his functionality will not be available to the IMM eSign client base. Please ignore any information that you might see as it will not be applicable to the IMM client base.

IMM has also recently signed a partnership agreement with Notarize to make remote online notary services (RON) available to the IMM client base. The partnership is presently being formalized and further announcements and information will be coming during the early part of December 2021. Please stay tuned for further information.

2. Adobe Sign Console and Internet Explorer

If you are presently using Internet Explorer and you have accessed the Adobe Sign console, you most likely have received a message suggesting that Internet Explorer is no longer a supported browser and that you should utilize another modern browser. Adobe has suggested to us that Internet Explorer should continue to function after the December release – however new features or functions will not be tested with IE, so Adobe cannot make representation as to the expected results when using IE with their console. Please note that for the optimum experience and reliability in performance, non-IE browsers are highly recommended for your employees to use with the Adobe Sign console.

We hope that you will find this information to be useful. If you should have any questions or concerns, please contact our technical support center – or your IMM representative for further details.

July 7, 2021

Microsoft Print Spooler Vulnerability

As you may already be aware, Microsoft has recently announced two severe vulnerabilities in its Windows Print Spooler service. While not directly affected by these vulnerabilities, IMM does have two products that rely on this service:

  • IMM eSign (RTS Edition) has a Virtual Printer on each workstation, which uses the Print Spooler. This Virtual Printer allows a 3rd party system to print documents to the IMM Virtual Printer, and sends the print files to IMM eSign for document signing.
  • IMM eChecks: This is installed on the Server and prints official paper checks to any printer designated on the network, also using the Print Spooler service.

 

As there is no patch yet for these vulnerabilities, both Microsoft and the Cybersecurity and Infrastructure Security Agency (CISA) are encouraging administrators to disable the Windows Print spooler service in domain controllers, and in any systems not used for printing. Please note: Take care if you disable print spooler services to not impact IMM eSign operations or functionality.

 

A helpful summary can be found here: https://www.techrepublic.com/article/critical-flaws-in-windows-print-spooler-service-could-allow-for-remote-attacks/

If you have any questions, please contact IMM Customer Support at [email protected].

April 16, 2021

Sunset of Support for IMM eSign & eSignPlus v2015 & v2017

To maintain the quality of our customer support and overall customer satisfaction, we are announcing the formal support sunset date of March 1, 2022, for IMM eSign and eSignPlus v2015 and v2017.

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 March 1, 2022. After this date, IMM will no longer provide any form of technical or product support for versions 2017, 2015, and older.

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 or subscription service, 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. Emailing your upgrade request to [email protected]; or
3. Click “Upgrade Request” and complete the form

For any questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

March 10, 2020

IMM eSign Remote Signature Update

Adobe has advised us that they are planning to implement an updated release of Adobe Sign the second week of March. This release is not scheduled to result in any downtime of the Adobe Sign/IMM eSign Remote services. The release is currently projected to have minimal changes – mostly surrounding the Adobe portal user interface. We wanted to make you aware of this upcoming release so if you notice any changes, you will know where and why they are there.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

March 10, 2020

Coming Soon: Expanded IMM eSign Browser Support

As IMM is aware of a number of financial application systems that are moving browser requirements to Chrome and/or Firefox, we wanted to take a moment and share how IMM will be able to support browser migrations as they become desired or necessary:

 

  1. IMM eSign release level 2020.1 is currently projected to be available for customers at the end of summer 2020.
  2. IMM eSign 2020.1 will include support for the following:
    1. Support for both Chrome and Firefox browsers
    2. Adobe Reader will no longer be required
    3. Signature pads will be supported for in-person signing with both Chrome and Firefox.  Fill-from screen will also be supported in both browsers.
    4. For IMM eSign for Credit Unions “XML Edition” – document redesigns will not be necessary.  Generic IMM eSign javascript will be supported – however if your institution leverages custom javascript, this may need to be reviewed.
    5. For IMM eSign for Credit Unions “RTS Edition” – fill-from screen will be supported in both browsers.
    6. For IMM eSign for Banks – fill-from screen will be supported in both browsers.
  3. IMM eSign 2020.1 will have many other new features as well.  A comprehensive release overview will be made available by the end of Q2 2020.  Stay tuned for more information as it becomes available.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

February 14, 2020

IMM eSign+ Product Alert

Please be advised that we have been notified of an upcoming and planned Microsoft system patch. This patch is set to occur automatically by Microsoft on or around March 10, 2020.

 

We believe that this patch could have an impact on the operation of eSignPlus for certain clients. We are reaching out to those clients that we believe could be impacted.

 

However, being cautious, we are posting this update/alert just as a form of secondary notification to our valued IMM eSignPlus clients.

 

In order to navigate this very complex situation resulting from the Microsoft patch, we have detailed the potential impact of the planned patch and how you can navigate it. Please click below to review this important information.

February 10, 2020

Attention: Action Required for IMM eSign Remote Signing Users

Adobe will be sun-setting all “SOAP” API’s and utilizing solely “REST” API’s effective June 30, 2020. This will have an impact for IMM eSign clients with the below two scenarios – as the Adobe API’s are the method used for IMM eSign to communicate remote signature transactions to the Adobe Cloud:

 

  1. Your IMM eSign version is version 5.3, 6.8, 6.9, 2015.1, 2015.2 or 2016.1. All IMM eSign clients running these versions will need to upgrade to a current version of our software which does not utilize the API’s being sunset by Adobe.
  2. If your financial institution utilizes the native Adobe Sign portal to perform “Ad-Hoc” transactions (send documents directly from Adobe for eSignature and bring these documents back via our Ad-Hoc downloader) – then you will need to upgrade to a current version of our software which does not utilize the API’s being sunset by Adobe.

 

ACTION REQUIRED

If you fall into either #1 or #2 as described above. Please check your production version(s) of IMM eSign and the Ad-Hoc downloader and report back to IMM Support using the link below.

 

Please click here to Report Back to IMM Support ➜

 

If it is determined that your organization does require an upgrade, we will place you in our deployment queue and an IMM project manager will contact you to schedule a patch to avoid issues.

 

If you are affected by this product alert, the resulting upgrade to IMM’s current software version must be completed and in production by June 30, 2020 in order to avoid potential service disruption.

 

If you have any questions regarding the above, please contact IMM Support at 800.836.4750 Option 3 or [email protected].

December 12, 2018

Support Sunset for IMM eSign+ 5.3x

To maintain the quality of our customer support and overall customer satisfaction, we are announcing the formal support sunset date of June 30, 2019, for IMM eSignPlus 5.3x (fka: TotaleAtlas Workflow).

 

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 June 30, 2019. After this date, IMM will no longer provide any form of technical or product support for versions 5.3x and below.

 

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. Emailing your upgrade request to [email protected]

 

For any questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

March 10, 2020

Coming Soon: Expanded IMM eSign Browser Support

As IMM is aware of a number of financial application systems that are moving browser requirements to Chrome and/or Firefox, we wanted to take a moment and share how IMM will be able to support browser migrations as they become desired or necessary:

 

  1. IMM eSign release level 2020.1 is currently projected to be available for customers at the end of summer 2020.
  2. IMM eSign 2020.1 will include support for the following:
    1. Support for both Chrome and Firefox browsers
    2. Adobe Reader will no longer be required
    3. Signature pads will be supported for in-person signing with both Chrome and Firefox.  Fill-from screen will also be supported in both browsers.
    4. For IMM eSign for Credit Unions “XML Edition” – document redesigns will not be necessary.  Generic IMM eSign javascript will be supported – however if your institution leverages custom javascript, this may need to be reviewed.
    5. For IMM eSign for Credit Unions “RTS Edition” – fill-from screen will be supported in both browsers.
    6. For IMM eSign for Banks – fill-from screen will be supported in both browsers.
  3. IMM eSign 2020.1 will have many other new features as well.  A comprehensive release overview will be made available by the end of Q2 2020.  Stay tuned for more information as it becomes available.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

February 13, 2020

IMM eReceipt Sunset Announcement

Microsoft has sunset Windows 7 client and Windows Server 2008 software systems. IMM eReceipts 6.3.3 (formerly known as TotaleReceipts) only operates on these retired MS software systems. Therefore, IMM will be formally sunsetting support for eReceipts version 6.3.3 and older versions effective May 31, 2020.

 

All customers must begin migration planning as soon as possible in order to upgrade their eReceipt system to a supported version before May 31, 2020. Please review our Support Guidelines at our website: immonline.com in the Support Section for more information.

 

As a part of our commitment to customer success, we will assist you as you migrate to a current version of eReceipts. Please make sure that you schedule your upgrade as soon as possible to avoid complications, risks and additional costs of running an unsupported version. You may contact us to initiate the upgrade process by using the methods below.

 

 

For any questions, please contact our Support center or your IMM Client Success Manager.

August 3, 2021

Sunset Offline eCheck/Starter Check Module

To maintain the highest quality of customer service and satisfaction, we are announcing the formal support sunset of our Offline eChecks/Starter Check Module effective June 30, 2022. You will not be required to uninstall or delete the product but after this date, IMM will no longer provide any form of technical or product support for this module.

Please be advised the module will be prorated through June 30, 2022 on your October 1st annual maintenance invoice. If you have additional questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

April 23, 2021

Canon Ending Support for CR-50 & CR-80 Scanners

Canon will sunset support for the CR-50 and CR-80 check scanners in April of 2022. As a result of this, IMM will also discontinue supporting these models at that time.

The current replacement model available through IMM is the CR-L1 scanner. This scanner uses the same driver as the CR-50/CR-80 models. We highly recommend upgrading to the current unit as soon as possible to avoid any interruption of service or support with your IMM eTeller Check 21 solution. Please feel free to utilize our Canon Check Scanner Order Form.

If you should have any questions about this informational communication, please contact our support center – or your IMM Client Success Manager.

March 10, 2020

Coming Soon: Expanded IMM eSign Browser Support

As IMM is aware of a number of financial application systems that are moving browser requirements to Chrome and/or Firefox, we wanted to take a moment and share how IMM will be able to support browser migrations as they become desired or necessary:

 

  1. IMM eSign release level 2020.1 is currently projected to be available for customers at the end of summer 2020.
  2. IMM eSign 2020.1 will include support for the following:
    1. Support for both Chrome and Firefox browsers
    2. Adobe Reader will no longer be required
    3. Signature pads will be supported for in-person signing with both Chrome and Firefox.  Fill-from screen will also be supported in both browsers.
    4. For IMM eSign for Credit Unions “XML Edition” – document redesigns will not be necessary.  Generic IMM eSign javascript will be supported – however if your institution leverages custom javascript, this may need to be reviewed.
    5. For IMM eSign for Credit Unions “RTS Edition” – fill-from screen will be supported in both browsers.
    6. For IMM eSign for Banks – fill-from screen will be supported in both browsers.
  3. IMM eSign 2020.1 will have many other new features as well.  A comprehensive release overview will be made available by the end of Q2 2020.  Stay tuned for more information as it becomes available.

 

If you should have any questions, please contact our technical support center – or you IMM representative.

August 19, 2022

Adobe Reader Compatibility Update

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.

 

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.