1. Download the latest version of the SafeSend PC add-in above
2. Customize as desired and store settings by creating a custom MSI installer
   • Refer to Related Articles for direct links to other processes pertinent to the one detailed in this article.
3. Choose the desired existing endpoints and run the installer or deploy via GPO over your existing, older version of SafeSend
   • Existing licenses and settings will be carried over automatically

The latest version of SafeSend PC add-in is now deployed.

The instructions below were written as a general guide for the .NET CORE 6.0 capable web server of your choice.

1. Create a new server with the latest version of SafeSend in the host of your choice
2. Copy settings to the new version:
   1. If using Azure:
      1. On the source/old SafeSend App Service, click Configuration->Application Settings->Advanced Edit
      2. Select all json text and copy
      3. On the destination/new SafeSend App Service, click Configuration->Application Settings->Advanced Edit
      4. Select all json text and paste the previously copied text in its place
      5. Click OK
      6. Click Save  
   2. If you've configured using settings.json:
      1. Open your existing settings.json file and open the newest version of the settings.json file for comparison
         1. You can open both in any text editor, placing the two documents side-by-side, or...
         2. You can open both files in a text compare tool, which will highlight the differences
      2. Copy your existing configuration over to the new settings.json, setting by setting
         • This may seem tedious, but it allows you to keep your existing configuration without losing all of the new settings/features within the updated settings.json file
3. Side load or deploy to your test users, then verify the latest version of SafeSend is working by navigating to <yourWebURLhere>/manifest
   • Make sure that you remove the old manifest for the test users first, otherwise, you could get double-prompted
   • To enable debug mode within your web client, you'll need to use /manifestlog instead; visit Web Add-in: Debug Mode for full details
4. Once you're satisfied with your test deployment, remove the previous version of Safesend for everyone else
   1. If you’re using Exchange Server, deploy the latest version as desired
   2. If you’re using Exchange Online, update your existing web add-in manifest.xml with the manifest file you tested with above in Step 4
      1. Please note, if you get an ID mismatch error, update the ID tag in the manifest.xml file before attempting to upgrade SafeSend again
      2. Once SafeSend is updated in Exchange Online, it could take up to 12 hours to propagate; the logs of the old version should be checked before shutting down the server to verify that there are no clients still using the old version

The SafeSend Web add-in has successfully been updated.