Spiceworks Reviews

If our customers need backup support, we can work with them and provide it. Whatever solution the customer requires, we will ensure it is provided.

The software is cloud-based, so I do not need to store any data locally. It is a fully software-based solution, eliminating the need for investment in hardware. We have the capability to create reports as needed. It is good software to use, as there were no incidents where I needed to contact technical support. Additionally, it is free software.

I am unable to provide suggestions for improvement at this moment, however, I can provide feedback later. 

Currently, there do not seem to be any issues.

I have used the solution for one year.

I would rate its stability at nine out of ten. It is a stable product.

The customer service is okay, however, I would appreciate much more clarity on what I want to know exactly.

It performs its intended functions. We may use it, but perhaps not for ourselves, but for our customers, potentially with Channel Partners. Whenever we are posting any query or reply on a ticket, it should verify that information with the knowledge base. 

I would rate the overall solution eight out of ten.

I use the solution to manage inventory. It helps us create and assign tickets.

I have used many software, but Spiceworks is the best. The tool provides multiple features. It is a valuable product for inventory. It is also useful as a ticketing system. The solution is easy to use and easy to manage. Many people can use it very easily. The features are not complicated. It is very easy to run, install, and understand. That is why my organization decided to use it.

The solution’s asset management capabilities have benefitted us in many ways. We are able to manage all the inventory. We have a complete database. We have a record of everything. It is very valuable. I rate the usability of the user interface and dashboard a nine out of ten. The tool is easy to learn compared to other software.

The GUI must be improved. The GUI looks old-fashioned. The vendor must do some web development for it.

I have been using the solution for almost three years.

I have never faced any downtime. When we increased the inventory, the tool became very slow. So, we increased the RAM, and it was automatically fixed.

We have ten IT personnel to create tickets and manage inventory using Spiceworks.

We used Zendesk before. We switched to Spiceworks because Zendesk was very complicated.

The initial setup is easy.

The tool is cheap.

We resolve the issues ourselves. We do not contact the support team. We also have a system administrator. We can manage everything. I will recommend people to use the product. It's very easy to understand. It's a basic ticketing software. We can buy it if we want to learn more about ticketing systems. It has multiple features. We can design it the way we want. We can customize it the way we want. Overall, I rate the solution an eight out of ten.

I have been using Spiceworks as a ticketing system for logging incidents, service requests, and other service desk-related functionality ever since I joined my company about a year and a half ago.

We're currently using a pretty old version of Spiceworks which is about three or four years old now and, although it is hosted in the United States with our USA team (which includes our infrastructure manager and IT security director), I believe it is based on-premises. When I joined the company here in Pakistan, it was already in place, and I just had to come in and start using it to support my team as a service desk manager.

In our engineering department, Spiceworks is being used globally as a remote service desk system by people who are not only in the United States and Pakistan, but also in India. In my team, there are six engineers working on it at present, in addition to the L2 team which includes two system administrators, a Linux administrator, and others, which comes out to a total of about 10 or 12 Spiceworks users in our company.

If you're in the market for a low-cost service desk system, Spiceworks is a good software solution to start out with, especially when it comes to startups and those organizations that don't currently have any existing service desk software in place.

One of the biggest ways in which Spiceworks could improve is by developing better and more automated workflows. For example, in another solution called ServiceDesk by ManageEngine, you can have levels of approval in the event that there is a request for new software, or when someone requests a VPN or WiFi connection. This kind of multi-stage approval feature provided by ServiceDesk does not appear to exist in Spiceworks, and it is one of their main shortcomings for me. There are also several other automation features in ServiceDesk that are not present in Spiceworks.

Another feature that I have always wanted in Spiceworks is categorization. Let's suppose that I select a certain piece of software within Spiceworks, and I want to see the subcategories, Spiceworks should be able to auto-populate those subcategories. This is unfortunately not possible within Spiceworks at the moment.

