• NCD ThinSTAR Management Service (TMS) software, Version 2.0 or later on the management server, which includes the NCD ThinSTAR Operating Software for terminals.
• Microsoft Windows NT 4.0, 2000 & 2003 or later professional server. ThinPATH Manager cannot be installed on a Windows NT 3.51 server, or Windows 95/8.

Operation of the ThinPATH Remote Restart Tool requires two installed SNMP libraries, MGMTAPI.DLL AND SNMPAPI.DLL. These libraries do not have to be running, just installed.

A warning message appears during installation of the ThinPATH Manager if the MGMTAPI.DLL AND SNMPAPI.DLL files are not installed in the WINNT\system32\ directory on the Windows NT server. Even without them installed, the installation process finishes. However, the ThinPATH Remote Restart Tool cannot function without these Microsoft distributed files.

To install the MGMTAPI.DLL AND SNMPAPI.DLL files:

1. Go to Start > Settings > Control Panel > Network on your Windows NT server.
2. Select the Services tab and scroll down the list to see if the SNMP Service is installed. If it is, no further action is necessary.
3. If the SNMP Service is not installed, click Add.
4. Scroll down the list, select SNMP Service, and click OK.
5. Insert the NT source CD (if necessary).
6. After the files are copied, remove SNMP from Network Services if desired.

The default terminal upgrade policy in the ThinSTAR Management Service for the ThinPATH Web Configuration Tool is "Upgrade DISABLED." Under this policy, this tool is not automatically installed on terminals when they restart. To install the ThinPATH Web Configuration Tool on a terminal, please refer to the NCD ThinPATH Manager System Administrator's Guide.

Most of the changes you make to terminal properties while using the ThinPATH Configuration Tool take effect as soon as the terminal restarts. Changes to several types of terminal properties, including network settings, display resolution, and SNMP settings, do not take effect until after the terminal restarts a second time. When you make a configuration change that requires an additional restart, a dialog appears on the terminal to inform you and the terminal automatically restarts after a timeout.

The ThinPATH Configuration Tool is not supported in a dial-up environment.

Configuration files created while using a Beta version of the ThinPATH Configuration Tool do not work with version 1.0 of the ThinPATH Configuration Tool. You need to recreate your configuration files after installing version 1.0.

If you want to completely remove all files related to the product, you must manually delete the .tcf files (ThinPATH Configuration Files) yourself. The uninstall program does not automatically delete them in case the system administrator wants to keep them for possible future use.

Changes to some terminal settings made in the ThinPATH Web Configuration Tool do not take effect until the terminal is restarted. Although the software does not indicate which changes take place immediately and which require a terminal restart, in general, all changes to network settings require a terminal restart. This includes the parameters on the Network Configuration, Advanced Network, and Management > Network pages. In addition, if you change the settings for Enable Connection Hotkeys or Display NCD ThinSTAR Connection Manager's Configure Tab, the changes do not take effect until the terminal restarts.

Unreleased or beta versions of some browsers may incorrectly display current terminal settings due to improper caching. Changes made to terminal settings using the ThinPATH Web Configuration Tool take effect immediately, but the settings displayed in the browser are sometimes the old settings. This can also be caused by an incorrect browser cache setting.

Workarounds include upgrading the browser to a released version, clicking on the page again, or changing the cache setting in the browser. To set the cache setting in the Internet Explorer, select View > Internet Options > Temporary Internet Files and change the setting for Check for Newer versions of stored pages to "Every visit to the page".

If you interrupt an Apply operation, not all terminal setting values may be set and some changes may be lost. This is more likely to occur if you are used to a high speed network.

A restart command issued with the option to wait until the last connection on each terminal ends is known as a "polite restart." This command in the ThinPATH Remote Restart Tool instructs terminals to delay the restart until after all current connections close. Terminals restart immediately, however, when a polite restart command is issued if there is no active session on the terminal. The restart can occur even while you are working in Terminal Properties.

ThinSTAR 400 terminals that do not restart are sent a Wake-on-LAN command. If they were turned off using the front power switch, the ThinSTAR 400 terminals "wake" or power up and restart. If the ThinSTAR 400 terminal does not respond to the Wake-on-LAN command, the power supply is probably not plugged in, so a remote restart is not possible and the terminal's status remains "Wake-on-LAN."

If the ThinSTAR Management Service is not started on the Windows NT Server, the status field in the ThinPATH Remote Restart Tool cannot update.

The ThinPATH Remote Restart Tool is not supported in a dial-up environment.