Issue License needs to be activated or repaired, but there is no Internet access on the computer hosting the license. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator  Cause The computer cannot be moved to a location with Internet access for activation or repair. IT policies prohibit temporary Internet access for licensing purposes. Resolution SBO Offline Activation Tool Use the SBO Offline Activation Tool for offline license activation. Access the tool here: SBO Offline Activation Tool. Click Instruction and Help in the tool for step-by-step guidance and helpful videos/charts. SBO Offline License Repair The same tool can repair offline licenses. Access the tool here: SBO Offline Activation Tool. After launching the tool, go to Special Operations → Repair License. If repair fails, contact Support for further troubleshooting.

Issue After updating Java (e.g., to Java 7 Update 65 or later), WebStation graphics may appear blank or white.  Note: If the error you see is “Error. Click for details” and not a blank window, please refer to the article: WebStation graphics not working after Java updated to Java 7 Update 51. Customers also need clarity on when Java was removed from WebStation and replaced by HTML5. Product Line EcoStruxure Building Operation, TAC Vista Environment Java Building Operation WebStation Cause Compatibility issues between Java and WebStation in TAC Vista or older Building Operation versions. Java applets were historically used for TGML graphics, causing security warnings and browser compatibility problems. Transition to HTML5 technology eliminated these issues. Resolution For Java-related issues (TAC Vista or SBO 1.5 and earlier) Update Java Install the latest Java version (e.g., 1.7u67). On x64 systems, install both x86 and x64 Java versions. If issue persists, perform clean reinstall: Close all browsers. Uninstall all Java versions. Backup exception.sites file: C:\Users\<username>\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites Delete folder: C:\Users\<username>\AppData\LocalLow\Sun Reinstall latest Java (both x86 and x64 if applicable). Verify Java installation using Java uninstall applet. Restore exception.sites file to its original location. Technology Transition Note Pre-2014 (SBO 1.0–1.5) TGML graphics displayed using Java applets. 2014–2015 (SBO 1.6) HTML5 Viewer introduced as Beta in WebStation. Users could enable HTML5 manually; Java remained default. 2015–2016 (SBO 1.7) HTML5 fully implemented as the default graphics viewer. Java completely removed from WebStation. 2017 onward (EBO 2.x and beyond) Modern HTML5 UI with responsive design. No plugins required; optimized for Chrome, Edge, Firefox.

Issue The instance values the Function Block program had when the backup was taken is lost when the backup is restored in an AS-P running in PCT. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause When the program is first initiated, the values for it is written to the database. If the “Program executions” Is turned off, the instance values the program had when the backup was taken is not read. Hence the values are set to 0.   On a real AS-P, a Cold start is performed after the restoring of the backup. When restoring a backup on an AS-P in PCT, one or two cold starts are done, followed by an additional warm start at least for the PCT 2. Resolution To get the instance values from the backup when it is restored, the “Program execution”/”Enable program” In PCT should be turned on before the restore is done.   Since a warm start is done for the PCT, the issue regarding Retain level vs. FB Backup property needs to be taken into consideration. Refer to Function Block Program - Retain Versus Backup

Issue There is no complete end-to-end guide on how to test SNMP alarms in EcoStruxure Building Operation (EBO). Existing documentation only covers creating SNMP alarms, not validating their functionality. Product Line EcoStruxure Building Operation Environment SNMP Notifications Cause Documentation provides steps for creating SNMP alarms but lacks instructions for testing and verifying alarm notifications. For general information regarding SNMP traps, refer to the following Web Help links: SNMP Notification Distribution Method Create Notification Wizard - Configure SNMP Page Resolution Follow these steps to test SNMP alarms in EBO: Install MIB Browser Download and install MIB Browser from iReasoning. Load Building Operation MIB File Download the Building Operation MIB file. In MIB Browser, go to File → Load MIBs, and select the Building Operation MIB file. Create and Trigger an Alarm in EBO Configure a simple alarm on a digital point in EBO. Ensure the alarm can be triggered manually for testing. Configure SNMP Notification in EBO Create an SNMP notification with the following settings: Address: SNMP manager IP (use localhost if manager is local). User Name: SNMP manager user credentials. In Filter Settings, select Normal and Alarm states. Add condition: Source server = * . Important: Open the SNMP notification object (double-click or press Enter) to access filter settings. Viewing properties alone will not display filters. Enable Trap Receiver in MIB Browser Navigate to Tools → Trap Receiver in MIB Browser. Trigger the Alarm Activate the alarm in EBO. Verify that the SNMP trap appears in the MIB Browser’s Trap Receiver window.

