Issue When opening I/NET and getting an Initialization failure error and unable to log on to start the program. Product Line TAC INET Environment I/NET Revision 2.40 and higher on Windows 7 PCs. Cause There was a security update that disabled the Named Pipes and TCP/IP that is required for SQL to run. Resolution Start , All Programs select Microsoft SQL 2005 or 2008 Expand Configuration Tools and select SQL Server Configuration Manager Select SQL Native Client Configuration and expand it then click on Client Protocols Verify that TCP/IP and Named Pipes are enabled Click on SQL Server 2005 Network Configuration and click on Protocols for MSSQLSERVER Verify that Named Pipes and TCP/IP are enabled Open up Services and verify that SQL Agent, SQL Server and SQL Browser are all running and set to automatic. Start the I/O Configuration and verify that the connection is made to the correct database Restart I/NET again and it should allow you to start the program now. For Remote Client with I/O Configuration: Repeat the above on SQL Server PC Ensure that port 50069, 1433 and 1434 are open between the PCs

Issue Disable FTP (File Transfer Protocol) in all X5/7/9xx controllers Environment Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 Cause In some high security project installations, local IT groups require that FTP (File Transfer Protocol) be disabled on all devices within their network. Resolution FTP into the Xenta 5/7/9xx controller by typing FTP://x.x.x.x (where x.x.x.x is the IP address of the controller) in the Windows Explorer address bar. Login with the root username and root password. Browse to the sys/system/ftp.cfg file and copy it to the desktop of the local machine. Open the ftp.cfg file with notepad on the local machine. Set the FTPMaxUsers="4" line to FTPMaxUsers="0" and save the file. Copy the file back to the FTP session on the controller and paste / replace it over the existing file. Logout of the FTP Session Cold start the controller Now the Xenta 5/7/9xx controller will not have FTP access. If there is a need to re-enable FTP please follow this steps on the Xenta 511, 527, 555, 701, 711, 721, 731, & 913 Login into the controller via the web interface with the root level username and password. Navigate to Configuration > Servers > FTP Server Set the Max. number of users back to a valid number of 1-5 and click save. Cold start the controller. If FTP needs to be re-enabled on the Xenta 527-NPR the only option will be to reload the system program. This is because the 527-NPR does not have a full web configuration interface like all other Xenta 5/7/9xx controllers to set the number of users.   Update note: In later versions of the Xenta Server, FTP is disabled by default (the number of users are set to 0). If you still can't login to FTP, try to format the controller, reload the system program and try it again. Then it should work now.

Issue Microsoft Visual C++ Runtime Library Error After you install I/NET on a computer containing Microsoft Office XP or one of the Office XP programs, you may receive one of the following error messages: Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSDMN.EXE abnormal program termination Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSEARCH.EXE abnormal program termination Environment XP computers containing Microsoft Office or other loaded programs, one of which may be I/NET  Cause This behavior occurs if a program (not necessarily I/NET) conflicts with the Mosdmn.exe and Mosearch.exe files or with video settings, antivirus or 3rd party programs conflicting with your operating system. Resolution The Mosdmn.exe and Mosearch.exe files are part of the "Support for fast searching" feature in Office XP. This feature is similar to the Find Fast feature in Microsoft Office 2000. Fast searching uses the Indexing Service in Office XP to create a catalog of Office files on your computer's hard disk. To resolve this issue, use the following methods, as needed, in the order presented. Method 1: Clean Boot with Only MoSearch The Mosearch.exe (Microsoft Office Search Service) and Mosdmn.exe (Microsoft Office 10 Search Filter Daemon) Startup items may be conflicting with some other program (or programs) running in the background. Therefore, clean boot your computer with only MoSearch selected on the Startup menu to determine whether this program is the source of the conflict. To do this, follow these steps:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the General tab, click Selective startup. 4. On the Startup tab, click to clear all check boxes except for MoSearch. 5. Click OK, and then click Yes when you are prompted to restart the computer. 6. If the error message can be reproduced, repeat the preceding steps. In step 3, also click to clear the Process System.ini file and Process Win.ini file check boxes.   If the error message cannot be reproduced, this indicates that MoSearch is conflicting with some other program or programs running in the background. Follow these steps to locate the conflicting program:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the Startup tab, click to select one of the check boxes. 4. Click OK, and then click Yes when you are prompted to restart the computer. 5. If the preceding steps reproduce the error message, the last item added to the Startup menu is causing the conflict. If the error message is not reproduced, repeat these steps until all Startup menu check boxes are selected. 6. If all the Startup menu check boxes are selected and the error message is still not reproduced, start Msconfig again, and then click to select the Process System.ini file and Process Win.ini file check boxes.   Restart the computer. You may need to install a clean version of I/NET depending on your computer setup.   This is the solution for the Microsoft Visual C++ Runtime Library error with XP Office. Other solutions may entail removal or reconfigure of video drivers, antivirus programs, or other 3rd party programs conflicting with your operating system.

