Connectors and Group Relationships

[TimSmith38238]

I am new to AMP, in fact we are in the very beginning stages of implementation.  We are confused and thought it would be a good idea to reach out to the community.  What is the relationship between Groups and Connectors?  It seems very odd that we have to select a group unless there is a very specific reason for it.  We are concerned about moving machines around from group to group or even moving a machine to a Triage Group without giving it a new Connector.  Can someone help complete my understanding here?

[Matthew Franks]

Tim,

Check out this Deployment Methodology document, specifically the Groups and Policies sections.  It should help clear things up a bit.

Thanks,

Matt

[Ken Stieers]

By Connector do you mean what's on the Download connector page?
If so, when you select a group, and download the connector, you're just deciding what group (and hence which policy) is applied to machines where you run that install.
Once machines show up in the console, you can move them around wherever.
Assuming you're building out your own groups and policies:
Typical workflow is to get some machines in, put them in your group, tweak the policy until you like what it's doing.
Then download the connector with that group, and deploy how you normally deploy software.

[Troja007]

Hello @TimSmith38238,

maybe this graphics helps a little bit. It shows the relationship between Policy Object and Groups.

The connector itself receives al the settings from the policy assigned to the group. So finally,

• if there are two groups with where the same policy is attached and you move the endpoints, there is no change on the connector.
• If there is a different policy attached to a group and you move the endpoint in this group, the policy on the endpoint will change.

Hope this helps,

Greetings,

Thorsten