Building Automation Knowledge Base

Issue Confusion about the current release version of Security Expert and the limited release Security Expert for the Enterprise Download Service. Product Line EcoStruxure Security Expert Environment Security Expert Enterprise Download Service Cause Two parallel development branches now exist for Security Expert: Maintenance Builds –  version 4.3.370.15 (Released 2025-May-01 - latest stable release) Limited Release Builds –  version 4.3.386.2, intended for use with the new Enterprise Download Service. This has led to confusion because: The limited release version (4.3.386.2) has a higher version number than the current maintenance release (4.3.370.15).  The Supported Software 2025 landing page does not host the actual installation files for the limited release. Instead, it now provides a ZIP file containing instructions and a request form. Initially, version 4.3.386.2 was directly downloadable, but it has since been replaced with the ZIP package. Resolution To Access the Current Maintenance Release Visit the EcoStruxure™ Security Expert – Software and Firmware page on the Extranet. Sort the list by date to find the most recent maintenance version (currently 4.3.370.15 Released 2025-May-01).   To Access the Limited Release (Enterprise Download Service) Go to the Supported Software 2025 landing page. Select either: “2025 Enterprise Download Service (VM Bundles)”, or “Client/Server Security Expert - v.4.3.386.2”. Both links download the same ZIP file, which includes: Instructions for requesting the limited release. A site evaluation form that must be submitted  to TeamVipers@se.com who will review and provide the installation files.   If You Need to Roll Back from 4.3.386.2 to 4.3.370.15 Due to database version incompatibility, rolling back requires the following steps: Backup the current SecurityExpert and SecurityExpertEvents databases. Record the site’s license SSN. Uninstall the current Security Expert version. Important: Any configuration or event data added after the backup will be lost and must be manually re-applied. Restore the database backups from version 4.3.370.15 or earlier. Install the maintenance version (4.3.370.15).

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work.   Important Note: The SIM must not have a Username, Password, or PIN. These features are not supported. Refer to Steps to follow to unlock SIM PIN when using SIM Card under Flex server The user must ensure that no firewall is applied by the SIM provider. If a firewall exists, it may block connectivity. We recommend using SIMs without any firewall restrictions. Ensure the data plan of the SIM should not be less than 2GB per month for approximately 100-200 streams. Issue This article provides information on the SIM cards that are currently supported in EcoStruxure Building Activate and are added to the central database to support field deployment of Flex servers. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause This eliminates the need for manual support for the already validated SIM operators individually on each server. Resolution Below is the list of the Network Service Providers whose APN exists in the backend and have already been added: MCC code (Country Code) Operator APN 260 play {"generic": "internet"} 260 plus {"generic": "mbb.mobi-data.com"} 732 claro {"generic": "internet.comcel.com.co"} 454 smc hk {"generic": "Smartone"} 520 ais {"generic": "internet"} 240 tele2 se {"generic": "mbb.mobi-data.com"} 260 t-mobile {"generic": "internet"} 262 t-mobile {"generic": "internet.v6.telekom"} 505 telstra {"generic": "telstra.internet"} 204 nl kpn {"generic": "matooma.m2m"} 208 208 28 {"generic": "datapro"} 234 voda uk {"generic": "wap.vodafone.co.uk"} 901 901 40 {"generic": "internet.m2mportal.de"} 208 free {"generic": "free"} 208 bouygues telecom {"generic": "mmsbouygtel.com"} 208 sfr {"generic": "sl2sfr"} 208 orange {"generic": "orange"} 268 vodafone {"generic": "internet.vodafone.pt"} 268 nos {"generic": "umts"} 405 vi india {"iot": "IOT.ZENATIX.COM"} 404 vi india {"iot": "IOT.ZENATIX.COM"} 405 ind airtel {"iot": "iot.com"} 404 ind airtel {"iot": "iot.com"} 724 tim internet {"generic": "timbrasil.br"} 724 vivo {"iot": "smart.m2m.vivo.com.br", "generic": "zap.vivo.com.br"} 724 claro {"generic": "claro.com.br"} 310 at&t {"iot": "armstrongdynm.com.attz", "generic": "NXTGENPHONE"} 440 fl1 {"generic": "soracom.io"} 302 bell {"generic": "mnet.bell.ca.ioe"} 302 rogers {"generic": "M2Minternet.apn"} 302 at&t {"iot": "armstrongdynm.com.attz", "generic": "NXTGENPHONE"} 404 idea {"generic": "Internet"} 431 etisalat {"generic": "mnet"} 430 etisalat {"generic": "mnet"} 424 etisalat {"generic": "mnet"} 424 du {"generic": "du"} 405 404 11 {"iot": "IOT.ZENATIX.COM"} 405 vodafone {"iot": "IOT.ZENATIX.COM"} 405 airtel {"iot": "iot.com"} 404 airtel {"iot": "iot.com"} 404 vodafone {"iot": "IOT.ZENATIX.COM"} 404 404 11 {"iot": "IOT.ZENATIX.COM"} 404 jio {"generic": "jionet"} 405 jio {"generic": "jionet"} Additional Information Ensure the SIM card is active and properly inserted. Verify the antenna cable is securely connected to the board. Confirm the SIM card has no firewall restrictions and meets the data plan requirements.  

