# On premise module on other cms fork

**URL:** https://community.xibo.org.uk/t/on-premise-module-on-other-cms-fork/38431
**Category:** Uncategorised Topics
**Created:** [September 16, 2026, 12:35pm UTC](https://community.xibo.org.uk/t/on-premise-module-on-other-cms-fork/38431 "2026-09-16T12:35:34Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Testeur\_IT](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/testeur_it/32/17945_2.png) [@Testeur\_IT](https://community.xibo.org.uk/u/Testeur_IT)
#### Post date: [September 16, 2026, 12:35pm UTC](https://community.xibo.org.uk/t/on-premise-module-on-other-cms-fork/38431/1 "2026-09-16T12:35:34Z")

</div>

Hi,

We run a custom fork of Xibo CMS 4.4.3, forked from the official tag and ported from MySQL to Microsoft SQL Server 2022 (all SQL queries rewritten to T-SQL, running the standard Docker Compose stack — PHP/Apache + pdo\_sqlsrv + SQL Server 2022 container — on Linux). The rest of the CMS behaves like stock 4.4.3 as far as we can tell (XMDS, display registration, scheduling all working and tested end-to-end with a real Android player).

We’re about to deploy Stick (Signage) players on a fully isolated LAN with no internet access, and we’re planning to purchase the On-Premise Licensing module ($210) + 15 Xibo for Android licences.

Before committing to the full purchase, we’d like to check a few things given our non-standard setup:

1. **Does the module perform any of its own direct SQL queries against the CMS database** , or does it operate purely through the existing Xibo Storage abstraction layer / file exchange (request.txt / android.txt in library/android)? We want to confirm there’s no MySQL-specific SQL syntax baked into the module that wouldn’t run against SQL Server.

2. **Where exactly should the config snippet (`$licence_pool_email`) go** — `web/settings.php` or `custom/settings-custom.php`? Our `web/settings.php` already includes `custom/settings-custom.php` automatically if present, so we’d rather use that hook than edit a file that’s otherwise generated by our deployment process. We’ve seen conflicting guidance on this in older forum threads (e.g. one referencing Xibo 2.0.3 on XAMPP/Windows).

3. Can you confirm the licence exchange is genuinely a **one-time process per device** , and that it’s tied to the **Android player’s hardware ID** , not to any identifier of the CMS server itself? We plan to validate the whole setup on a build VM first, then clone/export that VM (Hyper-V) to the client’s production server — so we need to be sure the licence activation survives that move without issue.

4. Is it possible to **purchase the module with a single test licence first** , validate the full flow on one device, and add the remaining 14 licences afterwards — or does the on-premise module/pool need to be set up with the final licence count from the start?

Happy to open a support ticket if that’s a better channel for this — just wanted to check here first in case someone has run On-Premise Licensing against a modified/non-MySQL CMS before.

Thanks!