Issue What resources are available to get more information on the M-Bus protocol? Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment M-Bus Cause The M-Bus protocol information is available on www.m-bus.com. Select The M-Bus: A Documentation Rev 4.8 Resolution The M-Bus protocol specifications is broken down in multiple chapters. Basics of Serial Bus System Overview of the M-Bus Physical Layer Data Link Layer Telegram Format, Meaning of Fields, Communication Process Application Layer Structure of fixed and variable data blocks. Network Layer Appendix Table of units, medium, data field codes, VIF extensions.

Issue Need to sequence several outputs to be on for 10 seconds then off for 15 then the next on for 10 and so on, but the site has specified no event sequences are to be used. Environment I/NET DDC Cause Need to sequence several outputs to be on for 10 seconds then off for 15 then the next on for 10 and so on, but the site has specified no event sequences are to be used. Resolution Create a DDC relay for output 1 that is an interval timer relay with the time set to 10 (time the device is on) Set the DI select to an input trigger point Create a second DDC relay to function as a delay before make relay. Set its time to 25 seconds, or the device on time plus the interval time before the next output. Set the output of this relay as a Line and the DI select as the trigger point. Copy the DDC relay from step 1. Change the DI select to the line from the previous step and the Output to the next device in the series. Copy the DDC relay from step 2. Change the DI select to the output triggered in the previous step and change the Output to a new line. Copy the DDC relay from step 1. Change the DI select to the line from the previous step and the Output to the next device in the series. Copy the DDC relay from step 2. Change the DI select to the output triggered in the previous step and change the Output to a new line. Repeat steps 5 and 6 until you have completed the series. If you wish for this to cycle in a loop, have the output from the last Relay trigger the DI point which starts the series. If this is an internal point you may want to add a calc to keep it equal to 0.

Issue Running I/O Server as a service and an error 1075: The dependency service does not exist or has been marked for deletion pops up. Environment Running I/Net as a Host Tool under TAC Vista and wanting to configure I/O Server to run as a service. Cause I/O Server requires that MSSQL be tied to the dependencies of the service and when it is not listed, it will generate that error. Resolution When this error comes up, there are several things that needs to be checked to verify that it is set and connecting to the correct database in I/NET: Right Click on My Computer and go to Manage. Select Services and Applications, expand that and select Services. Select I/O Server, Right Click and select Properties then click on Dependencies. MSSQL should be listed in there and more than likely it is not and has to be added. To add it, go to run and type regedit, go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\INet7IoSrv] DependOnService – add the SQL instance (for example MSSQL$TACVISTA) and the TAC Vista Server (TACOS). This multi string value should list:RPCSS,TACOS, MSSQL$TACVISTA Restart the PC and it I/O Server should be running as a service now.

Issue Downloading a save for a 7793 MCI to a 7798 MCI, what needs to be done to accomplish this task. Environment All versions of I/Net that uses both the 7793 MCI and 7798 MCI. Cause System running multiple controllers and wants to switch out one for another for functional purposes. Resolution Note: This only works if you are using the first address points of the 7793 MCI. Start I/NET and go to the Offline Editor Connect to the 7793 MCI and select copy Create the file and choose the 7798 MCI Once completed, connect to the 7798 MCI and go to Resident I/O point. Verify that the point addresses are correct Make necessary changes to names, add, delete, modify accordingly Once completed, save and exit. Connect to the 7798 MCI and select Software Restore, then download the new save file to the controller.

