What are the best practices with k1000 Label to include only Newly bulit machines from k2000 system? (deployed that and then removed from label)?
What are the best practices with k1000 Label to include only Newly built machines from k2000 system?
Deployed that and then remove the machine from the label after a day or some action is done?
I would like to use this label so it can auto move to the current OU in AD, Install software for the department it belongs to, and other software for new machines via k1000. After all of this is done if by date, after a day or after all those steps are done it no longer in that label.
How do you best handle this?
Deployed that and then remove the machine from the label after a day or some action is done?
I would like to use this label so it can auto move to the current OU in AD, Install software for the department it belongs to, and other software for new machines via k1000. After all of this is done if by date, after a day or after all those steps are done it no longer in that label.
How do you best handle this?
1 Comment
[ + ] Show comment
Answers (2)
Please log in to answer
Posted by:
Channeler
6 years ago
If you are using version 4.1 or newer, the K2 puts a file called k2000_deployment_info.conf in \ProgramData\Quest\KACE.
Some customers use a custom inventory rule to read the date/time stamp inside that file to put the machine in a smart label (or remove it from a smart label).
You could aslo make it simple, create a Smart Label based on a Custom Inventory Rule that will verify if k2000_deployment_info.conf exists in \ProgramData\Quest\KACE. And if it's there you know it was imaged by the K2000.
See:
https://support.quest.com/technical-documents/kace-sma/7.2/administrator-guide/136#TOPIC-733823
You could aslo make it simple, create a Smart Label based on a Custom Inventory Rule that will verify if k2000_deployment_info.conf exists in \ProgramData\Quest\KACE. And if it's there you know it was imaged by the K2000.
See:
https://support.quest.com/technical-documents/kace-sma/7.2/administrator-guide/136#TOPIC-733823
Posted by:
five.
6 years ago
FileInfoReturn(C:\ProgramData\Dell\KACE\k2000_deployment_info.conf, CreatedDate, DATE) OR FileInfoReturn(C:\ProgramData\Quest\KACE\k2000_deployment_info.conf, CreatedDate, DATE)
That is what mine looks like. Checks both the new and old locations for the file.
Comments:
-
Thanks this is very helpful... - itadder 6 years ago
For deploying our default apps, we have a Smart Label for each app. The label checks for computers in our KACE OU Smart Label, and verifies the software hasn't been installed yet. This Smart Label is then applied to a software install. - PaulGibson 6 years ago