Issue Can AC-powered sensors be connected to the same Central I/O module that already has DC-powered sensors? Or is it better to separate them across different I/O modules? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch UI Cause Is it technically feasible and advisable to mix AC and DC powered sensors on the same Central I/O module? Resolution Yes, AC and DC powered sensors can be connected to the same Central I/O module. Here's why:   Signal vs. Power Supply Regardless of whether a sensor is powered by AC or DC, the signal transmission (e.g., 0–10 V or 4–20 mA) is always DC-based. The type of power supply (AC/DC) does not affect the signal processing by the I/O module. Module Design Considerations All Central I/O modules share the same backplane, so separating AC and DC sensors across modules does not provide any electrical isolation benefit. The Signal Ground Rail (SGR) is critical. Each I/O module must be connected to the SGR to: Prevent current from flowing through the backplane. Ensure stable and accurate signal measurements. RET Terminal and Jumper Use Even if RET terminals are at the same potential, using a jumper between them can cause: Unintended current flow through the jumper. Measurement inaccuracies due to shared current paths. The SGR is designed to handle these currents safely and independently, avoiding interference between devices. Best Practice Recommendation Use the Signal Ground Rail (SGR) for all RET connections. Avoid relying on jumpers between RET terminals to prevent cross-device current interference. Mixing AC and DC powered sensors on the same module is acceptable, provided proper grounding practices are followed.

Issue When adding an Enterprise Server (ES)S to an Enterprise Central (EC) the following error is seen: "Cannot add a server to the system with an already existing unique ID". The option to restore an Enterprise Server (ES) backup with new GUIDs is greyed out and not available. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The error indicates that the ES has been cloned and has the same Globally Unique Identifier (GUID) as another ES in the system. The GUID is a unique identifier tied to the server's configuration and database structure. Changing the GUID of an Enterprise Server by restoring from a backup with new IDs is not supported due to system integrity and object referencing constraints within EBO.  Resolution Restoring an Enterprise Server with new IDs (GUIDs) is not possible or supported. The recommended approach is: Set up a new Enterprise Server instance. Use the Export/Import feature to transfer supported objects from the template ES. Manually configure any settings or objects that cannot be exported.  

Issue Users encounter the following error when launching Device Administrator: “The following error(s) occurred while reading the server list file: - The site-specific server password could not be loaded. It will be set to the default password ‘admin’. - One or more SSH public keys are invalid.” Additionally, devices may show: - “SSH public key fingerprint changed!” - “Wrong logon” errors for connected Servers  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Device Administrator Access Method: Remote Desktop Multiple Windows user accounts or sessions 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. Cause This issue is caused by shared use of a single server list file across multiple Windows user accounts or sessions. When another user opens Device Administrator—even without modifying or saving the server list—the SSH keys become invalid due to security hardening measures. This behavior is by design to prevent unauthorized access and is part of Schneider Electric’s cybersecurity strategy. Resolution Recommended Workflow  Create and Save the server list on the original user account or PC. Export the server list using the built-in export feature in Device Administrator. Import the server list on the target user account or PC. ⚠️ Do not copy the XML file manually between users or systems. This will invalidate SSH keys and passwords due to security restrictions. Best Practices Use unique filenames when exporting server lists (e.g., include user initials). Avoid using shared server list files across users or sessions. If the server list becomes corrupted or invalid: Re-import the previously exported working server list. If unavailable, recreate the list and export it immediately for future use. Additional Notes This issue can occur even if only one user accesses the system, especially if the server is accessed via Remote Desktop and multiple sessions are involved. The server list file ( Servers.xml ) should always be managed through the export/import functionality to preserve encryption and key integrity. Affected devices may require re-authentication or re-adding if the server list is corrupted and cannot be recovered. References Import and Export a List of Field Server Workflow

