Discussion Forums/PDQ Inventory/Inventory - Questions
Answered
Customized Scan Profiles
KC Picha
asked this on November 07, 2011 09:08
Just switched from Admin Arsenal to PDQ Inventory Pro. I'm having a harder time getting getting all my systems scanned with PDQ Inv Pro than I did with Admin Arsenal. After 2 weeks, I still have just 2/3 of my systems scanned. Took less than a week to do this with Admin Arsenal.
Two things might help me. How does one setup a customized scan profile to scan systems on a regular basis?. Also is there a way to identify a collection and manually re-scan just systems that PDQ Inv Pro hasn't been able to scan for some reason?
Thanks
Comments
Are there computers that are returning errors when you attempt to scan them? How many systems are you attempting to load into your inventory?
To set up a customized scan profile, go to Preferences. When you create your new Scan Profile, you specify the schedule that you want that profile to use. In the example below you see that I have created a Scan Profile to scan only Applications and Hot Fixes. In the second window I have the Schedule tab enabled and I have the scan to not be older than 3 days on any target. That means that once that schedule hasn't been run for 3 days on a target the scan will automatically initiate.
You can also see an example of creating a customized Scan Profile by visiting the Admin Arsenal channel on youtube.
To create a collection which contains targets that have never been successfully scanned: Create a new dynamic collection (CTRL+N) and select Computer filter. Then select Never Scanned with a value of Is True. This Collection will have all computers that effectively have no inventory.
Thanks, S
Thanks, Shane. I found the Scan Profiles schedule. RIght in front of my face, don't know how I missed that one.... I have 1193 systems and so far have successfully scanned for OS and applications on 850 of them. They are scattered across the country, so I expect it to take a while. Yes, I do get a variety of error messages, and try to re-scan those. Now that I have the Never Scanned collection this should help me narrow down iteratively.