Use the approved 4.1.0 installer for your edition and confirm the version shown in the installed application. Published package availability is shown in Downloads & beta access.
Activate the selected profile
In the MSP client, open Configuration > Security & Experience. Select Standard, Enhanced, High Assurance or DoD-Aligned, then select Turn Secure Communication ON & Verify. The 4.1.0/4.1.0 workflow applies the selected client/server profile, waits for a required server restart and performs staged DNS, TCP, TLS, API and security diagnostics. If OFF was selected, the ON action uses Enhanced.
Do not rely on a saved dropdown value as proof of protection. The displayed ON state must follow successful verification of the server's effective profile and encrypted transport. Secure profiles also have database and protected-working-data requirements; HTTPS alone is not sufficient evidence of all protections.
Recover from a profile mismatch
4.1.0 distinguishes an invalid or revoked API key from a mismatch between a saved client signing profile and the server's active mode. Use the application's activation/verification action with the authorized key. It checks the server's current mode before applying a profile change and validates the final connection after restart. Do not rotate keys or turn security off merely to bypass an unexplained mismatch.
Troubleshoot by stage
DNS: confirm the configured hostname resolves to the intended server. TCP: confirm the intended service port is reachable under the approved firewall rules. TLS: check trust, hostname matching and certificate validity. API authentication: check that the API key is valid and not revoked. Compatibility/profile: confirm the server/client compatibility and requested mode. Record the exact failing stage and time for Support.
Turning protection off
The OFF action requires an explicit confirmation and applies to both client and server. Treat it as an approved configuration change, not a routine fix for connection problems. Retest the final state and retain the change record.
Evidence handling
Keep application-managed protected key material with the corresponding backup. Never publish a configuration bundle that includes secrets. Send Support a sanitized diagnostic bundle only after reviewing its contents.