Issue It is not possible to login to an Automation Server and it fails with the error "Domain Controller version too low' for certain users. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Remnants of an EcoStruxure Building Operation domain exist in the controller where it has not been removed completely and it is set as the Default Logon Domain. Resolution Login with Administrative Rights: Use a user account with Administrative rights in the Local or another domain explicitly using the Domain name. Delete Partial Domain: Once successfully logged in, delete the offending partial domain. Retry Login: Attempt to log in again. Additional Information: Ensure that the domain is completely removed to avoid future login issues. Verify that the Default Logon Domain is correctly set after removing the partial domain.

Issue After correctly following the process outlined in Setup External Log Storage using MSSQL., EcoStruxure Building Operation (EBO) server fails to connect to the external database, generating the following System Alarms:  Unable to connect to data source Login failed for user The system alarm specifically details an issue with the ODBC SQL Driver as below: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium (AS-P) External Log Storage [MSSQL]  Cause The system alarm details indicate an issue with the ODBC SQL Driver, specifically: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" This suggests a compatibility or configuration issue with the ODBC driver or connection string.   Resolution The following has been seen to correct the issue: Verify User Credentials Ensure that the username and password used for the ODBC connection are correct. Note: SQL Server credentials are case-sensitive, so double-check for any discrepancies in letter casing. Remove any uppercase for the username. In some cases, using only lowercase letters for the username in the ODBC connection string has resolved the issue, e.g,. Instead of "My_User" use "myuser"

  Issue This document gives guidelines on the device constraints that effect the system capabilities or the system limitations of the Flex Server.  Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Understanding this document helps in efficiently designing architecture and Single line Diagrams. Identifying potential bottlenecks in a system allows for preemptive action. If you know a system parameter has limited device capacity, you can optimize the distribution methods or plan for upgrades before it becomes a critical issue. Understanding the limitations of system allows for the implementation of backup measures. Resolution Thes guidelines provide the recommended Flex Server design limits for common applications. These are the configurations that have been tested and supported by Schneider Electric. Environmental factors such as network traffic and radio interference may reduce the stated limits of these guidelines. Deviations from these guidelines may result in performance related issues or product failures.   Flex Server Capacity Parameter Maximum Number Number of total devices (all protocols combined) 50 Number of controlled points (all protocols combined) 500   BACnet Parameter Maximum Number Number of BACnet MSTP devices per RS485 port 32 a b e Number of BACnet MSTP networks per server 2 c Number of BACnet IP devices 50 d e   a. Maximum number of devices according to protocol specifications and guidelines. b. BACnet MS/TP adheres to RS485 rules for wiring, wire type, termination etc. c. There is one onboard RS485 port, an additional port can be added via USB. d. BACnet IP uses default UDP port 47808 (0xBAC0). e. The total number of devices across all protocols must not exceed 50   Modbus Parameter Maximum Number Number of Modbus RTU devices per RS485 port 32 a b e Number of Modbus RTU networks per server 2 c Number of Modbus TCP devices 50 d e   a. Maximum number of devices according to protocol specifications and guidelines. b. Modbus RTU adheres to RS485 rules for wiring, wire type, termination etc. c. There is one onboard RS485 port, an additional port can be added via USB. d. Modbus TCP uses default TCP port 502. e. The total number of devices across all protocols must not exceed 50   LoRa a Parameter Maximum Number Number of LoRa sensors per server 32 b c d Maximum number of messages per day (per server) 100   a. LoRa distances – LoRa is noted for its long range and deep penetration. LoRa transmissions can penetrate glass, metal and concrete found in most buildings. The radio’s antenna and installation can affect the range of LoRa sensors. You must test the transmission and signal strength, when installing wireless devices. b. Maximum number of devices according to protocol specifications and guidelines. c. Every LoRaWAN sensor manufacturer has their own decoder. d. The total number of devices across all protocols must not exceed 50   SNMP Parameter Maximum Number Number of SNMP devices 10 a Maximum number of messages per day (per server) 1024   a. The total number of devices across all protocols must not exceed 50   Object Limits Object Type Maximum Number Analog values 500 a Digital values 500 a Multi-state values 500 a Analog Input 500 a Multi-state input 500 a Analog output 500 a Digital output 500 a Multi-state output 500 a   a. The total number of combined points must not exceed 500

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Data cannot be seen on Partner Portal for RS485 devices. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Data for the Modbus devices can be seen on third-party tools like Modscan but not on the Partner Portal. Resolution Follow the steps below if the Flex Server RS485 port is not sending any data: Ensure connections are made according to the installation instructions. Verify the correct port is configured. Double-check that the connections are not reversed. Inspect for any loose wires. Confirm the Modbus/BACnet ID is correct. Verify the baud rate configured for the end device. Check for any loose wire strands shorting on the bus or to the ground. Ensure no Modbus device is connected to the BACnet bus, or vice-versa. Confirm the number of devices in the loop matches the specifications in the installation instructions. Check if the loading of devices causes significant changes in resistance. Do not connect more than two resistors on a single bus. Ensure cables used are as per the specifications in the installation instructions.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Note: Always completely power OFF the panel whenever inserting or removing hardware in the panel. Issue Not able to see the network panels status, trouble messages, events, cause and effects etc. Product Line ESMI Fire Detection. Environment FFSULH1009. Cause Networking issues can significantly impact the performance and reliability of the Esmi Ultima system. This article provides troubleshooting steps to resolve common networking problems. Resolution The following network-related troubles can occur on the Esmi Ultima Fire Alarm Control Panel. See the detailed descriptions below for explanations on each trouble message.   Trouble Message Description Network Communications Trouble This event indicates there is no communication between this panel and its neighbor. This could be caused by a configuration error (such as using the wrong baud rate), a wiring error, or damage to the wires connecting the panel to its neighbor. If this trouble occurs on one link on the panel, then the panel is still in communication with other panels on the network. If this trouble occurs on both links on the panel, then the panel is no longer in communication with other panels on the network. Note: make sure remove the 0 ohm resistance from the network card. Unexpected Network Node This event indicates a panel has been detected on the network that is not in the configuration. This is a configuration error and should never occur once the network has been properly configured. Network Card Missing This event indicates that the panel is configured for networking, but there is no network card installed, or it is installed incorrectly. This trouble may also occur if the network card processor fails. Connection Error This event indicates that the panel has failed to get a meaningful result for the link impedance measurement. This may occur if stray leakage current enters the link wiring from elsewhere, or if there is a component failure or missing jumper on the network card. This event may also be shown when the network is disconnected or when the NET OUT + wire is disconnected. Network Panel Missing This event indicates that another panel is configured but has not been found on the network. This may occur if the missing panel is switched off or disconnected from the network. This fault will also occur if there is no communication between a panel and either of its neighbors on both links. In this case, the panel will show multiple instances of this trouble; one for each other panel on the network. Network Node Double Addressed This event indicates that more than one panel on the network has the same node number. This is a configuration error and should never occur once the network has been properly configured. Full Short Circuit Trouble This event indicates that a short circuit has been detected by the link impedance measurement. This indicates a wiring error, or damage to the wires connecting the panel to its neighbor. Full Open Circuit Trouble This event indicates that an open circuit has been detected by the link impedance measurement. This indicates a wiring error, or damage to the wires connecting the panel to its neighbor. The following two troubles are optional and are not included in the default firmware build. Partial Short Circuit Trouble This event indicates that the link impedance measurement has detected an impedance below the normally expected range. Partial Open Circuit Trouble This event indicates that the link impedance measurement has detected an impedance above the normally expected range.

