Issue Running Bomgar Remote Support Client from Linux for support from Product Support Services Product Line EcoStruxure Building Operation Environment Building Operation Edge Server - Standard Cause Bomgar session downloads Bomgar-scc-[long string of characters].desktop file and need to run to connect with a Product Support Services agent. Resolution The file needs to be granted permission to execute and then run. Open browser on Linux OS for website: https://seconnect.se.com  Enter the 7-digit Session Key and press SUBMIT button. After saving the client to the Downloads folder, right-click on the bomgar-scc-[long string of characters].desktop file, then click Properties.  Click on the Permissions tab, then check the checkbox next to Execute to Allow executing file as program.  Open Terminal, then type "sh " (without quotes and not forgetting a space), then drag the file to the Terminal window, then press Enter. The full command will look similar to this image.  Once the executable runs, this image will appear on the screen as the full session begins.  Click Allow to let the agent view and control your computer. 

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you make changes to RSTP the controller MUST be restarted. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured properly per Configuring RSTP on a Managed Switch for SmartX IP Controllers Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. Configure the Root Bridge Switch (closest to Automation Server) settings first Then configure the additional Switches in order of increasing Bridge Priority. Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary so consult the documentation or contact the vendor or manufacturer to assist with configuration. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), there may be limits on the size of each loop based on their site switch network configuration and architecture.   RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION MUST BE EBO 3.1 or higher which includes ClientAPI support Fusion Fridays - Session 07 ​​​​ The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. bind Network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, restart, re-enable RSTP Mode, restart, and check again. If Firmware 3.02.01 is installed, please upgrade to 3.02.02. SmartX is now SpaceLogic.

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Product Line TAC IA Series Environment I/A Series MNB 1000 with firmware 1.510 and later only. Cause The field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Resolution The Web Service page has been removed from the MNB-1000 Plant Controller firmware effective with release version 1.510.   All functions that were previously included on the MNB-1000 Web Service page are now included in the WorkPlace Commissioning Tool -- Device Properties window for MNB-1000 controllers.  The changes to the Device Properties screens were documented in the WorkPlace Tech Tool 5.7.7 release notes, available here.

Issue In MNB-1000 with firmware Revision 1.50E, the Router Table can be viewed and /or reset without resetting the Plant Controller. This allows users to clear table entries that could cause router problems, without needing to reset the MNB-1000. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller) with firmware Revision 1.50E, or later. WorkPlace Tech Tool, Commissioning Tool (WPT CT) version 5.7.7 and later Cause Product enhancement. Resolution To view or reset the Router Table, choose from the following procedures, depending on the version of firmware: For MNB-1000 with Revision 1.50E, use a web browser to access the Plant Controller to view or clear its Routing Table. Click here to see the Release Notes for Revision 1.50E, for more details. For MNB-1000 with Revision 1.510, use the WorkPlace Tech Tool Commissioning Tool, version 5.7.7.  Go to the Device Properties, Diagnostics Tab, and Router Table Information button. Click here to see the Release Notes for WPT 5.7.7, for further details.

Issue Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E until 1.532  Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, until 1.532. Cause Common IP (Internet Protocol) ports echo (7), daytime (13) and time (37) are open. Having any of these IP ports open may be a cause of concern for customers that are sensitive to network security issues; these customers include defense installations, financial institutions, and government buildings. Resolution The services using the echo, daytime, and time protocols have been disabled which prevents IP ports 7, 13, and 37 from being open. These services and protocols have no purpose during the normal operation of the MNB-1000. Disabling the echo protocol and closing of port (7) has the side effect that the MNB-1000 cannot be “pinged”. Using the command line program Ping will not detect an MNB-1000 that has firmware v1.50E installed. Use WPCT instead of Ping to verify communications with the MNB-1000. Click here to see the Release Notes for firmware Revision 1.50E. Update; In firmware 1.532, the ping function was re-initiated as the default.  Please see the TPA-IA-19-0004.00 Firmware 1.532 Release Notes.  It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Unable to gain access to Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager MPM-GW MPM-UN MPM-VA Cause The admin password has been changed and the user has lost the password Resolution For MPM with firmware 2.14 and earlier: Send the MPM 'default.db' file to Product Support.  From a web browser, you can save the default.db file to the local drive by typing the address http://[ip_address]/root/default.db (replace [ip_address] with the actual IP address of the MPM, or 10.50.80.2 if bootloader is used) For MPM with firmware 2.15 and later: Send the MPM Node ID or MAC Address to Product Support. Refer to the document StruxureWare Building Expert Password Recovery When Accessing MPM - Reference Guide for the procedure to obtain the MPM Node ID or MAC Address.

