Building Automation Knowledge Base

Issue Maximum number of expansion modules and doors per controller Product Line EcoStruxure Security Expert Environment SP-C Security Expert Security Expert Controller SP-RDM2 Security Expert Security Expert Door Expansion Module Cause Documentation states that one SP-C supports up to 128 doors but this is dependent on the communications.  Resolution The current recommendation from Product Management is a maximum of 24 to 34 doors per SP-C. This equates to about 10 to 17 reader expansion modules.  

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. License not found Product Line EcoStruxure Security Expert Environment Security Expert Server Cause This error generally occurs when trying to license Security Expert from a Client machine and not the  Server machine where the Security Expert services are installed. Resolution Go to the Security Expert Server and license/update the license from that machine using the Security Expert client.

Issue Unable to configure alarms to remain active after being acknowledged if they are still in the alarm condition. Product Line EcoStruxure Security Expert Environment Security Expert Cause Security Expert handles alarms a little differently to the rest of our product lines. The main difference being that everything is event based with each transition being an event which can itself trigger an alarm if it has been configured to do so. Those alarms are then seen as "active alarms" in the system (showing up in the Active Alarms Status Page View) until they are acknowledged by an Operator. Each alarm transition is separate with there being no direct tie to the current status of the object/condition that triggered the original alarm. Resolution What you can do is have both an Active Alarms list and an Acknowledged Alarms list in the same status page view. That way you will be able to see the last events that have triggered an alarm and if it has been acknowledged by an operator yet or not. This coupled with a status list of the objects you are monitoring can provide the operator with enough information to identify and manage each event transition of the alarm condition.

Issue Partners and branches need to understand the terminology used with Security Expert and what those terms mean from a Continuum perspective Product Line EcoStruxure Security Expert Environment Security Expert Continuum Cause A table key to map object terminology between Security Expert and Continuum Resolution   Continuum Security Expert Objects Records User Operator Personnel User Area Door Group (Area) = Intrusion/Antipassback/Counting Area Rights Access Levels AC1/IOUs Reader Expanders/RDM2 Numerics Virtual Inputs/Outputs Plain Enlgish Programmable Functions/Function Code/services Event Viewer Status Pages Alarm Viewer Status Pages Listview Status Pages Power Supply Analog Expander Network Sites NC/ACX Controller SPC Doors Doors Security levels Security levels Schedule Schedule Scedule Exception Calendar Action Holiday Holiday Reset Manual - Factory default – short Reader, L2D0, download Array Data Values Permisssions/Security Levels Record Groups +V V+ Ground V- Data 1 1 1 Clock 0 0 0 LED L1    

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 After making changes to object names in the system, outdated or incorrect names may still appear under the Hardware folder in EcoStruxure Web Services (EWS).     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) EcoStruxure Security Expert Smart Connector Integration EcoStruxure Web Service (EWS). Cause When significant changes are made to object names in the system, the Smart Connector may retain outdated data. If a standard Discovery does not update these names, the most effective solution is to clear the Smart Connector database and re-establish the connection.   Resolution To clear the outdated data from the Smart Connector:   Step 1: Access the Smart Connector Portal Open a browser and navigate to http://localhost:8082 (assuming Smart Connector is installed locally). Log in to the Smart Connector Portal. Step 2: Delete the Existing Processor Configuration Go to Configurations → Processor. Locate the Security Expert Discovery Processor. Click the Delete (bin icon) next to it. ⚠️ Do not delete other processors (e.g., Alarm Processor). Step 3: Delete the Existing EWS Server Navigate to the EWS Servers section. Locate the SecurityExpertServer. Click the Delete (bin icon) to remove it.   Step 4: Reconfigure the Processor and EWS Server Follow the instructions in Section 4.4 of the referenced document [1] to: Add a new Security Expert Discovery Processor Configure a new EWS Server Allow 10–15 minutes for the initial discovery process to complete. This will create a fresh snapshot of the current Security Expert database. Once the discovery is complete: Refresh the Hardware folder in EcoStruxure Building Operation. Rehost the new EWS objects as needed. Step 5: Verify Alarm Processor Configuration After re-adding the EWS Server, ensure the Alarm Processor is correctly configured to reference the new server. Refer to Section 4.5 of the same document [1] for detailed steps.   Reference [1] Refer to the official integration guide documentation for more information. Security Expert SmartConnector Version 1.1.0.8 - Installation & User Manual  

