Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-Install Deleted Agent in Ncentral #2

Open
milanofabio opened this issue Sep 26, 2019 · 1 comment
Open

Re-Install Deleted Agent in Ncentral #2

milanofabio opened this issue Sep 26, 2019 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@milanofabio
Copy link

The previous version of the Agent Installer would re-install the agent if the agent was removed from NCentral.

"On a device that has been deleted from N-central, the agent will be reinstalled and begin checking into N-central shortly after the reinstall has completed"

Is it possible to add the same functionality ?

@rad-ryanc rad-ryanc self-assigned this Jan 2, 2020
@rad-ryanc
Copy link
Contributor

rad-ryanc commented Jan 2, 2020

Hmm, I'm curious as to what you are witnessing that is prompting this question, since that functionality is incorporated in the same way as it was in the original InstallAgent Package.

First of all, let me make the following assumptions to help me better understand and identify the issue:
1 - Auto-Import for Laptops/Servers/Workstations is enabled
2 - The Agent Deployment Package is fully setup as instructed on the primary Domain Controller
3 - The "Uninstall Local Agent" checkbox is marked when a Device is removed from N-Central
4 - The Agent is confirmed to have been removed from the local Device
5 - The Device is rebooted and it does NOT re-appear in N-Central

Looking at the above list, not all of these can be true simultaneously, at least one is false or at least partially incorrect. Please review them and let me know which assumption about the scenario is incorrect.

The functionality you mentioned depends on a few things:
1 - The Group Policy in either Package only runs at Startup, so the Device must be rebooted in order for it to fix the Agent
2 - Neither Package has a way to tell specifically if "an Agent exists on the local Device, but not in N-Central" -- It can only look at local configuration data for barriers to installation/check-in (so if the "Uninstall Local Agent" box is not checked, or the removal process issued by N-Central fails, the Agent will be orphaned)
3 - If the Agent is deemed perfectly healthy, no action is taken by either Package on the current installation, so in a case like I mentioned in Item 2 just above, the Agent will have to become damaged or otherwise incapacitated for either Package to re-install it, and thus re-appear in N-Central

Does that help?

@rad-ryanc rad-ryanc added the question Further information is requested label Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants