Jump to content


Kops

Select OU in Task Sequence

Recommended Posts

Our AD structure separates computers by floors 0-5. We had previously used a WMI query based on a computer name to determine which OU to place the computer in, based on the first character of the name. For example, a computer named 3239PC1 would be 3rd floor, room 239, and be placed in the 3rd floor OU. We are now changing our computer naming scheme to reflect the asset tag number of the device, so I can no longer query the name to determine the OU.

 

I use a OSDComputerName variable to prompt for a computer name during task sequence, but haven't been able to find something similar to prompt for which OU to deploy to. Has anyone been able to do something like this?

Share this post


Link to post
Share on other sites

Thanks for the recommendation. That looks quiet impressive, definitely something I am going to experiment with.

 

I was able to get this working in a much simpler fashion though. I created a collection variable called 'OU' on the 'All Unknown Computers' device collection, so I am now prompted for both OU and OSDComputerName during OSD. Then, in my task sequence, I am using about 5 different 'Join Domain or Workgroup' tasks that have a condition checking 'If OU = Level 1' or 'If OU = Level 2' etc, and based upon this, will add the computer into the correct OU.

Seems to be working like a charm :)

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.

Guest
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.

Loading...


×
×
  • 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.