{"id":338,"date":"2019-08-20T14:08:24","date_gmt":"2019-08-20T18:08:24","guid":{"rendered":"https:\/\/blog.markdepalma.com\/?p=338"},"modified":"2019-08-20T14:08:24","modified_gmt":"2019-08-20T18:08:24","slug":"excluding-a-scope-device-group-query-from-another-scope-query-in-ivanti-landesk-endpoint-manager","status":"publish","type":"post","link":"https:\/\/blog.markdepalma.com\/?p=338","title":{"rendered":"Excluding a scope\/device group\/query from another scope\/query in Ivanti (LANDesk) Endpoint Manager"},"content":{"rendered":"\n<p>I recently started piloting patch management and needed the ability to exclude a number of device groups from a scope. We were already using Endpoint Manager for 3rd party patching using a simple task\/scope targeting all workstations. The problem was that the task was overwriting the reboot settings of the agent configuration for devices in the patch pilot. I needed to create a new scope for all workstations that <strong><em>excluded <\/em><\/strong>all devices in the pilot (which were in multiple device groups in Endpoint Manager).<\/p>\n\n\n\n<p>To accomplish this I did the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Created a dummy scheduled task and used my pilot device groups as targets in the task (you can also use a query, a scope, or individual devices here)<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image.png\"><img loading=\"lazy\" decoding=\"async\" width=\"996\" height=\"748\" src=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image.png\" alt=\"\" class=\"wp-image-343\" srcset=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image.png 996w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-300x225.png 300w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-768x577.png 768w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-624x469.png 624w\" sizes=\"auto, (max-width: 996px) 100vw, 996px\" \/><\/a><\/figure>\n\n\n\n<ul class=\"wp-block-list\"><li> Created a query that <strong><em>excluded <\/em><\/strong>machines that were part of this task<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"570\" src=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1-1024x570.png\" alt=\"\" class=\"wp-image-344\" srcset=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1-1024x570.png 1024w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1-300x167.png 300w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1-768x427.png 768w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1-624x347.png 624w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-1.png 1592w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>&#8230;and created a scope using that query<\/p>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-2.png\"><img loading=\"lazy\" decoding=\"async\" width=\"393\" height=\"445\" src=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-2.png\" alt=\"\" class=\"wp-image-345\" srcset=\"https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-2.png 393w, https:\/\/blog.markdepalma.com\/wp-content\/uploads\/2019\/08\/image-2-265x300.png 265w\" sizes=\"auto, (max-width: 393px) 100vw, 393px\" \/><\/a><\/figure>\n\n\n\n<p>This new scope is what I used as a target for my legacy 3rd party task. This is an easy way to exclude exclude a scope\/device group\/query from another scope\/query. This can be very handy for more complex targeting.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I recently started piloting patch management and needed the ability to exclude a number of device groups from a scope. We were already using Endpoint Manager for 3rd party patching using a simple task\/scope targeting all workstations. The problem was that the task was overwriting the reboot settings of the agent configuration for devices in [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[107],"tags":[112,114,111,109,110,113],"class_list":["post-338","post","type-post","status-publish","format-standard","hentry","category-ivanti","tag-device-group","tag-landesk","tag-management-suite","tag-query","tag-scope","tag-software-distribution"],"_links":{"self":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=338"}],"version-history":[{"count":6,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/338\/revisions"}],"predecessor-version":[{"id":348,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/338\/revisions\/348"}],"wp:attachment":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}