Spiceworks Room for Improvement

Grey Howe
Spiceworks Consultant at a tech services company with 501-1,000 employees
Recently, they deployed a login process that links to their online community. While I understand that change, I don't agree with it. They've also tried to integrate it with social logins, like Twitter and LinkedIn, and that type of login authentication has no place in a corporate application. Resources spent on this social aspect could have been used to fix the existing login to sync with AD for the IT users (it already syncs to AD for end users) and everyone would have been happier. This would have been especially good since Spiceworks has become more and more predominant for enterprise level IT instead of the SMB market that they started with. Taking that in to consideration, I also believe that their new CEO needs to take the application in a new direction and make it enterprise ready with performance and capabilities that can meet that environment. Right now, if you have >2000 endpoints in Spiceworks, you will probably hate using it just because it's so bogged down. I've done installations for clients that were in excess of 5,000 nodes and it's just dreadful. They may be edge cases for Spiceworks, but I see them becoming more prevalent as time wears on, especially if Spiceworks continues to dominate the IT landscape with their community. View full review »
Aaron Krytus
Network Manager / Senior Network Engineer at Warnock, Tanner & Associates
Reporting for any application is a must. Where the reporting is very useful in SpiceWorks, I would like a more powerful reporting tool to better filter what I want and do not want. There are some built in filters, but a simple if-then ability would be incredibly helpful to narrow down my reports. View full review »
Bernie McCormick
Director of Technology at a K-12 educational company or school with 501-1,000 employees
The SNMP sniffer requires a lot of work to get right. View full review »

Sign Up with Email