I have been using Spiceworks for one and a half years now. 

Despite lacking some advanced features, I can confirm that Spiceworks is a stable solution.

The older version of Spiceworks that we are using caters towards startups and medium size organizations, but here in Pakistan even some banks might see benefit in using it, especially those who are still using older solutions anyway. The newer versions of Spiceworks with extra scalability and workflow features may be even more interesting to these companies, but many of them have not been introduced to the solution yet.

Seeing that it is a low-cost solution, I would advise you to go ahead with Spiceworks and experiment with it to see if you can get things working properly, especially if you currently don't have any existing service desk software in place.

Spiceworks is a particularly good software solution to kick off with when you're a startup. When experimenting with it, your people can get exposure to the context and you can easily customize it. When I joined my organization, I did a lot of customization with the fields and everything at first in order to properly streamline the processes. It really helps to start with building up your processes first and foremost.

Once your organization gains awareness of the service desk processes, they can then either look out for better software or stick with Spiceworks.

One alternative that we are now moving towards implementing is ManageEngine ServiceDesk, mainly because it provides better, more automated workflows.

Although we are still using Spiceworks, we are hoping to be able to phase it out by the end of this year in favor of ServiceDesk.

Although Spiceworks is a good service desk solution for startups and the like, I believe it is lagging behind other solutions such as ServiceDesk in that it lacks multi-stage approval and categorization, plus a number of other features that I would like to see in such a solution. If Spiceworks manages to integrate the kinds of features you see in ServiceDesk Plus, for example, then I think it would make for a very good service desk system.

I would rate Spiceworks a six out of ten.

We use Spiceworks to monitor routers, switches, access points, and IP addresses.

Spiceworks' dashboard allows you to drill down to the notes, where I can take an inventory of the network and see the devices I need to monitor.

I would like to see more information when drilling down into access permissions, assignments management, or tagging. When I click a note or a device, I should be able to see more details about the router and modem. For example, I want to see the version, downtime, availability, latency, etc. I should have easy access to everything about our assets at a glance. 

The feature currently works like this: You click a note, and it gives you information about the device, including the model, interface, resource usage, etc. Having all those things at a glance for each of those devices would make the reporting more robust and user-friendly.

I used Spiceworks for around three years.

Spiceworks is stable, but I think more work needs to be done to make it more stable and globally accepted so it can compete with solutions like SolarWinds.

Spiceworks is scalable.

I rate Spiceworks support 10 out of 10. Their support staff is knowledgeable and responsive.

I rate Spiceworks eight out of 10 for ease of setup. I found the setup to be straightforward, but it depends on who is doing the deployment. It requires minimal maintenance around twice a year. 

Spiceworks is an open-source product, but I think they should offer some useful premium features that people can pay for. 

I rate Spiceworks seven out of 10. Comparing Spiceworks to other products, I would say most people see it as a tool for small businesses, but they would go with one of the bigger names for a large enterprise network. Other commercial products are more user-friendly and have more features.

If more companies started adopting Spiceworks globally, maybe that would change, but people still see it as a tool for small and medium-sized businesses.

This solution is primarily used as a ticketing system. For example, it can be used in finance and other areas. 

I used it in my home lab, just to do some tests.

I'm linking it to IT issues in the office. If there are problems, for example, the printer is not working, people write a message to me, create a new ticket, then send the ticket to me. I try to solve the problem. 

It's easy to understand. The documentation is also very helpful in figuring out the product. 

It's simple to use. 

The solution offers very useful integrations. 

It is stable and reliable. 

There's a bit of a learning curve. the first time you interact with it, you may find it difficult. For example, it's hard to manage a switch from a page. 

Sometimes, it can be difficult to integrate what you need. 

The initial setup can be difficult. 

I've been using the solution for one month.

It's quite stable and reliable. There are no bugs or glitches. 

Only three people are using the solution right now. I use it in my home. 

You can scale the solution. It wouldn't be an issue. 

