![Unbound Crypto-of-Things [EOL] vs. VIPRE Endpoint Security report](https://www.peerspot.com/assets/media/images/icons/pdf-c33db68f.svg){kind=icon}
![Unbound Crypto-of-Things [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_64/mttvnuadhumxlxcs597qp46bmov9.png?_a=BACAGSGT)
![Unbound Crypto-of-Things [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/mttvnuadhumxlxcs597qp46bmov9.png?_a=BACAGSGT){kind=small}
![Unbound Crypto-of-Things [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/mttvnuadhumxlxcs597qp46bmov9.png?_a=BACAGSGT){kind=small}
There just was a lot about it that I didn't like. For blocking certain items, such as USBs, we felt like it was slowing down the network too much. Therefore we utilized a GPO for blocking things like that instead. Our environment was big and I didn't feel like the console did a good enough job. We outgrew the product. I've been asking for a change for a couple of years now, and it finally got approved. In terms of the console, I had over 2000 endpoints in there and there wasn't even a search feature for me to look through them. If I had to find where a policy was I had to sort in alphabetical order to find an endpoint that I wanted. They need to offer a search function within the console - maybe something that shows a "last connected" notice. That way, it's easier to manage obsolete machines that you don't need anymore. They had a very vague setting, like after so many days, when do you want us to remove these, you'd see them. I just wish the console was a little more responsive when I would do commands. The reports could have been better. The product would show a lot of endpoints as not communicating. That was another pain point. We constantly had to run an SQL query to clean up the database as I would know immediately when I was in the console, that it just wasn't being responsive. I could tell I was being given bad data and that we had to clean up the database. As soon as I would clean up that database, it was like a purging of the SQL database and it would become a lot more responsive. The problem was that our environment was too big. We're going through a growth spurt right now. In the end, the solution is small and much better suited for a small business. We would get a lot of false positives and instead of them fixing the false positive, they would just want us to put in an exception, which I didn't care for. The product is based on an older model of signature files. It doesn't use any artificial intelligence or anything. It was slow to refresh the policies and computer scans. The larger we got, the more it became an issue. If a company stayed small, I'm not sure if they would have noticed.
