N-able Uninstall

0 views

Skip to first unread message

Tammara Freimark

unread,

Aug 3, 2024, 3:52:59 PM8/3/24

to ealpodlade

Any features and associated Checks deployed by the Agent are removed as part of the uninstall process. This can result in a longer than anticipated uninstall time as each of these programs is removed along with the Agent.

When you delete a device, that action is recorded in the User Audit Report. The User Audit Report includes the date/time of the removal, the username, the details of the action, and the Event type such as, Agent Uninstalled Manually from Device.

If the Agent was installed over Group Policy, the Agent must be uninstalled using the existing Group Policy Object. Otherwise, the Group Policy may detect the Agent as uninstalled and attempt to reinstall it the next time it runs.

To ensure the Agent uninstalls successfully, do not remove or change the permission of the software distribution point to ensure this location is accessible by the Agent uninstaller, for example the directory NetworkInstaller.

unbelievably crap software, if you ever make the mistake of purchasing n-able RMM make sure you remove it from all of you clients machines well before you stop paying. There support is shit when you are a paying customer and it just gets even worse after that.

ran an evaluation it caused my desktops to go so slow no doubt scanning them but some became unusable. so i decided to remove it and that is when i ran into a problem. there is no way to remove this software. you have to go to each computer and delete registry etc to get rid of it it is worse than a virus.

The unstable behavior is not observed when the user triggers the update from System Preferences. So now when the Run Managed Patch task runs and finds that an Apple patch requiring a reboot needs to be installed, we no longer attempt the scripted installation that may lead to a bricked Mac. Instead we open the Software Update prefpane and display a branded notification to the user asking them to click the Update Now button.

This of course requires that your Run Managed Patch task be set to run while the user is logged in (as a best practice, we recommend two Run Managed Patch tasks be setup: one that runs while the user is present to do most patches and display the new Apple behavior, and one that runs only when the user is logged out to do updates that cannot be installed with the user present).

Windows RC Agent v10.11.0
FEATURE: Uninstall protection with uninstall code
UPDATE: Background improvements to the Antivirus Update Check to address 3rd party check changes more quickly
BUGFIX: Update to Grisoft AVG in the Antivirus Update Check to resolve an agent crashing issue

N-able considers various features and functionality prior to any final generally available release. As such, comments given in this forum are not (nor should they be interpreted to be) a commitment from N-able that it will deliver any specific feature or, if it delivers such feature, any time frame when that feature will be delivered. N-able is always trying to improve and enhance its products. All discussions herein are based upon product team current interests, and product team plans and priorities can change at any time.

Support tells me that this is a known issue and that the developers are working on a fix, but none has been provided in the four days since I opened a ticket. Their only workaround is to uninstall the entire RMM agent.

I tried to set up Software Restriction Policies in Group Policy based on the path, hash, and even the SentinelOne certificate, but somehow the installer kept getting past that and re-installing the EDR.

Uninstall the Ecosystem Agent at your own risk! I have no idea what else it might be needed for. It looks like it might have been used for Patch Management on this machine some time ago (currently disabled). I did check another machine running Patch Management and it did not have the Ecosystem Agent.

One month after I opened a ticket on this, there is still no resolution. The Ecosystem Agent and SentinelOne EDR have not re-installed themselves, but the SentinelOne alerts are still failing and cannot be deleted.

Today at 3:52am, without any action or consent on my part, the SentinelOne agent re-installed itself on the machine on which EDR is deactivated. I see that the Ecosystem Agent was also re-installed. Support told me on March 15 that they are working on pushing a fix to the Ecosystem agent, but it is broken again for me.

On April 9, I received a generic notice that SolarWinds (now N-able) would be pushing an EDR update on April 13. Although the notice did not mention the blocked uninstall issue, I hoped that it would uninstall EDR on this device, since it had been set to Off for the past two months. It did not uninstall automatically, but after turning EDR On and back Off, it seems to have completed the uninstall.

So I am having the exact opposite issue. I was able to get the newer versions to remove, but anything that returned "C:\Program Files\Dell\SupportAssist\uninstaller.exe /arp" as the UninstallString is failing in my automation as I can't get the prompt to not display (I have around 700 agents to remove this crap from, some with multiple versions, so I feel your pain).

Ran into a similar problem. I had a bunch of computers all with different versions of Support Assist. I compiled this from a few different sources. So far I have had really good success. I am using PDQ deploy. I am not the most PowerShell proficient but perhaps this will help.

This is what I came up with..Uninstalls "Dell SupportAssist" and "Dell SupportAssist OS Recovery Plugin for Dell Update"Hope this helps someone else too.. The code probably could be cleaned up or simplified a bit but it worked for me.

Whether you have standard bloatware you remove from end-user machines during onboarding, you want to blacklist applications due to security concerns, or you just need to uninstall an application remotely across an entire organization, NinjaOne can help you make the process fast and easy.

Remote access is ideal for when either a complex uninstallation process is required on an individual device, or if you cannot uninstall an application via other means. Using remote access to uninstall software does not scale well.

Policy conditions and custom scripts allow you to fully automate application removal across your endpoints. While the other methods mentioned above are also incredibly effective, only through IT automation can you uninstall programs remotely and ensure they stay unavailable to end-users.

Search for specific phrases by enclosing them in double quotes. Filter by topic by adding "topic:Topic_Name" preceding the search term or using the Apply Search Filter menu. Examples: "topic:Vinyl" upgrade, "topic:Cloud_Studio" connectors, or "topic:Management_Console" "cloud logging".

Upgrading a private agent from an earlier private agent version to a later one can be done without uninstalling the prior agent version, as described in Upgrade an agent below. However, there are additional considerations when upgrading from a 10.x to an 11.x Linux private agent.

Upgrading a private agent on Linux can be performed by using the same commands used during initial installation. You do not need to run the configuration script when upgrading an existing private agent.

Linux private agents can be upgraded to 11.x from any supported 10.x agent version without any additional commands. A PostgreSQL database upgrade and PostgreSQL ODBC driver upgrade will be completed automatically when the agent is upgraded, provided the PostgreSQL requirements are met.

The length of time it takes to perform a full sync depends on the number and complexity of projects in each environment. For typical environment usage, a full sync typically takes up to 10 minutes to complete. However, environments with a very large number of projects may take several hours to sync. If having an outage is a concern, see the recommendations for large deployments below.

The scheduler has a delayed startup of 10 minutes, as indicated in Scheduler.log. During this time, scheduled operations will not be triggered to run. Once the delay is complete, scheduled operations that would have been triggered to run during the delay will be triggered to run.

If having an outage is a concern during an agent upgrade, we recommend using high availability (two or more agents) so that requests are routed to another available agent in the agent group. If your current subscription does not have agent grouping, contact your Customer Success Manager (CSM).

When a full sync is expected to occur, such as when upgrading from a 10.x to an 11.x agent version, we recommend a rolling upgrade approach, where you install new agents in standby mode one at a time in an existing agent group prior to decommissioning existing agents. This approach provides a clean rollback path should the need arise.

Starting agents in standby mode involves adding a setting to an agent's properties file (jitterbit-agent-config.properties) to make sure the agent stays out of commission and will not start to accumulate a backlog of requests before the full sync is complete.