| Platform |
How |
What happens |
| Server |
See the server upgrade chapter |
Always first. Web add-ins are served from the server and update with
it. |
| Windows |
Re-deploy the new AdaAgentSetup-<version>.exe /S
(same detection rule), or re-run the same PowerShell command |
Services are replaced at once. Locked add-in DLLs are renamed to
*.old-<timestamp> and each Office app loads the new
add-in on its next start. Leftovers are cleaned on the next install.
With tamper protection on, setup runs as SYSTEM automatically. The
existing token is kept if none is given. After the update the tray shows
“Ada was updated. Close and reopen these apps to activate the new
version: …”. |
| macOS |
Re-run the Terminal command or a new .pkg |
Setup withdraws the LaunchAgent definitions before stopping
services, so no watchdog raises a false tamper alarm. It then reinstalls
and reloads daemon → agent → helper. If setup fails midway, the previous
definitions are restored. The token is kept if none is given. |
| Web add-ins |
Nothing on clients |
The task pane loads its code network-first from the server.
Re-upload a manifest only after a key rotation or an address
change. |
