Check-In Control

NAVIGATION  Agent > Configure Agents > Check-In Control

The Check-In Control page specifies when and where each agent should check in with a Kaseya Server. You can specify the primary and secondary Kaseya Server names/IP addresses used by the agent to check in, the bandwidth consumed by an agent to perform tasks and the check-in period.

  • The agent only checks into the primary server but not the secondary server, unless the primary server goes offline.
  • The primary and secondary Kaseya Server values and the minimum and maximum check-in periods are subject to the policies set using System > Check-in Policy. This prevents users from selecting settings that place undue stress on servers running the Kaseya Server service.
  • Changes made using this page take effect at the next agent check-in and display in red text until then.
  • Check-in Control information can also be maintained using the Agent Settings tab of the Live Connect and Machine Summary pages.

Secondary Server Limitations

Legacy remote control functions are relayed through the primary Kaseya Server address. When an agent checks into the secondary Kaseya Server address, legacy remote control sessions do not connect because they are directed to the wrong VSA relay server address. The secondary server function is used for agent migrations only. Agent functionality is limited to check-ins only when using the secondary server address. For full agent functionality, the agent must be checking-in to the Primary server.

Migrating Agents from one Kaseya Server to Another

You may decide for performance or logistical reasons to migrate managed machines to a new Kaseya Server. For instructions, see How to migrate agents to another VSA instance.

Changing the Port used by Agents to Check into the Kaseya Server

  1. Set the Primary Port to the new port.
  2. Set the Secondary Port to the old port.
  3. Wait for the new settings to take effect on all the agents.
  4. Display the System > Configure page. Enter the new port number in the Specify port Agents check into server with edit box and click the Change Port button.

NOTE   If any agents have not migrated to the new port before you switch the Kaseya Server, you will have to manually change the port at the managed machine. Right click the agent icon in the system tray to display the agent menu on the managed machine and select the Set Account... option. Enter the server address and port. For example, 192.168.1.7:1234.

Primary KServer

Enter the IP address or fully qualified host name of the machine ID's primary Kaseya Server. This setting is displayed in the Primary Kaseya Server column.

Kaseya agents initiate all communication with the Kaseya Server. For this reason the agents must always be able to reach the domain name or IP (Internet Protocol) address assigned to the Kaseya Server. Choose an IP address or domain name which can be resolved from all desired network(s), both on the local LAN and across the internet.

Best Practices: Although a public IP address may be used, Kaseya recommends using a domain name server (DNS) name for the Kaseya Server. This practice is recommended as a precaution should the IP address need to change. It is easier to modify the DNS entry than redirecting orphaned agents.

Primary Port

Enter the port number of either the primary Kaseya Server or a virtual system server. This setting is displayed in thePrimary KServercolumn.

IMPORTANT  Do NOT use a computer name for your server. The agent uses standard WinSock calls to resolve a fully qualified host name into an IP address, which is used for all agent connections. Resolving a computer name into an IP address is done by NETBIOS, which may or may not be enabled on each computer. NETBIOS is an optional last choice that the Windows will attempt to use to resolve a name. Therefore, only fully qualified names or IP addresses are supported.

Secondary KServer

Enter the IP address or fully qualified host name of the machine ID's secondary Kaseya Server. This setting is displayed in the Secondary KServer column. The agent only checks into the primary server but not the secondary server, unless the primary server goes offline.

Secondary Port

Enter the port number of either the secondary Kaseya Server or a virtual system server. This setting is displayed in theSecondary KServercolumn.

Check-In Period

Enter the time interval for an agent to wait before performing a quick check-in with the Kaseya Server. A check-in consists of a check for a recent update to the machine ID account. If a recent update has been set by a VSA user, the agent starts working on the task at the next check-in. This setting is displayed in the Check-In Period column. The minimum and maximum check-in periods allowed are set using System > Check-in Policy.

Best Practices: The agent maintains a persistent connection to the Kaseya Server. As a result, quick check-in times do not effect response times from the agent. The quick check-in time sets the maximum time to wait before re-establishing a dropped connection. Setting all your machine's quick check-in time to 30 seconds guarantees each agent recovers from a dropped connection within 30 seconds, assuming connectivity is successful.

Bind to Kserver

If checked, the agent is bound to a unique Kaseya Server ID. Bound agents cannot check-in successfully unless the unique Kaseya Server ID they are bound to using the Agent > Check-in Control page matches the unique ID assigned to the Kaseya Server using the System > Configure > Change ID option. Prevents IP address spoofing from redirecting agent check-ins. A lock icon in the paging areas shows the agent is bound. To unbind agents, select machines IDs, ensure Bind to Kserver is unchecked and click Update. The lock icon no longer displays for selected machines.

Bandwidth Throttle

Limit the agent to consuming a maximum amount of bandwidth on the system with this control. By default the agent shares bandwidth with all other running applications so you typically do not need bandwidth throttle enabled. Disable bandwidth throttle by entering a 0.

Warn if multiple agents use same account

The Kaseya Server can detect if more than one agent is connecting to the Kaseya Server and using the same machine ID.group ID.Organization ID. This problem could be caused by installing an agent install package pre-configured with the machine ID on more than one machine. Check this box to receive notifications of more than one agent using the same account each time you log into the Kaseya Server as a user.

Warn if agent on same LAN as KServer connects through gateway

If you are managing machines that share the same LAN as your Kaseya Server then you may get this alert. By default all agents connect back to the Kaseya Server using the external name/IP address. TCP/IP messages from these agents travel through your internal LAN to your router, and then back to the Kaseya Server. Some routers do a poor job of routing internal traffic back through themselves. Check this box to receive a notification when the Kaseya Server detects an agent may be on the same LAN but connecting through the router.

NOTE   Agents on the same LAN as the Kaseya Server should specify the internal IP address shared by both the agent and the Kaseya Server on the Check-In Control page.

Update

Click Update to update all selected machine IDs with the options previously selected.

Check-in status

These icons indicate the agent check-in status of each managed machine. Hovering the cursor over a check-in icon displays the agent Quick View window.

Word 50% / HTML 50% Agent is currently offline

Word 50% / HTML 50% User Logged In and Agent is Active

Word 50% / HTML 50% User Logged In and Agent is Inactive

Word 50% / HTML 50% User Not Logged In and Agent is online

Word 50% / HTML 50% User Not Logged In and Agent is Idle

Word 50% / HTML 50% The agent has been suspended

Word 50% / HTML 50% Agent has never checked in

Select All/Unselect All

Click the Select All link to check all rows on the page. Click the Unselect All link to uncheck all rows on the page.

Machine.Group ID

The list of Machine.Group IDs displayed is based on the Machine ID / Group ID filter and the machine groups the user is authorized to see using System > User Security > Scopes.