1

Need to talk to someone about the new Cloud Services and the big change with Spiceworks. Is there a number to call?

6 Spice ups
2

If you have questions, we’re more than happy to help with answers here!

2 Spice ups
3

Is there a cost to move to Spiceworks cloud or do we just move everything based on your instructions that is posted and what we have moves over? Or if we decide to go in a different directions, we can still maintain our database and history of our our tickets?

We have the On Prem and what will happen after December 2021?

4

There is still no cost to move to the cloud offering. You should also be able to get whatever help you need from the forums from the many that have gone this route before you!

The On Prem version will continue to work, although it’s not being developed anymore and it’s highly doubtful there will be any updates to it, so for your safety it might be prudent to go to the cloud help desk.

5

I’ll just echo what Robert said; all of our IT Tools are free. There is a bit more on that here (as to how and why it’s free):

I’d also recommend checking out this topic as it has some more of the information you may be looking for (in regards to legacy Desktop, CHD, and our other tools and apps):

That said, if you have any questions or need assistance with anything, don’t hesitate to reply or reach out!

2 Spice ups
6

There is nothing stopping you from keeping your on-premises version of Spiceworks and using it forever. What you lose is ongoing support and security updates. It will become best-effort support from the Spiceworks support team and community. Additionally, there had been recent announcements from Microsoft and Google to support only certain secured email connections which Spiceworks programming does not support. There is the distinct possibility that Spiceworks Desktop will not be able to poll for or send email when those requirements take effect. There will be no guarantee that Spiceworks Desktop will work in Windows 11.

You can still port your tickets over to the Spiceworks Cloud Help Desk for historical purposes, even if you decide to move on. Note that there is an inactivity period that will cause Spiceworks CHD to not accept mail for that organization. In your case, that shouldn’t really affect you.

2 Spice ups
7

The only cost involved is your working time and your data. Spiceworks cloud plans don’t cost you subscription money and Spiceworks is committed to keep it so. But I don’t know if your time is free too. So the costs of using Spiceworks cloud edition is your working time costs and you don’t need to pay money to Spiceworks.

No. When you read the instructions, you’ll learn what will be copied to the cloud edition and which parts remain ignored. There exist size and volume restrictions as documented in the instructions. And it is not a move. It is a copy. Your data in your legacy edition will not be deleted because you follow the instructions to import these into your cloud edition.

It sounds to me careless to assume to be able to run the legacy edition permanently. I would expect its feature set to decrease more and more. It is better to prepare for EOL by exporting all your data and create backups. For exporting, you might want to use different export formats in parallel as different formats come with different documented limitations. So I would expect that you may loose the capability to keep history of your tickets indefinitely. I only don’t know how quick or slow such a moment will arrive. Being prepared and having alternatives for accessing your historical data sounds to me more careful. If you move into a different direction, this exported Spiceworks data may be helpful to be imported in your new solution and may need some pre-processing to become compatible with your new solution.

The 2nd link provided by Sean is the EOL announcement. The topic includes much more information and will give you an idea of which issues to expect when corresponding Spiceworks backend services will be shut down. It also includes mentions of which Spiceheads are considering which 3rd party alternatives, some including their motivation or constraints. This includes 3rd party solutions able to import data of the exported legacy edition of Spiceworks.

8

Except for the EOL discussion of on-prem, this thread looks like it fell out of 2016.

9

Thank you for all the responses, However, how secure is Spiceworks in the Cloud? What if a ticket has PII or proprietary information in the ticket? When we logged into this, one User received a warning saying “this website is not secure”. We stopped at moving anything to the cloud-based on this issue. Please, let us know before moving forward.

Thank you

10

Please review https://community.spiceworks.com/support/security-center/security-details for your security-related questions.

As far as the “This website is not secure” message, without knowing the failure reason (like did you use a CNAME DNS record to redirect your https://helpdesk.mycompany.com to https://mycompany.on.spiceworks.com thereby mismatching the security certificate), then we may not be able to comment. Could you provide the error? Redact the URLs and other PII of course.

1 Spice up
11

I’m a bit biased so when I say it’s very secure, I know my being employed here does tend to be called out. That said, there are two sections in our Security Center you might be interested in:

https://community.spiceworks.com/support/security-center/security-details

https://community.spiceworks.com/support/security-center/data-collection#cloud-help-desk

There is also some info in our FAQ you might find helpful:

https://community.spiceworks.com/support/help-desk-cloud-edition/docs#faq

As for being reported as unsafe, any chance it is this issue, or were they experiencing something different?

1 Spice up