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

Before Spiceworks, we used the CMDP and integrated it with RTS. In my case, I loved using KACE. It integrates with VMware and Dell.

There are many differences between KACE and Spiceworks. In Spiceworks, when I need to create a document, I need to open one part, download it, and then have one document with just computer names, another with only clusters, and another with all information. Then I need to combine and manage these three documents, which is cumbersome. 

In KACE, it's easier. I just click a button and specify what I need, like names, software, users, etc. KACE creates this document automatically.

Another point, KACE integrates with VMware. If I have an internal case like "Install seven ZIP and configure it," I can open the software section, click on Seven ZIP, enter the computer name, and remotely deploy the Seven ZIP file.

One aspect involves scenarios where I use the Image Deployment feature. Typically, in Windows, we use a USB drive, or previously, a CD. However, with KACE, it's different. We connect the computer via an RJ-45 cable, and during bootup, it initiates a PXE boot—I'm not entirely sure about the exact process.

The computer then locates the cybersecurity server and prompts, "Which Windows image would you like?" After selecting the image, within an hour, I have a computer fully equipped with all the necessary software, perfectly integrated with Active Directory.

I have a lot of good things with KACE that I don't have with Spiceworks.

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

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.

Previously, we used Manage Engine. It was a bit slow, and a little bit old, which is why we switched.

I've used and evaluated others - Spiceworks is the best bang for the buck.

I've used SCCM and it sucks. A lot. It took three months to configure/setup, and it didn't provide a good helpdesk solution. SCCM also doesn't manage non-Microsoft endpoints, so switches and routers were not tracked, and it was impossible to get a feel for how big the environment really was. The worst part was deploying an agent from SCCM to all MS endpoints; Spiceworks is agentless.

I have used Commit CRM for 3 years, that solution isn't free and has a nice customer service, a PC program and a web interface. As I wrote earlier that solution costs and my employer didn't want to pay.

My employer used an IT Company for the solution, with me introducing them to Spiceworks we saved over £700 per month meaning we could start to develop the IT infrastructure.

We tried a few help desk solutions, but really appreciated the amount of effort put into Spiceworks for a free solution with occasional ads. If anything, I would say they attempt to do too much with their product.

We did not previously use a ticketing or network monitoring system. I opted for Spiceworks since the non-pro version is free, I briefly used it at a past job, and the network discovery tool is provided.

Spiceworks was the best product per our testing, and was recommended by other IT professionals at the time. We evaluated many low cost or free solutions, and none came close to Spiceworks abilities and ease of use. Price was also a big factor during times when management was not looking to spend capital, but still demanded consistent process, asset tracking, and reporting improvements.

No other options were evaluated as it is one of the only 100% free solutions.

I evaluated Microsoft Service Manager and ZenDesk, but I settled on Spiceworks. The capabilities, ease of use and price point (free) made Spiceworks the obvious choice for us.

I have used several ticketing systems in my career, including CA.

Eventually we ended up going with BMC Track-It!, as some colleagues had experience with the product and we were looking for something with change management and ITILv3 compliance built in.

I still believe Spiceworks is a great help desk for a Level 1, 2 and even 3 IT department. (See Gartners “Maturity Levels of an Information Technology department.)

It costs nothing, but I see Spiceworks as a gateway tool. Learn the ropes of service & operation management in a free tool, then switch to a more advanced tool afterwards if necessary.

Before Spiceworks we used SysAid which was quite good also, but not worth the extra money compared to Spiceworks.

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

Before and even after implementing Spiceworks we've been working with HP Service Manager. Although a classic in incident management software, it was sort of avoided by users (clients) because they considered it to be way harder and slower to use than emails. Once we implemented Spiceworks to collect user incident mails, HP Service Manager started to be avoided even more from our internal clients.

The IT department I worked as part of, implemented the software on their own.

I used PRTG Network Monitor, and the reason I chose Spiceworks was because of the simplicity, the budget that I had available which is zero.

We have move to “I support” for our help desk solution, mainly due to the lack of change control and automated approval’s.

I don't know the reason for change. We try now to convince our management to get a real pro product. Many arguments are available.

I didn't pick it, it was done by senior IT management.

This was a solution I implemented to improve customer relations and to meet SLA’s. Previously, this was done via email.

No previous solution was used.

This was the first product we used.