1

how many tickets a month can spiceworks on prem process? or is there no limitation ?

6 Spice ups
2

I’ve never come across an official limit. I would say this: the development effort seems to be behind the cloud version. So if you are looking at a big scale deployment, I’d speak to Spiceworks directly as to what their roadmaps are. (I’ve no inside info on this).

It’s free to use however, so see if you can break it :wink:

3

The only limits are your disk IO speed and resources.

4

ok some times we have issues we handling +1000 tickets / month.

there are times spiceworks is hanging and i need to restart the service after that we are good for a few weeks.

5

That is likely down to your setup, if you are scanning as well as using inventory or if you use a shared box or slow disks or lack of resources and so on.

If you only use helpdesk, consider migrating to the cloud where you don’t have to look after it at all.

6

hy , that could be an solution but can we on the cloud setup use our own email ?

and what about the custom attributes can this be transfered or can we restore a backup to the cloud ?

and i guest we cant read out the database , for eg we have an dashboard wit all the open tickets (read out of the database in php).

what about the existing tickets can we migrate them in the cloud version ?

@rod-it

7

  1. Email address - yes, using forwarders, there are guides on here

  2. Attributes - no idea I don’t use the cloud

  3. Migrate - yes, export and import

See here for more information.

Perhaps export/import and use the cloud as purely a lab for now, see if it does what you want before committing.

https://community.spiceworks.com/support/help-desk-cloud-edition/docs/import-tickets

8

wil the cloud version run faster ? the current setup on prem

80 GB SSD
RAM 12GB DDR4
4vcpu

on busy times of the day on prem hangs

9

Yes it will, it’s a different code base.

4 vCPUs and 12GB of ram to Spiceworks is a little pointless, it can’t access that amount of ram and virtual machines work best with less resources anyway, especially CPU, so you could first try dropping that to 1 vCPU or even 2 vCPU and 6GB ram and see how you go