Issue After adding an OPC UA server to EBO an export is done from the Device discovery tab to find the objects in the OPC UA server. When the OPC UA server database is big this can take up to a day to finish and sometimes the export is never finished. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause In EBO version 7 there is a workaround for this issue, it is possible to split the export up in smaller pieces and export objects from specified folders from the OPC UA server instead of all objects in the OPC UA server database.   Resolution Introduction The ‘Export configuration’ section in the settings dialog for discovered devices makes it possible to configure the export procedure. By setting the parameters in this section, you can specify the start node and the depth for each export file. This means that you can break down the export into many files instead of one large file containing everything. When importing the series of export files it is recommended to keep the same structure as the OPC UA server has, but it is not a requirement. You can import the export file anywhere under the device, but again, the recommendation is to keep the same structure as on the OPC UA server.   Selecting start node for browse The start node is specified by setting the ‘Start node namespace index’ (specified as an integer value) and the ‘Start node identifier’ (specified as a string value). The supported ‘Start node identifier’ types are string (s=), integer (i=), opaque (o=) and guid (g=). Both ‘Start node namespace index’ and ‘Start node identifier’ are found as properties on each OPC UA object. If these values are empty, faulty, equal to the object node or equal to the root node, the device object is included in the export file. Otherwise, it is omitted. Selecting the depth of browse The depth of an export file is specified as an integer value. It is recommended that this is set to a low number if the export time is expected to take a long time. Values 0, -1 or empty means that no depth limit is used. Getting started   A first step could be to export the root objects. The following configuration will handle that: The export file with this configuration will produce the following result when imported. Since the ‘Start node namespace index’ and the ‘Start node identifier’ are empty, the device object is included, and the import can be done on the ‘OPC UA Client Network’ object Only the root objects were included in the export file since the ‘Export depth’ was set to ‘1’. Next, we would like to populate the ‘BuildingAutomation’ object with 2 levels of child objects. For that we need the namespace index and the identifier of the ‘BuildingAutomation’ object found at the bottom of the property list:   These values are entered into the export configuration: The export file with this configuration will produce the following result when imported on the ‘BuildingAutomation’ object: Now we have a structure with all the root objects. All of them are empty except for BuildingAutomation that has two levels of child objects.   If you realize that the depth chosen was to low, you can simply set the ‘Export depth’ to a higher value and create a new export file from the same start node. The ‘Export configuration’ will now look like below: When importing the new export file we still use the ‘BuildingAutomation’ object as the start object, but since we already have two level of child nodes we need to select the merge option in the import dialog as in the picture below:    

Issue Bindings to graphics and programs on SpaceLogic IP controllers are being unexpectedly added or removed. Product Line EcoStruxure Building Operation Environment SpaceLogic IP Controller Custom Types 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. Cause When a custom type is modified, a re-typing process is automatically triggered. The outcome of this process—specifically whether bindings are retained or lost—depends on the reference type used within the custom type. Resolution Care should be taken when designing custom types, as bindings within the type can be defined using one of three reference types: - No Reference Inner Reference Outer Reference Each reference type behaves differently during re-typing operations and can impact whether bindings are retained, added, or removed.     When a custom type is modified or re-applied (e.g., attached to an object instance, version-changed, or undo check-out), a re-typing process is triggered. The behavior of bindings during this process depends on how they are defined in the custom type:   No Bindings in Custom Type If the custom type does not contain any specific bindings, then during re-typing, existing bindings in the instance will be removed. Bindings Should Be Defined in the Custom Type To preserve bindings during re-typing, they should be explicitly added to the custom type using either: Inner References Outer References (with inner reference locked) Inner Reference Behavior If inner reference bindings are defined in the custom type, they will be automatically added to the instance during re-typing, even if they were not previously present. Outer Reference (Locked) Using outer references with inner reference locked ensures that bindings are preserved and not unintentionally modified during re-typing For more detailed information on the re-typing process and reference behavior, please refer to the Re-Type section in WebHelp.