Technical support has been good. We have been satisfied with their level of assistance. 

I've also used Jira. Spiceworks, however, has different tools I can use. 

The implementation process can be difficult, however, once it is up and running, it's pretty easy to get going. 

I can deploy the product in about two hours. It doesn't take too long. 

There isn't really any maintenance needed. It's pretty simple once it's up nd running. You don't have to have a lot of people watching it. 

The pricing of the product depends on the company and how big it is. In a big company, it is hard to deploy something like this. There are a lot of servers and there is a lot of communication needed. In a big company with maybe 1,000 people, you would pay a high price. It might be about $300 annually for a bigger company. If you pay annually, it's better and cheaper. 

I'm an end-user.

I haven't focused on the version. I'm not sure which version I'm using. 

I'd recommend this solution as it makes life easy. I'd rate it seven out of ten. 

We use Spiceworks for IT ticketing. The main users are me and my staff, which includes two other people. We serve about 60 or 70 other people who submit tickets via email. They don't use Spiceworks to monitor how many tickets they have open. For the most part, they don't go to that page. They just send in their tickets and wait for us to respond. Since we're a smaller company, then the response time typically isn't too long.

Using Spiceworks, I was able to set up notifications. So, if the drives were getting full or something like that, it was helpful. Ticketing works really well. We've set up an email address where employees can send their requests. It creates a ticket automatically and sends it to me and my staff. We can then go see what the problem is and resolve it.

And we have some rules set up in there. If one of those rules is triggered, then it automatically sends an email. It tells us we need to look at that email. so that we can determine whether or not it's safe to go ahead and let through things like that are very helpful in keeping us able to serve our users.

When I first started using Spiceworks, it really increased visibility. I have some other stuff that I'm using now for that kind of visibility, but at that time I went with Spiceworks because it was free. I set it up and used it for visibility in the network, then we set up the ticketing stuff several years ago as well. That works well for us.

It lets us know whether devices are getting out of date and tracked warranties. Spiceworks also gave me visibility in terms of what software was installed on each device and its status. I could see where it was on the network as well as the versions of operating systems and stuff like that.

In terms of visibility features, there was one thing I didn't like about Spiceworks. Once a device was recognized on the network, Spiceworks never got rid of it even after you took it off the network. You had to go in and manually remove it. That's the case on the version that I'm running anyway. If a computer gets connected to the network and then you replace it with something else, it still hangs out in there. This makes it difficult when you're looking for stuff or wanting to check on something. You've got all these old stuff out there that you have to filter through, and I just don't have the time to manually maintain that.

I've used Spiceworks for seven or eight years.

It's stable. It's well developed and the maintenance is pretty simple aside from having to go in and take out old devices. But you don't really have to mess with it to keep it running. Every once in a while something will glitch up. I just have to restart it and it works fine. This only happens maybe once every six months. 

Usually, if I have to restart it, it's because the server that's hosting it has shut down and it didn't restart correctly or something like that. The servers reboot periodically, so sometimes it doesn't come back up cleanly or whatever and I restart it. But for the most part, it's pretty maintenance-free when it comes to glitches and stuff.

We have 14 virtual servers and a workstation with around 80 to 100 laptops, so the scalability is good for a small business. I don't know how well it would work in a large corporate environment, but we're a relatively small business, so it works well for us.

I don't remember ever having to contact Spiceworks technical support.

Setup is pretty easy. You just install it and connect it to your network. It goes off and did its thing. I did it myself in one afternoon. It's pretty simple to maintain. We don't have somebody who administers it. I and another person pretty much keep an eye on it. 

The free version of Spiceworks that I'm using is a good solution if you don't have any other options for visibility into your network. I haven't looked at a paid version. I didn't actually know there was one. 

