Updating LOGOS – for your IT

How to install a newer LOGOS release over the one you have, silently, without losing anything: the server first, then the PCs. (LOGOS never updates itself; the web console’s Settings > Updates says when a newer release exists.) Moving the server to another machine: section 6. A pool grown too big by a send-up of every element: section 7. The server cannot reach the LOGOS Licensing Service, or is air-gapped: section 8. Lost your only administrator: section 9.

What an update keeps, always: the server’s data folder C:\ProgramData\LOGOS Server – server.db (the people, their passwords and two-step sign-ins, the projects, rights and clearances, the licence, the sign-in settings, the audit), pools\ (all the work and its history), server.json, seal.entropy and audit.key (the sealed secrets’ keys) and backups\. None of them is an installer file: the installer never writes, replaces or removes them. On the PCs: each person’s settings, saved sign-in and files, and the organisation’s settings (HKLM\SOFTWARE\Policies\LOGOS).

Before you start: the files, the folder and the window

The commands below are written for LOGOS 1.8.1 and the folder C:\LOGOS-update\1.8.1. For another release, put its number in their place (for example 1.9.0) – type the number itself, never the words in angle brackets.

  1. Download the files. Sign in at logosmodular.com with the account that holds the licence: My Account > LOGOS licences & downloads. Download LOGOS Server for your organisation (LOGOS-Server-1.8.1.msi, the server’s installer), LOGOS Server backup script (LOGOS-Server-1.8.1-Backup.ps1, signed) and, for the PCs in section 5, LOGOS (LOGOS-1.8.1.msi).
  2. Put the two server files on the server machine, in a folder of their own: make C:\LOGOS-update\1.8.1 and copy LOGOS-Server-1.8.1.msi and LOGOS-Server-1.8.1-Backup.ps1 into it (from the PC you downloaded them on: a USB drive, a network share, or copy and paste over Remote Desktop). Any folder on the server’s own disk will do, but not C:\Program Files\LOGOS Server or C:\ProgramData\LOGOS Server – the installer and the server own those. Keep the folder after the update: section 4 uses this MSI to go back, and the installer’s log is written here.
  3. Open one administrator PowerShell on the server machine (sign in to it, or over Remote Desktop): Start, type PowerShell, right-click Windows PowerShell and choose Run as administrator. Go to the folder and check the two files are there:
cd C:\LOGOS-update\1.8.1
Get-ChildItem

Type every command in sections 1 to 3 in this window, in this folder.

1. Before: a copy of the server’s data (2 minutes)

In the administrator PowerShell, in C:\LOGOS-update\1.8.1:

powershell -ExecutionPolicy Bypass -File .\LOGOS-Server-1.8.1-Backup.ps1

(The same script is also installed as C:\Program Files\LOGOS Server\Backup-LOGOSServer.ps1 – the copy of the release you have now. -Destination D:\Backups puts the copy elsewhere.) It stops the LOGOSServer service, copies the whole data folder – with its access list – to C:\ProgramData\LOGOS Server backups\LOGOS Server <date>_<time>, checks the copy (same files, same sizes), starts the service again and waits until it answers. Exit code 0 = done. (The server’s web console shows this command line, with -DataFolder filled in when the data folder is elsewhere, under Settings > Backup – with the copy of server.db the server made itself at the last update.)

Tell the people to save their work and close the LOGOS programs for the next step.

2. The server (users are cut off for about half a minute)

In the same administrator PowerShell, in C:\LOGOS-update\1.8.1 (the two lines: the first runs the installer and waits for it, the second shows its result):

$r = Start-Process msiexec.exe -Wait -PassThru -ArgumentList '/i "C:\LOGOS-update\1.8.1\LOGOS-Server-1.8.1.msi" /qn /norestart /l*v "C:\LOGOS-update\1.8.1\LOGOS-Server-update.log"'
$r.ExitCode