Issue Users need clarification on what happens when a Software Companion subscription is expired or approaching expiration. Key questions: What messages appear in EcoStruxure Building Operation (EBO)? Are email notifications sent to customers? Can expiration notices be silenced at the EBO front end? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation subscription licenses Cause The License Enforcement and Information page in Webhelp provides limited details regarding Software Companion subscription expiration behavior. Resolution 1. What messages appear at the EBO level? 30 days before expiration: A banner appears in EBO stating: “System license renewal date is approaching. Please renew.” After expiration: The banner changes to: “System license renewal date has passed. Renewal required.” 2. Are email notifications sent? EBO does NOT send email notifications. Software Companion notifications: Up to two designated Renewers per system receive email reminders at: 6 months 3 months 1 month prior to renewal date Within Software Companion: System status color changes as renewal date approaches Red indicates the renewal date has passed 3. Can the expiration notice be silenced in EBO? Users can temporarily hide the banner using the Hide button. Permanent removal requires applying a valid license (subscription renewal).

Issue There is no fully detailed explanation of how to install an SSL Certificate from an External Authority (CA) Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause When trying to install an SSL certificate from an external CA can fail Resolution Configure a DNS name for the AS/ES (This prevents the certificate from being locked down to a specific IP. I.E. Configure an A record for "AS_Name".com Purchase SSL Cert through a 3rd party, or use your organization's internal CA/ root CA Download and install OpenSSL or can use OpenSSL installed with EBO  Run Command Prompt as an administrator Use command "cd c:\program files\OpenSSL-Win64\bin Use OpenSSL to generate a CSR in order to obtain the certificate from the 3rd party openssl req -new -newkey rsa:2048 -nodes -keyout EcoStruxure.key -out EcoStruxure.csr Follow the prompts to fill out the information for the CSR Supply CSR, other certificate contact information, and a means of validating the request to the 3rd party CA Verify identity with CA (this may not be necessary if you use your company's internal CA/ root CA Receive host and intermediate CA certificates from 3rd party CA Make sure the CRT/CER files are in the C:\Program Files\OpenSSL-Win64\bin directory of Windows Explorer Use OpenSSL to convert the CRT or CER files into PEM files, as PEM is the only format EBO will accept openssl x509 -in certFileName.cer -outform PEM -out convertedCertFileName.pem Use OpenSSL to convert the private key file generated at step 6 from .key to .prv openssl rsa -inform pem -in filename.key -out filename.prv Run WorkStation as administrator In WorkStation, Control Panel > Certificates click on the server you are trying to add the cert to, either an AS or ES. Click on Manage Certificates > Add Existing  Put in a name for the certificate (it can be anything you'd like) Click the ellipsis next to host, intermediate, and private to add the appropriate PEM files and click ok  Select the newly added certificate from the drop-down and save the changes to activate Warm start the server After this process is completed, verify that connection to WebStation via HTTPS shows a secure connection/trusted certificate.

Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) Cause It is often required that alarm notifications to be sent to multiple stakeholders simultaneously for timely response.   Best Practice: Use an email distribution list (DL) or group on your mail server and reference that DL address in EcoStruxure Building Operation. This simplifies recipient management and reduces maintenance overhead. Resolution   Open Email Setup in WorkStation (or Project Configuration Tool) > navigate to Notification > Configure Email. In the “To” field, enter multiple addresses using this syntax: user1@domain.com;user2@domain.com;user3@domain.com Separate addresses with semicolons ( ; ) and do not include spaces. Alternatively, select user accounts or groups to manage recipients dynamically. Ensure each user account exists on the BMS server and has proper alarm handling permissions. Configure SMTP settings (server, port, SSL/TLS, credentials) under right click  Server Properties > Email.   Choose how notifications appear: Inline email text, or As an attachment (TXT, XLSX, or PDF), with dynamic filenames if needed. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com If email delivery fails, Building Operation generates a system information alarm indicating SMTP issues. Recipient Limit Note: EcoStruxure Building Operation does not impose a hard limit on the number of email addresses in the “To” field. However, your SMTP server or email provider may enforce limits (e.g., Microsoft 365 allows 500 recipients per message; Gmail and ISPs have similar restrictions). To avoid delivery failures, use distribution lists or user groups for large recipient sets.

Issue After renaming a server, folder, or object, users may suddenly lose or gain access via WorkStation or WebStation. Access changes depend on the original permissions assigned to the user or group, and these permissions are not automatically updated following renaming. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES)  Building Operation Automation Server Premium (AS-P) Cause Permissions in EcoStruxure Building Operation are based on path names. When a Server, Folder, or Object is renamed, its path changes. Existing permissions remain tied to the old path—so users either lose or inherit permissions until these are updated. Resolution After renaming Servers, Folders, or Objects: Review all relevant Users and Groups in your system. Update path permissions to match the new names. Navigate in WorkStation to Control Panel → Account Management. Select the user or group, go to Software Permissions, and verify or adjust their assigned paths. Refer to WebHelp (Editing Path Permissions of User Accounts or User Account Groups - EcoStruxureWebHelp)  Validate effective permissions, ensuring they use the correct access levels: Read, Write, Create, Delete, Edit, Force, or Command. See also Relative Path Permissions. Refer to WebHelp (Assigning Relative Path Permissions to User Accounts or User Account Groups - EcoStruxure WebHelp)

