Documentation
Documentation

iMIS 2017 Support Policy

Microsoft has announced End‑of‑Life (EOL) dates for key infrastructure components used by legacy iMIS environments, including iMIS 2017:

  • Microsoft SQL Server 2016: July 14, 2026
  • Microsoft Windows Server 2016: January 12, 2027

After these dates, Microsoft will no longer provide critical security updates, increasing risks for any system still running on these older versions. iMIS clients on iMIS 2017 should develop a migration policy to Cloud-hosted iMIS EMS to address these risks and we are clarifying our support policy as follows:

iMIS 2017 Application Support

ASI will continue to support properly licensed iMIS 2017 environments, including applicable service packs and security updates.

iMIS 2017 was released and certified against SQL Server 2016 and Windows Server 2016. While some clients operate iMIS 2017 on newer SQL Server versions without issue, those environments were not part of the original certification matrix. If a client experiences an issue that is reproducible within the iMIS application, it will be addressed through normal ASI Support. If an issue is determined to originate from database behavior, configuration, or compatibility specific to newer SQL Server versions, ASI may not be able to provide direct remediation. In those cases, customers will be referred to their AiSP, implementation partner, or database administrator. ASI Support will collaborate as appropriate by helping isolate the issue, providing application‑level guidance, and coordinating with partners when database-level changes or tuning are required.

Transitioning to Cloud-hosted iMIS EMS

Cloud-hosted iMIS EMS offers clients a solution built for modern demands to help your organization stay secure, efficient, and positioned for growth and improved performance. iMIS clients on iMIS 2017 are encouraged to work with their AiSP and ASI account team to plan a transition to Cloud‑hosted iMIS EMS, which may include options that support SQL access or phased removal of customizations that are not cloud-friendly. For more information, see iMIS Upgrade Planning.