Follow

Why do agents in a particular group keep getting "duplicate" accounts created (same machine name, different GUID)?

QUESTION


Why do agents in a particular group keep getting "duplicate" accounts created (same machine name, different GUID)?

No install packages were found in the login scripts and there is no Active Directory deployment set up for the group under Agent tab > View AD Computers.

ANSWER

Customer had an agent installation package that was deployed via AD group policy. Since the package had /t /w /g=unnamed options, everytime a machine restarts, the new agent is re-installed with brand new configuration in unnamed group. It was then moved back to the same group as the old account by the Naming Policy.

The AD deployment could not be seen on the View AD Computers page since the agent on the domain controller was also re-installed with a different GUID because of the installation package options. However the KAgentDeployment group policy still existed on the domain so the package was still running.

Any agent package deployed using Active Directory or a logon script should have the /e intead of /r switch. This will exit the install if the agent is already installed.

To clear up this issue it was necessary to make the above change to the agent package, cancel the previous AD deployment by deleting the KAgentDeployment group policy on the domain controller, then create a new AD deployment using Agent tab > View AD Computers.

MORE INFORMATION
N/A

APPLIES TO

Kaseya v5.1
Kaseya K2 v6 and later
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.