Ask the Community
Groups
AD Deployment-based Agents not updating properly since upgrading to a newer VSA version - Connect IT Community | Kaseya
<main> <article class="userContent"> <div> <ul><li> <strong>SYMPTOM </strong><br>AD Deployment-based Agents not updating properly since upgrading to a newer VSA version.<br><br>There are now two Agents viewable for one machine. It is unknown how this occurred.</li> </ul></div> <p> </p> <div> <ul><li> <strong>CAUSE </strong><br>The currently applied AD-based KAgentDeployment policy is an older-based policy w/ older Windows Agent installation file components.<br><br><p>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.</p> <p>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:</p> <p><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D0A6D4C24-8CBD-4B35-9272-DD3CBFC81887%26displaylang%3Den">http://www.microsoft.com/downloads/details.aspx?FamilyID=0A6D4C24-8CBD-4B35-9272-DD3CBFC81887&displaylang=en</a></p> </li> </ul></div> <p> </p> <div> <ul><li> <strong>RESOLUTION </strong><br><p>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.</p> <p>From there, for these symptom machines that are not updating, the following has to occur:</p> <p>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).<br>2) Reboot the machine.<br>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.<br>4) In the Agent > Install Agents > Rename page, merge the previous problematic offline agents with the properly reinstalled online agent.<br><br><br>For multiple accounts appearing, the following can be taken to resolve this:<br><br>1) If one agent is exhibiting problems, uninstall that one or whichever one is preferred to be uninstalled. <br>2) In the Agent > Install Agents > Rename page, merge this now offline agent with the other still online working agent.</p> </li> </ul></div> <p> </p> <div> <ul><li> <strong>APPLIES TO </strong><br>AD / Active Directory<br>Kaseya Windows Agents</li> </ul></div> </article> </main>