Siberson Veriket Endpoint Agent Installation For Windows

Contents

1. Overview

2. Prerequisites

3. Security Software Exceptions (AV / EDR / XDR)

4. Installation Package Structure

5. Installation Process

6. Post-Installation Verification

7. Operational Validation

8. Silent / Enterprise Deployment Notes

9. Troubleshooting

‌

1. Overview

This guide explains how to install the Siberson Veriket Data Classification Endpoint Agent on Windows endpoints. The endpoint agent is deployed together with a configuration file and, once installation completes successfully, the workstation should display the core Veriket runtime components in Task Manager.

The document is intended for administrators performing manual rollout, pilot deployment, controlled validation, or preparing a standardized enterprise packaging workflow.

| Important
Keep the installer package and Config.ini file in the same directory during deployment.
Run the installation with administrative rights.
If a third-party AV, EDR, XDR, or similar endpoint protection stack is active, define the required allowlisting / exclusions before rollout. | | --- |

‌

2. Prerequisites

Before starting the installation, confirm the following baseline requirements:

·         Supported Endpoint: A supported Microsoft Windows endpoint with x64 architecture.

·         Administrative Access: The account performing the installation must have local administrator privileges.

·         Disk Capacity: Sufficient free disk space must be available for the package extraction, installation, and runtime files.

·         Network Reachability: The endpoint must be able to reach the relevant Veriket backend / management environment defined in the deployment configuration.

·         Deployment Files: The installation package and Config.ini file must be present together in the same folder.

·         Change Window: The installation should be executed during a controlled support window if endpoint security products are known to inspect new installers aggressively.

3. Security Software Exceptions (AV / EDR / XDR)

Endpoint security tools may inspect or interrupt legitimate Veriket installation and runtime activities. In environments protected by Antivirus (AV), Endpoint Detection and Response (EDR), Extended Detection and Response (XDR), Host Intrusion Prevention (HIPS), or application control platforms, the Veriket agent should be allowlisted before deployment to avoid false positives, quarantine actions, incomplete installation, or unstable runtime behavior.

The recommended scope is as follows:

‌

Operational recommendation: validate exclusions on a pilot machine first, then monitor the endpoint protection console for any detection, prevention, or quarantine activity during installation and first startup.

4. Installation Package Structure

The supplied installation folder contains two required files:

·         Veriket.Agent.Install.vx.xx.xx.x64.msi: Windows Installer package for the endpoint agent.

·         Config.ini: Deployment-specific configuration file used during installation and first-time connection.

The Config.ini file is a mandatory companion file. It should remain in the same folder as the MSI package during deployment. The configuration file is typically pre-generated by the administrator or Siberson support and should not be edited unless explicitly instructed.

‌

Figure 1. Installation package showing the Veriket MSI package together with Config.ini in the same directory.

5. Installation Process

5.1 Prepare the Package

1. Copy the installation package to a local or approved software distribution directory on the target endpoint.

2. Confirm that both deployment files are present in the same folder.

3. If required by your environment, perform the rollout from an elevated command session or via software distribution tooling running with administrative context.

5.2 Launch the Installation

4. Double-click the MSI package or execute it through an elevated administrative context.

5. If Windows or endpoint protection prompts for approval, allow the package to continue.

6. Wait while Windows starts configuring the Veriket Agent.

‌

Figure 2. Windows begins configuring the Veriket Agent after the MSI package is launched.

5.3 Monitor Installation Progress

During installation, Windows displays a progress dialog while the Veriket components are copied, registered, and initialized. Depending on workstation performance and endpoint security inspection overhead, the elapsed time can vary.

‌

Figure 3. Installation progress dialog for the Veriket Agent.

·         Do not remove the Config.ini file during installation.

·         Avoid interrupting the workstation or forcibly terminating the installer session.

·         If the progress window stalls for an unusual duration, first review whether AV / EDR activity is blocking the package.

