-
Can I manually set the server address for an individual agent/endpoint?
QUESTION Can I manually set the server address for an individual agent/endpoint? ANSWER Each managed endpoint connects to the Kaseya server by the server’s IP address. When an agent is deployed to an endpoint, the agent contains the Kaseya server’s address. Generally agents should be updated via the server or redirected…
-
Pages Show .NET Errors
QUESTION There is a condition in Microsoft .NET that may cause multiple symptoms in Kaseya. Symptoms observed include some web pages not displaying properly (dashboards or vPro pages in Monitoring for example), or being entering a user name and password and being immediately returned to the logon page, or not being able to…
-
Agent Procedures appear stuck / not running on a newly installed Agent
KB#: KKB000616 · QUESTION I deployed a new agent using a package with settings copied from a template account. The Template has a number of Agent Procedures scheduled, which appear in the "Pending Procedures" tab. Some of them did not run on the new account and remain Pending for a long time. Why is this happening? ·…
-
Do any ports need to be opened on the firewall for remote access to work?
QUESTION Do any ports need to be open on the firewall for Remote Control to work? ANSWER There are no inbound ports required on either the remote or local computer to perform remote access functionality. It is important however that outbound port 5721 is open on the remote computer. Outbound port 5721 is how the remote…
-
How do I configure vPro hardware so that it can be detected and managed through Kaseya?
Question How do I configure vPro hardware so that it can be detected and managed through Kaseya? Answer Before you can manage vPro devices using Kaseya, you must configure the hardware and validate communication and credentials using a web browser from the agent machine you intend to manage them from. This machine must be…
-
Why are Agents not installing via LANWatch?
Question: Why are Agents not installing via LANWatch ? An error "The network path was not found" is seen in the log Answer: You have entered apparently valid credentials and used a valid package to install agents on machines. However, after scanning the LAN using LANWatch, some you see some obvious error messages,e.g.…
-
Why is one or more of my Kaseya Agents not visible and seems to have disappeared?
KB#: KKB000391 Question Why is one or more of my Kaseya Agents not visible and seems to have disappeared? Answer The agent machine(s) has not actually disappeared, but instead is being renamed based on the naming policy set for the group ID in System > Machine Groups > Naming Policy within the Kaseya Server VSA Web…
-
On Windows 7 and on Vista's PC's do I have to disable the UAC (User Access Control)?
KB#: KKB000633 · QUESTION On Windows 7 and Vista's PC's do I have to disable the UAC (User Access Control) for the Kaseya software to run scripts or perform tasks? · ANSWER UAC has no impact on the Kaseya software installed on each computer. The permissions and UAC settings are all sorted out during the software install.…
-
I have attempted to deploy new agent but are not able to connect. The icon is grey on the computers and the message "'Machine ID.Group ID' not recognized by the KServer .
KB#: KKB000058 QUESTION I have attempted to deploy new agent but are not able to connect. The icon is grey on the computers and the message "'Machine ID.Group ID' not recognized by the KServer . ANSWER Please check your subscription to make sure you have not exceeded your license limit. Kaseya Portal > Subscriptions Please…
-
How can I troubleshoot Lan Watch issues?
Problem How can I troubleshoot Lan Watch issues? Resolution On Windows machines, LAN Watch tries to connect to the folder \\admin$ using the credentials that you supplied. The first test that the computer you are trying to connect to, is available? On the machine you are running the LAN Watch from, start a Windows command…