OpenGnsys

Legacy clone engine scripting enters EoL

Soleta Networks — Wed, 01 Apr 2026 11:39:22 GMT

We are excited to announce that the legacy clone engine scripting libraries and utilities, including:

Core Libraries: Boot.lib, File.lib, Inventory.lib, PostConf.lib, Registry.lib, System.lib, Cache.lib, FileSystem.lib, Net.lib, Protocol.lib, Rsync.lib, Disk.lib, Image.lib, PostConfEAC.lib, String.lib, UEFI.lib, and ImagenesSincronizadas.lib

Standalone Scripts: bootLinux, bootOs, bootOsCustom.template, bootWindows, buildToOrder, cloneRemoteFromMaster, configureOs, configureOsCustom.template, createBaseImage, createDiffImage, createImage, createImageCustom.template, createLogicalPartitions, createPrimaryPartitions, deployImage, formatFs, generateMenuDefault, getFsType, getIpAddress, getOsVersion, grubSyntax, poweroff, README.es.txt, reboot, remoteConsole, restoreBaseImage, restoreDiffImage, restoreImage, restoreImageCustom.template, installOfflineMode, launchOgagentInstaller, listHardwareInfo, listPartitions, listPrimaryPartitions, listSoftwareInfo, menuBrowser, ogCrearImagenBasica, ogCrearSoftIncremental, ogRestaurarImagenBasica, ogRestaurarSoftIncremental, runAplicationX.sh, runhttplog.sh, sendFileMcast, setBootMode, updateBootCache, updateCache, and related utilities are officially discontinued in favor of our new and improved Scripting Infrastructure.

🚀 What's New: Post-Configuration & Custom Scripting

The new infrastructure simplifies automation and gives you flexible, organized control over post-deployment tasks using standard scripting languages.

Post-Configuration Scripts* store and execute custom scripts that run automatically after image restoration:

Live environments: /opt/opengnsys/client/postconf/live. Place your Bash scripts here for execution in live mode. These scripts are run after the image restoration.
Windows environments: /opt/opengnsys/client/postconf/windows. Place your .ps1 PowerShell or .cmd Batch files here. These scripts are run in the first boot of this OS in the mini-setup mode.

Access these scripts directly from ogCP: Images → Edit Images Then, select the scripts that you want to run after the image restoration.

On-Demand Custom Scripts: Run ad-hoc maintenance, diagnostics, or configuration tasks anytime. Universal script directory: /opt/opengnsys/client/shell/. Store reusable Bash, PowerShell, or other compatible scripts here for Linux and Windows environments.

Access these scripts from ogCP: Commands → Run → Run Scripts

Scripting Environment Variables: To facilitate dynamic scripting, specific environment variables are automatically injected into your scripts during execution: OG_DEVICE_PATH (Bash): This variable is set automatically in Bash scripts and specifies the /dev path to the partition where an image is being restored (e.g., /dev/sda1). You can use this variable directly in your scripts to target the correct device without hardcoding paths.

✅ Benefits of the New Infrastructure

Clean separation of concerns: post-conf vs. on-demand execution
Native support for Bash, PowerShell, and CMD syntax
Dynamic Device Handling: Use OG_DEVICE_PATH to safely identify target partitions from your scripts
Integrated visibility and management through ogCP

📅 Support Timeline

Legacy scripting support will continue until August 2026. After this date, legacy libraries and scripts will no longer receive updates, testing, or technical support.

🔁 Migration Guidance

We strongly encourage all users to begin transitioning their workflows to the new scripting infrastructure now. Start by:

Replace your existing PostConf.lib based custom script logic.
Refactoring tasks into Bash (.sh) or PowerShell (.ps1) files. Utilizing OG_DEVICE_PATH in Bash scripts to handle partition targeting dynamically.
Placing them in the appropriate directory (postconf/live, postconf/windows, or shell/).
Testing execution via ogCP before decommissioning legacy calls.
Comprehensive migration examples and best practices are available in our updated documentation portal.

🆘 Need Assistance?

If you have questions about adapting your automation workflows, need help converting legacy script logic, or want guidance on structuring new post-configuration tasks, our support team at opengnsys@soleta.eu is here to help.

Thank you for being part of our community and for your continued trust in our solutions. We're committed to empowering you with more flexible, maintainable, and powerful tools for your imaging and deployment operations.

legacy ogLive images enter EoL

