/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

VSA Discovery

AD Deployment-based Agents not updating properly since upgrading to a newer VSA version

SYMPTOM
AD Deployment-based Agents not updating properly since upgrading to a newer VSA version.

There are now two Agents viewable for one machine. It is unknown how this occurred.

CAUSE
The currently applied AD-based KAgentDeployment policy is an older-based policy w/ older Windows Agent installation file components.

On the Domain Controller-based machine, visit the Group Policy Manager and check for existence of a group policy called "KAgentDeployment". If this is present (one or more), then this is evidence that this is the cause of the issue.

Also, one can download the much easier to use Group Policy Management Console (GPMC) SP1 app onto the Domain Controller-based machine and use this to find this policy. The download for this is here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=0A6D4C24-8CBD-4B35-9272-DD3CBFC81887&displaylang=en

RESOLUTION
One will need to recreate the Deployment policy on the Domain Controller used with the not-updating agents that are associated with AD Deployment policies (Users or Machines), delete them & recreate them so that the K2 v6 Agent package installer is used in this situation. If it is not needed, then simply delete this policy on the Domain Controller.

From there, for these symptom machines that are not updating, the following has to occur:

1) Using a non-Kaseya remote method, uninstall both Agents present on the machine (you will see that there are two listings in the Add/Remove Programs listings).
2) Reboot the machine.
3) Reinstall the Agent w/ an appropriate updated Win package or with a latest version-based KAgentDeployment Logon policy or Machine policy (as described above) if you are updating the Domain Controller for these machines with this policy.
4) In the Agent > Install Agents > Rename page, merge the previous problematic offline agents with the properly reinstalled online agent.

For multiple accounts appearing, the following can be taken to resolve this:

1) If one agent is exhibiting problems, uninstall that one or whichever one is preferred to be uninstalled.
2) In the Agent > Install Agents > Rename page, merge this now offline agent with the other still online working agent.

APPLIES TO
AD / Active Directory
Kaseya Windows Agents