Issue Can licenses be transferred in Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Cause Unsure if a single SSN can be authenticated on multiple PC's or if licenses can be transferred or moved. Resolution Each PC requires a separate SSN. These licenses can be transferred between PC's. As part of the licensing process, the hardware details of the computer are recorded against each SSN, so any hardware changes require re-licensing, this also means SSN's cannot be shared across computers, and if used on a virtual machine – it must be assigned a static MAC address. Licenses can be transferred between machines without issue, Product Support will add a registration onto the license and clear the hardware profile after receiving a request. The installer will then do a License Update from the Security Expert server.

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 When hosting objects from EWS/Smart Connector, such as Security Expert, into EcoStruxure Building Operation (EBO), additional or mismatched object names can result in unresolved bindings and duplicate EWS IDs. Common symptoms include:  - Duplicate EWS IDs with different names - Unresolved or broken bindings - Binding loss after deleting containers   Duplicate EWS IDs with different names Unresolved or broken bindings     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) Security Expert Smart Connector Integration EcoStruxure Web Service (EWS) Cause Typical reasons for this to occur: Hosted object names do not match those in Security Expert. Deleting containers without proper renaming can cause binding loss. Resolution   Best Practices for Future Hosting Always rename the hosted object in EBO before rehosting from the hardware folder. This ensures that existing bindings are preserved. Avoid hosting the entire `SecurityExpertServer` container—only host changed or new objects. For Unbound or Irrelevant Objects: - If objects have no bindings, naming is not critical from an EBO perspective - Delete the container and rehost the object from the **Hardware folder**.   To Retain Existing Bindings  Identify the correct object name in the Hosted Containers folder  Copy the name to avoid typos. Delete the duplicate object with the correct name. Rename the existing EWS ID to match the copied name. Save the rename Verify bindings: Right-click the renamed object Select Delete Click Show References Confirm bindings are still valid. Click No to cancel deletion. Repeat this process for each object (inputs, outputs, doors, etc.) that has existing bindings.  

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 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 For hardware failure or persistent issues, it is necessary to replace Security Expert hardware components Product Line EcoStruxure Security Expert Environment Security Expert SP-C or SP-C-Web controller Expanders (i.e. RDM2 or SP08) Card Readers Cause A hardware failure occurs or a persistent issue happens that requires steps to replace Security Expert hardware Resolution At times it's necessary to replace Security Expert hardware   Steps to replace Security Expert SP-C Controllers: 1. Determine if the original controller has encryption turned on If the failed controller was setup for encrypted communications with the Security Expert server, the newly installed replacement controller will not have the encryption keys to be able to decode the packets from the server. Attempting to bring it online will be unsuccessful. On the controller's Configuration tab press the Disable controller encryption, then Yes to confirm. A replacement controller will typically be unencrypted. As soon as it shows online you can decide if you want to encrypt it. If it was already encrypted in Security Expert before replacing it, you might need to hit the encryption button again to get it in sync. Note: It can be helpful to use the event server diagnostic. If you see messages including “unencrypted” set encryption on the controller and see if it comes online. 2. Disconnect the old controller from its networks unplug ethernet and RS-485 module network and other hardware 3. Replace the Serial Number in Security Expert In Security Expert, navigate to Sites | Controllers. Replace the Serial number of the old controller with that of the new one. 4. Disable encryption In the Configuration tab, click Disable controller encryption. 5. Default the Controller If the controller has been used on a different server, default the new controller. See the SP-C Installation manual for detailed steps on performing a controller default https://ecoxpert.se.com/search?documentUUID=b4fb1237-fd07-2ee5-d9ad-4324178c364c&title=SP-C%20Security%20Expert%20-%20Security%20Purpose%20Controller%20-%20Configuration%20Guide  6. Enter the event server settings on the controller Log in to the new controller's web interface. In Settings, enter the same IP settings, event server and ports as those of the old controller, then restart the controller. Note: Remember to remove the jumper used to default the controller 7. Connect the new controller to the networks and hardware The controller should come online in Security Expert if all the network settings, serial number and encryption settings are in sync. 8. Download the controller In Security Expert, right click on the controller record and select Force download. The controller should receive the download. 9. Enable encryption Once the controller is online, in the Configuration tab click Enable controller encryption in Security Expert if desired. Steps to replace Security Expert SP-C-Web Controllers: 1. Take a backup of the old SP-C Web controller Login to SP-C Web, In System | Backup controller This creates a .bak file prompting to save in a folder or in the downloads folder 2. Disconnect the old controller Unplug the controller from the ethernet network, the RS-485 module network and other hardware. 3. Register the new controller Log in to the new controller and register it in System | Licensing 4. Restore the previous backup taken Navigate to System | Backup and Choose File and browse to the previously created .bak file 5. Configure the IP settings In System | Settings, enter the same IP settings as those of the old controller, then restart the controller 6. Connect the new controller to the networks and hardware and Test Steps to replace Security Expert Expanders: 1. Disconnect the old expander from the RS-485 module network and any inputs, outputs or card readers. 2. Connect the new expander to the module network and hardware. 3. Set the new expander's address to the same as that of the old expander.  In Security Expert, navigate to Sites | Controllers, right-click the controller and select Module addressing.  In SP-C-WEB, use the Expanders Wizard. To address a keypad, power cycle it and then press [X], [Enter]. Enter the new address and press [Enter] to save. Note: Sometimes the old expander can remain in the module addressing window even after being physically disconnected. To free up the address, module update the expander record. This will fail, but the address should become available. 4. Module update the new expander. The expander should start operating normally using the programming from the original expander. Steps to replace Security Expert Card Readers: 1. Disconnect the old card reader from the reader port. 2. Connect the new card reader 3. Apply any Custom Configurations If the reader needs any custom configuration, apply it within two minutes of the reader starting up using the config card. 4. Wiegand and RS-485 readers should connect automatically For OSDP readers, put the card reader into installation mode, then send an OSDP install mode command to the reader expander.   Additional configuration after controllers have been replaced If used at the site, areas that are configured for duress alarms default to un-armed after a SP-C has been replaced and need to be re-armed via forced arming. If used at the site, the alarm dialer (Contact ID) "Service Mode" defaults to "0 - Manual Mode" after a SP-C has been replaced (see the arrow below) and needs to be changed to "1 - Start with controller OS". Service mode Test the replaced hardware to ensure the issue is resolved

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 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).

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 What third party Card Printers are supported for use with Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Client Third-party Card Printers Cause There is no list of supported printers as there are too many devices to test.  Some testing has been done as listed in the resolution below.  If an issue should come up with a card printer then raise a support case and they will assist where possible and offer suggestions regarding the update of printer drivers, windows and printer preferences, etc. If necessary and the customer cannot resolve an issue then they may wish to supply the particular printer for testing and validation. Resolution There is currently no list of supported Card Printers, the following two printers have been tested by Engineering  with Security Expert: Datacard SD260 Datacard CD800 Indications that the HID Fargo HDP8500 and Fargo DTC4500e also work with Security Expert. In general, if the card printer presents itself in Windows as an XPS printer, then the printer should work with the Security Expert Client. This may require a printer driver to be downloaded and installed from the printer manufacturer for the printer to show up in the "Printers and Scanners" list in Windows.   Note: R&D has indicated that currently (12/19/2024) there is no list of printers or documentation as to what specific features or configurations are supported by each printer above.   Some functionality in Security Expert and within printer drivers allows the selection of landscape or portrait orientation. However, hopper selections are not currently supported. Printer testing was done with standard iso card printing using landscape and portrait using a single hopper. Any other requirements outside the above will rest fully with the partner/branch/customer to test and confirm it works as needed.    In unsupported printers it has been observed that some printer functions, such as badge orientation and hopper choice, may not work for all printers using the pop-up printer configuration window within Security Expert client. In those cases a workaround may be to manually change the default printer options in Windows to the required setting before printing badges. If specific functions or badge printers are required then a feature request can be submitted to potentially implement that in a future version of Security Expert. This will need to be raised with your local solution category management.

  Issue After transitioning TAC INET Access to Security Expert, SP-C health status shows the message "Ring-loop failure at reader expander".   Product Line EcoStruxure Security Expert, TAC INET Environment  Security Expert SP-C   TAC INET Access Control Cause This message indicates that the ring-loop connection is not made.  For the ring-loop connection, the opposite end of the INET subLAN must be connected to Reader 2 on the SP-C. Resolution This message can be ignored if an INET subLAN loop is not used. The Ring-loop Failure error can be avoided by running a jumper wire from Reader 1 pin D0 to Reader 2 pin D0, and another jumper wire from Reader 1 pin D1 to Reader 2 pin D1 on the SP-C that is hosting the INET subLAN If an INET subLAN loop is used, this message indicates a break in the ring loop.    Reference Guide I/NET Access Control Transition to EcoStruxure™ Security Expert (Hardware            Guidelines for Transitioning from I/NET Page 23)

