MicrosoftMicrosoft
MicrosoftThom_A Thanks for your feedback. For clarification, when we state that SSMS 20 is no longer supported, it means that if you find a problem in SSMS 20 then we will fix in the current release (SSMS 21) and not back port it to a SSMS 20 release. We don't block customers from using SSMS 20 (or earlier releases) and we recognize that many customers (and companies) cannot immediately update to the newest release.
erinstellato Can you please clarify the documentation about that topic? Currently it states that no other SSMS version but the latest major version get security updates. Combined with the SSIS as preview-only and the typical "Class not registered" on connecting to older SQL Server Integration Services version, this is a disaster.
MicrosoftJensDamm When you state "Typical "Class not registered" on connecting to older SQL Server Integration Services version", I believe you're referring to the requirement that in order to connect to the legacy SSIS service, you must use the version of SSMS that aligns to the specific version of SQL Server to which you're trying to connect, as documented here: https://learn.microsoft.com/ssms/system-requirements#supported-sql-offerings. Is that correct? If so, then should there be a high-impact security vulnerability specific to SSIS for an older version of SSMS that customers use to connect to the legacy SSIS service, then we would patch that specific release of SSMS to address the security vulnerability. Please help me understand what "this is a disaster" means. Thank you.
erinstellato With Disaster I mean corporate reaction on setting all older SSMS versions SEoL (Security EoL). Microsoft forces us to keep the old SSMS version, as you recognized, but in the same time, the automated vulnerability scans find the old SSMS and guess the reaction: it will be uninstalled and replaced by the only supported version of SSMS v21 (at the current date). This causes issues because we cannot access the SSIS instance anymore...
Please reverse the SEoL for older SSMS versions in the official documentation or add support for legacy SSIS connections in the latest SSMS.
MicrosoftJensDamm What does "corporate reaction" mean? And what automated vulnerability scans are you running and how do they determine that an older SSMS is vulnerable?
