![]() ![]() $Uninstall3 = $Uninstall2 -Replace "MsiExec. $Uninstall2 = Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall | Get-ItemProperty | Where-Object \uninstall.exe -ArgumentList "-mode","unattended" Use the check boxes to create a view to display agents meetings specific criteria. $path = $UninstallString -replace "uninstall.exe", "" Kaseya remote control - Click the agent icon Kaseya live connect - Ctrl click agent icon Quick view - Hover over agent icon KRC Private Session - Hover over agent icon and select the appropriate option form the menu Create a View. $UninstallString = (Get-ItemProperty HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\NinjaRMMAgent*).UninstallString I'd sense used the Get-ChildItem to uninstall several other programs, but I know it will pull more than one path so I'd love to re-write this to loop thru all the possible msi and exe and hit them both in a few lines rather than this, but it works as is, any input from someone more knowledgeableble than me please, I'm not proud. and this worked and all are removed from 500 stations with this one so I don't need it any more. A similar tool is used to migrate from platform to platform - after removing everything, it reboots, downloads the agent from the new VSA server, installs it and registers it into the correct machine group.Īll this is done with APIs - no SQL required, so works in SAAS as well as on-prem versions.Darn, the MSI and agent both need to be removed, I wrote this to finish it up, but if anyone has a better way or can assist with a loop to pull both keys in one pass, I'm just tired. We also have a tool that runs when the agent is online to "offboard" an agent - it cleans everything up, removes the agent, deletes all the folder and reg data, then tells VSA to delete the agent. Many of the MSPs that we work with have a minimal number of excess agent licenses, so this is quite helpful. If a customer fires an old system back up, it just checks back in and we start billing again. ![]() Right now, it does some weekly and monthly tasks, including creating local admin accounts with agent-specific randomized passwords on all the workstations, but this week we started work on a feature that finds the agents that haven't checked in within a specific time and deletes them from VSA.įor those who questioned this - this makes the agents available for use on other devices. If the install fails and won’t verify, check to make sure all components. Kaspersky will try to uninstall any other anti-virus software that it finds. The new version of KAV now has an uninstall option Install> Install> Advanced Options Uninstall prior A/V. We leverage that for some externalized scheduled processes. 2) Remove any previously installed (or failed installs) AV products. We have a Windows Service that interfaces between VSA and the PSA to process alerts and decide if they should become tickets or not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |