Issue The file structure is incorrect for MNL-FLOW-BAL 3.0 software for use with Windows 7 64 bit OS.  The FlowBalance.exe needs to be run in Windows XP (Service Pack 3) compatibility mode. Product Line TAC IA Series Environment Windows 7 64 bit MNL-FLOW-BAL Balance Software Cause The paths for certain files being used by the software cannot be modified. When loaded on a 64 bit PC, the default paths are incorrect for the rest of the processes to find. Resolution Manually create and insert the folder structure required. Set the FlowBalance.exe compatibility Copy the TAC folder in the Program Files (x86) folder from Windows Explorer. Paste into the Program Files folder Open the pasted TAC folder and delete all the files except for the XIF folder and the FlowBalance.cfg file in the LON FlowBalance folder. Right-click the FlowBalance.exe icon created on the desktop Open properties/compatibility tab. Set as Windows XP (Service Pack 3)

Issue Using the EGL, EGRL, EGLL5 which are obsolete Environment Vista Cause temperature/resistance data of EGRL, EGRLL, EGRL5 temperature sensors, or customer needs data to calibrate the sensors. Resolution EGL is replaced by the STD100-250 EGRL - STR100 EGLL  (2 thermistors) was not really replaced, as the average temp calc nowadays is done in the controller. The room version was named EGRLL. All these are for the Vista series. For more information regarding sensors, please visit Exchange Extranet.    Click here for the temperature/resistance chart for the old EGL, EGRL, EGLL5 Click here for the original Product and Installation pdf.

Issue When configuring a SmartConnector, the custom assembly cannot be seen in the Add Processor Configuration tab.   Product Line EcoStruxure Building Operation Environment Microsoft Windows Server 2012 and newer, Windows 10 Cause Microsoft Windows Server Unsigned or unknown certificates Some files need to be "unblocked" after download in order to avoid security warnings from tools like Visual Studio about potentially unsafe content.   This is because the dll’s for the custom processor have been downloaded from an internet based source.   Otherwise, all the required dll’s for the solution may not be available in the service installation directory (normally “C:\Program Files (x86)\Schneider Electric\SmartConnector”). This information can be seen in the SmartConnector log file. SmartConnector will log an error when going to the point of adding a new processor if it can’t find a reference. It will point to the assembly which is missing. Microsoft Windows 10 The service needs to be restarted once the dlls for the custom processor have been added in the service installation directory. (“C:\Program Files (x86)\Schneider Electric\SmartConnector”) Resolution Microsoft Windows Server range To "unblock" a file, Right-click it in Windows Explorer Choose Properties from the context menu Click the Unblock button in the lower right-hand corner of the resulting dialog Hit OK or Apply Important: ZIP files should be "unblocked" before their contents are extracted. Note: Depending on the security policy level on the system, you may need to perform the same action for the DDLs once uncompressed. Microsoft Windows 10 To restart the service by Opening the service windows Select the SmartconnectorService entry Either click on the Restart button, or Stop then start

Issue Is there a specific amount, or percentage of free memory that must be maintained for Continuum controllers to operate? Environment NetController CX9900 CX9940 Infinet i2 ACX2 b3 Cause Is there a specific amount, or percentage of free memory that must be maintained for Continuum controllers to operate? Resolution There are no published metrics or guidelines regarding the use of Continuum controller free memory. For most of the Continuum controllers there is no required minimum amount of free memory in order for the controller to function properly. The notable exception to this is the CX99xx. Remote validation will stop working in the CX99xx if freemem goes too low. This is because the system memory and the user memory come from the same heap. Also, in the CX99xx, if a Plain English program uses a commport to read and write data, and the controller has insufficient memory to switch from a RAW port to AutoSet, the controller will lock the commport. A safe target for freemem is 15% of the total. These issues were fixed in the NC2/ACX2 by having separate heaps for memory allocation by the system and OMS (object management system). The newer IP level controllers and the i2/b3 controllers can be loaded up until there is no freemem but be aware that as you load up the controller memory with programs, the scan time will typically increase.

Issue Need to mirror a switch port in order to capture controller data with Wireshark.   Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Cause Need a step-by-step guide to set up a mirrored port and an understanding of how it works.  Resolution View the attached video.   Use the link to the original post in Area360 to get written instructions.