Issue Attempts to login are unsuccessful and device reports that logins are blocked. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server tracks attempts to log in by recording the IP address and Username of the login attempt. After 5 login attempts it will block any attempts to login to with that username and IP address for 10 minutes. Resolution Use a different user account on the Xenta Server to login and perform the necessary work or wait 10 minutes for the lockout to expire. If the lockout is continuing after 10 minutes then ensure that if the Xenta Server is in a Vista database that it is not running and trying to communicate to the Xenta Server with an incorrect username and password. Any changes to the root user password must also be changed in the Vista database to avoid perpetual blocking of login attempts on that computer and IP address.

Issue After running LANMON 3 on an I/NET C-LAN, it may return some error codes. The list below will help determine what they mean and the best way to address them. Environment I/NET Controller LAN LANMON output text file Cause Controller LAN errors captured by the LANMON program. Resolution One of the most useful new features of LANMon 3.0 is the detection and labeling of several types of communications errors. The label associated with the detection of a communications error is stored in the disk file just in front of the communications packet to which the error label applies. The error labels are presented in ASCII text along side the hexadecimal data. This text should allow most I/NET technicians to perform some level of useful investigation into controller LAN communications problems and reduce the necessity for sending LANMon files in to Technical Service for analysis. The following paragraphs lists the error descriptions associated with the type of errors detected by LANMon. The Bold text represents the label you will see on the screen or in the capture file when LANMon detects that type of error. ERR: Retry This error indicates that LANMon has detected a retransmission of the same command. This is the most common error type and can be used to find which controllers are having problems receiving from others. You should reference the destination and source addresses listed in the retry packet and accumulate/record this information. If there is a prevalence of specific nodes (destination or source) showing up in the retry packets, this would serve as a significant pointer to examine for network problems in that physical area (possibly in the cabling, environmental disturbances, power, grounding, and controller hardware and/or application software) ERR: LAN reconfiguration This error indicates that LANMon detected the occurrence of a LAN reconfiguration. This is a normal expectation when a controller/node is added or removed from the network as a result of LAN cable disconnect or power. When intentional changes are not in-work on the network configuration, a LAN reconfiguration is typically the result of several sequential errors (typically retry’s) which prompts the sending controller/node to initiate a LAN reconfiguration on the basis that it appears a node has been lost and everyone needs to have a new picture of the network layout. ERR: SDLC CRC Error This error indicates that the LANMon Tap received an RS485 packet with incorrect CRC indicating the packet is corrupted in some way. This error results from data distortion on the cabling or from intermittent disruptions such as from EMI, noise or grounding fault. With this error, the primary address you are interested in is the source address. If you are seeing a number of CRC errors from the same node address, or a collection of node addresses, you may want to look for cabling or loading problems in that area, or the length of cable getting to the area. You should make note of where LANMon is positioned when seeing this error. The error could be expected to get worse as to get further away from the reporting node address. For this reason, it is often recommended that you perform LANMon captures and analysis from at least two points on the network and those points should be the two most distant ends of the network. ERR: LAN master conflict with ## This error indicates LANMon has detected a NULL command output from a controller/node other than the currently recorded LAN master. The ## number will show the address of the node currently understood to be the LAN master. The packet following this error message will contain the address of the contending LAN master. This master conflict error is frequently the result of multiple simultaneous LAN reconfigurations. There should only be one LAN master and it is the function of that one LAN master to output the NULL command each time the token makes one pass around to all the network addresses and arrives back at the LAN master.   The following error descriptions will be encountered far less frequently and are not typically used for LAN diagnosis. ERR: Bad address LANMon detected a destination or source address greater than 3F16 (6310) ERR: Bad NULL LANMon detected that NULL was sent out without the same destination and source address, or without the broadcast header. ERR: Bad reconfigure LANMon detected that reconfigure command “01” was sent out without the same destination and source address, or without the FF broadcast header. ERR: Bad token LANMon observed what appeared to be a token command but had byte count greater than 3, or had destination and source addresses the same. ERR: Frame overrun LANMon received >160 bytes on the Async port from the LANMon Tap which exceeds design limits/expectations. ERR: Frame underrun Async frame from LANMon Tap to PC was considered too short to contain any SDLC (CLAN) data. ERR: Lost frame synch The LANMon program running in the PC got out of synch with the data stream from the LANMon Tap. This should be an unusual error. If it is repeatedly encountered, You can try running the LANMon utility on a faster PC, or you can try running it with Monitor mode OFF. B E1 m N O ERR: Bad frame CRC The LANMon program detected a CRC error in the Async frame of data from the LANMon Tap. With the standard short (6 ft.) RS232 cable between the PC and Tap, this should be a very infrequent error. ERR: Unknown error code This is a catch-all error indication intended to present any error codes returned from the SDLC controller in the Tap that are not currently defined. You should not see this error message. ERR: Frame too short The Async frame of data from the Tap to the PC is considered too short to contain a valid SDLC packet.

