SSMS Tools Pack supports organization-wide deployment with PowerShell license activation and shared default settings.
You can activate a machine with a PowerShell one-liner after installation.
It needs at least .NET 4.7.2 and all add-in DLLs. Change SSMSToolsPackC22 to the correct version you're activating.
The PowerShell command is:
[Reflection.Assembly]::LoadFrom('<InstallationLocation>\SSMSToolsPackC22.dll') | Out-Null; [Silent]::Activate('YourLicenseKey')
You can prepend a T-SQL script to any SQL statement sent by the add-in.
For example, this is useful in a Row-Level Security controlled multi-tenant environment which needs a SESSION_CONTEXT variable set before any statement is executed.
This way the RLS can work with SSMS Tools Pack without any issues.
However, be careful not to add any result-set-returning statements, because those interfere with internal add-in operations.
Default Settings Deploy allows you to easily distribute a Default Settings file to
multiple users in your organization. Set up the settings you want your users to have and create
the default settings file: STPDefaults.ses in SSMS Tools->Options.
Then put that file into the SSMS Tools Pack install directory on your users' machines.
The Default Settings file will be automatically imported if its creation date is newer than
the last time a user opened SSMS. This way you can distribute it whenever you wish and it will be
automatically imported the next time a user opens SSMS. The backup of the user's current settings
is saved before they are overwritten to: c:\Users\YourUserName\AppData\Roaming\SSMSToolsPack\STPSettingsBackupForDefaultsOverride.ses.
The user has to have read permissions on the SSMS Tools Pack install directory for this to work.
SSMS Tools Pack supports built-in Accessibility Color Schemes for visually impaired users, including Windows high-contrast settings.
The settings are automatically imported from the last automated backup if it exists on the first SSMS run.
This is useful when switching between major SSMS versions where settings weren't automatically transferred.