Issue Dehumidification using Xenta 121-FC Environment Xenta 121-FC Xenta 121-HP Cause Some aspects of how the dehumidification mode in the Xenta-121 operate are undocumented. Resolution The dehumidification feature of the Xenta 121 can operate either by turning on external dehumidification equipment using one of the digital outputs or, if no external equipment is provided, it will use the cooling for dehumidification. In the latter scenario, the heat continues to be operational when the cooling is forced for dehumidification. Additionally, if there is an outside air damper, it will be controlled to its minimum position before forcing the cooling on. When is external dehumidification enabled? For On/off cooling, cooling is enabled for dehumidification when the nvoDehumidActive value is greater than 10% and is disabled when the nvoDehumidActive value drops below 5%. For all other types of cooling, nvoCoolPrimary is set to match the nvoDehumidActive whenever it is a greater than cooling PID output + 5% or whenever the cooling PID output is less than 5%. The dehumidification feature can be configured using the ZBuilder configuration tool. However, the individual features can also be accessed via the points listed below using either Vista Workstation or another Lon management tool such as LonMaker: Applic UCPTappOptions Bit Usage If FALSE If TRUE Additional notes 5 Dehumidification control enable Not active Active   6 Dehumidification type Internal External Only applicable if bit 5 = true. External control can be hardwired or via SNVT. Internal will force cooling as a dehumidification method. 7 External dehumidification active on Open contact Closed contact Only applicable if bits 5 and 6 are both true. UCPTappOptions2 Bit Usage If FALSE If TRUE Additional notes 7 External dehumidification type Digital Analog If true then the RH reading is mirrored to the analog output (0-100% = 0-10V). Only applicable if UCPTappOptions bits 5 and 6 are both true.

Issue Are there any redundancy options for Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Stratus everRun Cause Need to provide redundancy for the Security Expert Server. Resolution There are a couple of options for providing server redundancy that can be used with Security Expert. The first option would be to use a downtime prevention product such as Stratus everRun as a hot standby solution. The second option is having a secondary Security Expert server as a cold standby server, if the primary server fails/needs to be taken offline the Security Expert services on the cold standby server can be started to take over. This option is largely manual, there is no automatic switching between two servers with this configuration. There are also a number of considerations to take into account with this option: In this scenario the controllers would be programmed with 2 x event server IP addresses for the primary and cold standby server as a result only 1 server/set of Security Expert services must be running at a time, having both running and therefore the controller having 2 x valid paths back to 2 x different servers concurrently will cause issues with the upload of events, online status and downloads A suitable system/process would need to be put in place to ensure the databases are restored from the primary to the cold standby server There will be 2 different Security Expert servers running which will require 2 separate Security Expert Server license with the same feature set enabled on both Considerations will need to be made with regards to the name of the machine to ensure the Download and Event servers can run, either the machines must have the same name or the name of the server needs to be renamed when required to the name of the cold stand by server An operator would need to verify the state of programmable functions and services. If the primary server failed during the middle of the download when the cold standby server is up and completes a full download some functions/services may require manual starting.

Issue Upgrading CyberStation from v1.7 to 1.93.  The instructions say to use \Continuum\CyberKeyWriter2.exe to upgrade the key (dongle). The program is not there. Environment CyberStation v1.7 Cause Upgrading CyberStation from v1.7 to 1.93.  The instructions say to use \Continuum\CyberKeyWriter2.exe to upgrade the key (dongle). The program is not there. Resolution CyberStation v1.7 had CyberKeyWriter.exe not CyberKeyWriter2.exe. CyberKeyWriter2.exe will be added to the \Continuum directory during the upgrade. Once the upgrade to the new version of CyberStation is done, use CyberKeyWriter2.exe and the Key Code from the Repair Dept to upgrade the key.  

Issue When trying to open web pinpoint on a remote client session the users receive the error below: Product Line Andover Continuum Environment MS Server 2008 and newer Windows 7 and newer Continuum 1.9x and 2.x webClient Remote Desktop Cause This issue is caused when a remote desktop connection is made on a Windows 7, Windows 2008 server or newer Operating Systems.  The console becomes locked.  It will stay locked until the local session is restored with a logon. Resolution  Resolution: 1)      Create a Bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console ***********************************************************************************************   2)      Place this file on the desktop of the Web Server system. 3)      When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be ran “As an Administrator” This will disconnect the session and restore the console.

Issue When tunneling through a UNC (Niagara R2) or ENC (Niagara G3) to an ASD bus using XPSI, communication timeout errors occur. Product Line TAC IA Series Environment PSI/XPSI software (any version) UNC (R2) or ENC (G3) with ASD bus connected Serial tunnel client (R2 or G3) Cause Delays introduced by the Internet between the PSI/XPSI computer and the remote tunnel client can result in communication timeout errors. These delays affect the ASD bus communication speed. Resolution Set the baud rate of PSI/XPSI to 1200 to minimize or eliminate timeout errors: Open PSI/XPSI software. Navigate to Site Setup Configuration. Set Baud Rate = 1200 as recommended in the TAC I/A Series Enhanced ASD Driver Engineering Guide (F-27429, Chapter 5, Table 5.1). Reference: TAC I/A Series Enhanced ASD Driver Engineering Guide, F-27429.

