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

JKB00332 Optimizing CockpIT Synchronization with Directory Service Adjust the Directory Refresh Period, Directory Scan Timeout, User Login Timeout settings to optimize synchronization. All of these settings can be adjusted in the Server Settings window in the Administrator Site. The tab for the Server Settings window is in the Welcome section, the section of the site that appears when you first login in to the Administrator Site. Directory Refresh Period (default is 600 seconds) This setting determines how often CockpIT will synchronize with the directory service. The default setting is 600,000 (every 10 minutes). · The synchronization interval should be at least three times longer than the time it takes to synchronize in order to avoid a synchronization overlap. · You can improve system performance by increasing the interval between synchronizations. Updates to the directory service will not be synchronized with CockpIT until synchronization takes place. When the interval between synchronizations is longer, CockpIT will be updated less frequently. In such a case, you can start synchronization manually by restarting the JDs service. Directory Scan Timeout (default is 400 seconds) Maximum time that CockpIT will spend trying to synchronize with the directory service before declaring a communication failure. This period should be at least five minutes longer than the interval between synchronizations. User Login Time Out This is the maximum time that CockpIT will try to communicate with the directory service if there is a network failure while a user is trying to login.   Back to top