2.5Changing the configuration later

To change any setting made by the wizard, run it again from Start > SYNERGY Management Gateway Setup. It recognises the existing installation and shows Reconfiguring an existing installation. Secrets and the administrator account are left alone.

Keep these points in mind:

• The wizard rewrites appsettings.Production.json from the values on its pages. Apart from the request body limits, the pages start from the product defaults, not from your current file. Go through every page and re-enter the values that differ from the defaults, including the public base URL, the allowed origins and the database. Settings that were added to the file by hand and are not offered by the wizard are not carried over either; copy them back from the backup. The previous file is kept as a timestamped backup (appsettings.Production.<timestamp>.bak.json) in the same folder, which you can use for comparison.
• Secret fields are empty and are left unchanged unless you type or generate a new value.
• Set Windows sign-in to Unchanged unless you want to change the IIS Windows authentication settings.
• Applying restarts the IIS services and the application pool, which briefly interrupts users of every site on the server.
• The rewritten file no longer contains the sections earlier versions of the wizard wrote for the directory client, licensing, feedback and usage statistics. Two of them can change behaviour when they disappear:
• Directory client tuning. Until somebody saves the Directory client screen, the product reads these values from the configuration file. If they differed from the defaults, open Directory › Directory client and select Save current values before you run the wizard again (Chapter 5, Before the first save in Directory client settings), so the values are kept in the database; otherwise the product falls back to the built-in defaults (3 attempts, 1000 ms, health checks on, user, computer, group, organizationalUnit).
• Feedback and usage statistics. If an earlier wizard switched off feedback or usage statistics in the file, re-running the wizard removes that setting and the product's defaults apply: feedback on, and usage statistics collected unless an administrator has answered on the Licence screen. Answer the usage statistics question on the Licence screen; to keep feedback off, add "Feedback": { "Enabled": false } to appsettings.Production.json by hand after the wizard has run.

Many settings are not in the wizard at all and are changed in the console instead: directory connections, the directory client settings, single sign-on, email, MCP server settings, telemetry export, update schedule and usage statistics consent.

Upgrading to a new version

You can upgrade by running the MSI of the new version, or let the update agent install it for you (see the next section).

To upgrade by hand:

1. 1Read RELEASE-NOTES.md and KNOWN-LIMITATIONS.md of the new version.
2. 2Back up the product's database. Database changes only go forward; an older version cannot run against a database that a newer version has upgraded, and the installer cannot put a previous version back.
3. 3Run the new Synergy.ManagementGateway.msi on the server as administrator.
4. 4When it finishes, open the console and check the version in the About dialog.

An upgrade replaces the program files but leaves the configuration file, the web.config files and the secrets untouched, so you do not need to run the setup wizard again. The application upgrades its database tables the first time it starts.

Important: If you have entries in the kill switch lists (page 8), check them against the release notes before upgrading. If a release renames an operation you have disabled, the application refuses to start until the entry is corrected. The start-up log (C:\Logs\startup-*.log) names the entry that matches nothing and suggests the closest valid one.

Installing an older version over a newer one is blocked by the installer.

Tip: Users who had the console open during an upgrade should reload the page. A browser tab left open across an upgrade may stop responding to menu clicks until it is reloaded.