Issue This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.

Issue After replacing an older revision MNL controller with a new one, WorkPlace Tech is unable to download the existing application file into the new controller reporting an error "The selected device is Invensys IA(x) ... controller, the application requires Invensys IA(y) ... controller".  In this error message the controller type info (...) will be the same in both parts of the message but the IA(x) and IA(y) part of the message is different.  Environment MNL-50 MNL-100 MNL-110, MNL-130, MNL-150, MNL-200, MNL-Vx Cause Replacement controller is of the same type but of a different version. This issue occurs any time a version 2 controller is replaced with a version 3 controller. for example, this error will occur if a MNL-V2RV2 controller is replaced by the newer version, MNL-V2RV3.   Resolution Open application in the WorkPlace Tech Tool. Open the Hardware Wizard and click the [Back] button to open the Controller Selection page. When the Controller Selection page has been opened, you will note that the [Older] tab has been displayed with the existing controller type displayed. Select the tab corresponding to the controller type, for example if replacing a MNL-V2RV2 controller, select the MNL-VAV tab. Select the model of the replacement controller, for example when replacing a MNL-V2RV2, the replacement is the MN-V2 [MNL-V2RV3]. Click the [Next] button to complete the selection of the replacement controller type then click the [Finish] button to close the Hardware Wizard. Recompile the application and download it to the replacement controller. If the controller is part of a LON network that has been commissioned by a LON Network Management tool, it will be necessary to replace the existing device object and commission the new controller.

Issue After a CX99xx is updated for SNMP option enabled, the hyper terminal screen does not show the SNMP option setting button when the hyper terminal PC is indirectly connected to the target CX99xx via other local CX99xx. Environment NetController (CX9900, CX9940) Cause This issue happens when the hyper terminal PC is indirectly connected to the target CX99xx via other local CX99xx. Resolution After successful update the CX OS file for SNMP, connect the hyper terminal PC directly to the target CX99xx.

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue If the result of a divide by zero is sent to a physical AO, Vista Workstation will display this value as -2. The physical output, however, will be sending out the maximum specified voltage (default 10V). In Menta simulation mode, if a divide by zero scenario is simulated, the following error will pop up: tam32 Division by zero Connected to a controller viewing live Menta, a divide by zero equation will result in a displayed value of 1.#QNAN. All subsequent equations using this value will also output 1.#QNAN. Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Division by zero results in an invalid value that is interpreted differently by the controller's physical outputs, the Menta application, and the Vista Workstation. The application will continue to run, but any output affected by the invalid value will not act as expected. Division by zero is not usually intentional (there's no equation that says "A/0"). Instead, it is usually the result of an unforeseen sequence of events where complex equations result in a 0 in the denominator of an equation, and simulations did not ever produce this unique situation. Resolution To troubleshoot whether a divide by zero is occurring: The best solution is to connect live to the controller with a serial cable and watch the live Menta. Look for any values that read 1.#QNAN and trace it back to the source. If live Menta is no available, the simulation mode can be helpful. Recreate the scenario as best as possible with all inputs set to the real life instance. To prevent a divide by zero error: Never allow an equation to write to the denominator of a division equation without programming divide by zero prevention. Add an expression block prior to the division equation that says "if the value is zero, then output a safe value" Add a max block to the input that compares the value with 0.0001, so that a zero will never pass through.