Issue When attempting to rename an Enterprise Server (ES) or add a SmartX (Automation) server under an ES, the following error may appear: All subservers must be online at least once before adding (renaming)   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server – version 2.x and later Cause A mismatch exists between the contents of the MountPoints and Versions folders within the ES database. Although GUID(Globally Unique Identifier)-named pairs may look similar, their contents differ—and cannot just be copied. Resolution Backup: Confirm you have a clean, recent backup of the ES database. Identify unmatched files: Compare the following folders: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server\db\System\MountPoints  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server\db\System\Versions Delete unmatched versions: In the Versions folder, delete only those GUID-named files that do not have a corresponding file in MountPoints.   Manual comparison required: You must compare GUIDs manually or via script—files can’t be auto-synced.    

Issue Guidance is needed for converting Andover Continuum to EcoStruxure Building Operation (EBO) using the Continuum Conversion Tool (CCT), including best practices and troubleshooting tips Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool (CCT) Andover Continuum EcoStruxure Building Operation Cause Although documentation for the Continuum Conversion Tool exists, it is spread across multiple resources and formats (Knowledge Base articles, WebHelp, training materials). This fragmentation can lead to confusion or missed steps during migration. Resolution Refer to the following official resources for detailed guidance: EcoStruxure Building Operation - Technical Reference Guide - Version 6.0 Starts at chapter 214, Page 6312 Andover Continuum to EcoStruxure Building - Frequently Asked Questions - Technology Refresh Training Resource Library: Continuum Transition(Forum) Webhelp: Continuum Conversion Workflow Webhelp: Continuum Conversion Tool Best Practices Perform a Full Backup Back up all Continuum databases and controllers before starting the conversion process. Validate Firmware Compatibility Ensure all Continuum devices are running supported firmware versions prior to migration. Reference:  Continuum Infinet Transition - Make Ready incompatible controllers Conversion of Continuum devices from i2 to b3 Migrating Infinet controllers from Continuum to EBO Change the firmware version in a Continuum controller Continuum Software and Firmware Compatibility Matrix Use a Test Environment First Run the conversion in a non-production environment to identify potential issues before live deployment. Check Naming Conventions Standardize object names in Continuum before conversion to avoid conflicts in EBO. Review Converted Objects After conversion, verify that all points, alarms, and schedules have migrated correctly. Reference: Converting Continuum b3/i2 Tristate outputs to EBO Multistate outputs Document Changes Maintain a detailed record of conversion steps and any manual adjustments for future reference. Plan for Downtime Schedule migration during low-occupancy periods to minimize operational impact. Reference: Andover Continuum Conversion Tool Slow Troubleshooting Common Issues Issue Possible Cause Resolution Conversion Tool Runs Slowly Large database size or insufficient system resources Close other applications, ensure adequate RAM, and run conversion in smaller batches. Missing Objects After Conversion Unsupported object types or naming conflicts Review conversion logs, manually recreate unsupported objects, and standardize names before retrying. Licensing Errors Incorrect EBO license or missing feature Verify EBO license includes Continuum conversion support; update license if needed. Firmware Mismatch Continuum devices not on supported firmware Upgrade firmware to recommended versions before conversion or use Roam I/O to upgrade after conversion. Alarms Not Migrating Correctly Alarm configuration differences between Continuum and EBO Validate alarm mappings post-conversion and adjust manually where necessary.

