Jump to content

Clients do not join dynamic group after migration from On-Prem


bink

Recommended Posts

Hello team,
we are migrating a customer from Protect On-Prem to PROTECT with the Migration Policy.

We now face the issue that the clients won't join the dynamic group they are supposed to. We have to completely uninstall the agent beforehand and then push the new agent via GPO e.g.

But this eliminates the purporse of the migration policy and the whole process of migrating gets cumbersome.

Is there anything else we need to be aware of? The dynamic group template etc. are all correct. We checked them like ten times

Thanks in advance

Link to comment
Share on other sites

  • Administrators

The membership in dynamic groups is evaluated by the management agent on endpoints. If the agent communicates with the ESET PROTECT server and the issue is with membership in DG, please raise a support ticket for further investigation of the issue. What kind of dynamic groups do you use that are not working?

Link to comment
Share on other sites

2 hours ago, Marcos said:

The membership in dynamic groups is evaluated by the management agent on endpoints. If the agent communicates with the ESET PROTECT server and the issue is with membership in DG, please raise a support ticket for further investigation of the issue. What kind of dynamic groups do you use that are not working?

We are using nothing special. We want the agent to evaluate the membership according to the FQDN. 

We know that this template is working because, just like I said, if we uninstall the agent beforehand and push the new agent, the group allocation works just fine.image.thumb.png.9d2f57f2c9184126d98afcadc8bc0b59.png

Link to comment
Share on other sites

Should we open a support ticket? Or do you have any suggestions why the membership evaluation isn't working?

Link to comment
Share on other sites

  • ESET Staff
1 hour ago, bink said:

Should we open a support ticket? Or do you have any suggestions why the membership evaluation isn't working?

I would recommend to do so. In theory, there should be no impact of migration -> once AGENT detects connection to new PROTECT, it will remove/forget all dynamic groups used previously and re-synchronize dynamic groups from new PROTECT.

So in short, problem description might indicate there is a problem with re-synchronization of dynamic groups once migration is done, or for some reason, AGENT is not properly detecting it's identifiers. Also it might be possible that just re-evaluation of dynamic groups is not triggered after migration - any chance you checked whether restarting of AGENT service or whole system resolves this?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...