How can we improve the SDA (K2000)?

Ability to apply K1 labels from the K2 as postinstall tasks

It would be beneficial to be able to leverage the label feature in the K1 at time of system deployment.

141 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Christopher Blake shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Marc commented  ·   ·  Flag as inappropriate

    The way I understand this feature request, and how I'd like to see it work, is that the K2000 would have a post installation task titled "Apply K1000 labels," which would give us a list of labels from the K1000, and we'd select which labels we want to apply. Would require tighter integration between K1 and K2, to sync labels on a schedule.

  • horstj commented  ·   ·  Flag as inappropriate

    I believe that there is already a way to do this. We have our system set up to do this now using the custom inventory label of the K1000. I set it up so that the K2000 does three postinstall tasks to accomplish this. First it installs the K1000 agent, then creates a text document labeled "New Computer", and finally runs cmd with the "runkbot.exe 4 0" to force the agent to check in. I then have a custom inventory label in the K1000 that is automatically applied at that check in when it sees the text document. You can then base all of your SI's and MI's off of that label. This has worked like a charm for me and I believe it does exactly what John is looking for.

  • Tentacle Master commented  ·   ·  Flag as inappropriate

    John they maybe how it needs to work, but from what I can gather, and it would be cool, the ability in the k2000 post-install tasks, to assign a manual label that will/is used by the K1000. So for instance post install installs the kagent, then another post install task assigns a label to it. Then, the next time the kagent checks in, it says "oh by the way, assign this manual label to me automatically"

  • Christopher Blake commented  ·   ·  Flag as inappropriate

    It's not uncommon to create manual labels for software distribution, patching, etc. It would be nice if we could have the scripted install add the machine to the manual K1 label somehow if need-be.
    E.G. - One has a label called "Photoshop Machines" and another "Marketing Department". "Photoshop Machines" has an MI associated, and "Marketing Department" has 4 MI's and 8 scripts, and a patch schedule. The marketing department orders 30 new machines; I'm going to want to make a scripted install for marketing and just let K1 deliver the software whilest I sip my coffee. If I could apply the labels at image time I never have to get involved (or forget) to do anything further.

  • AdminJohn Karabaic (Admin, Quest KACE) commented  ·   ·  Flag as inappropriate

    I need more clarification on this request. I think what you're saying is

    1. K2000 deploys K1000 agent as part of build
    2. K1000 agent does initial checkin as part of build
    3. Label memberships established on K1000 as part of that initial checkin

    That intial checkin should result in no K1000 actions, like patching and such, or should it?

Feedback and Knowledge Base