Issue Customers need guidance on migrating DMS-3500 systems to the Building Operation platform. Product Line EcoStruxure Building Operation, TAC IA Series Environment DMS-3500 EcoStruxure Building Operation Cause The DMS-3500 system and its databases are not compatible with Building Operation. Schneider Electric does not provide a supported migration path for these legacy systems to Building Operation. Resolution   Direct migration is unsupported. To integrate DMS-3500 data into Building Operation, use a Niagara device as a gateway between the two systems.  

Issue Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server Automation Server Workstation Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of Struxure EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch Building Operation Software Administrator Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric EcoStruxure\Building Operation X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing EBO, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db).     Launch Building Operation Software Administrator, click Start Service, and then OK.   Launch EcoStruxure WorkStation and log into the enterprise server Select the enterprise server and go to the Main Menu > Actions > Restore.   In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red, it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed-up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;   Select the automation server and go to the Main Menu > Actions > Restore.   In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue Steps to backup within EcoStruxure Building Operation (EBO) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site with AS and/or ES Backup, Automation Server, Enterprise Server, Workstation, .xbk, xbk, backup set, db backup, db_backup Cause Must an AS or ES be stopped in order to do a full backup? Is a raw copy of the database folder from within Windows Explorer sufficient for backing up an ES?  For instructions on how to restore a backup in StruxureWare/EcoStruxure Building Operation, see How to restore a EBO server backup set. Resolution No need to stop AS or ES: EBO freezes the database during backup. Configuration changes are queued until backup completes; historical data is buffered. Do not use raw folder copy: Always use the built-in backup function. Three rules to remember: Restores must use the same software revision. Do not rename the backup set. If renaming is needed, zip the backup and rename the zip file. Default backup schedule: Every Sunday at 1:00 AM. When creating a backup, give the appropriate prefix to the standard name format. See screenshot below. The backup file will be shown as the screenshot below. Should the backup name need to be changed, then either create a new backup, or zip up the backup using the new name. Backup Procedure Enterprise Server (ES) Automation Server (AS) In Workstation, select the Server in the System Tree. Go to Actions → Backup. In Backup Options: Include column: Select servers to include. Backup content: All Data: Historical + configuration databases. Configuration only: Configuration database only. Add a Backup set description (up to 255 characters). Click Backup. Verify that each backup succeeded and click Close. Backup file location: C:\ProgramData\Schneider Electric\StruxureWare\Building Operation 1.X\Enterprise Server\db_backup\LocalBackup or C:\ProgramData\Schneider Electric\EcoStruxure\Building Operation 2.X\Enterprise Server\db_backup\LocalBackup   Backup Files of AS: Log in to AS from Workstation. Navigate to System → Backup and Restore → Backup sets → Local. Right-click the backup file → Save To... (choose folder on HDD).