Issue Prevented from logging in to Security Expert due to client licenses being available. See message "Licensed number of connections exceeded" when attempting to login. Login Message Product Line EcoStruxure Security Expert Environment Security Expert Client Cause The Concurrent client connections are being used up by active Security Expert clients or clients that have not been properly logged out.   Available licenses can be confirmed by checking under About | License. The Concurrent client connections feature will show the number of used connections out of the total available for use.  Consumed Connection Licenses Resolution 1 - Log out unused Security Expert clients. Currently logged in Operators can be determined by checking the Windows application event logs Security Expert Data Service events for "New Operator Logon" and "Remove Operator by Disconnect". These contain the record id and name of the operator identifying who has logged in. Those Operators are still logged in if there is no reciprocal disconnect message seen. If it can't be determined from the Operator which machine is being logged into this can be identified by viewing currently open ports to the server using Wireshark.   2 - Correctly close the Security Expert client to release the client license Closing the Security Expert client by clicking the "x" on the windows taskbar can close the application without first logging out the current Operator. This can result in the concurrent client license not being released. To then release the consumed licenses the Security Expert server must be restarted. Taskbar Log out the Operator before closing the Security Expert client or close the Security Expert client by clicking the "x" at the top right of the client window. Close Client   3 - Operator timeout This setting is disabled by default. Set the "Enable operator timeout" setting on Operators for an appropriate time. After this amount of time with no activity the Operator will be automatically logged out releasing the client license. Operator timeout

