-
VSA Agent Packages: 'Set As Default Package' and 'Show On Download Page' Access Rights for User Roles.
Problem: There was an issue prior to 9.5.0.15 with two Access Rights for User Roles controlling agent packages that were not being honored: Set As Default Package and Show On Download Page: Cause: This was reported to our Engineering team and resolved in the latest patch for 9.5: "Fixed an issue where the create/edit…
-
Steps to Change the Default Remote Control - Screen Recordings Folder.
Question: What permissions do I need to set up after I move the Screen Recordings folder to a different drive? Answer: Screen Recording files are by default stored in C:\Kaseya\Storage. If you are moving this to a different folder, IUSR and IIS_IUSRS should have correct permission and database needs to be updated with the…
-
Unable to Edit/Delete Agent Package Created by other VSA Users.
Question: How can a Master/System VSA user delete agent install packages created by other VSA users? Answer: An agent package can only be edited/deleted by its owner; not even users with Master/System role and scope, by design. The Master/System user can, however, take ownership of the package and then edit/delete the…
-
'K Agent Update Done' script loops on Machines.
Problem: I have a few machines that whenever I try to update the Kaseya Agent on, the procedure loops in "K Agent Update Done". The following shows up in the "Procedure History" tab over and over again: Cause: This is likely happening because the machine hasn't been rebooted in X amount of time, i.e. after MS patches have…
-
9.5 Agent: "Installation of the Agent Failed" on Windows systems.
Problem: Whenever I try to install the Kaseya Agent on a Windows system, a cmd window pops up stating to press any key to continue and the installation ends up failing with this error: Cause: If you are trying to install the Kaseya Agent with an account containing spaces or any special character in its name, this can break…
-
Newly Installed Agents are not Checking into the VSA.
Problem: Newly installed Kaseya Agents get installed on endpoints yet they don't check into the VSA: Answer: If the agents are installed and showing online on the endpoint but not showing up in the Kaseya UI, then you'd need to verify if the agent license count has been exceeded. To verify this, simply navigate to System >…
-
How do I create a clean Windows workstation as a benchmark for testing?
Question: How do I create a clean Windows workstation as a benchmark for testing? Resolution: * Do a clean installation of Windows 7 or 10 on a workstation (ideally on a VM) * Create a Local Administrator user on the machine (do not create a Domain or Microsoft account) * Do not connect the machine to a domain * Do not…
-
Kaseya Server Installation Fails for SQL 2017
Problem The Kaseya Server installation/upgrade fails with the following error: System Error [0] Message: CREATE or ALTER ASSEMBLY for assembly 'KID' with the SAFE or EXTERNAL_ACCESS option failed because the 'clr strict security' option of sp_configure is set to 1. Microsoft recommends that you sign the assembly with a…
-
Reapply Schema Error: Table 'DeploymentPermissions' already has a primary key defined on it.
PROBLEM When running a reapply schema/reinstall database schema, and encounter the following error: Fatal MessageSys Error: ESET/index/eset.PK_DeploymentPermissions.sql System Error [0] Message: Error #1779: Table 'DeploymentPermissions' already has a primary key defined on it. Could not create constraint. See previous…
-
Agent Failing to Change Machine Groups
Issue: When I try to change the group of an agent, I get the following error: The Targeted group ID is already at the maximum number of allowed agents. Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count=1, current count=0 Cause: You might have set a limit to the…