Inventory collections not updating after 19.3.9.0 update
Matt Ford
Ever since installing the 19.3.9.0 update, all of our dynamic collections stopped updating unless we stop/start the pdq inventory service. There will be a mismatch between number of computers reported to be in a collection vs the list of computers actually in the collection, or deleting a computer from the collection doesn't actually remove it (still shows in the collection). Basically they just don't update anymore.
1
Comments
I recommend reaching out to support@pdq.com
Same issue here on 19.3.9.0
After working with support for the last 2 weeks, what I noticed was that the issue was only visible on remote clients. When I ran the PDQ products from the central server, collections showed the correct data. What has so far fixed it for me was building a new PDQ central server (not sure if this was required, it's just something I did). I then imported all of my collections/packages/scan profiles/reports/variables/settings/etc and re-imported them into the new central server. I then did a complete uninstall and fresh install of the remote clients and all has been well for 2 days so far.
Matt Ford, did your solution hold up for you? We're having similar issues.
Chris Durward actually no. A later product version alleviated the issue quite a bit but never fully disappeared. I reduced the number of collections we had and a lot of sub collections that were like:
"Outdated Whatever Product"
-> Currently Online
removing a lot of "this collection depends on the membership of this other collection" helped a huge amount. It still happens once in a while but it's really rare. Hitting F5 while in Inventory forces a full refresh from the database and sync's the collections again. Turns out, the backend was being updated with all the correct information, it was the end client not updating with the newest data.
Thanks for the info. I'm surprised that removing the "this collection depends on the membership of this other collection" options helped as I would've thought that would cut down on the amount of queries the software is doing. Were you just unchecking that box or were you deleting the collections that were nested below?
I was deleting the collections and just moving the "online" flag requirement to the collection above it.
So, instead of "Outdated Whatever Product" -> "Currently Online"
it is now "Outdated Whatever Product (online)"