Issue When planning an upgrade to EcoStruxure Building Operation (EBO) 7.x or the latest version for existing sites, users often want to complete engineering work before applying commercial licenses through Software Companion. Product Line EcoStruxture Building Operation Environment EcoStruxture Building Operation Project Configuration Tool 2.0 Cause Software Companion only provides Engineering licenses for new sites, but not existing sites. This limitation means that existing sites cannot be engineered without applying the commercial license first. Resolution To engineer or upgrade existing sites before applying commercial licenses, use Project Configuration Tool (PCT) v2: PCT is a standalone engineering platform, independent of the live system. It allows flexible design and upgrade workflows without impacting production. After engineering or upgrading: Deploy the EcoStruxure BMS server to the live site directly from PCT, or Use an XBK backup and import for deployment. Recommended Steps Download and Install PCT v2.x Windows Installer – v2.2.1.12 Ubuntu Installer – v2.2.1.12 Release Notes v2.2.1 Create or Import Existing Site in PCT Use the Import XBK backup feature for existing sites. Perform Engineering and Upgrade Tasks Configure controllers, graphics, and logic as needed. Validate compatibility with the target EBO version. Deploy to Live Site Either direct deployment from PCT or export XBK and restore on the live server. Additional Resources Project Configuration Tool – Support Tools Specification Sheet

Issue When opening (pulling up) the sunblind, it stops at the end of runtime and then rolls back down. Similarly, when closing (pulling down), it stops at the end of runtime and then rolls back up. Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Lonworks devices including REG-N MSE4 (SVEA 32237-346) Sunblind actuators Cause The actuator is preconfigured for venetian blinds, which include lamella angle adjustments. For simple sunblinds, these parameters cause unintended motor actions after reaching the end position. Resolution For non-venetian blinds: Set the following parameters to zero: UCPTdownPanelAngle UCPTupPanelAngle UCPTpanelTurnTime UCPTpanelTurnTimeBottom Ensure SNVTsetting commands have zero in the rotation part. This disables unnecessary panel angle adjustments and prevents rollback after full movement.

Issue EBO Automation Servers may fail to synchronize time with configured Network Time Servers. The system log reports: chronyd[1566]: Can't synchronise: no majority This error occurs when multiple configured NTP servers report significantly different times, preventing the NTP service from establishing a consensus. Product Line EcoStruxure Building Operation Environment Building Operation Automation Servers Cause EcoStruxure Building Operation uses chronyd as the time synchronization daemon on Automation Servers. chronyd is part of the Chrony suite, designed for fast and accurate time sync, especially on embedded systems or devices with intermittent connectivity. Why the Error Occurs: Equal Weighting of Servers: chronyd treats all configured NTP servers equally. There is no concept of “Primary” or “Secondary” in its logic. Quality-Based Evaluation: chronyd continuously assesses each server based on: Round-trip delay Jitter Offset Historical stability Majority Consensus Requirement: chronyd attempts to find a majority agreement among the sources. If the servers report significantly different times, and no consensus can be reached, synchronization fails with the error: Can't synchronise: no majority No Failover Logic: chronyd does not switch between servers. It uses both the Primary Network Time Server and Secondary Network Time Server concurrently to calculate the most accurate time based on latency and jumps.  Example Scenario: If Server A reports UTC+10:00 and Server B reports UTC+10:05, chronyd may reject both if it cannot determine which is correct, resulting in no synchronization. Resolution 1. Use a Single Reliable NTP Server Configure only one NTP server to avoid conflicting time sources. This ensures chronyd has a clear reference and avoids “no majority” errors. 2. Ensure NTP Server Stability To maintain reliable time synchronization, verify the following: Reachability Use ping <ntp_server> from a device on the same subnet as the AS to confirm the server is reachable. Ensure UDP port 123 is open for NTP traffic through any firewalls. Time Accuracy Use tools like ntpq -p <ntp_server> or chronyc sources to check the server’s reported time and offset. Avoid servers with large offsets or jitter values. Latency Prefer servers geographically close to the site or hosted within the same network. High latency can cause chronyd to reject the server as unreliable. Consistency Ensure the NTP server is synchronized with a reliable upstream source. Avoid mixing public and private NTP servers unless they are known to be in sync. Redundancy (if needed) If multiple servers are required, ensure they are synchronized with each other. Use trusted pools like NTP Pool Project for reliable public servers. Monitoring Periodically check synchronization status via WebStation or system logs. Look for chronyd messages indicating sync success or failure.

