Smart Label to Identify new and reimaged machines
Hi Everyone!
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
Answers (2)
Top Answer
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.
Comments:
-
Thanks Nico! I knew I forgot a tidbit of info. As of right now we aren't using the SDA to deploy new images because we are sharing our instance across different business units with central IT being the admins. They don't want to get into creating various scripted installs for each org, so they just said forget it all together.
My plan, until we can at least get them to agree on a base simple image, is to install a fresh copy of Windows 10 from iso, install the agent, and use the smart labels to push the required software. So maybe I can just use the CIR on another file that Windows 10 creates and do the same thing! So it looks like I'll just have to create 2 labels. That's not the end of the world! :) - mytmouse 3 years ago-
this is right. - Nico_K 3 years ago
-
Sorry to hijack the thread here, just have a quick question.
I am looking to do the same thing, currently using OS installed date with a smart label, but it looks that will be an issue once feature upgrades happen.
Can I use the "Deployment Time:" field under the "SDA Deployment Information" category for a smart label, and not need a CIR? Or is there an issue with the data format? - ajones88 3 years ago-
You can do this also directly.
But a CIR is an easier way because it contains some possibilities to use it more than only for this single use.
I personally have a report for systems to provide it to non tech people so they like to read it differently than a tech - Nico_K 3 years ago-
Awesome, thanks Nico! - ajones88 3 years ago
-
Hey Nico! Sorry to bring back up an old thread. But we finally got our new SDA deployment setup. But when I check the directory C:\ProgramData\Quest\KACE\ I don't see the file k2000_deployment_info.conf Does something on the SDA need to be enabled to have it drop this file?
I also checked on the SMA under inventory information and the SDA Deployment Information section says "No Data Available" is that collection deprecated?
Thanks! - mytmouse 3 years ago
I have 2 CIRs that I use. The first one shows the last install date for Windows, and returns a date field, which can be used in a Smart label. e.g.
| 11/18/2019 08:15:10 [date] |
ShellCommandDateReturn(%windir%\SysNative\WindowsPowerShell\v1.0\powershell -NoLogo -NonInteractive -NoProfile -command "(gcim Win32_OperatingSystem).InstallDate")
The second one shows when each of the Windows feature updates were installed.
Build 1709 - 3/21/2018 2:18:19 PM
Build 1803 - 3/14/2019 9:56:17 AM
Build 1809 - 8/27/2019 2:35:07 PM
Build 1909 - 11/18/2019 1:15:10 PM
[string]
ShellCommandTextReturn(%windir%\SysNative\WindowsPowerShell\v1.0\powershell -NoLogo -NonInteractive -NoProfile -command "$winBuilds = @{};Get-ChildItem -Path 'HKLM:\SYSTEM\Setup' | Where-Object -FilterScript {($_.Name -like '*Source OS *')}|foreach-object -process {$winBuilds.Add((Get-ItemProperty -Path $_.PSPath -Name ReleaseId).ReleaseId,(Get-ItemProperty -Path $_.PSPath -Name InstallDate).InstallDate)};$winBuilds.Add((Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name ReleaseId).ReleaseId,(Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name InstallDate).InstallDate);foreach($item in $winBuilds.GetEnumerator() | Sort Name){Write-Host "Build $($item.Name) - $([timezone]::CurrentTimeZone.ToLocalTime(([datetime]'1/1/1970').AddSeconds($item.Value)))"}")
