Java Autodeploy, Exclude Targets

Comments

4 comments

  • Christian Bacher

    If you know all the devices it's easy:

    Create a custom "static" collection and put in all this devices.

    enter image description here

    Now you can set the conditions of the regular Java deployment to "Is Not A Member" and point to your static collection.

    enter image description here

    Now all devices in you static collection are skipped for this deployment.

    Now create your second deploment for this special devices and say "Is A Member" and point again to the collection.

    Now you can be sure that the second java setup only runs on this devices inside the static collection.

    0
    Comment actions Permalink
  • Neff, Ryan

    Thank you for the reply and suggestion. I will have to try this route for sure. I also have 1 user account that runs on those locked down computers + I have a collection of those targets that have that user account. Maybe I could have a condition that ignores the registry entry for that user account on the main Java Auto Deploy?

    0
    Comment actions Permalink
  • Webmaster

    2nd thought, registry entry might not work.

    So can the Static collection live anywhere on the Inventory list now that I set it as a Member?

    0
    Comment actions Permalink
  • Neff, Ryan

    I think I get it now, It took me a while to wrap my head around the idea. The schedule targets Old Java so anything listed in there gets update with the condition of "is Not A Member" and that points to the new collection I just created and marked those locked down machines as Members. Therefore schedule deploys to all targets except collection with members.

    Perfect

    0
    Comment actions Permalink

Please sign in to leave a comment.