Deploying Syncture
Syncture installs for each Windows user, with no administrator rights, from one file that stays the same for every release. This is how to deploy it silently to every computer that runs Revit.
The file
Package it once.
https://downloads.syncture.com/Syncture-Setup.exeSyncture-Setup.exe holds no version of Syncture. When it runs, it reads which release is current, downloads that release's installer, checks its size, its SHA-256 and its signature by DI Osama Almughanni, BSc, and runs it. So the file you package today installs whatever is current on the day it runs, and the package never needs replacing.
After that, Syncture keeps itself current from inside Revit. It looks forty seconds after Revit starts and every two hours, puts a new version beside the one in use, and every Revit loads it at its next start. Nobody at a desk is asked anything.
Exit codes
What your deployment tool reads when it has run.
- 0
Done.
- 1
Failed. The log says why.
- 2
Revit is open, so Syncture could not be removed. Retry.
- 3
No Revit that Syncture supports is on this computer. A required assignment is offered again within about a day, so a Revit installed later still gets Syncture.
- 4
It ran as SYSTEM or another service account for one person. Run it in the user's context, or add --machine.
- 5
syncture.com could not be reached. Retry.
- 740
--machine without an administrator. Run it elevated, or as SYSTEM.
- 1602
The administrator prompt was cancelled. Nothing was changed.
- 1618
Another Syncture install is running on this computer. Retry.
Every switch, where each kind of install puts things, and commands to copy are in Command line.
Intune
Detect that Syncture is there, never which version: it updates itself, and a rule that names a version makes the tool install it again and again.
- App type
Windows app (Win32), with Syncture-Setup.exe packaged by the Microsoft Win32 Content Prep Tool.
- Install command
Syncture-Setup.exe --silent
- Uninstall command
Syncture-Setup.exe --uninstall --silent
- Install behavior
User. Syncture installs into the person's own profile and their own Revit add-in folders, so it has to run as them.
- Return codes
Add 2 and 5 as Retry, and 3 and 4 as Failed. 1618 is already Retry.
- Detection rule
Registry, key exists, on the key below.
- Assignment
Required, to the groups of people who use Revit.
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\SynctureConfiguration Manager
- Deployment type
Script installer, with Syncture-Setup.exe as its content.
- Installation program
Syncture-Setup.exe --silent
- Uninstall program
Syncture-Setup.exe --uninstall --silent
- User experience
Installation behavior: Install for user. Logon requirement: only when a user is logged on.
- Detection method
Registry, HKEY_CURRENT_USER, the key below without its hive, which must exist.
- Return codes
Add 2 and 5 as Fast Retry. 1618 is already Fast Retry.
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\SynctureFor everyone on a computer
One install per computer, shared by every Windows account on it, and kept current by Windows.
With --machine, the program goes into %ProgramFiles%\, which only an administrator can change. Revit finds it through Autodesk's folder for add-ins every account loads, which moved: %ProgramFiles%\ for Revit 2027 and later, which ignores the old one, and %ProgramData%\ for 2026 and earlier. Syncture writes each release's manifest where that release reads it. The publisher is trusted for the whole computer, and Installed apps lists it once, for everyone.
- Install command
Syncture-Setup.exe --silent --machine
- Uninstall command
Syncture-Setup.exe --uninstall --silent --machine
- Context
Intune: Install behavior System. Configuration Manager: Install for system, whether or not a user is logged on.
- Return codes
As above. 740 means it did not run as an administrator or SYSTEM.
- Detection rule
Registry, key exists, on the key below. In Intune, not associated with a 32-bit app.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\SynctureA Revit started by somebody without administrator rights cannot write to Program Files, so this install is kept current by one task in Task Scheduler, Syncture Update. It runs the installed Syncture-Setup.exe with the install command above, as SYSTEM, every two hours and after Windows starts, proves every file by its signature, and puts a new version beside the one in use. Each Revit loads it at its next start. Removing Syncture removes the task. To decide when updates arrive, hold a version with TargetVersion below, or disable the task.
Revit loads an account's own Syncture.addin instead of the one for everyone, so the two never stand side by side. An install for one person is refused on a computer where Syncture is installed for everyone, and any account that installed its own steps aside the next time its Revit starts. The window of Syncture-Setup.exe offers the same choice, under Install for, and switches either way.
Holding a version
Every computer follows the current release unless you say otherwise. To hold an estate at one version, set TargetVersion, a REG_SZ under the policy key below, to a published version such as 1.0.120, by Group Policy or Intune. Every install and every update then puts that version in place, older or newer. Delete the value and each computer returns to the current release at its next look. A value that is not a published version is refused, and nothing changes.
HKLM\SOFTWARE\Policies\SynctureComputers that only run allowed programs
Syncture-Setup.exe is the one program that starts. It runs the release's installer inside its own process, and Revit loads the add-in from %LOCALAPPDATA%\, or for everyone from %ProgramFiles%\, which AppLocker's default rules already allow. Every file is signed by DI Osama Almughanni, BSc through Microsoft's Artifact Signing, which renews its certificates every few days, so allow the publisher and never a single certificate.
In AppLocker, that is a publisher rule for this publisher:
O=DI Osama Almughanni, BSc, L=Wien, S=Wien, C=ATIn App Control for Business, it is a signer rule on the identity every one of our certificates carries:
1.3.6.1.4.1.311.97.165444369.877520527.440914597.660676320Workspace keys
An encrypted workspace needs its key on every computer before anybody publishes into it. The same file deploys and checks keys, and Deploying a workspace key says how.