Scan Profile > Collection > Drill Down From Parent
Hello,
I have a top-level collection that limits my "All Computers" to a subset of devices that run 64bit and other distinguishing features I want to limit (subnets,hostnames,etc..). The reason for the limit is due to scans locking up older hardware running 32bit O/S due to some software on these devices.
I have another collection that drills down from the parent collection (such as, devices that have not been rebooted in last 10 days and has an update flag). I then use the subset collection to attach to the scan profile.
My problem is, it appears the scan profile will not honor the "drill down from parent" settings on the secondary collection. Items that were 32bit were included in scans that I did not want inclusion where it should have been limited to 64bit.
When I open the scan history on the device, I can certainly see the scan tried to run.
The devices do get filtered from parent when viewing them on the PDQ Inventory client. IE: I do not see the scanned devices in the GUI and they do filter 32bit when looking at the sub-collection.
Note: Scans may have ran against the devices in the past and failed, but I certainly don't see a "retry scan" option that would have it retry the scan again. I assume that failed scans in past have no bearing on future scans.
Running v15.1.0.0 Enterprise Mode.
Thoughts? Did I miss a help area somewhere? Bug?
Right now, I have made a top-level collection and moved away from using sub-collections for scan profiles. I have yet to fully review if that "fixed" my issue, but I thought I would post here for any pointers.
Comments
When you included the sub-collection, is that the only one you included, or did you also include the parent collection?
I tried to replicate your issue in my lab, but I was unable to.
I created a "Windows 10" collection at the root of the tree, then a "64-bit" collection under that with "Drill down" checked. I pointed my Standard scan profile at that collection and set a Once Trigger for 1 minute in the future. When that trigger fired only my 64-bit Windows 10 computers were scanned.
I only included the sub-collection.
What you described is what I would have anticipated, you have the issue identified correctly.
When I ran the scan as a parent collection, by including the sub-collection filters combined with the parent into a new collection, the scan successfully limits to only the devices in the parent view.
I have yet to toggle the scan back to the sub-collection due to things working as currently configured to see if I can recreate. Unfortunately, the devices are production.
Nothing seems to be extra special about my scan profiles.
Details: Computer Details
Triggers: Scan Age 12 hours, only at 9AM
Collections: Linked to collection described above (a sub-collection)
*********************
Okay, while I was typing this I see some other strange things here.
Not only did the scan profile not honor the parent collection filters, it appears it also did not honor the sub-collection filters. Meaning, it ran the scan on every device, regardless of what collection it was pointing to.
Sub-Collection: http://folnc.us/pdq1
Parent Collection: http://folnc.us/pdq2
Scan History (32bit): http://folnc.us/pdq3
Scan Profile (trigger): http://folnc.us/pdq4
Huh, that's definitely weird. Please contact support@pdq.com and reference this thread.