Issue Integration between Power Monitoring Expert (PME) and EcoStruxure Building Operation (EBO) fails due to default security settings that prevent embedding external web content. Product Line EcoStruxure Building Operation Environment Building Operation WebStation PME Web Applications Cause By default: PME restricts other applications from embedding its web content. EBO blocks external web content from being embedded in its UI. To enable integration, both systems must be configured to allow embedded content. Resolution  ✅ Enable External Content in EBO WebStation Log into Building Operation Workstation. Navigate to: Tools > Control Panel > Security and Communication > Security Settings Under WebStation, check the box: ✔ Enable external content to be embedded in WebStation  ✅ Authorize EBO to Embed PME Web Applications Open PME Web Applications. Go to: SETTINGS > Security > Authorized Hosts Add the Building Operation server URL to the Hosts That Can Frame list. Example: https://localhost:446 Click Save. Reset IIS (Internet Information Services) on the PME server to apply changes. Notes Ensure both systems are updated to compatible versions. Use secure URLs (HTTPS) when configuring host permissions. Resetting IIS may cause temporary downtime—schedule accordingly.

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 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 configuring BACnet alarms in EcoStruxure Building Operation (EBO), users may encounter a potentially misleading message in the Monitored Variable description: Monitored variable: Choose the method for referencing the property that you want to monitor. Select System reference to define a path-based reference to an object or property that is currently located on the EcoStruxure BMS server. While technically correct, this statement may cause confusion. It suggests that any object or property on the EBO server can be used as a monitored variable for BACnet alarms. However, only specific BACnet objects and properties are supported for each alarm type. Product Line EcoStruxure Building Operation Environment EcoStruxture Building Workstation Bacnet Alarms Cause The ambiguity arises from the assumption that all BACnet objects and properties are valid for alarm monitoring. In reality, only a subset is supported depending on the alarm type. Misconfiguration can lead to unexpected behavior or non-functional alarms. Resolution To ensure proper configuration, refer to the table below for supported combinations of BACnet objects and properties for each alarm type: Alarm Type Monitored Variable Object Monitored Variable Property Change of State BACnet Digital Input Value BACnet Digital Output Value BACnet Digital Value Value BACnet Multistate Input Value BACnet Multistate Output Value BACnet Multistate Value Value Change of Value BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value Floating Limit BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value Floating Limit Setpoint Reference BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value BACnet Loop Setpoint Out of Range BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value BACnet Digital Input Value BACnet Digital Output Value BACnet Digital Value Value BACnet Multistate Input Value BACnet Multistate Output Value BACnet Multistate Value Value Buffer Ready BACnet Trend Log (Any) — Additional Reference For more details, see: 🔗 BACnet Alarm Types and Monitored Variables Table

Issue The HVAC Optimization module in the Building Advisor (BA) portal is currently displaying data that is two months behind the current date. Snapshot: The image below illustrates the data available within the HVAC Optimization module as of October. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Advisor HVAC Optimization Module Cause This does not represent a defect in data collection or in the functionality of the Building Advisor Portal Resolution The limited data display is intentional and aligns with the system’s design principles. Energy providers often apply retroactive adjustments to consumption records, and interim placeholder values can be unreliable. By excluding these, the system ensures data integrity and accuracy. Additional Notes: This behavior is expected and documented. No action is required unless data is missing beyond the expected two-month delay.

Issue Which port (P1 or P2) should be connected to the high and low pressure? Product Line Field Devices. Environment EasyLogic CP Series Differential Wet Pressure Transmitter (CP-LI-DP-TR-xxxx) Cause The product documentation does not clearly specify which port corresponds to the high-pressure side and which to the low-pressure side. Resolution P2 is the high-pressure port. P1 is the low-pressure port.  

Issue How to check installed Power Monitoring Expert (PME) and Cumulative Update (CU ) versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Power Monitoring Expert Cause When troubleshooting integration issues between Power Monitoring Expert (PME) and EcoStruxure Building Operation (EBO), it's important to identify the installed PME version and its corresponding Cumulative Update (CU). Knowing the exact PME and CU versions helps ensure compatibility and can assist in diagnosing integration problems between PME and EBO. Resolution To check the installed PME and CU versions: Open the Windows search bar and type regedit . Press Enter to launch the Registry Editor. Navigate to the following registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Schneider Electric\Power Monitoring Expert\X.X\CumulativeUpdate Review the values listed under this path. These entries will indicate: The installed PME version The Cumulative Update (CU) version, if applicable

Issue Users are intermittently unable to gain access through doors equipped with INET hardware that has been transitioned to Security Expert. When this occurs, a “Read Raw Credential Data” event is logged for the affected door, showing the correct credential was presented. Product Line EcoStruxure Security Expert Environment Security Expert INET transition sites using INET SCU controllers Cause Some sites using transitioned INET hardware continue to experience memory consumption issues with the SP-C controller. This can result in sporadic access failures at random doors, even though valid credentials are presented. Resolution Temporary Resolution Restarting the parent SP-C controller via its web interface temporarily resolves the issue by clearing the memory.  Recommended Action To avoid recurring disruptions and benefit from the full functionality and stability of Security Expert, it is strongly recommended to phase out obsolete INET hardware and replace it with native Security Expert modules.   Refer to the following product announcements for further guidance: PA-00786 – End of Commercialization: TAC I/NET Access Control PA-00971 – I/NET Access Control End of Support Update and New Hardware Refresh for Transitions “We no longer recommend continuing to use I/NET field hardware with Security Expert intelligent controllers, as it will leave end users vulnerable to disruptions and potential failures as the legacy hardware continues to age. Instead, we will focus on supporting I/NET database transition tools, aiming to streamline the transition and installation process.”