It prints nothing while it works (up to a minute; see below for a failure). The installer’s log is C:\LOGOS-update\1.8.1\LOGOS-Server-update.log.

  • 0: done. 3010: done, Windows asks for a restart (not needed by LOGOS Server itself). 1603 or any other: it failed, and Windows Installer put the old version back as it was – send us the log. If the new version’s service cannot start (for example a damaged server.json), Windows Installer tries the start again several times before it gives up: the update can take about 4 minutes to fail and put the old version back. It is not stuck – wait for it. The reason is in the Event Log (LOGOS Server, event 1002).
  • What it does: stops the LOGOSServer service; replaces the program in C:\Program Files\LOGOS Server; sets the data folder’s access list on the folder and every file in it (SYSTEM and Administrators full control, the service modify, nobody else); registers the service again (as NT SERVICE\LOGOSServer since 1.4.1, automatic start, restarted after a failure); starts it. On its first start the new server copies server.db into C:\ProgramData\LOGOS Server\backups\ (named server.db.<old>-before-<new>-<time>.db; from 0.14.0, server.db.0.14.0-or-earlier-before-<new>-<time>.db) before it brings any table up to date, and writes a line in C:\ProgramData\LOGOS Server\server-updates.log and a “server-updated” row in the audit.
  • The cut-off: from the stop to the new server answering – usually 10 to 30 seconds. People stay signed in (the sign-ins live in server.db). A pool that was open in a program must be opened again (“That pool is no longer open on the server: open it again”); work not yet saved to the server is still in the program – save it again.
  • tailscale serve (or Caddy/IIS) is not affected: it forwards to 127.0.0.1:8742, and the update keeps server.json’s address and port. During the cut-off the https address answers with an error (502); then it works.
  • Not kept: a change you made by hand to the service (another log-on account, other recovery settings) or an extra entry you added to the data folder’s access list or to a file in it – the installer sets both back to its own. Note them before, and make them again after.
  • From 1.4.0 or earlier to 1.4.1 or later – the service’s account changes. The service ran as NT AUTHORITY\LocalService (an account other Windows services share); it now runs as its own virtual account NT SERVICE\LOGOSServer (no password; Windows manages it). The update takes LOCAL SERVICE off the data folder and everything in it and gives them to the new account; the sealed secrets (two-step sign-ins, the licence’s secret, the audit key, the identity provider’s secret) are sealed for the machine, not the account, and open as before. The installer’s log (/l*v) shows the access list before and after: search it with Select-String -Path C:\LOGOS-update\1.8.1\LOGOS-Server-update.log -Pattern 'The data folder','Checked:' (the log is UTF-16, which findstr does not read – it finds nothing there). Two things to look at before you update: – a poolsRoot, dataDir or auditExport in server.json on another local disk: the update adds the new account to that folder (modify) and changes nothing else there – remove LOCAL SERVICE from it afterwards if you had given it access; – one on a network share (\\host\share): the service now reaches it as the server computer’s account (DOMAIN\SERVERNAME$), where LocalService was anonymous. Give that computer account Change on the share and Modify on the folder before you update, or the server cannot open those pools (the security guide for IT, SECURITY-IT.md, published with each release).

3. Check it worked

In the same administrator PowerShell (each line’s answer is shown after it):

Get-Service LOGOSServer                                          (Status: Running)
curl.exe http://127.0.0.1:8742/v1/health                         ({"result":{"ok":true,"org":"...","version":"1.8.1"}})
Get-Content "C:\ProgramData\LOGOS Server\server-updates.log" -Tail 3   (update from LOGOS Server ... to 1.8.1: server.db copied first to ...)

(curl.exe, with .exe: in Windows PowerShell plain curl is another command.)

  • From a PC: https://<server>.<tailnet>.ts.net/v1/health shows the same.
  • The web console: Settings > Updates says “This server runs LOGOS <version>”; Audit shows “server-updated”.
  • Sign in from a LOGOS program and open a pool.

