9/7/2023 0 Comments Force uninstall webrootIf you DM me your key, i can investigate. If you have something different, then it’s not a business console and could be a consumer console. (that article displays a site and the UI is the same for business (single site) MSP (multiple sites). Business or MSP with multiple business sites. There are only two types of administrative consoles. After that they end and if the agent didn’t check in within 30 days of initiating these commands, they will stay installed and possibly active. NOTE:The uninstall commands live for 30 days in that server farm. 1-Tells your console that it’s no longer a device to manage which means it’s no longer considered an active license and 2-sends the uninstall command to the respective agent/endpoint. If WR is still on the endpoint and not responding to our backend systems, could be a firewall blocking the URL they need to function or something else blocking it’s communication.ĭeactivate actually does two things. Remote access to those devices will determine its local status. > Not seen in XX days, means the agent is no longer operational and/or not installed, possibly. However, i’ve not tested this in some time. > Expired agents usually switch into unmanaged mode making them stand alone and you should be able to uninstall directly on the endpoint without console interaction. Give these a try and let us know how it agents and agents not seen in over 100 days may need to be handled different. (del C:\ProgramData\WRData\dst*.db) After these are gone, rerun the uninstall agent command from the web console, refresh config on devices remotely (or manually run a scan) and see what happens. Can run a batch command or command line as well. Locate the c:\programdata\wrdata\ folder and delete any file that has dst*.db (Basically, any file that starts with DST.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |