Uninstalling 1E Platform

TeamViewer DEX Platform 26.5 | 1E Platform 23.11 | 1E Platform on-premises 9.x

Follow this step-by-step guide to safely uninstall the 1E Platform. Learn how to remove core components, clean up residual files, and ensure a smooth decommissioning process for your 1E environment.

Uninstalling every 1E server component

The 1E Server component can be uninstalled at any point as long as SLA is not installed. SLA has a dependency on 1E Server. If ActiveEfficiency Server is installed (because it was not removed when 1E was upgraded), it can be uninstalled at any point. If you use 1E Server Setup for uninstalling, it will automatically enforce dependencies and uninstall components in the correct order.

Use 1E Server setup to uninstall 1E instead of Windows Programs and Features appwiz.cpl, this should not require a reboot.

1E Server Setup is the recommended method of uninstalling all or individual components instead of using the Windows Control Panel. This is because 1E Server Setup can undo any changes that were done after deploying the components, which would not be undone by the standard application uninstaller.
Before uninstalling, make a backup copy of the installation folder.
The BI (Business Intelligence), SLA (Software Lifecycle Automation) and Catalog components have dependencies and should be uninstalled in the following order:
1. BI
2. SLA
3. Catalog

After uninstalling the 1E server

Uninstalling leaves behind the following artifacts. Like other Windows installers, uninstalling will leave behind any files, folders, and registry entries created after installation.

Location	Artifacts	Recommendation
Installation folder	You may find web.config files if IIS settings were modified after the previous installation.	Delete or rename the installation folder.
Logs folder	Log files remain.	Delete or rename the logs folder. If it is not deleted, a new installation using the same logs folder will continue to use the old log files.
Registry	Encrypted license details remain in HKLM\SOFTWARE\1E\Tachyon\LicData	The 1E registry key can be deleted or left. It is overwritten by the next installation.
SQL Server	TachyonMaster and TachyonResponses databases, as well as any databases used by additional installed components (Catalog, SLA), will remain at their corresponding SQL instances.	The databases can be deleted. If not deleted, the 1E Server installer provides an option to drop old databases or use them.

Uninstalling 1E Client for Windows

Manual uninstallation

1E Client can be uninstalled manually by using Windows Apps and Features, appwiz.cpl. A reboot is not normally required.

Disabling a feature or client module

Refer to Reconfiguring 1E Client for examples of how to use the -reconfigure command-line to reconfigure the 1E Client.

Uninstallation using the Windows Installer

1E Client can be uninstalled automatically by using a Windows Installer command line, where the {product code} is dependent on the version of the 1E Client. The example below also includes switches that prevent prompting and restart and creates a log file.

Copy

msiexec /x {BF6F5FA9-64C8-4B72-A6B6-14A582BF96B8} /qn /norestart /l*vx C:\Windows\temp\1EClient-uninstall.log

Tidy up after uninstallation

After uninstallation of 1E Client, the following is left behind. As with other Windows installers, uninstallation will leave behind any files, folders, and registry entries that were created after installation.

HKLM\SOFTWARE\1E\Common and HKLM\SOFTWARE\1E\NightWatchman are used by the 1E NightWatchman Agent, previously part of the 1E Agent.

Location	Artifacts	Recommendation
Installation folder	None.
Logs folder	Log files remain.	The log files can be deleted or renamed. If not deleted, then a new installation that uses the same logs folder will continue to use the old log file.
Client\Persist folder remains.	Leave this folder which contains status information about current instructions. The Persist folder should be deleted only if you do not intend re-installing the 1E Client with 1E enabled, or when preparing Sysprep and OS image, refer to Deploying 1E Client on Windows.
1E client registry	HKLM\SOFTWARE\1E\Client\Persist	This registry exists if the client feature of the 1E Client is enabled. It is used to keep a record of hash values for its persistent storage files, which includes status information about current instructions. This registry key should be deleted only if you do not intend re-installing the 1E Client with 1E enabled, or when preparing Sysprep and OS images, refer to Deploying 1E Client on Windows.
Content Distribution Cache	%ALLUSERSPROFILE%\1E\NomadBranch	The folder should be deleted only if you do not intend re-installing the 1E Client with Content Distribution enabled. Downloaded content is retained so that if Content Distribution client is re-enabled it will be scanned and re-registered, to make available for peer sharing with other Content Distribution clients.

Uninstalling 1E Client for non-Windows

macOS uninstallation

To uninstall the 1E Client from a macOS device invoke the uninstall.sh script from within a sudo bash script. uninstall.sh is available within the scripts directory of the Apple Disk Image (dmg) file of the macOS 1E Client. Alternatively, enter the following commands inside a sudo bash shell:

Copy

bash$ cd /Librarybash$ pkgutil --only-files --files com.1e.pkg.1E.Client | tr '\n' '\0' | xargs -n 1 -0 rmbash$ pkgutil --forget com.1e.pkg.1E.Client

Linux uninstallation

The following command line can be used to uninstall the 1E Client on Linux:

Copy

sudo rpm -e 1e.client

Uninstallation will leave behind files, folders, and registry entries that were created after installation:

Location	Artifacts	Recommendation
Installation folder	None.
Logs folder	Log files remain.	The log files can be deleted or renamed. If not deleted, then a new installation that uses the same logs folder will continue to use the old log file.
Client\Persist folder remains.	You should keep the Persist folder, which contains status information about current instructions, only if you intend to re-install the 1E Client.