Release notes.

• Settings → Server has a single Server FQDN. It is the console’s name, the name SCEP, EST and the revocation endpoints use, and the address agents are given, so a server in a public cloud is reached by its agents on its public name.
• Agents keep the name they were installed with, so changing the Server FQDN later means re-installing or re-pointing them.

Installers

• A custom install folder outside Program Files is now restricted to SYSTEM and Administrators, with read and run access for users, on every install, upgrade and repair. It used to inherit its parent folder’s permissions.
• A repair leaves existing configuration files as they are, and keeps the bundled PostgreSQL database: if its program files or service are damaged, the repair rebuilds them around the existing data.
• Upgrading the Windows agent keeps every setting you edited by hand and only adds new ones.
• A custom install folder is remembered across a major upgrade, for the server and the agent.
• Uninstalling the server removes its inbound firewall rules.

Console

• When the server’s FQDN changes, a self-signed console certificate that no longer names it is replaced, on save and at startup. Uploaded, ACME and deployment-pushed certificates are left as they are.

• The licence agreement is now version 1.4: an installation is one deployment of CertOps, activated with one licence key, together with backup copies of it. Installations that accepted version 1.3 ask an administrator to accept 1.4 once in the console.

• Settings → Server has a single Server FQDN. It names the console’s certificate, self-signed or ACME, drives hostname pinning, and is the server address the Deploy page, push installs and enrolment files give agents. Agents keep the address they enrolled with, so changing the Server FQDN means redeploying them.

• During an upgrade, setup now stops the server before the bundled database. Agents that check in while it runs no longer receive server errors; they reconnect once the server has restarted.

• One setup MSI installs the server, its bundled PostgreSQL database and the agent installer. Deploy agents from the console’s Deploy page.
• When an administrator signs out of an RDP session on a managed machine, it signs its configured account back in without a reboot. Windows 10 and 11 allow only one active session, so if you connected as a different account, sign the kiosk account’s disconnected session off first (Task Manager → Users), then sign out.
• With a self-signed console certificate, the certificate follows a change to the External Server FQDN.
• Console confirmations appear inline next to the button, not as browser pop-ups.
• A paid edition takes effect after one successful activation against our licensing service (EULA clause 8).

• The setup and the bundled agent installer carry licence agreement version 1.4: an installation is one deployment of Autologon Manager, activated with one licence key, together with backup copies of it.
• The agent installer bundled with the server is now version 1.0.4.

The Skyrsoft website is live, with a page for each product.