4. If you must go back

Type these in an administrator PowerShell on the server machine (as in “Before you start”).

  1. Stop the service: Stop-Service LOGOSServer.
  2. Remove the new version (an older MSI refuses to install over a newer one) – its MSI is in the folder you updated from, for example: Start-Process msiexec.exe -Wait -ArgumentList '/x "C:\LOGOS-update\1.8.1\LOGOS-Server-1.8.1.msi" /qn /norestart' (the data folder stays).
  3. Only when going back to 1.4.0 or earlier from 1.4.1 or later – do this BEFORE the older installer runs. From 1.4.1 the service runs as its own account, NT SERVICE\LOGOSServer, and the data folder and every file in it allow only that account (with SYSTEM and Administrators). 1.4.0 runs the service as LOCAL SERVICE, and its installer gives LOCAL SERVICE the data folder itself but not the files already in it: they keep the newer list, so 1.4.0’s service cannot open server.db, it does not start, and the 1.4.0 install fails and undoes itself (exit code 1603, “Error 1920 … failed to start … sufficient privileges”). So first give LOCAL SERVICE (*S-1-5-19, which works in any Windows language) the folder, and make every file follow the folder:

    icacls "C:\ProgramData\LOGOS Server" /grant "*S-1-5-19:(OI)(CI)(M)"
    icacls "C:\ProgramData\LOGOS Server\*" /reset /T /C

    The folder’s list stays protected: no Users or Everyone entry is added, only LOCAL SERVICE beside the three that are there.

  4. Install the old version from the folder of its own update (for example C:\LOGOS-update\1.8.0; keep each release’s folder for this): Start-Process msiexec.exe -Wait -ArgumentList '/i "C:\LOGOS-update\1.8.0\LOGOS-Server-1.8.0.msi" /qn /norestart', then Stop-Service LOGOSServer again.
  5. In C:\ProgramData\LOGOS Server: delete server.db-wal and server.db-shm if they are there, and put the copy from backups\ in place as server.db (or put back the whole folder that section 1’s script copied).
  6. Again only when going back to 1.4.0 or earlier from 1.4.1 or later: the older installer has set the folder’s own list (SYSTEM, Administrators, LOCAL SERVICE), but the files inside still carry the entry for NT SERVICE\LOGOSServer from step 3. Make them follow the folder again – this also takes that entry off them: icacls "C:\ProgramData\LOGOS Server\*" /reset /T /C (also needed after putting back section 1’s copy).
  7. Start-Service LOGOSServer.

The pool files need nothing: their format did not change from 0.14.0 to 1.0.0 (the release notes say so when one does), so the old version reads what the new one saved. What changed in server.db after the update (new people, rights, sign-in settings) is not in the copy.

5. Then the PCs

After the server. Through Intune / Configuration Manager / Group Policy, give them LOGOS-1.8.1.msi with the options below. By hand, on each PC: copy LOGOS-1.8.1.msi to a folder of its own on the PC (for example C:\LOGOS-update\1.8.1), open an administrator PowerShell (as in “Before you start”) and type:

