Feature License Propagation Issue using Engineering License ("New system")

[Katha]

Issue

When an Engineering License ("New system") is created and activated on an Enterprise Server (ES) that has been upgraded from EBO 6 or earlier to EBO 7.0.3, the feature licenses do not propagate to Automation Servers (AS) that are still running EBO 6.0 or earlier

Product Line

EcoStruxture Building Operation

Environment

• Software Companion
• Device Administrator
• Centralized Licensing

Cause

The current Engineering License offering with the "New system" does not support scenarios where the top-level server has been upgraded from EBO 6 or earlier to EBO 7.0.3.
In such cases, the license propagation mechanism may not function correctly.

Resolution

To ensure proper license propagation:

• Recommended Setup:
  Create and activate the Engineering License ("New system") on a top-level server with a clean EBO 7.0.3 database. In this configuration, feature licenses will be inherited correctly by AS units running EBO 7.0 and earlier.
  
  

• Alternative Workaround:
  If the ES has been upgraded from EBO 6 or earlier to EBO 7.0.3 and AS units cannot be upgraded immediately ( Multi-system) :

  • Consider manually assigning feature licenses ( Demo lic)  to the AS units.
  • Or, migrate AS units to EBO 7.0 or later to restore automatic license propagation.