5.4 Completion Expectations

Once installation completes, the Windows Installer session should close normally. In tightly controlled environments, there may be a short delay before all Veriket background components initialize and appear in Task Manager.

6. Post-Installation Verification

After installation, verify that the Veriket runtime components are active on the endpoint.

‌

Figure 4. Task Manager showing Veriket background processes running after installation.

6.1 Check Runtime Processes

Open Windows Task Manager and confirm that the following background components are visible:

‌

·         CPU and network utilization should typically remain low when the endpoint is idle.

·         A short stabilization period immediately after installation is normal.

·         If one or more Veriket processes do not appear, review installer elevation, endpoint protection logs, and local Windows event records.

6.2 Verify Endpoint Registration

If your Veriket environment includes a central administration or policy management console, verify that the newly installed endpoint becomes visible after policy synchronization. The exact navigation path can differ by deployment model, but the validation objective remains the same: the endpoint should register successfully and be manageable from the platform.

7. Operational Validation

After the agent is installed and running, complete a short validation cycle before broad rollout:

7. Confirm that no AV / EDR console detections were triggered by the installer or runtime components.

8. Verify that the endpoint remains stable after logoff, reboot, and user sign-in.

9. Perform a controlled classification-related test according to your internal Veriket policy set.

10. Confirm that policy communication and endpoint visibility remain stable over time.

8. Silent / Enterprise Deployment Notes

Because the supplied installer is an MSI package, enterprise rollout can typically be standardized through common software distribution tooling. Any final command line should be validated in your own environment before mass deployment.

·         Typical Silent Install Pattern: msiexec /i "Veriket.Agent.Install.vx.xx.xx.xx.x64.msi" /qn

·         Typical Logging Pattern: msiexec /i "Veriket.Agent.Install.vx.xx.xx.xx.x64.msi" /qn /L*v "C:\Temp\VeriketInstall.log"

·         Packaging Reminder: Place Config.ini in the same working directory or package source used during deployment.

·         Distribution Tools: Group Policy Software Installation, Microsoft Intune, Microsoft Configuration Manager, or approved third-party deployment tooling may be used depending on enterprise standards.

| Packaging Note
Silent deployment behavior can differ if the MSI package depends on deployment-specific transforms, properties, or external configuration logic.
Run a pilot deployment first and confirm the exact packaging standard with the Siberson delivery or support team. | | --- |

‌

9. Troubleshooting

9.1 Config.ini Is Missing or Not Detected

·         Cause: The configuration file is not in the same folder as the MSI package or has been renamed.

·         Resolution: Move Config.ini back into the same directory as the installer and retry the installation.

9.2 Installation Starts but Does Not Complete

·         Cause: Local security controls, application control policies, or insufficient privileges may be interrupting the installer.

·         Resolution: Re-run with administrative rights, review AV / EDR detections, and verify that the package is allowlisted.

9.3 Veriket Processes Do Not Appear After Installation

·         Cause: Startup components may be blocked, quarantined, or not initialized correctly.

·         Resolution: Review Task Manager, Windows Event Viewer, and the endpoint security console. Reboot the endpoint if required by internal policy and validate again.

9.4 Endpoint Does Not Become Visible in Central Management

·         Cause: Connectivity, policy, or configuration alignment issues may prevent successful registration.

·         Resolution: Verify network reachability, confirm that the correct Config.ini was used, and review the backend console or deployment logs.

9.5 High Delay During Installation

·         Cause: Real-time inspection from security software may be scanning the installer and newly created components.

·         Resolution: Re-check allowlisting definitions and validate the rollout on a pilot machine with monitoring enabled.

Document Closeout

This document is intended to serve as an operational installation baseline for the Siberson Veriket Data Classification Endpoint Agent on Windows. Administrators may extend it further with environment-specific command lines, management console screenshots, policy test steps, or standard operating procedure references.

Last updated: 2026-04-22