$r = Start-Process msiexec.exe -Wait -PassThru -ArgumentList '/i "C:\LOGOS-update\1.8.1\LOGOS-1.8.1.msi" /qn /norestart MSIRESTARTMANAGERCONTROL=Disable /l*v "C:\LOGOS-update\1.8.1\LOGOS-update.log"'
$r.ExitCode
  • The LOGOS programs should be closed. With MSIRESTARTMANAGERCONTROL=Disable Windows Installer never closes a running program (unsaved work is safe); a file still in use is then replaced at the next restart, and msiexec returns 3010: restart that PC before using LOGOS again. Always give /norestart: without it a silent install may restart the PC by itself when a file was in use.
  • The organisation’s settings given at the first install (AUTOSAVE=0, CRASHREPORTS=0, ALLOWPYTHON=0, DATAFOLDER=..., OPENWITH=0) are kept without naming them again; name one to change it.
  • For detection rules: the product code changes with every release; the upgrade code stays {3F6B1D2A-8C44-4E3B-9A51-7D0C2E6B9F14} (LOGOS) and {6E2A9C41-3B7D-4F85-A0C6-D19E4B2F7A58} (LOGOS Server); check the version (Help > About in LOGOS, or Apps & features).
  • The order: the server first, then the PCs (a newer program may use what only the newer server has; the server’s answers only grow, so a PC still on the older release goes on working meanwhile – update them the same day).
  • The organisation file is not needed again: an update keeps the PC’s server address. It is needed again only if the server’s address changed (a move to a new machine under a new name – section 6, step 5).
  • From 1.8.0 the LOGOS programs say when the server’s Get LOGOS page offers a newer LOGOS than the PC has (“LOGOS 1.9.0 is on your server’s Get LOGOS page (this PC has 1.8.0). Close LOGOS and install it – https://<server>/get.”), a quiet line under the window’s banner that the person can close. They download nothing by themselves; where IT installs LOGOS for people, place the installer on the Get LOGOS page after the PCs are updated, or tell people the update is coming.

6. Moving the server to a new machine

The server keeps its secrets (the two-step sign-ins, the licence’s enrolment, the identity provider’s client secret, the chat tokens, the audit chain’s key, the key that signs the organisation files) sealed for its own machine. A copy of C:\ProgramData\LOGOS Server – the backup script’s too – opens on another machine with none of them readable. To move the server, use the move bundle: one file, encrypted under a passphrase you choose, that the new machine unpacks and seals again for itself. All of them move – the organisation-file signing key too, so the new server signs with the SAME key and the PCs that already trust it accept its organisation files (no new key, nobody needs to sign in again for that). The audit continues unbroken across the move, and the old server will not start again (two servers must never run with the same people and licence).

You need: the new Windows machine, the LOGOS Server MSI of the same release or newer, an administrator on both machines, a way to carry one file (a USB drive or a share only IT can read), and a passphrase of at least 12 characters (a few unrelated words). Plan for the people to be off LOGOS from step 2 to step 6 (usually under an hour).

  1. The new machine, first. Install the LOGOS Server MSI as for a new server (msiexec /i LOGOS-Server-<version>.msi /qn /norestart). Stop its service: Stop-Service LOGOSServer (an administrator PowerShell). Do not finish the web console’s set-up page on the new machine, and do not enter a setup code there – the move brings the administrators, the settings and the licence’s enrolment. (The set-up page says so too: “Moving a server here? Don’t finish this page”.) If you already did: the import in step 4 refuses (“already holds a LOGOS Server that was SET UP ON THIS MACHINE”) – run it again with --replace-data, which sets that fresh set-up aside. And if a setup code was entered there, its enrolment replaced the old server’s at the licensing service (each new enrolment replaces the one before): after the import, enrol again with a new setup code (step 6) – Refresh will not work.
  2. The old machine: stop and export. Tell people to save their work and close the LOGOS programs. In an administrator PowerShell:

    powershell -ExecutionPolicy Bypass -File "C:\Program Files\LOGOS Server\Backup-LOGOSServer.ps1" -LeaveStopped
    New-Item -ItemType Directory -Force E:\move
    & "C:\Program Files\LOGOS Server\logos_server.exe" --config "C:\ProgramData\LOGOS Server\server.json" --export-move E:\move\logos-server.logosmove

    (The backup is your way back if anything goes wrong; -LeaveStopped leaves the service stopped.) E: here is the USB drive: use a drive letter this machine has (Get-PSDrive -PSProvider FileSystem lists them) – the New-Item line makes the folder (from 1.8.0 the export makes a missing folder itself, and says in plain words when the drive is not there or the folder cannot be written). Type the passphrase twice – it is not shown. It answers “The bundle … holds this server (N files, M sealed secrets …). This server is now marked MOVED”. Read any lines under it: a pool registered from outside the pools folder (older servers allowed it) is not in the bundle – copy that file to the same place on the new machine yourself. From now on the old server refuses to start; to be tidy, also Set-Service LOGOSServer -StartupType Disabled. If the export failed (“Nothing was exported and this server is unchanged”, or “The export failed, nothing was moved”): put right what it names and run only the export line again – the service is already stopped and the backup is taken.

  3. Carry the bundle to the new machine. Give the passphrase separately (not in the same email, not on the same drive). The bundle is the whole server – people’s password hashes and every pool: treat it as you treat the backups.
  4. The new machine: import. In an administrator PowerShell:

    & "C:\Program Files\LOGOS Server\logos_server.exe" --config "C:\ProgramData\LOGOS Server\server.json" --import-move E:\move\logos-server.logosmove

    Type the passphrase. It checks the whole bundle before writing anything: a wrong passphrase (“The passphrase is wrong”) or a damaged or changed bundle (“This bundle cannot be used”) writes nothing – make a new bundle if the file was damaged on the way. Then it writes the data, seals every secret again for this machine, and answers “Imported move … the audit chain checks (N rows)”. It refuses a data folder that already holds a server’s people, projects or pools – nothing is written. The set-up page was finished on this machine (step 1): it says “already holds a LOGOS Server that was SET UP ON THIS MACHINE” – run the same command again with --replace-data; that fresh set-up is kept in C:\ProgramData\LOGOS Server\backups\before-move-<time> and the bundle’s server takes its place. If a setup code was entered at that set-up, the refusal and the import’s notes say so: the licence then needs a new setup code (step 6). --replace-data is also for a second try of the import. server.json now holds the old server’s settings (organisation, address, port, trusted proxies …) with this machine’s folders; the installer’s own is kept as server.json.before-move.

  5. Start it and give it its address. Start-Service LOGOSServer, then curl.exe http://127.0.0.1:8742/v1/health (your port if it is another). Set up the HTTPS front end on this machine as on the old one (Caddy, IIS, or tailscale serve; the certificate is the front end’s and does not move – Caddy gets a new one by itself, an organisation certificate is installed again). Then point the server’s name at the new machine (DNS, or the Tailscale machine name): with the same name, the PCs, the organisation file, the identity provider’s redirect address and Slack’s Request URL all keep working. With a new name: change the public address in the web console (Settings), send people the new organisation file (the Get LOGOS page has it), add the new redirect address in the identity provider’s app registration, and change the Request URL in the Slack app. With Tailscale on the server, turn on Run unattended (the Tailscale icon in the notification area > Preferences > Run unattended), signed in to Windows as the user who signed Tailscale in. Without it Tailscale belongs to that Windows user: tailscale run by any other account (another user’s administrator PowerShell, a scheduled task) answers “Tailscale already in use by DOMAIN\user”, and the machine leaves the tailnet – and the PCs lose the server – when that user signs out of Windows. The machine’s name: the Tailscale menu’s This device line, the admin console’s Machines page, or tailscale status --self. Keeping the old name (so the PCs and the organisation file need nothing): in the admin console’s Machines, rename the OLD machine first (e.g. logos-old, or remove it once it is off), then give the new one the old name (its row’s menu > Edit machine name); then tailscale serve on the new machine as on the old one.
  6. The licence. Sign in to the web console (the administrators’ passwords and two-step sign-ins came with the move; everyone else signs in again on their PCs). Settings > Licence > Refresh: the licence is fetched with the moved enrolment. If a setup code was entered on the new machine before the import (step 1), that enrolment replaced the moved one: Refresh says “the licensing service no longer accepts this server’s enrolment – it was REPLACED”. Then in My Account’s LOGOS Server section choose Get a new setup code (moving the server) and enter it in Settings > Licence: the licence comes back at once (the seats are the organisation’s, not the machine’s), and the old machine’s copy of the enrolment is worthless. Otherwise – Refresh worked – recommended: make the old machine’s copy of the enrolment worthless – in My Account’s LOGOS Server section choose Get a new setup code (moving the server) and enter it in Settings > Licence; the new code replaces the enrolment and the old one is no longer accepted. (Air-gapped: the entitlement file moved with the data; nothing to do until the next file.)
  7. Check. Audit > Verify: “the chain checks”; the audit shows server-move-export then server-move-import. Sign in from a LOGOS program and open a pool.
  8. Afterwards. Delete the bundle. Keep the old machine’s data folder (or the step 2 backup) for as long as your records rules ask – it is sealed for the old machine, so keep that machine (or its disk) with it if you may need to read it; then wipe the old machine. The old backups\ folder is not in the bundle (its copies are sealed for the old machine).

If you give up the move (the new machine is not ready): on the old machine run logos_server.exe --config "C:\ProgramData\LOGOS Server\server.json" --cancel-move, set the service back to Automatic and start it. Then delete the bundle – never import it once the old server has run again.

7. If a send-up copied a whole pool into another (a pool grown too big)

What happened: LOGOS Agora’s Pool > Send the selected up to another pool, with every element selected, into a pool of a higher classification, made a copy of every element in that pool – each copy with a “derived from” reference and three audit rows, about 3 kB a copy however small the element (a model’s thousands of parameters become megabytes) – and a pool never deletes anything, so the copies stayed. The pool the elements came from is not changed by it. Before any step below, back up (section 1’s script). Never delete a pool file without that backup and the administrator’s say-so.

(a) Which elements came from it. In LOGOS Agora, open the big pool as one of its Owners (the Owner right for LOGOS Agora on its project): its Audit tab lists one import row per copy – each names the copy, the pool it came from (fromPoolName) and the original – all in the one commit of the send, at the time of the accident. Pool > Check the copies against their originals lists the copies too, and each copy’s Links tab says *derived from* and where from.

(b) and (c) on the release you have now (before 1.8.0). There is no tool before 1.8.0 that takes copies back out of a pool. So:

  • The big pool holds only the copies (it was made for the send, or held nothing of its own): web console, Projects & pools > Remove beside it. The programs stop offering it and everyone who has it open is closed out; its file stays, untouched, in the pools folder (C:\ProgramData\LOGOS Server\pools\). With the backup taken, move that file out of the pools folder (to an archive you keep as your records rules ask) – that gives the space back. Nothing else is touched: the pool the elements came from still has them all.
  • It also holds its own work, and nothing was done in it since the send (its Audit tab: no rows after the send’s commit but opens): put back its file from the backup taken before the send. Stop the LOGOSServer service; rename the pool’s file in the pools folder (add .after-send); copy the same file from the backup (C:\ProgramData\LOGOS Server backups\LOGOS Server <date>_<time>\pools\) in its place; start the service; open the pool in Agora and check it (Audit > Verify). Keep the .after-send file until you are sure, then move it out of the folder.
  • It holds work done since the send: keep the pool as it is – retire the copies you do not want (they stop being listed; the file stays big), and take them out with 1.8.0’s clean-up below. Do not restore an older file over work done since.

On 1.8.0. The web console, Projects & pools > Clean up copies beside the pool: it lists the sends into it (from its audit: when, by whom, from which pool, how many); pick the send, type the reason and the pool’s name. The server closes everyone out of that pool, copies its file to backups\ first, takes the copies out (with their references, the links to them and the files nothing else names – a copy someone has changed since is kept, and named), then compacts the file (SQLite’s VACUUM) and says the size before and after. The pool the copies came from is not touched. The pool’s audit log keeps its record of the send and of the clean-up (about 1.4 kB a copy; the record is never taken out) – in the test that reproduces it, a 168 kB pool grown to 1.62 MB came back to 0.84 MB. The server’s audit keeps pool-copies-removed (who, when, why, the sizes, the backup). And from 1.8.0 it cannot happen by one click:

  • only an Owner (the Owner right for LOGOS Agora on the project) raises a pool’s classification or sends elements up into it from a lower one – Full may still add new elements and files, and copy elements of the same classification;
  • the send says first exactly what it will do (how many, copied or moved, into which pool, how much) and asks; 50 or more elements, or every element listed, need the number typed;
  • the owner can move them (the originals retired, with a note) instead of copying, each file goes once, an element already there unchanged is not copied again, and the receiving pool’s owner can Undo the send the same day (Pool > Undo a send-up into this pool);
  • only the administrator lowers (de-classifies) a pool, in the web console (Projects & pools > De-classify: the reason, the pool’s name typed, two-step sign-in for an ITAR/CUI pool; audited) – and only after your organisation’s review. A pool FILE on a PC with no server is lowered by its owner (the person who made it), in Agora, the same way: the reason and the pool’s name typed, audited. Lowering changes the level only – nothing is copied, moved or deleted.

8. When the server cannot reach the LOGOS Licensing Service (1.8.0)

An online LOGOS Server fetches its licence from licensing.logosmodular.com (HTTPS, port 443, through the proxy Windows uses) once a day. If it cannot – the service down, DNS, a firewall, a proxy asking for a sign-in, a proxy that inspects HTTPS, a slow network:

  • Nothing stops at once. The licence the server holds is good 14 days from its last good fetch. A restart, an update (above) or a reboot changes nothing: the copy is in server.db. The server tries again every hour by itself.
  • Settings > Licence (web console) shows the last error in words – for example “the name licensing.logosmodular.com could not be found (DNS)”, “no connection could be made … (refused or blocked: check the firewall allows HTTPS out, port 443, and the proxy)”, “the TLS (HTTPS) security check … failed (… a proxy that inspects HTTPS: trust its root certificate, or exempt …)”, “a proxy … asks for a sign-in (HTTP 407)” – with the Windows error number for you. Refresh tries at once.
  • After 3 days the Licence card warns, and the Windows Event Log (Application, source “LOGOS Server”) says it once: event 4003 (Warning). The server sends no email: forward the Event Log to your monitoring to be told.
  • In the last 3 days every person signed in to a LOGOS program (Systema, Agora, Hodos, Kanon) sees a banner under the window’s pool banner: “Sign-ins to LOGOS stop on DATE unless the LOGOS server reaches the LOGOS Licensing Service again – your administrator has been told.” They can hide it until the program starts again; it goes by itself once the server reaches the service. It tells them you know – nothing for them to do.
  • After 14 days the LOGOS programs cannot sign in (event 4001, Error); people already signed in keep working until their session ends (at most 12 hours); the web console, the data and the accounts are untouched. The programs and the console say the licence has not ended – the server could not confirm it – and what to do.
  • What to do: let the server reach licensing.logosmodular.com:443 and press Refresh – or, while it cannot, download the entitlement file in My Account (logosmodular.com) on any PC with the internet and load it in Settings > Licence (good up to 400 days; the daily fetch takes over again once the service is reached).
  • When the service is reachable again the server recovers by itself within the hour – no restart (event 4004).
  • The server’s clock must be right: set back more than 48 hours, it refuses program sign-ins until it is set right (Windows: Settings > Time > Sync now).
  • A clock that ran AHEAD (a mistyped year, a bad clock battery) and was then set right reads as “set back” – the server has already seen the later time – and the programs stay refused until real time catches up. The way out: web console > Settings > Licence > The clock was wrong (shown only then): it shows the latest time the server saw and the time now, asks why, and asks for your two-step code; it accepts the current time and the programs sign in at once. If the console cannot be reached, on the server machine in an administrator PowerShell: logos_server --config server.json --clock-was-wrong shows the two times, and logos_server --config server.json --clock-was-wrong --reason "the year was typed as 2027; set right" does it (the running service takes it at once). It is recorded and reported, never hidden: the clock-back tamper flag stays, the reset is a flag of its own sent to LOGOS Modular Systems with the next licence refresh (air-gapped: in the licence report), and the audit and the Event Log (event 4008) have who, when and why. At most once a day; refused when the clock is not behind.

An air-gapped server ("airGapped": true) never calls out: it runs on the entitlement file from My Account, good to the earliest of 400 days, the term’s end and the AI add-on’s end. Since 1.8.0 the Licence card warns 30 days before the file’s end and before the term’s end (event 4007, Warning); load the new file before then. Named seats and the 30-day rule work the same offline. In the file’s last 3 days the programs show their users the banner too (“… unless your administrator loads a new entitlement file …”), and in the term’s last 3 days when it was not renewed. Details: docs/specs/licensing.md “When the Licensing Service cannot be reached”.

9. Lost your only administrator (1.8.0)

When the only person who could sign in to the server’s web console as an administrator has left, cannot be reached, or has lost both the password and the phone, get an administrator back like this. There is no back door: it takes a Windows administrator on the server machine (you) and a one-time recovery code from your organisation’s licence holder – or from LOGOS Modular Systems if the licence holder is the person who left. (Someone else can still sign in as an administrator? They do it in the console instead: People & rights > Administrators, or --reset-mfa NAME for a lost phone.)

  1. What the code is checked against. On the server machine, in an administrator PowerShell:

    & "C:\Program Files\LOGOS Server\logos_server.exe" --config "C:\ProgramData\LOGOS Server\server.json" --recover-admin NAME

    NAME: the account to recover – the old administrator’s (its password and two-step sign-in are replaced) or a new name (it is made, as an administrator). With no code it changes nothing: it prints the organisation, whether the server is enrolled online (its enrolment id) or licensed by file (air-gapped), and the administrator accounts there.

  2. The code. The licence holder signs in to My Account at logosmodular.com > LOGOS licences > LOGOS Server > Recover a server administrator, types NAME (tick “The server is air-gapped” if step 1 said “licensed by file”), and gets the code – 23 groups of 6 letters and digits – shown once, and as a file to download. Bring it to the server machine (the file on a USB stick, or copy the text). The licence holder is the person who left? Write to support@logosmodular.com from your organisation’s address, with what step 1 printed: we check who is asking and their authority first – a call back to a number we already have on record for your organisation, or a request on your letterhead signed by an officer – and then send the code. The code works once, for 24 hours, only on this server and only for NAME.
  3. Recover. Still in the administrator PowerShell:

    & "C:\Program Files\LOGOS Server\logos_server.exe" --config "C:\ProgramData\LOGOS Server\server.json" --recover-admin NAME --code D:\LOGOS-admin-recovery-code.txt

    (or --code followed by the code itself, dashes and all). No internet is needed, and the service keeps running. It prints a one-time set-up link (24 hours). If it refuses, it says what is wrong – a typing mistake, another organisation’s or server’s code, another account name, run out, used already – and changes nothing.

  4. Set it up. Open the link in a browser that reaches the console (or send it to the new administrator by a channel you trust – whoever opens it sets the password): choose the password and, on an https:// server, set up two-step sign-in with an authenticator app. Then sign in to the console.
  5. Afterwards. Every administrator sees a notice of the recovery in the console for 30 days; it is in the audit (admin-recovered), the Windows Event Log (event 2004) and your log collector’s export; and the licence holder was emailed when the code was issued. Remove the old administrator’s account if its person has left (People & rights > Administrators > Remove), and add a second administrator at once, so it does not happen again – the console shows a notice while only one can sign in.

What the code does not do: it opens the console, never the data. The data files are protected by who holds Windows administrator rights on the server machine, its disk encryption and the data folder’s access list – the security guide’s “Recovering a lost server administrator” (the security guide for IT, SECURITY-IT.md, published with each release).