/build/static/layout/Breadcrumb_cap_w.png

Targetting fresh K2000 image/scripted installations for selecting 1st run installations based on Active Directory OU.

Objective
To deploy certain applications targeting only workstations that have been freshly installed with Windows 10

Obstacle/Question
Using the K2000 & K1000, how do I target these machines to install specific applications to specific workstations?
I thought about adding "marker" files as Post Installation Tasks, but is there another way for this to be accomplished?

Example:
We have 30 workstations to replace in the Business Office. We will image them using the K2000 and a scripted installation.
We will also create the computer object in Active Directory add them to our "Undeployed" OU . We have standard applications
associated with the "Undeployed OU" to ditribute the standard applications such as MS Office, Firefox, Plug ins, etc.
We need to install App1, App2  & App 3 on these workstations undauntedly.
How do we target these?

TIA,
Israel


3 Comments   [ + ] Show comments
  • You will need a custom inventory rule to target recently imaged devices

    https://www.itninja.com/question/capturing-deployment-date-w-5-0-and-1709 - Channeler 6 years ago
    • Thanks for the response,
      I do believe that KACE's best practices are that you install the app first,
      run a check in (RunKBOT), and then use the software label that KACE created.
      By doing this, you have no access to the Custom Rule addition. If you create your
      your own Software Title and associate an installation file with it, then you do have
      the ability to create a Custom Inventory Rule.
      But, in saying that, I will revisit that idea.
      Thanks again! - IDeLeon007 6 years ago
  • Why don't you just install the applications as post-install tasks as part of the scripted install? - chucksteel 6 years ago
    • Thanks for the response ChuckSteel,
      I suppose I could create multiple scripted installations with each Unit
      having it's own desired applications associated with those installations.
      I'll try that out.
      Thanks again! - IDeLeon007 6 years ago
  • Try taking a look at the answer I gave to an earlier question:
    https://www.itninja.com/question/command-line-to-run-a-patching-schedule

    You could use a CIF and a Smart Label to determine if the computers were in the appropriate OU, then install the software. - PaulGibson 6 years ago

Answers (0)

Be the first to answer this question

 
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