My biggest advice to people thinking about using Spiceworks would be to stay on top of managing their devices. The version that I'm running doesn't clean that up for you. The visibility solution that we use now removes a device from the list if it doesn't check in within a specified period of time, so it doesn't have a lot of deadhead stuff out there. It tries to maintain an accurate current list rather than just allowing everything to stay there forever until you manually remove it. I don't know if a newer version takes care of that or not. Or if there's the setting that I could have set up to take care of that,

I would rate Spiceworks seven out of 10.

My primary use is for documentation and monitoring the vital services.

My biggest need for using a network monitoring system was to track activity and find out what I've actually got out in the universe. When I came here, I had absolutely no documentation on this network whatsoever, and that's an 875 node network.

I have found a couple of features to be valuable. One, it shows the users that are currently logged in, which is not something that Active Directory by default will ever let you know upfront. It's something you have to craft a script for and it's kind of a pain to have to do it every time. If I just want to quickly look and see who's logged on to their machine Spiceworks will tell me that. That's a very accurate and easy way to find software inventory of every machine that's out there. I do have a Microsoft Configuration Manager Server here and that will work okay. But Spiceworks definitely gives a much broader overview. The SCCN machine on the South Room Inventory and Compliance might tell me some of the other software that's on. For example, I've already caught several world-class operators here in our work environment putting the software on their machines that should not have and it was documented and they were disciplined because of it. I would say policy enforcement is definitely one of the bigger features overall that this solution gives.

The network mapping could be improved. Putting together an actual, bonafide network map would be really nice. I've been messing around with their Google Map snap-in that they've got and that's great if I've got a massively corporate Enterprise Scale Network with branch locations in 50 different cities around the U.S., but I don't. I have an 875 square-mile Indian reservation that I have to keep an eye on. And the mapping that they've got there doesn't even come close to being usable to me. 

So if they could implement a little bit better GIS-based mapping, I could take a Google Earth image and zoom right down here on my 875 square miles. And I could show the links, I could show the nodes, I could show the switches, routers, et cetera. And everything else in between. But I don't have any tool that is capable of mapping the way that I need to map this network.

It doesn't have some of the integrations I'd like to see, some of the ticket generation alerts, things of that nature. It does alerts, but it tells us when stuff is down and when it comes back.

I would also say that a faster network search engine would be good. When it does device discovery, that really takes a long time. It took me two weeks to get everything that I imagine is in the network onto that. Because, like I said, I have no documentation into this network and what I've been able to find is I've got 1,375 DHCP leases out there. Half of those are desktop phones, another 200 or so are probably cellular phones or WiFi devices that connect up. And then I have about 575 actual devices out on the network and those are things that Spiceworks has all been able to tell me. But the time it took to do that discovery was quite lengthy. 

I have been using Spiceworks for about a year and a half.

Overall, the stability is fairly decent. It's pretty good. I've got some reservations about how any resource you click on goes out to the Cloud. I could also do with the UI advertising being a little less. I've inadvertently clicked on several of the ads thinking it was going to show me some value-added feature within Spiceworks and I get bounced off to some other place, but that's not what I want. And I am a bit emotionally triggered and pissed off because of it because it's wasting my time and it's not what I want.

As the Interim Director of Information Technology, I am the only one using it.

I've got an IT Department of 10 technicians and I've had a couple of folks look at it, but I think I'm probably its biggest user.

I've never used support.

The initial setup was a bit time consuming, but it was fairly straightforward. It was about 90 minutes to run through the setup on just that product alone. That's not including the time it took to stand up the server, load the OS, get the drivers and updates and all that done. It took 90 minutes to load just Spiceworks.

It's a pretty good product. I like it. It's given me some fairly valuable information that I've needed on a couple of occasions that no other product would present to me.

On a scale of one to ten, I'd probably give it a seven, based on the fact that it does give me some information that nothing else has. But the pain points like the length of duration for the discovery, the GIS mapping, the ability to map is kind of lackluster takes the three points away.

We're using Spiceworks mainly for infrastructure monitoring.