Issue Security Expert Data Service fails to start with error 1067: The process terminated unexpectedly  Product Line Security Expert Environment Security Expert Server Cause Port used by the service is blocked or already in use Permission issues with the service logon account Prerequisite .NET Framework is incomplete or not installed correctly Resolution In Windows go to Windows Features and ensure that all .NET Framework items show a check mark to indicate that each sub item has been enabled. See Ensuring Windows features are installed for Security Expert SOAP service for details. In Windows Event Viewer, examine the Application log, it will typically have an entry with details about the reason for the error. In this case, we see an Address Already In Use Exception in the Socket Connection Listener. This is a clue the error is with the network port. The Security Expert data service has been configured to use the default port 8000. On the server, list the network ports using netstat. We can see PID 5660 is already using the port. Get the name of service associated with PID 5660. Once the service is identified, take corrective steps to ensure the two services don't use the same port. Make sure the Windows account the service is using to log on has the appropriate permissions. If port 8000 isn't being used, first Reboot the Security Expert PC and if the error still persists, uninstall Security Expert, reboot and reinstall.

Issue A duress input is only triggering duress alarm events and not the return to normal events after the duress input is reset. The point going into alarm is seen on the Monitoring | Status page when viewing all alarms but the return to normal events are not being displayed. Product Line EcoStruxure Security Expert Environment Security Expert Cause The problem is due to how the Event Filter and Event Report are configured. Resolution Check to see that the Event Filter includes all of the Event Types that should come through as shown alarms. In the example this would be at least "Input Opened" and "Input Closed" under the "All Input Events" folder.   Event Filter: Create an Event filter and include the correct Event Types that you wish to report on.   Event Report: Add the Event Filter you configured in step 1. To show those Alarms, create/modify a Status Page under Monitoring | Setup > Status Page Editor, set the Type to Event Windows and add the Event Report from step 2 above to the Record field.