Issue When importing IAC400 or IAC600 controllers into Building Operation via the Micronet Interface, digital outputs cannot be overridden or forced to a different value. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment IAC400 IAC600 Building OperationServer Cause During the import process, the Digital Output Override State is incorrectly configured in the XML export file. Specifically, the <P1="IsNonVolatile"...> line contains a value that prevents the output from being overridden. Resolution ⚠️ Important Notice Satchwell MicroNet is not supported in EBO 2022 and later. To continue supporting MicroNet devices, you can implement a multi-version system: Keep Servers with MicroNet devices on Building Operation 3.2. Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality. To enable digital output override functionality: Create the SBO Export File in Visisat Use Visisat to generate the XML configuration file for the controller. Edit the XML File Before Importing into SBO Open the XML file using a text editor such as Notepad++. Locate the line containing: <P1="IsNonVolatile" Value="1" ...>​   Change the value from "1" to "0" : <P1="IsNonVolatile" Value="0" ...> Import the Modified XML File into SBO/EBO Use the Data Import function in the MicroNet Interface to bring the corrected configuration into Building Operation. Note This issue does not affect IAC420 controllers.

Issue IAC touch screens unexpectedly reset to their default address (65) every Sunday when time broadcast is enabled. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Building Operation Enterprise Server Building Operation Automation Server MicroNet transition IAC touch screen Cause When the AS or ES broadcasts time to MicroNet devices, the day number is incorrectly sent as 0 on Sundays instead of 7. The IAC touch screen does not recognize day 0, which triggers a reset to factory defaults, including its network address. Impact: The touch screen resets to address 65. If the original address was not 65, communication with controllers on the SubLAN fails. Manual reconfiguration is required to restore connectivity. Resolution The issue is resolved in SBO version 1.8 and later. ⚠️ Important Notice Satchwell MicroNet is not supported in EBO 2022 and later. To continue supporting MicroNet devices, you can implement a multi-version system: Keep Servers with MicroNet devices on Building Operation 3.2. Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Remote Tools: RealVNC, TeamViewer, LogMeIn, UltraVNC, etc. Cause Remote control software may not fully render graphical elements or interactive UI components of BMS applications. This is often due to: Graphics acceleration limitations UI rendering differences between local and remote sessions Security or permission restrictions in remote sessions Example: When using RealVNC to access the SmartStruxure License Administrator, the dropdown menu for adding license details may not appear, even though it functions correctly in a local session. Resolution Local Verification: Run the BMS application directly on the host machine to confirm full functionality. Remote Software Settings: Enable full desktop rendering or mirror driver (if available). Disable any performance optimizations that reduce UI fidelity. Alternative Access Methods: Use Remote Desktop Protocol (RDP) instead of third-party remote tools. Consider web-based access if supported by the BMS platform. Additional Notes These issues are not specific to one remote control tool; they may occur across various platforms.

Issue When installing Sigma 4.08 using a software license, the following error appears in the License Administrator after entering the Entitlement ID: “Unable to connect to 'Server'” Product Line EcoStruxure Building Operation Environment Satchwell Sigma Building Operation License administrator Cause The License Administrator requires an active internet connection to communicate with Schneider Electric’s online licensing server when validating or activating an Entitlement ID. If the PC is offline, the License Administrator cannot reach the server, resulting in the error. Resolution If internet access is not available, use the Offline Activation Tool to activate the license manually: 🔧 Offline Activation Process Download the Offline Activation Tool Offline activation Tool Generate a Request File Open License Administrator Enter the Entitlement ID Choose Offline Activation Save the generated request file Transfer the Request File Move the file to a PC with internet access Upload to Licensing Portal Go to the Schneider Electric Licensing Portal Upload the request file Download the response file Activate License Transfer the response file back to the original PC Load it into License Administrator to complete activation