Issue How to create a Continuum Cyber workstation Product Line Andover Continuum Environment Continuum Cyberstation / Workstation Andover Continuum Software and Firmware Compatibility Matrix Cause Creation of Continuum Cyber Workstation. Resolution Download the version of CyberStation Software from Exchange and follow the 'Setting Up Workstation Parameters' section of the Cyberstation Installation Guide included in the zip file.  

Issue A Continuum Workstation has become corrupted and cannot be re-added Product Line Andover Continuum Environment Continuum Cyberstation / Workstation Continuum Database Initialization SQL Database Cause Workstation will not initialize correctly and Continuum does not start correctly even though database can be seen correctly from the PC Resolution Occasionally a workstation can get corrupted, within Continuum, such that the computer cannot connect as that particular workstation.  A new workstation needs to be created within Continuum using Database Initialization.  Consider the following:  During the initialization process new Workstation Name, Folder Name, Device Node ID, and Network ID are required.  When initializing an IP conflict may occur, requiring a manual change to the computer IP address first. Once created log in using the new Workstation,  copy over any required objects from the old Workstation and then delete the old Workstation. Please refer to How to create a Continuum Cyber Workstation for supporting information  

Issue Servers not visible after upgrade due to permission change Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The Domain Local Group " Reports Administrators" is removed when an ES is upgraded to v4.0 or greater. This Group is automatically deleted during the upgrade because Report Server is not supported in v4.0 or greater. It is possible for local users to be selected as User Group members of " Reports Administrators", so the permissions for these users may change after the upgrade. This is not good practice, only the Reports Server login user should be part of the " Reports Administrators" Group " After the upgrade the Group "Reports Administrators" is removed and the Servers are not accessible Resolution Any users that were part of Group "Reports Administrators" should be reassessed and their permissions corrected 