Issue All Controllers appear offline with any associated I/O showing a status of “Unknown”. The Security Expert Event Service's memory usage builds up until it gets close to 2GB when the controllers go offline.  Restarting the Security Expert Event Service brings the controllers back online. After a period of time the issue re-occurs and controllers again appear offline. Product Line EcoStruxure Security Expert Environment Security Expert Cause A potential memory leak in the Event Service would cause the service to stop working resulting in controllers appearing offline. Resolution 1. Upgrade to Security Expert version 4.3.370.1 or greater as discussed in known issue. 2. A potential workaround to mitigate the frequency of the problem is to disable the Event service from using MSMQ. As long as there are no site integrations using MSMQ then this option can be disabled in the Event Service Config file. Go to ..\Program Files (x86)\Schneider Electric\Security Expert and edit the SecurityExpertEvtSvr.exe.config file. Search for the MSMQ key <add key="MSMQ" value="1" /> and replace it with the following. <add key="MSMQ" value="0" />

Issue Esmi Transition tool stopped working after upgrading to SX-SOAP version 1.7.0.0 or higher Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Esmi Transition Tool SX-SOAP Cause The SOAP service no longer allows unencrypted communications over HTTP (port 8030) Instead use HTTPS over port 8040. Resolution 1. Open Esmikko Database transition tool 2. Go to the tab "Data Sync Service" the change the SOAP Server Address from http://localhost:8030/SecurityExpertSOAPService/service.svc to https://localhost:8040/SecurityExpertSOAPService/service.svc or https://SERVER_HOSTNAME:8040/SecurityExpertSOAPService/service.svc Note: bolded characters in the second line     3. Click on the button Create Data Sync Service Settings File The tool will stat working.

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 It may be necessary to replace the Security Expert Server and/or the Security Expert Software Product Line EcoStruxure Security Expert Environment Security Expert Cause In case of upgrade, software issues or PC/Server hardware failure replacing the Security Expert Server may be needed Resolution 1. Hardware Reset If the server footprint changes, for example, the previous server’s hard drive or motherboard died, then a hardware reset will be required before the license can be used on the new server. Contact Schneider Electric Product Support to tell them that your server hardware profile will be changing and a hardware reset is needed. 2. Stop the Security Expert services Right-click on the service and select Stop Note: While the services are stopped, the controllers will save incoming events (up to 50,000 per controller). Once that limit is reached, the events are First in First out. 3. Back up the SecurityExpert and SecurityExpertEvents databases If the database is encrypted, export the encryption certificates. See the Security Expert Installation Manual for specific instructions on backing up and restoring databases and encryption certificates. https://ecoxpert.se.com/search?documentUUID=71d622e3-2fc1-477a-b08a-5b37ac4b2756&title=SX-SRVR%20Security%20Expert%20-%20Client%20Server%20-%20Installation%20Guide  4. Uninstall Security Expert from the old server From Windows Programs and Features, Right-click Security Expert> Uninstall Once the Uninstall is complete, Manually Restart the Server/PC 5. Disconnect the old server from the network. Connect the new server with the same IP address and/or hostname. If the IP address or hostname of the server changes, update the event server settings in the controllers via the controller’s web page to match the new server. 6. Install Security Expert on the new server and activate the license Ensure that the new Security Expert installation is the same version or higher. 7. Stop the Security Expert services Restore the encryption certificates and databases to the new SQL Server instance. 8. Updating the Database If you are restoring a database from an older version to a later version, uninstall and reinstall Security Expert to upgrade the database. 9. Start the Security Expert Data Service 10. Update the Download Server In Security Expert, navigate to Global | Download server and update the Computer name to match the new Server name. 11. Update the Event Server Computer name in Global | Event server 12. Restart the Security Expert Event Service You should start receiving events from controllers 13. Start the Security Expert Download Service