Ideas
Help us build the next great product for you! Select the product you are using at left to see if anyone has already suggested your idea (feel free to vote and comment!) and then click on Add a new idea to get your creative juices flowing.
If you'd like to help us refine the features we build based on your ideas and get early access to the new stuff, come participate in our Beta programs too: https://beta.vipre.com/welcome/
Help us build the next great product for you! Select the product you are using at left to see if anyone has already suggested your idea (feel free to vote and comment!) and then click on Add a new idea to get your creative juices flowing.
If you'd like to help us refine the features we build based on your ideas and get early access to the new stuff, come participate in our Beta programs too: https://beta.vipre.com/welcome/
This is an interesting one. The way this works today, a module in the agent installer checks for and removes incompatible software; this all happens locally to the endpoint so there's not much info that makes it back to the cloud console. And even if it did, where would this info be stored? It's specific to the individual device...
So options I could see:
We could add something to the agent to record a little local "history" i.e. to record what packages were removed, and a tab or something in the agent to look that history up. And/or we could send events to the WIndows Event Log stating we removed stuff.
We could surface info back to the cloud console and just put it in the audit trail. And/or we could store it in the individual device history somehow.
I should note for the record, the specific version of the "incompatible software" that VIPRE attempted to remove is not yet supported by CART (i.e. not in the list provided within policy). We support an older version, but apparently the vendor has made changes that caused some removal issues. We are working to update the uninstall defs to fix the issue.
Attachments Open full size