Soleta Networks — Thu, 10 Jul 2025 20:33:23 GMT

We are excited to announce that the older live images, such as ogLive-focal-5.4.0-42, ogLive-focal-5.13.0-27 and any other similar ogLive image available are discontinued in favor of our new and improved live image series: ogrelive, starting with versions like 6.1.0-32-amd64. See our documentation for more information about the new ogrelive system.

The new ogrelive images offer enhanced performace, updated features (new browser), and improved reliability and stability to better meet your needs, it has been extensively tested in production with UEFI and BIOS legacy computers.

Support for legacy ogLive images will continue until August 2025. We encourage all users to transition to the latest ogrelive images to take full advantage of the latest updates and ongoing support.

If you have any questions or need assistance with the migration, our support team at opengnsys@soleta.eu is here to help!

Thank you for being part of our community and for your continued trust in our solutions.

OpenGnsys Enterprise 3 has been released

Soleta Networks — Thu, 19 Jun 2025 13:30:52 GMT

OpenGnsys Enterprise 3 installer is now available, this release contains:

A new live system (ogrelive) based on Linux kernel 6.1, this includes a new GUI kiosk to report progress.
Grub2 based boot management for UEFI and legacy BIOS equipment.
Multiboot support for Linux and Windows UEFI and legacy BIOS.
Unified agent ogClient for Linux, Windows and live modes.
Native BCD and hive register updates on Windows.
Powershell and Bash scripting support for advanced configurations.
Windows 11 support (already available since June 2024).

Legacy components available in OpenGnsys 1.1.1d has been now removed, this includes:

PHP 7 support has been discontinued since November 28, 2022 (~3 years ago), used by the web interface ("web console").
Python 2.7 stopped receiving maintainance since January 2020 (~5 years ago) used by ogAgent.
Grub4DOS support for legacy BIOS equipment has been discontinued.
Non-OpenSource tool that is used to update BCD and hive Windows registers has been replaced by native Python-hivex code.
Old live images such as ogLive-focal-5.4.0-42 and ogLive-focal-5.13.0-27 are now discontinued in favor of the new live (ogrelive) image.
Legacy bash shell scripts have now been removed on the server side.
Legacy networks services such as faucet (tcp/2006), NetBIOS (tcp/139, udp/139), rsync (tcp/873) are now disabled.

We do not recommend running OpenGnsys 1.1.1d in production these days.

If you have more questions, please contact us at opengnsys@soleta.eu for more information.

Windows 11 is supported by OpenGnsys Enterprise

Soleta Networks — Wed, 18 Jun 2025 09:46:52 GMT

We launched a survey to find out which Windows 11 versions are most used by our users. These are the results:

Windows 11 Enterprise 23H2 Build 22631.4974
Windows 11 Pro Education 24H2 Build 10.0.26100.1742
Windows 11 Enterprise LTSC 24H2 Build 26100.3476

Version 23H2 is particularly popular because users tend to make this decision before the start of the academic year, and it was the available version in summer 2024.

If you have more questions on Windows 11 support, please contact us at opengnsys@soleta.eu for more information.

ubuntu 20.04 LTS EoL in April 2025

Soleta Networks — Wed, 05 Feb 2025 20:46:52 GMT

Ubuntu 22.04 LTS (Focal Fossa) enters End of Life (EoL) in April 2025.

We provide a new installer of OpenGnsys Enterprise for Ubuntu 22.04 LS for new installations.

We also provide support to migrate an existing installation from Ubuntu 20.04 LTS (focal) to Ubuntu 22.04 LTS (jammy).

web console and OgAgent enters EoL in August 2024

Soleta Networks — Tue, 19 Dec 2023 09:14:13 GMT

The following OpenGnsys Enterprise components available for Ubuntu 20.04 LS will enter End of Life (EoL) in August 2024:

legacy web interface (also known as "web console"), which is replaced by the new ogCP web front-end.
ogAgent, which is replaced by ogClient. There are versions of ogClient available for Linux and Windows in our download area. To ease migration, both ogAgent and ogClient can be installed in the same computer.

ogCP is already provided by default by the OpenGnsys Enterprise installer. Please, check documentation for more information on to access it.

Make sure your ogCP web interface is up to date with the following commands:

$ sudo apt update
$ sudo apt upgrade ogcp

OpenGnsys VLAN support

Soleta Networks — Mon, 25 Sep 2023 07:41:03 GMT