Issue It may be useful to have logic in Menta programs trigger an event in Vista so that it can be recorded and stored in the event log. Environment Vista Workstation Menta Cause Alarms that have the Priority parameter set to 0 are used for info purposes only and only show in the event viewer and not the alarm viewer (queue). Resolution Events can be triggered by a Menta program by creating an Alarm block in Menta and setting the Priority parameter to zero. This causes the alarm to only function as an event and keeps it from showing up in the alarm queue. The following is taken from the Menta Technical Manual: The alarm priority is specified with the Priority parameter. There are 10 levels, 1 to 9 and 0, where 1 is the highest. Events with priority 0 (Information messages) have the lowest priority. They are not placed in the alarm database of TAC Vista and do not appear in the alarm overview. An example where using a priority zero alarm might be useful is to record as an event whenever an air handler enables and disables its economizer. This would be done as follows: 1. An ALARM block is created and named EVENTS\ECONOMIZER_ENBL. The Priority parameter is set to 0. Alarm Control is set to the standard alarm control object which is $Alr_Cntrl. The Tripped Alarm text is set as "ECONOMIZER ENABLED" and the Reset Alarm text is set as "ECONOMIZER DISABLED". 2. The ALARM block is then connected to the Economizer function. Now an event will be generated each time the economizer is enabled and disabled but an alarm will never pop up in the alarm viewer. An Events Viewer object could now be created to make it easier to view just economizer events without everything else. This is done as follows: In Vista Workstation right click the Root object and select New > Object > Viewer - Events. Type in a description and enter the Object ID of the economizer event that has been created. This can be found by locating an instance of the economizer event in the standard event viewer and copying the Object ID from there. The event viewer could be set up to display all priority 0 alarms instead of one specific event type by entering a 0 in Priorities in the Alarms section under the Event Specifics tab. The amount of time displayed in the event viewer can be filtered under the Date and Time tab. It may be useful to remove unneeded columns from the new event viewer so that only the relevant information will be displayed. In this example everything is unselected except Time, Object ID and Text under the Select Column(s) tab. The event viewer will automatically update and could be used for real-time monitoring of whatever event(s) it has been configured to display.

Issue Security Expert database size increasing rapidly and getting large. SecurityExpert Database size From the screen capture below, it can be seen that the Security Expert transaction log file SecurityExpert.ldf has increased to a large size. SecurityExpert database log file Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Recovery model of the Security Expert database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size.   New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution For Security Expert, it is recommended that the Recovery model be set to the default of SIMPLE.   You can reduce the size of the logs and also prevent them from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpert database from Full to Simple in SQL Server Management Studio. To do this, right click on the SecurityExpert database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery Model Simple Right click on the SecurityExpert database and select Tasks > Shrink > Files Shrink In the Shrink File - Security Expert window, change the File type to Log. Shrink File Type Log Click OK Repeat steps 2-5 for the SecurityExpertEvents database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue BACnet controller objects that have not been overridden appear in purple on I/A Series R2 graphic screens, indicating an override condition incorrectly. Product Line TAC IA Series Environment I/A Series R2 graphic screens BACnet controller inputs displayed on Niagara graphics MNB controller firmware version 1.2 or higher Cause Purple color indicates the BACnet OVERRIDDEN flag is set to TRUE. This behavior is normal and results from compliance with BACnet Specification 135-2004 for BTL certification. Read-only BACnet objects (e.g., Analog Value, Binary Value) must indicate an override condition because their Present Value cannot be changed via BACnet services. Niagara interprets this as overridden, even though it is simply read-only. Resolution Two approaches to prevent purple override indication: Buffer the Value Using Native Niagara Objects Use a Niagara AI object to display the value without transferring the override condition. If BACnet points are in a poll-on-demand container, add a gx type object linked to the BACnet point (invisible) to initiate polling. Display the value using another gx object linked to the AI object. Disable Status Color on GxText Objects Configure the statusColorEnabled property of the GxText object to false. This prevents the purple background from appearing.

Issue Requirement for a number of users to be able to access Security Expert using Web Client at the same time. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Unsure how many Web Client users are licensed with the standard license or how to add additional user licenses. Resolution Included with the base SX-SRVR license is an allowance for having three (3) concurrent Web Client operators.  Additional operator licenses (SX-WEB-OPR) must be purchased to allow Web Client logins beyond the licensed amount of three, purchase as many of these as is required.

Issue WorkPlace Tech 5.8.x, 5.9.x, 5.10.x, and 5.11.x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, 5.10x, and 5.11.x 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, 5.10.x, and 5.11.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 Windows 11 Professional (Workplace Tech 5.10.4 only) WorkPlace Tech Tool release 5.11.0 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 10 64-bit Professional Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional 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 WorkPlace Tech Tool releases 5.11.x requires one of the following versions of Microsoft Visio (64-bit version ONLY) Microsoft Office Visio 2019 64-bit Microsoft Office Visio 2021 64-bit Microsoft Office Visio Office 365 Subscription 64-bit Plans 2 Warning: WorkPlace Tech 5.11 is not compatible with EBO WorkPlace Tech Editor. Do not install WP Tech 5.11 on a PC that has EBO WorkPlace Tech Editor installed. Continue to use WP Tech 5.10 on PCs where EBO WorkPlace Tech Editor is required.   Note: Workplace Tech Tool 5.10.0 and later releases 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?.