1

We use Spiceworks inventory in Spiceworks Version 7.5.00107.

It is an install on our internal web server. Install download file was named spiceworks.exe

I “assume” this is the “Spiceworks Desktop” product referred to in the EOL notices, but there in nothing in the application that uses the word “Desktop”. There is no user desktop component being used.

We connect to the webpage of this local Spiceworks server and we log in with user accounts that we created in the local spiceworks application.

In this thread, it is implied that we can continue logging in and using this local server after the EOL. (Admittedly not a good idea)… but technically not an issue.

In this doc, it states “Desktop apps will be unable to authenticate using Spiceworks authentication services (you will be unable to add new Desktop app users, register new installations of the Desktop app, manage/reset user passwords with Spiceworks authentication services)”

Can someone confirm that the above statement about not being able to log in… is not related to the process of going to my local spiceworks server and logging in with the users we have created in our local spiceworks server?

Yes… we will get off this old sever eventually… but want to assure that we can still log into our local spiceworks server after Dec 31. (I don’t see how that log in process has anything to do with the statement above)

Thanks

5 Spice ups
2

For clarification, Spiceworks desktop 7.5 (also known as Spiceworks.exe, Spiceworks inventory, Spiceworks helpdesk), the Windows based installer has been out of support for a number of years.

Ideally it should have been on it’s own server, and not alongside other websites, since it uses it’s own Apache for web traffic.

Pre-created users will still be able to login (for now), but may at some point in the not too distant future, also stop. You wont be able to invite new staff, reset passwords* or use the SW services for anything outside of what remains functioning, locally.

As far as not seeing how this relates to you, ALL admin and tech accounts are based on community logins, the same email address will log you in here as it will to the desktop - the desktop/community binding is being disabled, your continued usage of the legacy product will be unknown, but will likely still work, like cached credentials do.

If you still have emails flowing between your users and your Spiceworks install - you are either lucky, or also using a legacy email system that still retains support for BASIC authentication, which is not secure or encrypted.

I hope this helps clarify.

1 Spice up
3

Thanks for the info. I believe you answered my question.

In our case there are no emails, the server is a standalone local server, and it is just the inventory component being used (no network scanning).

So that leaves us with the user account logins… I always assumed that the authentication was just to the local server only, but you make a good point about those accounts actually being community accounts.

For now we’ll have to play the wait and see if the accounts can still authenticate post 12/31 unless we get more comments here.

Thanks

1 Spice up
4

All official comments are in your second link, however, if you are not scanning or using email, and only use this as a manual input for inventory, may I suggest SnipeIT as an alternative. If you’re not familiar/handy with Linux, there are turnkey, pre-build setups out there.

FYI, while it may have been a minute, when you setup a new tech/admin, they are sent an invite link - this comes via the community, hence their ID is linked.

FYI 2, as a precaution, you may wan to export your inventory as a report, so you have it “in-case, you can’t get in”

If and/or when you are satisfied your post has been answered, please mark a best answer to show so.

1 Spice up
5

Thanks again… your further comments help also.

Appreciate the SnipeIt recommendation… at quick glace it does look like a good inventory alternative