Issue The SP90 Actuator alarm "BV:22 Temperature Sensors Missing or Interchanged" is triggered. Can we simply swap T1 and T2 in the configuration to fix this, instead of physically swapping the sensors? Product Line Field Devices Environment SpaceLogic SP90 Series Smart Actuator Cause The installer has installed the temperature sensors in the incorrect pipes. Resolution Firmware versions V439 (for actuators products marked V1xxx on the product label) and V539 (for actuators marked V2xx on the product label) introduced MSV:42 (T1 input) and MSV:43 (T2 input) which enable the temperature sensors to be swapped.   You are able to select each as: 1: Disabled 2: Supply temperature 3: Return temperature   If the SP90 actuator is at a lower firmware revision, it can be upgraded. Contact Product Support for the firmware files and upgrade instructions.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Having issues with the panel's networking and unable to operate the touch screen or receive trouble messages on the screen. Product Line ESMI Fire Detection. Environment FFSULH1009. Cause The display touch screen may not be working. Resolution You can identify the current situation by checking the LED status as described below:    LED Status LED indicators provide diagnostic information to identify communication.   LED Label  Name  Color  Description LED 1 Heartbeat Red Identifies functional status. LED 2 Tx Comms Green A blinking green light indicates that the module is transmitting data. LED 3 Rx Comms Green A blinking green light indicates that the module is receiving data. LED 4 Trouble Yellow A flashing yellow light identifies an error condition. LED 5 Not In Use Green Not In Use LED 6 Not In Use Green Not In Use LED 7 Not In Use Yellow Not In Use LED 8 Comms for SPI Bus Green Communication present when flashing LED 9 Full Duplex Yellow Full duplex (on) half duplex (off) LED 10 Ethernet Speed Red 10MHz (off), 100MHz (on) LED 12 Communication Green Communication present when flashing   Refer to ESMI Ultima Networking Troubleshooting for further assistance with network related problems

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue How are Elsys LoRaWAN sensors configured with a smartphone using NFC Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause All Elsys sensors are equipped with NFC for easy configuration with a smartphone. There is a requirement to configure these sensors using a Smartphone or tablet using Elsys 'Sensor Settings' application. Resolution Download the ELSYS “Sensor Settings” application from Google Play or the IOS App store and install it on a smartphone or tablet.     Ensure the mobile device supports NFC. Enable NFC on the device and start the application. Position the mobile device directly on the NFC antenna of the sensor. Ensure both devices remain close and stationary to maintain optimal connectivity. Remove the mobile device. The current settings will be displayed in the application. Set the 'Timebase' to 120 seconds using the application. Remember to revert it to 600 seconds after commissioning!    Make note of the following sensor keys: DevEUI: The unique ID of the sensor, found in the blue panel at the top. AppEUI: Application ID (8 bytes or 16 hex digits). Default is 0, can be changed if needed for the application. AppKey: Application unique key (16 bytes or 32 hex digits) that is the encryption key used for messages during every over-the-air activation. Tap the sensor's NFC antenna to transfer the new settings after making the desired changes. Ensure the application confirms the updated settings. Wait for the sensor to reboot, indicated by the LED flashing. The sensor settings should now be updated. Validate your settings by reading the NFC data after the sensor has restarted. Verify that settings have been applied by using the ‘Read’ functionality in the app and touching the sensor’s NFC antenna.    Remember to change the 'Timebase' back to 600 seconds after the commissioning is completed!

