locked
How to limit Image Deployment to needed PCs only, not all WKS ? RRS feed

  • Question

  • Hi All,

    We have lot of existing SCCM agent PCs that needs to be reimaged using PXE, however We dont want to deploy all TS/Images to all WKS collections which we consider is overload on AllWKS, neither Helpdesk is ready to add reimage needing PC to PXE Custom collection for deploying them

    I wonder is there any other creatives ways out, if anybody tried ?  Goal is all PC shouldn't bear the load of Imaging policies which are huge in our environment (10+ Images, each Image has 150+ actions in it, leading to 1500 policies), hence wanted to limit it to needed PC only

    Wondering at SQL SRPOC level or any custom actions we can do in PXE Image so on so forth ?

    Thanks, Vasu 


    Vasu

    Tuesday, August 4, 2020 10:11 AM

Answers

  • Well, we have brainstormed a lot and are tying below way now

    Step1: Deploy all needed Images to Default UNKNOWN collections, so any new PC/Baremetal will get them 

    Step2: Deploy all needed Images to Specific collection say "PXE needing PCs"

    Step3: Deploy a Task Sequence to All Workstations with a script that adds its PC name to collection in Step2 and reboots PC back to F12

    Step4:  So if an existing /known PC reboots into WINPE, its PC name is added to PXE collection and receives TS/Images immediately 

    This way we achieved our goal of eliminating the load of near 1500 policies from different Images that are sitting on all WKS, by limiting them to few tens of PCs that actually goes PXE Reimaged 

    Thanks,


    Vasu

    • Marked as answer by Vasu Miriyala Saturday, August 15, 2020 1:45 PM
    Saturday, August 15, 2020 1:45 PM

All replies

  • Hi Vasu,

    Thanks for posting in TechNet.

    Generally speaking, most folks always use purpose-built collections for targeting deployments and also in general, most folks will recommend to never use any generic collections for targeting deployments. Based on my experience, for task sequences, there is no additional deployment time filtering and you need to rely on collections.

    Thanks again for your time!

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 5, 2020 7:49 AM
  • Hi,

    May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 7, 2020 2:55 AM
  • Well, we have brainstormed a lot and are tying below way now

    Step1: Deploy all needed Images to Default UNKNOWN collections, so any new PC/Baremetal will get them 

    Step2: Deploy all needed Images to Specific collection say "PXE needing PCs"

    Step3: Deploy a Task Sequence to All Workstations with a script that adds its PC name to collection in Step2 and reboots PC back to F12

    Step4:  So if an existing /known PC reboots into WINPE, its PC name is added to PXE collection and receives TS/Images immediately 

    This way we achieved our goal of eliminating the load of near 1500 policies from different Images that are sitting on all WKS, by limiting them to few tens of PCs that actually goes PXE Reimaged 

    Thanks,


    Vasu

    • Marked as answer by Vasu Miriyala Saturday, August 15, 2020 1:45 PM
    Saturday, August 15, 2020 1:45 PM
  • Hi Vasu,

    You have done an awesome job! Thank you very much for your feedback and sharing! I think maybe other people with the same needs will benefit from it. Thank you!
     
    Thanks and regards,
    Simon

    "MECM" forum will be migrating to a new home on Microsoft Q&A!
    We invite you to post new questions in the "MECM" forum's new home on Microsoft Q&A!
    For more information, please refer to the sticky post. Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 17, 2020 8:01 AM
  • Thanks Simon... 

    Vasu

    Monday, August 17, 2020 4:32 PM