/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


What are the best practices with k1000 Label to include only Newly bulit machines from k2000 system? (deployed that and then removed from label)?

03/15/2018 1256 views
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?
1 Comment   [ + ] Show comment

Comments

  • Where I work, we have all of the computer built by the K2000 go into a KACE OU in Active Directory. A Smart Label detects if the computer is in that OU and installs our default software and it's set to run updates every 2 hours. When the computer is ready to be shipped to the appropriate office, we use ADUC to move the computer to the OU for that office, and KACE removes the Smart Label.

    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.


Community Chosen Answer

3
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


Answered 03/15/2018 by: Channeler
Red Belt

  • This is how we do it and it works very well for us.
    • Thanks is very helpful .

All Answers

1
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.
Answered 03/15/2018 by: five.
Second Degree Green Belt

  • Thanks this is very helpful...
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