Issue After an upgrade the SP-C-WEB is showing "NOT REGISTERED" with the option to register the controller. Attempts to register the controller fail as it is already registered. SP-C-WEB not registered When attempting to create new records their is a "License Limit Reached" message displayed and the new records are unable to be created. SP-C-WEB license limit reached Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause Browser has cached settings for this controller that are interfering.  Resolution Use browser incognito mode and/or clear the browser cookies and cache.

Issue BACnet requires applications to listen on the same port across the IP subnet to receive BACnet discovery broadcasts. Two applications running on the same machine can not use the same port as the Listening Port. Product Line EcoStruxure Building Operation, Continuum, TAC I/A Series Environment Building Operation Enterprise Server I/A Series WorkPlace Tech Continuum Cyberstation Cause The site can not provide a separate machine or VM for each BACnet application, which is recommended for independent operation. Resolution With this configuration, one application will act as BBMD to receive and distribute BACnet Broadcast Messages. The other application will act as a Foreign Device, relying on BBMD to relay BACnet Broadcast messages. Once BACnet devices and the Application, configured as Foreign Device, have shared their IP and Port, messages between them will be unicast and will not pass through the BBMD. Ensure one application can be configured as a BACnet BBMD and the other as a Foreign Device. Configure one as BBMD, usually EBO Enterprise Server Configure the other application as a Foreign Device referencing the BBMD IP and Port

