When you set up and prepare Spiceworks, it's easier, like, with the enterprise version, when you get a new computer. We just say, "Yeah, put your manuals in." 

Then, when we integrate with Active Directory (AD), and when we finish setting up, we need to decide whether to put it on the VPN because we're not in the Prisma Cloud environment. 

And when we put it on the VPN, the VPN would allow the Help Desk Platform (HDP) to just install the software.

Overall, only a couple of people were required for the deployment. It was an IT team of engineers. 

We handled the implementation ourselves.

In-house. I installed and set up.

When I deployed, the application was very basic. There were no consultants like me available. The community was small and Spiceworks had one person as their support group. The devs and founders would often respond to threads in the community. I didn't need any help. Now, the application has grown so much that I would highly recommend that any IT department with more than 3 people, or more than 2000 nodes to manage, contact someone like me (there's one other guy in Atlanta that does the same thing I do for Spiceworks consulting) before doing your installation. The training James and I can provide is invaluable and we'll make sure your database doesn't get horked up!

I implemented the use of Spiceworks.

In-house. It was a relatively simple installation considering it was done with only two techs over a few days.

I implemented it solely, in-house. I had little issue. Best advice I can give is- test, test, test!

In-house team. Just make sure you dedicate appropriately sized server to accommodate the size of your environment.

In house. I recommend dedicating a VM. Use standard ports, 80 and 443 for the webserver and leverage DNS to configure access to Spiceworks via a “user friendly” hostname.

I personally handled the implementation. Create a special mailbox/mail account specifically for your help desk and let Spiceworks handle the rest. It’s good!

The previous IT Manager handled most of the initial setup, but my advice would be to spin up a virtual machine and take a crack at it first. Stay as vanilla as possible. Try reproducing your current solution, or as close as you can get, starting with the help desk. Then move to inventory, user portal, etc. Then start utilizing features you didn’t have and implementing them. It is a very complex process migrating a help desk, so be sure to take your time and test.

It was all done in-house.

We implemented it in-house. There's no ned to use an outside contractor because the setup is very easy and you learn a great deal by doing it yourself.

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

I implemented it in-house but there are vendors that will do implementation if you want to pay for it. I think that the typical Spiceworks user is going to end up implementing on their own. My advice is to test it. Everything is free so no harm in downloading and installing on a virtual server.

Implementation was done in-house by my team's technical coordinator.

I implemented it in-house.

We implemented it in-house.

I did it myself after reading the FAQs on their website.

We didn't use it in-house.

In-house implementation.

This application was setup by colleagues who work at the company.

We did it in-house.

It was implemented in house.