Installation on Windows (Connect 2024)

Available builds

The installation package for Connect Server contains four different builds for Windows:

Notes on the platform-independent version

The platform independent build "portable" requires the prior installation of .NET 8 incl. ASP.NET Core. The current version is provided by Microsoft at the following link:

We recommend using the "Hosting Bundle" provided by Microsoft, as this contains all the required components.

When using the platform-independent version, updates for the .NET Framework can be installed independently of the Connect software. In the event of security-critical errors in the Microsoft .NET Framework, you can react immediately without having to wait for an update of the Connect Server. In addition, the installation files can be used for all supported operating systems.

Notes on the platform-specific versions

These builds are already compiled for the corresponding target platform and contain all files required for execution. This eliminates the need to install additional software. An update of the included software components is only possible by installing an update of the Connect Server.

Installation

Create an empty folder (e. g. "C:\Program Files\Galileo Group\Connect\server") and copy all files of the desired Connect Server version into this folder.

Configuration

The Connect Server is delivered with a ready-to-run configuration. The integrated web server listens on port 80 after startup and responds to HTTP requests. For more information about customizing the configuration (e. g. customer specific port for HTTP or another one for HTTPS), please refer to chapter Configuration (Connect 2024).

Starting the Connect Server (as a console application)

The Connect Server can be started as a console application. This scenario is recommended for test scenarios and small proof of concept projects. Note that in this scenario, closing the console as well as logging off terminates the Connect Server. Disconnecting a remote desktop connection (without logging off) does not affect the Connect Server.

To start the Connect Server as a console application, set the current directory to the directory containing the Connect Server and start the executable file named "GalileoGroup.Connect.Server.exe". Alternatively, you can start the Connect Server via Windows Explorer by double-clicking on the file "GalileoGroup.Connect.Server.exe".

Exiting the Connect Server (as a console application)

Activate the console window with the Connect Server and terminate the Connect Server by pressing the key combination Ctrl + C. Closing the console window is not recommended, as this may result in communication processes not being terminated properly.

Operation as Windows service

In Windows-based production environments, it is recommended to operate the Connect Server as a Windows service. In this scenario, log output is written to the Windows event log. The one-time setup is described below:

Creating a local user to run the service

To create the local user, enter the following commands in a PowerShell with administrator privileges:

After The user has been successfully created, it must be assigned the authorization to log in as a Windows service. Press Win + R keys, type "secpol.msc" into the dialog windows and press enter. Now a window will be displayed with a tree structure on the left side. Open the "Local Policies" node and then click on the "User Rights Assignment" node. In the right half of the screen, select the "Log on as a service" entry via double-click.

In the following dialog window, click the "Add user or group" button and select the newly created local user. If the user is not found, restrict the search path to the local computer name.

Now the new user needs the authorization to access the folder where the application was installed. In this example, the folder "C:\Program Files\Galileo Group\Connect\server" is used. To do this, enter the following commands in a PowerShell with administrator privileges:

Registering the Connect Server as a Windows service

The registration can also be accomplished using a PowerShell with administrator privileges. Here is an example which can be used as a template:

Deregistering the Windows service

To remove the Windows service, enter following command in a PowerShell with administrator privileges:

If you are using PowerShell 7, this task can also be accomplished using the Remove-Service cmdlet.