|
System Start-upOn System Startup...Determines whether the Agent will become enabled when the machine boots up. The following options are available:1. Enable Agent - Agent will always start off in the "Enabled" status. 2. Disable Agent - Agent will always start off in the "Disabled" status. 3. Keep last Agent State - Agent will start off in the status that was active in the last system shut-down. Screen SaverEnable screen saver detectionDetermines whether the Agent will detect screen saver activity. When this feature is used, screen saver CPU activity will be considered idle CPU activity, improving the Agent's chances of getting assigned to remote builds. Furthermore, the following changes in behavior will take effect during screen saver activity:- Tasks (Compilation and others) running on this Agent will always use a high priority thread, improving performance. - A "Screen saver running" indication will appear for that Agent in the Coordinator application. Important note: On some versions of Windows NT, screen saver activity detection may be unreliable. See the "Readme" document in the start menu for more information. Enable Agent while screen saver is runningDetermines whether the Agent will automatically become enabled when the screen saver starts, even if the Agent is disabled. When the screen saver activity stops, the Agent will resume its "Disabled" status. This option is available only when the "Enable screen saver detection" option is selected.Version UpdateAsk for a user confirmation before a remotely initiated version update is performedUncheck this option to specify that there is no need for the user to manually 'OK' version updates received from the Coordinator application. Any version update will then automatically be run on demand.MS Windows FirewallIgnore MS Windows Firewall related messagesCheck this option to prevent IncrediBuild from suggesting to open IncrediBuild ports in MS Windows Firewall on this machine. |
| Converted from CHM to HTML with chm2web Standard 2.7 (unicode) |