Jetro CockpIT™ Version 3.0 Knowledge Base

:: Quick search Users Cannot Access the CockpIT Logon Page Login Button Does Not Work Single User Cannot Access CockpIT Login Fails for All Users CockpIT Administrator Cannot Access the Site Jetro Client Failed to Download, Operate, or Install Users Cannot Launch Programs Now but Could Before Application Launching and Closing Takes a Long Time User Does Not Get a Newly Defined Application Specific Application Sometimes Works and Sometimes Doesn't White Screen Appears Instead of an Application Terminal Server Asks for Username and Password Terminal Server Fails to Communicate with CockpIT "No server available" Error Message Newly Defined Users or Groups Can Not Be Added to a Security Policy "Maximum concurrent users reached" Error Message "Failed to check in, wrong login parameters" Error Message Jetro Client Failed to Login Automatically When Restarting Computer Configuring CockpIT for the NAT Environment Removing CockpIT Plug-in Files Changing the Domain to Which CockpIT is connected to Determining the size of the Directory Service Optimizing CockpIT Synchronization with Directory Service Creating a Server Failure Alert Script Creating a Load Balancing File Changing a Server's Load Balancing File Backing-up CockpIT Data, Files, and Site Icons Restoring the CockpIT Administrated Server Farm JdsWebClient.dll or MstsCax.dll Can Not Be Found Failed to Trigger Application

JKB00322 Creating a Server Failure Alert Script   General: A network communication failure or other hardware or software problem can prevent the Terminal Server Agent software from communicating with CockpIT and trigger a failure alert. If a terminal server does not communicate with CockpIT for longer than the timeout period defined in the registry, the server will be announced as an off-line server*. * See for more about setting server time out period, see JKB00223 CockpIT Registry Settings under the entry “ServerTimeout.” A few things take place when a server goes off-line: 1. CockpIT stops directing users to this server. 2. The green server icon under the 'Server Load Monitor' page is replaced with a red icon. 3. Server failure alert is executed. The script for the server failure alert is a command line kept in the CockpIT registry. CockpIT runs this command line and adds the server name as a parameter to it. AlertScriptPath is the registry key defines the command line used as alert script. This parameter is empty by default. The following instructions explain how to implement and test a server failure alert. Methods: Attaching an alert script: 1. Create a script or batch file. Use parameter ‘%’1 to represent the server name in your script. When CockpIT executes this script this parameter will be replaced with the server’s name. 2. Add the path of the alert script to the alert script field in the Server Settings window (access the Server Settings window by clicking on the Server Settings tab from the Welcome screen in the CockpIT Administrator Site). 3. Click Save at the top of the server settings page. CockpIT will automatically restart the JDs service and read the changes in the registry. Testing server failure alert: 1. Write the following line in Microsoft Notepad: Net Send ComputerName Server %1 is down ! ComputerName is the name of the computer where you want the alert sent. This computer must have NT, Win2K or XP with Messenger Service enabled and running. 2. Save the notepad file as c:\alert.bat 3. Enter the path and script name into the server alert field in the Server Settings window (access the Server Settings window by clicking on the Server Settings tab from the Welcome screen in the CockpIT Administrator Site). 4. Restart JDS service. 5. Close the Jhgate service on one terminal server. 6. Wait five seconds or for the timeout period for your CockpIT farm. A pop up message will appear on your desktop.   Back to top