Agent Registration - bound multiple times to the same configuration set

[Rick Culler]

Should be an easy one here I hope.

 

I'm just trying to setup a proof of concept of WEM, however for the registration of the agents on a few test machines, all the agents report that the agent is bound multiple times to the same configuration set. Based on the online documentation, its kind of vague on where to look for these bindings.

 

 

[James Kindon]

your objects are defined here:

 

Active Directory Objects -> Machines

 

If you have specified the machines as well as the OU for example, then you can end up with this problem

 

If you haven't done that, and have only specified an OU for example, then we might need to check the DB (simple enough)

[James Kindon]

Sorry, forgot to add that status of these machines can be found here

 

Administration -> Agents -> Registrations 

[Rick Culler]

Thanks for the reply. I originally started this PoC 2-3 months ago, but got busy, and left it alone for a bit.

 

Under Active Directory Objects -> Machines, there isn't anything there (at least not anymore).

 

You were mentioning checking the database?

[James Kindon]

fire up SQL Management Studio. Backup the DB first (enter disclaimer here)

 

DB in question is dbo.VUEMADObjects - you should have objects in there

 

You can delete them on the fly out of that DB, will probably need to remove them all and then add back in via the console

[Rick Culler]

Perfect, going into SQL Management studio and manually deleting those objects worked. Appreciate the help.

 

Interesting and a little concerning that it took going into the database to resolve that issue though, considering I really haven't even done anything yet with the product.

[James Kindon]

Good to hear

 

Yeah its a little strange, the whole move from sites to config sets and the AD integration for machine assignments has been a little whacky - lets call it a "feature" :-)

[Brian Mooney1709157652]

I just got hit with this problem as well. I am trying the solution.

[Amar Honnungar1709160466]

On 1/31/2018 at 3:18 AM, James Kindon said:

your objects are defined here:

 

Active Directory Objects -> Machines

 

If you have specified the machines as well as the OU for example, then you can end up with this problem

 

If you haven't done that, and have only specified an OU for example, then we might need to check the DB (simple enough)

This is correct. Ensure that you dont put any servers/desktop objects but point it to the OU