Spiceworks is generic and free.

Since Spiceworks is a free tool, it's not very scriptable or customizable. 

I've used Spiceworks for two years.

Spiceworks is stable for our purposes.

Spiceworks' scalability is fine. Our usage has been moderate and we have five admins managing the solution.

I haven't contacted Spiceworks tech support. But support isn't readily available. They probably send you to a third party, so we really haven't pursued support for it. Spiceworks could add paid support as a service.

I would rate Spiceworks four out of 10. Just because it's free and out of the box, and you get what you pay for, and you didn't pay for it. So, not getting much. All right. Know what you're getting because it's free.

Spiceworks is for the IT guy that wants to monitor systems that he doesn't have a managed service partner behind him. And that's where Spiceworks has a really good place.

The nice thing about Spiceworks is always it's free. Monitoring of printers for low toner. Finding machines that have low memory or low hard disk space. This is a nice thing to have. I think it's getting better at discovering network equipment.

There are a lot of disadvantages to Spiceworks because it's not an agent-based solution. So you don't get near the quality of discovery versus something that's got an agent on it. It's not really multi-tenant, in the sense that you couldn't use Spiceworks to manage multiple clients from the same console. I think if they had a paid subscription for the support it would be nice. I'd rather pay so much per asset per month to be able to pick up the phone and call them.

I have been using Spiceworks for ten years. I know it very intimately.

I think we did have some trouble, but it was not really the fault of Spiceworks. It was more the way that we reconfigured our firewalls and ports, so it couldn't discover the many things. And with all this stuff going on with ransomware and stuff like that, it's going to be challenging for all of those companies to be able to browse a network, including your network equipment, but not allowing any ports open. It's kind of difficult.

It is pretty easy to expand so it is very scalable.

That's another downside with Spiceworks. You can't really call Spiceworks. You can go to the community and you can ask questions, but you can't pick up the phone and call a number. I'd rather pay so much per asset per month to be able to pick up the phone and call them.

I looked at about 10 different systems, Lansweeper being one. SysAid, Samanage.

Very easy to setup, download the install file, it determines the IP range and away you go.

No, the last install I did of Spiceworks, which was for a customer, they're running it no problem. It's self-sufficient.

The cost could be recouped within a few months. I resolved a very critical issue a client was facing after doing a major "non-roll-back" upgrade, comparing working system vs non working systems we were able to determine the a IE patch was causing the issue and through to tool were pushed out the new update and resolved the problem within a few hours. Without SpiceWorks all 300 systems would have had to be touched. 

I have used a product called SAManage and implemented it at a number of clients and it worked really well.

So Spiceworks would have an even more market share if they had a paid subscription model because you could turn off all the advertising that pops up all the time. But I think in general, I would give it a seven on a scale of ten compared to some of the other mid-tier stuff.

I primarily use this solution for the Spiceworks Inventory system, as well as for helpdesk-related stuff. I have used it to find information to fix various issues.

The most valuable features are the inventory and personalization.

Having an integrated asset management tool, where I can plug in things that are offline, would be good. If I have taken a device off of the network then it would be nice to have it included in the same system, and not somewhere separately. That is the only thing that I have to look for outside of this solution.

I have been using Spiceworks for about four years.

I have not had any issues with stability.

This solution does not seem to have any trouble scaling up, or down. I am the only person who is currently using Spiceworks in the company.

I am very satisfied with the community support. I find most of my solutions there.

Prior to using Spiceworks, I used a local tool. I switched because it has the ability to scan the network and find devices. I just have to punch in the credentials for the different devices and it will go off and do all of the scans for you. It will also provide all of the information about purchase dates and warranties.

The initial setup is straightforward. It is nice and easy to follow.

Spiceworks is a system that I recommend for both inventory and helpdesk, although it is good in its entirety. Other than support for integrated asset management, I cannot think of additional features that I would require.

I would rate this solution a nine out of ten.