Issue When a SHR100-T is setup with a 0-10 volt humidity sensor the temperature reading fluctuates Environment Xenta controllers I/NET Controllers SHR100-T Temperature Humidity Sensor Cause Interference from the 24Volt AC power supply in the same cable causes this temperature fluctuation. Resolution  The two tested fixes that stabilize the temperature reading are. Set the humidity as a 4-20mA signal, this will stabilize the temperature reading. Run the 24Volt AC power supply in a separate cable. This is the better option if this is noted before installation is started.

Issue What LonWorks data is accessible from a Xenta Server and what can the data be used for? Environment Xenta 500 Xenta 700 Xenta 900 XBuilder Cause There are different types of data accessible on a LonWorks network. TAC network variables / Public Signals - TAC proprietary communication for signals from Xenta programmable controllers SNVT - network variables available for bindings SCPT/UCPT - Configuration properties for LonWorks devices. UNVT - User defined SNVT. Data accessible from a Xenta Server can be used in Xbuilder in multiple ways: Polling - value polled for use in graphics page, values page, alarm, trending, and scheduling. Connection object - poll and send process to pass value from one device to another (could cross protocols). SNVT binding - binding from a SNVT created on the Xenta Server. Resolution Use the following table to identify which signals types are supported and how they can be used. Data type  Polling Connection Object  Binding  Public Signals  Yes 1  Yes 1  No  SNVT  Yes  Yes  Yes 2  SCPT/UCPT  No  No  No  UNVT  No  No  No 1 Xenta Server must be commissioned to have the TAC group address in its address table. Create group bindings in TAC System Plug-in for LNS networks Commission LonWorks network for Xenta Servers in Classic networks Commission and download Xenta Server acting as LonWorks unit in a LonWorks group in Classic network. 2 SNVTs must be created by Xbuilder on the Xenta Server device. These SVNTs are then bound using a network management tool such as LonMaker or NL-220.

Issue When an Alarm point goes into Alarm, it needs to come up on the forefront. Environment All versions of I/Net using graphics. Cause When creating Alarms and the point goes in Alarm but does not come to the forefront and stays on the graphic page. Resolution For the page to come up front when the point goes into Alarm, the following steps needs to be followed: Select System, Edit Graphic Page. Open the page that the point is on. Select the point and Right Click to display the properties. Select the Automatic Page Display check box. Close the editor and then save the changes. NOTES: In order for the auto pop up feature to function, you will need to have the point masked for messaging. Also set AMT Configuration and Host Masking with the corresponding check boxes.

