Jump to content


Variables during OSD

Recommended Posts

I'm want to make a new task sequence to OSD, without MDT, but I wanna to avoid to have too many task sequence. Problem: each department has his own software but sometimes they are common in other departments. And then I have the OU's for each department.


I'm going to try something like this:


Goal: one single task sequence, instead of having 10 or 20...


For software: declare a variable in a collection where that variable is something like "BundleSoftware_1 = true". In the task sequence, if this variable is true, then install the applications bundle;


For OU's, I would do the same. A will declare the same variable for several collection (department A, department B, department C, etc). If variable = RH, then would match the step where it registers the computer in RH OU.


I never did this, but I would like to know if anyone has setup something like this. Any other ideas would be great!


Thanks in advanced!

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.