Issue Clarification on the term "Semi Online System" within EcoStruxure Building Operation environments. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Device Administrator Cause The term refers to a specific system configuration used when full internet connectivity is not feasible for all components of the Building Management System (BMS). Resolution A Semi Online System is designed for secure environments where internet access is restricted for core systems but still allows licensing and administrative operations. Here's how it works: System Components EcoStruxure BMS Servers Network These servers are not connected to the Internet. They cannot access the License Activation Server. Device Administrator Computer This computer is connected to the Internet. It has access to the License Activation Server. It can also connect to at least one field server within the BMS network. Licensing Implications The system is treated as online for licensing purposes. Offline licensing workflows are not required. Licensing and administrative tasks are performed via the Device Administrator, which bridges the gap between the internet and the isolated BMS servers. Benefits of a Semi Online System Security: Core systems remain isolated from the internet, reducing exposure to external threats. Flexibility: Licensing operations can still be performed without requiring full internet access for all components. Compliance: Suitable for environments with strict IT policies or regulatory constraint

Issue Access to the correct version of Device Administrator or WorkStation is unavailable, and a backup of the Automation Server is required. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause In certain scenarios—such as on-site troubleshooting or version incompatibility—the appropriate tools (Device Administrator or WorkStation) may not be accessible. In such cases, an alternative method is needed to perform a backup.   Note: In EBO 2022 (4.0.3) and later, backups can be performed and downloaded using WebStation Resolution Follow these steps to perform a backup using WinSCP, a secure file transfer tool compatible with all system versions. WinSCP is compatible with all versions of EcoStruxure Building Operation. It requires communication over port 22 (SSH). Download WinSCP Launch WinSCP Open the application after installation. Log In Use the Admin username and password. Select SCP as the protocol.   Navigate to the Backup Folder Browse to the folder containing the server backup files. Refer to the image provided below for the folder location. Download the backup files to your local machine. Additional Notes Ensure SSH access is enabled on the Automation Server. If login fails, verify credentials and network connectivity. This method is suitable for quick, manual backups when standard tools are unavailable.  

Issue The “User Last Active” field does not update when users access controlled elevators using their access cards. As a result, users who primarily use elevators are incorrectly marked as inactive and automatically disabled after 90 days, despite regular use. Product Line EcoStruxure Security Expert Environment Security Expert Elevator integrations (e.g., OTIS, low-level relay) User inactivity policies (e.g., auto-disable after 90 days) Cause The “User Last Active” feature is designed to track access events at doors or keypads. When a reader expander is configured in elevator mode, the system does not associate elevator access with standard access events. Therefore, elevator usage does not update the “User Last Active” timestamp. Note: The current documentation does not clearly state that elevator access is excluded from this feature. It only references doors and keypads, which may lead to confusion. Resolution If tracking elevator access as part of user activity is required, we recommend submitting a feature request through your local Solution Category Management team. This ensures the request is formally reviewed and prioritized for future development.   Workaround: Create a Report of Disabled Users Open the User Report. Add a filter: Disable User equals Yes disabled user filter Save the report layout for future use. For detailed steps on applying filters in reports, refer to the Security Expert Community Post Security Expert User Reports.

Issue Users are visible in the Security Expert thick client, but when accessing the Web Client, a persistent “Loading” icon is shown instead of user data. Web Client Loading Product Line EcoStruxure Security Expert Environment Security Expert Web Client 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. Cause This issue is caused by hidden control characters—specifically the Unit Separator (US)—embedded in user data during the initial import into Security Expert. These characters are invisible in most editors but can be detected using tools like Notepad++ by enabling: View > Show Symbol > Show All Characters Unit Seperator Resolution Step 1: Identify Affected Users Copy the Unit Separator (US) control character between the brackets below: [] Open the Security Expert thick client. Navigate to the Users tab. Paste the US control character into the search field. This will return all users containing the hidden character. Step 2: Clean Up User Data For each affected user: Open the user record. Re-edit the First name, Last name, and Name fields. Ensure no invisible characters remain. Save the changes. Prevention – Best Practices for Data Import To avoid this issue in future imports: Sanitize data before importing into Security Expert. Ensure control characters (ASCII 0–31) are removed, except for common ones like tab, newline, and carriage return. Follow these recommendations: Export data in plain text (UTF-8) format. Use a text editor or script to scan for and remove non-printable characters. Validate CSV files using tools that highlight or strip out control codes before importing.

