State of Desktop app v8.0<\/a><\/p>","upvoteCount":0,"datePublished":"2019-04-25T15:57:05.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/42","author":{"@type":"Person","name":"jackie","url":"https://community.spiceworks.com/u/jackie"}},{"@type":"Answer","text":"Looks like no fix is going to be done, nor a replacement in the cloud version - but oddly - there have been no other posting from spice users - wonder what theyre using - if anything ?<\/p>\n
Its really annoying - and very disappointing.<\/p>","upvoteCount":1,"datePublished":"2019-04-29T10:57:47.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/43","author":{"@type":"Person","name":"martindraper2289","url":"https://community.spiceworks.com/u/martindraper2289"}},{"@type":"Answer","text":"
It is definitely a bummer. I’ve looked for documentation that would help me understand what specifically changed in 1809 to break event collection, but had no success.<\/p>\n
I have a feeling that it’s either something extremely simple, like a syntax change, or something massively complicated.<\/p>","upvoteCount":0,"datePublished":"2019-04-29T11:28:42.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/44","author":{"@type":"Person","name":"ich-ni-san","url":"https://community.spiceworks.com/u/ich-ni-san"}},{"@type":"Answer","text":"
just wondering really - as this was one of the original features and is built into the dashboard as a default, you’d think this would fit the test of :<\/p>\n
“We may release 7.5 patches if we discover severe issues that prevent normal usage for lots of users”<\/em><\/p>\n\nor perhaps SW can suggest a viable alternative ?<\/li>\n<\/ul>","upvoteCount":0,"datePublished":"2019-04-29T13:12:11.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/45","author":{"@type":"Person","name":"martindraper2289","url":"https://community.spiceworks.com/u/martindraper2289"}},{"@type":"Answer","text":"Has there been any change in the status of this problem?<\/p>","upvoteCount":1,"datePublished":"2019-08-26T14:27:54.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/46","author":{"@type":"Person","name":"geoffpeters2","url":"https://community.spiceworks.com/u/geoffpeters2"}},{"@type":"Answer","text":"
Likewise, I’ve just migrated Spiceworks DB from an 2008R2 to Server 2019 and now cannot see the Events for Any device found, even when viewing Spiceworks on the server.<\/p>\n
Event view was one of the most used daily features in Spiceworks for me.<\/p>\n
Is there something else we can use to see this information for the devices on the network?<\/p>","upvoteCount":1,"datePublished":"2019-11-19T15:20:33.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/47","author":{"@type":"Person","name":"d8805","url":"https://community.spiceworks.com/u/d8805"}},{"@type":"Answer","text":"\n\n
<\/div>\n
D8805:<\/div>\n
\n…Event view was one of the most used daily features in Spiceworks for me…<\/p>\n<\/blockquote>\n<\/aside>\n
Ditto. I’ve tried to set up the subscription/collection in event viewer but after 1 - 2 hours of fooling with it, I gave up.<\/p>","upvoteCount":0,"datePublished":"2019-11-19T19:33:42.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/48","author":{"@type":"Person","name":"ich-ni-san","url":"https://community.spiceworks.com/u/ich-ni-san"}},{"@type":"Answer","text":"
In an attempt to apply the tricks known to date with similar issues on 2019 Server, I went into Firewall and granted Spiceworks.exe permission for Domain use and this made no difference.<\/p>\n
A couple of years ago we were running our ERP agent successfully on Win 10, then in a February update it stopped working. Finally isolated it to their removing a dated security layer. Fast forward a couple of years and we mysteriously discovered it working again after several updates had passed through. To solve our production issue, we had set up VMs with Win2007Pro to run the manufacturing software agent on and gave up trying to make it work on Win10. (and rolled back a lot of Win10 machines to Win7Pro)<\/p>\n
Hopefully, the cause/solution will be something like this. Once identified it may be as easy as a setting change or an update that makes it work again.<\/p>\n
Keeping fingers crossed that someone with the time, knowledge, and inclination to chase this will track it down.<\/p>","upvoteCount":0,"datePublished":"2019-11-19T20:09:12.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/49","author":{"@type":"Person","name":"d8805","url":"https://community.spiceworks.com/u/d8805"}},{"@type":"Answer","text":"\n\n
<\/div>\n
D8805:<\/div>\n
\nHopefully, the cause/solution will be something like this. Once identified it may be as easy as a setting change or an update that makes it work again.<\/p>\n
Keeping fingers crossed that someone with the time, knowledge, and inclination to chase this will track it down.<\/p>\n<\/blockquote>\n<\/aside>\n
Anything is possible and I do think someone with intimate knowledge of the process might be able to solve it easily.<\/p>\n
That said, I’ve spent waaaayyyyy too many hours on this, to the point of comparing sysinternals process monitor logs/Wireshark captures from working and non-working spiceworks servers, and I think it has to do with a fundamental change in Windows RPC/SMB/event log API stuff.<\/p>\n
I don’t think a Windows Update will “fix” it because I think the problem is the result of something that was, and is now, fixed. I think only a workaround or change to spiceworks will get it working again. And it doesn’t appear there is going to be any further work done on the on-premise version.<\/p>","upvoteCount":0,"datePublished":"2019-11-19T20:47:40.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/50","author":{"@type":"Person","name":"ich-ni-san","url":"https://community.spiceworks.com/u/ich-ni-san"}},{"@type":"Answer","text":"
I’ve now uninstalled Spiceworks from the Server 2019 and fired up the 2008R2 server to run it and still be able to review the Event History.<\/p>\n
This isn’t optimal, but, if Spiceworks is all that will be running there maybe it won’t be a significant exposure to security threats once support ends for that OS.<\/p>\n
It would be preferable for there to be a way found around whatever is preventing it working on Win10-based servers. I’m not particularly keen on the cloud version of Spiceworks and may just quit using Spiceworks at all if further development of the on site version is now being phased out.<\/p>","upvoteCount":1,"datePublished":"2019-12-04T19:55:55.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/51","author":{"@type":"Person","name":"d8805","url":"https://community.spiceworks.com/u/d8805"}},{"@type":"Answer","text":"
Wow, for some reason after nearly 12 months without, this has suddenly burst back into life. !!<\/p>\n
Suspect windows updates have been applied to server and clients - all appears to be well.<\/p>","upvoteCount":1,"datePublished":"2020-04-23T12:09:39.000Z","url":"https://community.spiceworks.com/t/environment-charts-event-history-not-updating/694501/52","author":{"@type":"Person","name":"martindraper2289","url":"https://community.spiceworks.com/u/martindraper2289"}},{"@type":"Answer","text":"