Issue The F3 Search function in EcoStruxure Building Operation (EBO) WorkStation does not return results for Notification File objects (e.g., .xlsx, .pdf, .txt), even when using wildcards.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Search Cause This behavior is functioning as designed (FAD). Notification files generated using the "Write to File" option are not stored in the EBO database. Therefore, they are not indexed and cannot be retrieved using the F3 search function. Resolution Although these files are not searchable within EBO, they are saved locally in a fixed directory: ...\db\notifications To assist users in locating these files:  Create a Hyperlink Object in EBO that points to the above folder. Users can then open the folder directly within WorkStation and use the operating system’s search functionality to locate specific files. Note: The notification file path is not configurable. For more information, refer to the official documentation in WebHelp: Accessing a Notification Written to a File

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue The internet is not working at the site, so it's necessary to verify that all antenna connections are secure and the SIM card is correctly placed. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server powers up successfully at the site, but the internet connection fails. This issue might arise if the antenna or SIM card was displaced, disconnected, or damaged during transit due to mishandling. Therefore, it's essential to verify that all connections are secure. However, the technician or engineer on-site may not be familiar with the correct slots. Resolution Carefully open the Flex Server top cover. The internal layout will appear as shown in 'Image 01' below: Image 01 Image 02 Identify the slots as follows: Slot 1: Indicates the SIM card slot. Slot 2: Located on the Compute Module marked as 'MAIN', indicates the Cellular antenna slot. Slot 3: Located on the Wi-Fi module marked as 'ANT0 WiFi', indicates the Wi-Fi antenna slot. Verify all connections and ensure they are secure. Carefully close the Flex Server cover.