Issue How many TC900 thermostats can be connected to a single BACnet MS/TP network on an AS-P? Product Line EcoStruxure Building Operation, Field Devices. Environment Building Operation Automation Server Premium. Building Operation Automation Server Bundled. TC900 Protocol Series Thermostat Cause Understanding system limitations for a single COM port when using BACnet MS/TP protocol. Resolution   Maximum Number of TC900 BACnet Devices per MS/TP Network Port Device Type Baud Rate Max Devices AS-P 9600 bps 7   19200 bps 16   38400 bps+ 26 AS-B 9600 bps 4   19200 bps 10   38400 bps 15   76800 bps 20 Additional Notes Performance Optimization: MS/TP field buses perform better with an RS-485 repeater. This may be necessary depending on the network layout and connected devices. Device Load Consideration: All devices (including TC900 and third-party BACnet devices) should present a 1/8 Unit Load to ensure proper bus performance. Recommended Baud Rate: For optimal balance between speed and reliability, 38400 bps is typically the best choice.

Issue A streamlined and automated method is needed to move Enterprise Server (ES) backup files when the program is installed on the D:- drive and program data is stored on the C:- drive. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause   There may be operational or storage-related reasons to move or archive backup files. Installing the program on the D:- drive while retaining data on the C:- drive offers several benefits. Benefits of Separating Installation and Data Drives ✅ Storage Optimization The D:- drive often has more available space, allowing larger installations without impacting system drive capacity. ✅ Performance Improvement Separating installations from data can improve performance, especially if the D:- drive is a faster SSD. ✅ Simplified Backup and Recovery Storing data on the C:- drive simplifies backup and restore processes, avoiding the need to include the entire program installation. ✅ Improved File Organization This separation leads to a more structured file system, making application and data management easier. Resolution It is recommended to initially save backups in the default ProgramData folder on the C: drive and then move them to the D:- drive using a scheduled PowerShell script. PowerShell Script Example # Set variables $Now = Get-Date $Days = 5 $TargetFolder = "C:\\ProgramData\\Schneider Electric EcoStruxure\\Building Operation X.x\\Enterprise Server\\db_backup\\LocalBackup" $Extension = "*.xbk" # Backup file extension $LastWrite = $Now.AddDays(-$Days) $BackupLocation = "D:\\BackupArchive" # Destination folder for old backups # Ensure destination folder exists if (!(Test-Path -Path $BackupLocation)) { New-Item -ItemType Directory -Path $BackupLocation | Out-Null } # Move files older than $Days to the backup location Get-ChildItem -Path $TargetFolder -Filter $Extension -Recurse | Where-Object { $_.LastWriteTime -le $LastWrite } | Move-Item -Destination $BackupLocation -Force 💡 Tip: You can enhance this script with features like file compression, logging, or automatic cleanup of obsolete backups. Automation Recommendation Use Windows Task Scheduler to automate the script execution. 📘 How to schedule PowerShell scripts

Issue A malfunction in Power Monitoring Expert (PME) may occur due to the installation of a 32-bit version of SQL Server. Product Line EcoStruxure Building Operation Environment Power Monitoring Expert Cause The issue may stem from using a 32-bit SQL Server, which is incompatible or suboptimal for PME. Resolution You can determine the SQL Server architecture using either of the following methods: Method 1: Using SERVERPROPERTY Open SQL Server Management Studio (SSMS) and connect to the target SQL Server instance. Click New Query. Ensure the master database is selected. Run the following query: SELECT CASE WHEN CHARINDEX('64', CAST(SERVERPROPERTY('Edition') AS VARCHAR(100))) > 0 THEN 64 ELSE 32 END AS [SQL Server Bit Version]; Click Execute. 🔍 Result: The query returns either 32 or 64 , indicating the bit version of the SQL Server instance. Method 2: Using @@VERSION Alternatively, run the following query: SELECT @@VERSION; 🔍 Example Output: Microsoft SQL Server 2008 R2 (SP1) - 10.50.2550.0 (X64) Standard Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) Look for (X64) or (32-bit) in the output to determine the architecture.