Issue XBuilder project was upgraded and OGC graphic pages were converted to TGML using the automatic conversion. The same names were used for the graphic pages, but they will not display in the web interface. Java console reports: java.io.IOException: Wrong file format feature < 0 or reature > 7  at se.tac.applet.graphics.ogc.OGCStreamHeader.load(Unknown Source)  at se.tac.applet.graphics.ogc.OGCPicture.loadPicture(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.go(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.init(Unknown Source)  at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)  at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder 5.x.x Xenta Servers Xenta 511, 527, 711, 731 Cause The graphic object was properly converted, but the graphic page is still using the old template (Graphics.html) which is designed for OGC graphics instead of the new graphics page template (TgmlGraphics.html). This causes the java to interpret a TGML graphic file as an OGC graphic file. Resolution This can be resolved two ways Manually edit the Template property of the Graphic page objects in XBuilder to be TgmlGraphics.html. Delete the graphics page in XBuilder and recreate it. When the graphic object is linked to the graphics page it will properly assign the correct template based on the type of graphics file type.

Issue Error when starting Seven Reports getting an error "Copy of prompt.dll failed Error Code 2". Environment All versions of I/NET Seven and Windows OS. Cause Administrative privileges on the PC needed to run Seven Reports. Resolution Log off of I/NET and I/O Server. Shut the PC down and restart it. Log back in as an Administrator and run the Seven Report again.

Issue Can Inovonics wireless equipment be used with Xenta Servers? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Inovonics Frequency Agile product line which is compatible with the Xenta Server driver is being obsoleted by the manufacturer Inovonics at the end of 2011. Resolution If you have existing devices installed in the field then they should continue to work and function. New installations should explore other options for wireless sensors due to unavailability from the manufacturer. The ability to add a RS232 wireless Inovonics interface was removed from XBuilder beginning in version 5.1.8.

Issue Changed sa user name as requested and unable to log in to DbCreate using that username Unable to use standard "sa" password for "sa" username Environment DbCreate I/NET Seven SQL Cause Due to new security requirements from Windows and SQL you are unable to leave the SQL admin password as the default: Username: "sa" and Password : "sa".  When installing I/NET you will be asked to provide a new more secure password.  The "sa" username cannot and should not be changed. Resolution When installing I/NET have a new username for SQL ready.  This must be something that can be recorded and available to technician when needed When prompted, enter the new password.  You will have to enter in twice to verify the text To run DbCreate us the username: "sa" and the password that you entered during installation.

Issue Downloading to a 7920 MIP and it freezes up and stops communicating. Environment All versions of I/Net Software doing Access Control. Cause The software probably got corrupted during the download and needs to be cleared out to accept the latest bin file from the host. Resolution With Power on and the board mounted on the 7920, On Pin Header J4, connect Pins 1 and 2 Together, via jumper or whatever medium available Press the Reset button

Issue Station Address conflict Error in I/NET after adding a controller Environment I/NET Cause Each Station must have a unique Station Address Resolution Check Network Configuration at the host workstation for an available Station address Using the HHC, change the station address to an open address.

Issue During Construction it may be required to use a temporary database to allow access control to function before the IP infrastructure is in place. Environment I/NET Seven Cause A temporary database has been used during construction. The end user has an existing database that the new links and doors must be added to. In some cases the temporary database may be required to be used while the building is occupied so a smooth transition between the two databases is required. Resolution Construction Phase Determine in advance the link information to be used for each new Xenta 527, and the full address for each door Determine who will access which doors within the new construction and add these individuals to new or existing groups accordingly Commission doors and add badges using the temporary database by using the available TAP on the SLI. If you use a crossover cable to connect to the Xenta 527, be sure to clear routing tables at the end of construction Ensure that each Xenta 527 has an available patch cable and Ethernet port installed Inform the IT department or installer that I/NET must have port 50069 open DO NOT leave the Xenta 527 plugged into the Ethernet port during construction If the building becomes occupied, add badges to the door using a temporary database connected via TAP If you are using multiple SLI's during the construction phase, it is important to ensure you are using only 1 access control Database.  Any other machine must have access control disabled to ensure cards are not removed from the system. If you have to add additional badges to any of the SLIs or change the temporary Database, you may need to do a station restore for the changes to take effect. Adding the New Links and Doors to the existing system Verify that the Ethernet port by each Xenta 527 is functional by using a laptop to "ping" the Primary Host workstation. The lights on the Xenta 527 may show active Ethernet communication before the new construction IP is connected to the Local network. Connect to each controller using your temporary database. Perform a station save.  If you have any issues, this will function as your restore point. Connect to the Xenta 527 and ensure that the reference Hosts and link information is correct. Connect the Xenta 527 to the Ethernet port and cycle power. At the Host PC, Select Edit>Host Computer>Network Configuration Save the new Xenta 527's, SLI's, SCUs and Doors Select Access>Tenant Add the Doors to the appropriate Tenant Select Access>Groups Give the appropriate Groups access to the correct doors Verify you have given access to all appropriate people.  You may wish to compare the System View of each door on your temporary to the System View of each door on the site database Connect to the controller Select Edit>Controller>Station Save To clear the old database you will need to take the controller to Boot. select Edit> Host computer> software Restore Load the Bin file to the appropriate controller, but hit cancel after 10K have downloaded Load the Bin file again, this time allow it to finish. Connect to the controller Select Edit>Controller>Station Restore Choose the SLI option Select Edit>Controller>Station Restore Choose the DPU option Select all DPUs and restore Once this process is completed test several badges. Repeat steps 12-21 for each SLI under this Xenta 527 Repeat this process for each Xenta 527

Issue What functions can you do in I/NET if you change the Windows users rights? Environment All versions of I/NET Seven Software Cause Changing the Windows users rights affects the way I/NET functions. Resolution   User Account I/NET Seven Operation Administrator Power User User Install I/NET Yes Yes No Remove I/NET Yes Yes No Upgrade I/NET Yes Yes No I/NET Configuration Yes Yes Yes         DBCreate Functions       Create db Yes Yes Yes Import I/NET 2X Yes Yes Yes Verify existing db Yes Yes Yes Remove existing db Yes Yes Yes Backup db Yes Yes Yes Restore db Yes No No Import Docutrend Archive Yes Yes Yes Upgrade db Yes Yes Yes         Seven Reports       View Yes Yes Yes Run Yes Yes Yes Configure Yes Yes Yes Save Yes Yes Yes Print Report Yes Yes Yes Mount Archive Yes Yes Yes View Archive Yes Yes Yes Run Archive Yes Yes Yes Print Archive Report Yes Yes Yes         Archive Configuration       Event Archive Configuration Yes Yes Yes Run Yes Yes Yes Trend Archive Configuration Yes Yes Yes Run Yes Yes Yes View Yes Yes Yes         I/O Server Configuration       Promote Filemaster Yes No No Demote Filemaster Yes No No Promote Client Yes No No Demote Client Yes No No   There are two components of security available to users of I/NET Seven: I/NET Seven passwords and Microsoft Windows user accounts. I/NET Seven passwords are specifically aimed at limiting a user’s access to features and functions within the I/NET Seven system. The restrictions imposed by I/NET Seven passwords are application-specific (i.e., they only affect the I/NET Seven system) and do not provide a replacement for domain security methods. Microsoft is very clear about the importance of limiting permissions to users in a network environment. The user account permissions that are standard in Windows 2000 and Windows XP allow full management of the computer to users with “Administrative” group membership or any group containing administrative permissions. The “Power User” group permissions allow users to install programs but restrict what these users can do to the operating system. The “User” group is the most secure because its operators cannot modify operating system settings or other users’ data. Microsoft clearly states that operators assigned to the User group may have trouble running legacy programs. This should pose no problem for I/NET users since I/NET Seven has been specifically developed to run on the Windows 2000 and XP operating system. Most functions of I/NET Seven including general system operation, AMT (alarms, messages, and transaction) processing, reporting (Seven Reports), and archiving are available to an operator assigned to the User group or any group with those permissions. However, these operators cannot install I/NET Seven or delete or upgrade its database. Seven Reports is password-protected but can be configured within I/NET Seven to allow automatic logon to operators of a Host PC. The above spreadsheet shows the functions/operations that can be performed by members of the Administrator, Power User, and User groups. For further information about Windows security, please refer to Microsoft Windows online help for more information about user accounts, permissions, and Microsoft Management Console best practices". https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc750076(v=technet.10)