With the release of Microsoft SQL Server Management Studio 22, we have introduced an improved solution for patching, deployment, and uninstallation.
Users are no longer required to submit an installer manually, and automatic patching is now available.
However, this change breaks the existing PatchPro update chains, and they must be manually replaced by deleting the current configurations and publishing new ones.

PatchPro Configurations
PatchPro provides three configurations for SSMS:

1. Microsoft SQL Server Management Studio (Install:Only) (x64) (EXE)

2. Microsoft SQL Server Management Studio (Upgrade:Only) (x64) (EXE)

3. Uninstall Microsoft SQL Server Management Studio 21

Recommended Migration Process (SSMS 21 → SSMS 22)
If your systems are currently running SSMS 21, we recommend the following steps:

Publish all three configurations listed above.

1. Assign Uninstall Microsoft SQL Server Management Studio 21 to all systems you plan to upgrade.

2. Assign Microsoft SQL Server Management Studio (Install:Only) to install SSMS 22 onto all systems.

3. After all systems have been upgraded and SSMS 21 has been fully replaced by SSMS 22:

   • You can delete the assignments or the entire configurations.

   • Then assign Microsoft SQL Server Management Studio (Upgrade:Only) (x64) (EXE) to enable future automatic patching.

VulnDetect Notes

To upgrade from SSMS 21 → SSMS 22, it is necessary to uninstall SSMS 21 first.
We now provide uninstall jobs for all SSMS versions.

To complete the upgrade:

1. Create an uninstall job for SSMS 21 (or any previous version).

2. Create an install job for SSMS 22.

3. Once the uninstall/install job sequence has completed, your systems will be fully prepared for future automatic patching of SSMS 22.

1. Download the latest installer from Pythons website https://www.python.org/downloads/

2. Create a new Custom Software with the latest Python installer.

3. Set the Installer Arguments to /quiet InstallAllUsers=1 PrependPath=1 Include_test=0 if you want it installed System-wide or /quiet InstallAllUsers=0 PrependPath=1 Include_test=0 if you want it installed for the Users only.

(Note: If you wish to upgrade Python you will need to choose the installer arguments according to the already installed version)

4. Make sure the installer context is set to Per User as the install won't work in SYSTEM context.
   (even if you are installing it system wide!)

5. Select the targets for Python to be installed on.

6. When Python is being installed the UAC privilege prompt will appear where the users will have to allow the app to make changes to the device. Users without local Admin privileges can't accept this prompt.

7. When the install is done, the host needs to restart for the effects of the installer to be fully implemented.

1. Download the latest version of HP Support Assistant through their website https://support.hp.com/us-en/help/hp-support-assistant

2. Rename the file spxxxxxx.exe to spxxxxxx.zip.

3. Create a text document with the following content using your favourite text editor Start-Process -FilePath InstallHPSA.exe -Argumentlist "/S /v/qn", save it as installhpsa.ps1.

4. Create a new Custom Software Deployment Configuration, set the installer as installhpsa.ps1 and add spxxxxxx.zip as an additional file. It is vital that you set the installer context as Per User as the installation won’t work properly in the SYSTEM context.

5. Once the Custom Software is deployed and the installation is commenced the UAC prompt will appear and the user have to accept it. Users without local Admin privileges can't accept the prompt.