Best Practices Question
Smart Label to Identify new and reimaged machines
I'm trying to see if I can get some help with a smart label issue that I've run into. Maybe what I'm trying to accomplish won't work or I need to go about it in a different way.
I want to create a smart label that will catch not only new devices (Brand new or brand new to our instance) and also machines that were already on KACE, but needed to be reimaged. I plan on using these labels to deploy software to these devices. As I type this, I've had no issues with getting the "New Devices" to be caught in the label. I just filter on Created in the last day. They show up fine. My issue is with machines that had to be reimaged. I did some searching and found some SQL queries that used OS Installed on criteria so I created that label, but then saw that machines that updated to the new Win 10 2004 release were caught up in the smart label too. It looks like installing that alters the created on date. :( And since we aren't deleting the device in the K1000, I can't use the created date. I want to keep the historical ticket data for these reimaged devices for reporting purposes.
Any help is appreciated, I've been Googling and banging my head on my desk to no avail. LOL
Answer Chosen by the Author
There are a few possibilities:
1. systems which are completely new in the appliance:
easy way: use the wizard and check for CREATED.
2. systems which are newly imaged. If you are using the KACE SDA the easiest way is to use a CIR for collecting the creation date (by checking for the SDA deployment)
FileInfoReturn(C:\ProgramData\Dell\KACE\k2000_deployment_info.conf, CreatedDate, DATE) OR FileInfoReturn(C:\ProgramData\Quest\KACE\k2000_deployment_info.conf, CreatedDate, DATE)
You can also modify it by checking for other files which are created at the time of the deployment if you are using another solution.
Use then the wizard for your Custom Inventory Rule to create a smart label.