Great news! VLAN support just landed in OpenGnsys Enterprise.

This new feature allows any OpenGnsys Enterprise administrator to add or delete any valid ogServer address into the database and also modify any client's associated server address.

The server running OpenGnsys Enterprise can now be configured with multiple VLAN interfaces. Clients can boot into the ogLive environment using the corresponding server VLAN interface address thanks to a custom ogClient configuration file based on the ogServer address.

Be sure to update your OpenGnsys Enterprise installation. The related packages and their version in which VLAN support landed is as follows:

ogCLI 0.3.1-1
ogClient 1.3.1-4
ogServer 1.2.4-1

Except for the custom ogClient configuration file, everything related to VLAN in OpenGnsys is configured using ogCLI, the command line frontend of OpenGnsys Enterprise. You can see some examples of use cases below:

Add a new ogServer address entry to the OpenGnsys database. In this example the server address is 10.141.10.1. Returns the id of this new server.

$ ogcli add server --address "10.141.10.1"
{"id", "2"}

List all stored ogServer address in the OpenGnsys database

$ ogcli list servers

{
  "servers": [
    {
      "address": "192.168.2.240",
      "id": 1
    },
    {
      "address": "10.141.10.1",
      "id": 2
    }
  ]
}

Set server with id 2 as the server of client with address 10.141.10.100 (PXE template needs to be rebuilt after this, i.e.: set boot mode)

$ ogcli set server --id 2 --client-ip 10.141.10.100
$ ogcli set mode --mode pxe --client-ip 10.141.10.100

You can also set the server of a whole room. Just as before, but using the --room-id parameter.

$ ogcli set server --id 2 --room-id 1
$ ogcli set mode --mode pxe --room-id 1

Check for the server address a client is set to connect to when booting ogLive.

$ ogcli list client --client-ip 10.141.10.100

{
  "boot": "oglive",
  "center": 1,
  ...
  "server_id": 2
}

As a final step we need to create a custom ogClient file so that clients booting ogLive can use the correct configuration based on their VLAN network.

Following this example, to create a new custom ogClient configuration file to connect to ogServer using its 10.141.10.1 address we need to create a copy of the default config file but changing its name to ogclient-10.141.10.1.json:

$ ls -lah /opt/opengnsys/client/ogClient/cfg/
...
-rw-r--r-- 1 root root  372 Sep 14 13:51 ogclient.json
-rw-r--r-- 1 root root  378 Aug 28 11:26 ogclient-10.141.10.1.json
...

After creating the custom configuration file make sure the correct address is used for the "ip" and "ur" fields inside "opengnsys" section. In this example: 10.141.10.1

$ head /opt/opengnsys/client/ogClient/cfg/ogclient-10.141.10.1.json
{
    "opengnsys": {
        "ip": "10.141.10.1",
...
        "url": "https://10.141.10.1/opengnsys/varios/menubrowser.php",
...

After this, any client for which the ogServer address is set to 10.141.10.1 will use this configuration file instead of the default ogclient.json.

Any questions? You can contact us via e-mail at opengnsys@soleta.eu

We also offer technical support and training services, check the support section for more information.

Development comparison between 1.1.1 and 1.2

Soleta Networks — Fri, 30 Jun 2023 16:00:00 GMT

It might seem difficult at first to know who is doing what depending on the version of OpenGnsys you are currently using. Sometimes it might even resemble a famous comic strip...

(This is a homage to John Romita Sr. who passed away the 15th of June)

We have made available a document to understandthe development differences between OpenGnsys branches: 1.1.1 and 1.2.

This document shows the main contributors from 1.1.1 to 1.2.

You can read the document here

If you would also like to understand the differences between these two OpenGnsys development branches, then read this blog post.

Untangling OpenGnsys: Comparing branches and versions

Soleta Networks — Fri, 30 Jun 2023 16:00:00 GMT

The OpenGnsys project has different development branches and versions: 1.1.1d, 1.2, OpenGnsys Enterprise. This might be confusing to the end user so if you are interested in knowing what features are included in which versions you can read more about OpenGnsys versions and branches in the following PDF document here.

OpenGnsys 2.0 Enterprise now available for Ubuntu 20.04 LTS

Soleta Networks — Thu, 08 Jun 2023 11:00:12 GMT

Ubuntu 18.04 LTS entered EOL in April 2023. A new installer of OpenGnsys Enterprise 2.0 for Ubuntu 20.04 LTS is now available for download.