Issue How to back up a full version of SQL (not express)? Product Line TAC Vista Environment SQL 2005, 2008 full versions, i.e. Enterprise, Standard etc. TAC Vista 5.1.X Cause A customer may wish to backup the TAC Vista log database to prevent data loss if the SQL server crashes. Resolution There are 2 options available, depending on the TAC Vista SQL configuration the customer has configured. If the customer has selected "Typical" on the TAC Vista Server setup "SQL" tab, you can configure this through Vista workstation. Right-click on the Server object in Workstation and select "Properties". Select the "Log Backup" tab and configure the backup schedule there. If the customer has selected "Custom" on the TAC Vista Server Setup "SQL" tab, this can be configured through SQL Management Studio (which is free to download from Microsoft, if the customer doesn't already have it). Start SQL Management Studio and connect to the SQL server instance that is being used for TAC Vista. Expand the SQL server in the tree (in SQL Management Studio) and locate the "Management" folder. Expand that folder and locate the "Maintenance Plans" folder. Right-click on the folder and either select "Maintenance Plan Wizard" or "New Maintenance Plan". Configure as required.    

Issue By default, you are not allowed to shut down/restart the TACLIC/TAC License server when logging in to the Flexnet license admin web application from another PC than local. Product Line TAC Vista  Environment TAC Vista versions 5.1.8 and higher, using the web-based TACLIC tool.  Cause A remote shutdown/restart is required when adding/removing/editing license files in the License Files folder. Resolution The following steps should be done on the PC where the license server is located: In the "server.xml" file located in the "conf" catalogue (...\License Server\conf), edit the following string from " stopServerRemoteAllowed="false" "  to  " stopServerRemoteAllowed="true" " Then save the file and restart the license server.   The setting can also easily be changed using the tool called "TACLicenseServer Settings."

Issue Is it possible to save a copy of a TGML graphic in a standard format such as jpeg, bmp etc? Product Line TAC Vista Environment TGML graphics editor 5.1.X Cause For documentation purposes a customer may wish to have an image of a TGML graphic, perhaps in a system reference guide, with explanatory text. Resolution Open the graphic in TGML graphic editor. Select "Export..." from the file menu and then select the file format in the dialogue that appears.

Issue Specific Trend log stops working in TAC Xenta Get estimated values in some trend logs; others are working Trend log is not retrieved from TAC Xenta Product Line TAC Vista Environment TAC Xenta 301 TAC Xenta 302 TAC Xenta 401 TAC Xenta 282 TAC Xenta 283 TAC Vista Cause The issue can be that there is a "Non value" in the log. For example, if you are logging an expression block with division in it and there is a division by 0. This seems to lock the trend in TAC Vista, and no other values can be collected. Resolution In the properties for the log, click on erase log. This will delete all values in the device. Open your menta and make sure that there is no possibility of division by 0.

Issue Enterprise Server ES crash Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The ES/EC runs on a Windows platform and there are circumstances that can lead to a single crash or multiple crashes leaving the ES/EC not running Background - The ES service is usually running. The service can be seen below under the Windows services and via "Building Operation Software Administrator"  The ES v4.0 has crashed and will not restart. The "Building Operation x.x Connect Agent" collects any core dumps and packages them, so they can be quickly analyzed. It also checks if an ES is registered and online, then uploads the core dump files for automatic analysis. If the site is not registered or is offline, then these files are stored locally at %ProgramData%\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise [Server|Central]\db\Crash information (default for v4.0 "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\db\Crash information") The "Building Operation x.x Connect Agent" is a Windows Service and installed with the ES, the service should be left to run continually. If it is not running during an ES crash, the core dump may still get created, but does not get packaged up in a way that can be easily analyzed. Each packed crash dump file may look like "ES_ES_MYCOMPUTER_20221104T121314Z.zip" and likely be between 40MB and 200MB in size. The individual core dump will look like "server_20230314_132853__r4.0.3.176.dmp", but is very time consuming to analyze, without the other associated files Resolution Following a crash,the EC/ES will usually restart and operate correctly, however in some cases the EBO database or install file structure may be damaged and the EC/ES may fail to restart correctly EC/ES has crashed and is now running correctly Send the following information to Support - All core dumps from the "\db\Crash information" folder - All data from the "\db\logs" folder - Ideally a full backup of the ES (with history), always zip before sending to Support If the "Crash information" folder is empty, then check the "Building Operation x.x Connect Agent" is running. It is possible the core dumps have already been uploaded and analyzed automatically EC/ES has crashed, tried to restart but just stops again. (as seen in the first screen shot, "The server has made too many unsuccessful attempts to start..." is seen It is important to gather all the data as stated above, but also collected the EC/ES and AS backups from "\db_backup" It can be useful to get full copy of the files in "/db" Ideally the EC/ES is not critical to the operation of a site, but it can still cause a big problem. Checking the Trace and System logs may give a clue to the problem, e.g. a lack of disk space, but often there are only a few options   Collect the files above, then wait for a reply from support. Please state if the EC/ES is stopped and a resolution is being sort. Reinstall the EC/ES at the same version and choose repair current version, or upgrade to a newer CP Fix version or maintenance version. Uninstall the EC/ES, then re-install the same version with an empty database, then restore the last good backup to the ES. If option 2 or 3 is used, it is still important to log a case with support, so the crash can be investigated. The backup can be checked for errors using the XBK Analyzer.

Issue A Niagara G3 server station was running well for a long time.  Then in a matter of a couple of days, the station began failing to run.  The error listed in the Application Director Output is:   ERROR [java.lang.OutOfMemoryError: GC overhead limit exceeded 13:46:17 20-Mar-14 EDTjava.lang.OutOfMemoryError: GC overhead limit exceeded][sys.leasejava.lang.OutOfMemoryError: GC overhead limit exceeded] Error in run Product Line TAC IA Series Environment I/A Series G3 Enterprise Server Cause There is not enough memory allocated to the Java Virtual Machine (JVM). The email service is keeping a very large outbox because the network email server's IP address was changed. Resolution Increase the Java Virtual Machine (JVM) memory allocation Using a text editor, open the nre.properties file (located in the niagara 'lib' subfolder on the server hard drive). Locate the line: java.options=-Xmx256M. Change it to java.options=-Xmx512M. Empty the outbox file (i.e. delete it) and/or update the email server's IP address.

Issue While editing a graphic, the editors components categories and menu options are too small to be used. This happens when Windows display scaling is not set to 100%. Product Line EcoStruxure Building Operation Environment Graphics Editor High Resolution monitor (4K) Scaling Cause An issue has been identified with how the default scaling used by Windows affects the Graphics Editor in EcoStruxure Building Operation 2.0 and later. Resolution Follow the steps below to work around the problem Update Windows with the latest available updates Update .NET Framework to latest version Change the compatibility settings of the Graphics Editor as outlined below   Open the Graphics Editor application file location   Open the properties for the Graphics Editor application   Override the DPI scaling 

Issue Is there a quick reference I can search to find out what features are included in a particular license When manually adding my Product during offline embedded license workflow, how do I know which Features is included and in what quantity?  Product Line EcoStruxure Building Operation Environment Building Operation EBO 2022 v4.03 and lower  Embedded Offline Licensing Offline Activation of Licenses Workflow Cause Currently, no information lists features for each Product name listed in the Part Number Summary for EBO 2022.  A documentation defect (QC 49762) has been raised, which should resolve this.  This article has been created to assist somewhat during this process while waiting for this to be corrected.  The recommendation, if possible, is to perform license activation online to avoid having to enter this detail.   Resolution Important Note: This information is no longer valid for EBO 2022 (Maintenance Release 4.0.4) and EBO 2023 and greater.  The details below are still provided for reference only and are not needed for these later versions.   Attached are two documents that provide version 3.0 and 4.0 License details.  The documents contain all searchable details, including: Product Name Features Part Numbers     Additional details required for Device Administrator "Feature Name" offline entry:   SpaceLogic Server license details Feature Name (seen in Device Admin) License name (seen in Features document) Description / Comments Automation Server server.as.base   SmartDrivers smartdriver.license   SNMP Notifications server.alarms.snmp   Personal Dashboard client.dashboard   TimescaleDB server.timescale   MQTT Publish/Subscribe server.mqtt.rw Enables EBO, as MQTT Client, to publish data on an MQTT Broker and to subscribe to the same data. Serial Modbus server.modbus.rtu Allows SmartX server serial communication - Modbus RTU Serial MS/TP server.bacnet.mstp Allows SmartX server serial communication - MSTP ES Connection server.connect.to.es Allows SmartX server to be hosted by an Enterprise Server Server I/O server.io Allows SmartX server to use IO Field Devices server.device.as Allows SmartX server to host one field device SAML Authentication server.as.auth.saml   Zoning client.zoning Enables use of zoning tools BACnet IP server.bacnet.ip Allows SmartX Server to communicate using BACnet IP Software Assurance software.assurance         Feature Name (Automatically included with bundle licenses)   client.webstation Allows Webstation to log on to an AS   server.cloud.customer Cloud connectivity - Checked by Cloud SMS (Production)   server.as.scalable Included in the license that allows SpaceLogic servers upgrades. i.e. Standalone to Standard etc.   Example: Product Name: ASP-NL Bundle upgrade - Full to ASP Full    Search the document for the product name in the attached document. In this case, the version 4 document.  Below is the result seen in the document: From this, the associated Features and Quantity are shown. In Device Administrator, then add the respective features and quantities when adding the product manually to the Entitlement. Use the above table to correlate between Feature Name and License Name. The example shown below:  

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 If the passphrase is incorrect when trying to install a station .bog, the following error message can appear; Transfer failed. com.tridium.platform.daemon.DaemonResponseException: Request to platform daemon at (stationName) failed: bad return code to commit file instance at com.tridium.platform.daemon.DaemonFileUtil.transfer(DaemonFileUtil.java:661) at com.tridium.install.InstallScenario.commit(InstallScenario.java:1444) at com.tridium.platDaemon.ui.stationtransfer.FinalStep.run(FinalStep.java:341) at java.lang.Thread.run(Thread.java:750) Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace Cause The .bog has not been properly placed in the User Home / Stations for copying into the device or the passphrase is not known. Resolution Always use the Station Copier to install the .bog from the User Home / Stations path If the error message appears, open Workbench and navigate to the "Stations" folder under the "User Home" Expand the station you are attempting to install Double-click the .bog (1) and locate the "Bog File Protection" icon at the top of the page (2) Select the (1) "Force the File to start..." radio button and (2) Update.  Note the information regarding existing passwords. If the message "Cannot display page" occurs when you double click the .bog, open the "Details" and look for missing modules "Cannot load module '......=.....'. Any missing modules will need to be available on the Jace or ES before attempting the force start operation.  

Issue WorkPlace Tech 5.8.x, 5.9.x, and 5.10x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, and 5.10x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, and 5.10.x? Resolution Microsoft Windows WorkPlace Tech Tool releases 5.8 through 5.8.6 are certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.9.1 to 5.9.4 are certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Windows Server 2022 64-bit Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.8 through 5.8.6 require one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio 2021 Microsoft Office Visio Office 365 Subscription Plans 2 Note: Workplace Tech Tool 5.10.0 and future releases will require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow the instructions in the article link for the security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.