Issue What is the password policy for Security Expert operators, and how can it be configured to meet specific cybersecurity requirements? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Cause Some sites require customized password policies to comply with cybersecurity standards. These may include requirements such as: Enforcing regular password changes Preventing the reuse of previous passwords Setting minimum password length Requiring strong password complexity Resolution   Default Password Policy in Security Expert By default, Security Expert enforces the following password policy for operator accounts: Minimum password length: 8 characters Password change required: On first login For more information on Security Expert’s cybersecurity practices, refer to the SX-SRVR Security Expert System Hardening Reference Guide. Custom Password Policies via Active Directory Integration Security Expert does not support advanced password policy configuration directly within the client interface. However, enhanced password policies can be enforced by integrating Security Expert with Windows Active Directory. To implement this: Integrate Security Expert with Active Directory Follow the steps outlined in Option 1 of the How to Integrate Active Directory with Security Expert article or Option 2 for full Active Directory integration. See AN 288 Security Expert - Using Active Directory - Integration Guide for additional details. Configure Password Policies in Windows Domain Once integration is complete, operator accounts managed through Active Directory will adhere to the domain’s password policy. This allows you to enforce: Password expiration intervals Password history restrictions Minimum and maximum password lengths Complexity requirements (uppercase, lowercase, numbers, symbols)

Issue When a Reader Expander is offline from the controller, users with Credential Type-based access are unable to be authenticated. Product Line EcoStruxure Security Expert Environment Security Expert SP-C, SP-AC1, SP-ACX SP-RDM2, SP-MRDM2 Cause Reader Expanders store a limited number of user card records locally, depending on the Offline Operation setting. However, user credentials (such as credential types, biometric or PIN-based data) are stored only in the controller, not in the Reader Expander. It’s important to note that the term "card" in the Offline Operation feature (as described in the online help and the SX-SRVR Security Expert - Operator Reference Guide) refers specifically to the Card Numbers section [1] of a user record, not the Credentials section [2]. User record Resolution The Offline Operation functionality of Reader Expanders supports authentication using Card Numbers only. It does not support authentication using Credential Types when the expander is offline.  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Access Expert uses Docker containers and images for the Bosch and Schindler integrations and at times the virtual machine image(s) need to be updated. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Feenics updates virtual machine images which requires an update Resolution Feenics may update a Docker image for one of their integrations.  Note: A Docker software update may be indicated in the bottom right of the Docker Window This is only a software update for Docker and will not update the container image. An image update requires a command to Pull the image down from Feenics. The Docker software update is not required to update the Docker Image.  (see yellow highlight in the snapshot below)   Here are the instructions to update the Docker Container Image to the (latest) Open Docker Desktop for Windows 1. Under Containers, make note of the current bosch service name Ex. AX-bosch-service1 2. Stop the container/service using the stop button 3. Click the Red Delete button above the container Click Delete Forever No container after the delete Image still shows 4. Delete the Image by clicking on the Red Delete button under Images Select Delete Forever (Image) Image deleted (See below) 5. Click on the Blue button 'Search images to run' Type in the following to search for Images feenics/keep-bosch:latest   6. Select the 'feenics/keep-bosch:latest' Image and Click PULL You will see the progress of the image downloading 7. Click on Containers on the top left - the container will not be there 8. Click on Images and then Click the Play button on the Feenics/bosch entry 9. On the next screen, after selecting Play, select the down arrow next to Optional settings Enter the original container name that was noted above i.e. AX-bosch-service1, Click Run You will see messages from the bosch service startup Although the image is updated and running, you will likely see an 81 exception error in the startup log (see highlight above). Here are some additional steps to finalize this process.   10. Check in Windows Services> Docker Desktop Service One of the updates along the way may have changed the startup type to Manual Double-click on the service and select Automatic for Startup type Click Start (to start the service) Click Ok.   11. Open Windows PowerShell in ADMIN mode (standard mode will not work) Run the following command   docker run -d --restart unless-stopped --name feenics-bosch-service --env-file C:\ENV\env-us.txt feenics/keep-bosch   If you try to run the command with the same name as the original service, you will receive the following message in PowerShell  Successful running of the Power Shell command This command ensures Docker runs with the parameters that are stored in c:\env-us.txt 12. Click on Containers, and there will be 2 Containers Select the one that is NOT running and click the Red Delete button The Delete Forever prompt comes up, select the Delete forever button One container should remain and should be running The panel should be online and communicating 13. Test and verify everything is working with the Bosch integration