Cogent install V 11 remote config and as a service 2025 (update 26.11.2025 admin pass)

Download and run

Select all

Hm,

On start up

Start updated 26.11.2025 NB this comes after remote config is configured and Cogent is installed as a service

You should set this and change it.
If you need to create tunnels, then test with that user (admin) on the remote Cogent Master, this user has full rights
If you need to create a new user on slave Cogent, you must set security equal to image below

Now change organization to internal and edit the mirror

There should be no permission denied in the event log now and the tunnels from master should be available on the slave.

For tunnel you do not need OPC DA node, they are auto created at slave.

Upgrading to DataHub V11 – Security Considerations for Tunneling and other Remote Connections

End updated 26.11.2025

Cogent is installed

Lets move the files and configure Cogent.

Move the content in C:\Users\user\AppData\Roaming\Cogent DataHub\

Move to C:\CogentBase\2025

All files are moved to C:\CogentBase\2025

Make a Scripts folder also, lets keep it empty for now.

Edit the file path for the .exe file

from “C:\Program Files\Cogent\Cogent DataHub\CogentDataHub.exe” -P

to “C:\Program Files\Cogent\Cogent DataHub\CogentDataHub.exe” H C:\CogentBase\2025

.exe path now has a target also

"C:\Program Files\Cogent\Cogent DataHub\CogentDataHub.exe" -H C:\CogentBase\2025

Start Cogent, Cogent is running interactive.

Remote config now DataHub | Documentation

Before connecting to a DataHub instance remotely to configure it, you must first run it as a normal program, not a service, and prepare it in two ways:

remotemika, linux100

In the Default Roles section, uncheck the RequireTotpAuthentication button because this is an automatic, non-interactive connection.

With that new user still selected, in the Roles section check the Show Available button to display all the available roles. Scroll down to the RemoteConfig role and check that box.

Click apply

In the DataHub Properties window, select Remote Config

Check the boxes of the features you want to be configurable. Checking a box in the Local column allows connections only from a DataHub instance running on the same machine, whereas boxes in the Remote column allow connections from a Remote Config instance running on a remote machine. If you uncheck Local and check Remote, then a user on the local machine will not be able to configure that feature.

Select all