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

JKB00330 Creating a Load Balancing File   Background: Every Terminal Server Agent comes with a default load-balancing file. Load balancing policies are modified using a tool called the JDsSlpGenerator. The JDsSlpGenerator The JDsSlpGenerator uses performance counters from Microsoft Windows 2000 Terminal Server to evaluate activity on the server. Administrators configure how data from these counters will be evaluated by using Weight that change the importance of specific counters. See JKB00329 Overview of CockpIT™ Load Balancing for a complete discussion of counters, counter weights, and load balancing calculations. Figure 2. The JDsSlpGenerator Window. Instructions: 1. Open JDsSlpGenerator on the terminal server whose load balancing policy you wish to create. program files – CockpIT™ Server – TSAgent – JDsSlpGenerator 2. Click on the "create new policy" button. 3. Click on the "Add" button to begin adding counters. The counter selection wizard will appear. 4. To choose a counter, you must first choose a performance object. For instance, if you wanted to monitor the number of active sessions taking place on a server, you would select the Terminal Services as your performance object. Choose a performance object you would like CockpIT™ to consider when determining this server's ability. The JDsSlpGenerator will automatically display a list of possible counters for that performance object. 5. Highlight the name of the counter you wish to monitor and click on the OK button. The counter's name, weight and description will now appear in the JDsSlpGenerator screen. Repeat steps 4-6 until you have a complete list of the counters you wish to use for this server. 6. Double-click on the counter's name to change the counter's weight. 7. Click on the settings button to change the history depth, measurement period, or server factor for this server. Click OK to save changes. 8. When you have finished customizing the settings for this load balancing policy, click on the save button. 9. For instructions on implementing a load balancing file see JKB00331 Changing a Server's Load Balancing File. Back to top