The great guy who runs this site posted a script that takes the start of a computer name and sets the OSDDomainOUName variable to put a computer in the right OU during OSD. It can probably be modified to work in your situation.
http://ephingadmin.com/osd-move-computers-in-ad-auto-magically/ On Thu, Jul 31, 2014 at 11:02 AM, Murray, Mike <[email protected]> wrote: > Anyone already have a script that does this? Rather not reinvent the > wheel. Or at least a good example? > > > > Thanks, > > > > Mike > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Murray, Mike > *Sent:* Thursday, July 31, 2014 9:01 AM > *To:* [email protected] > *Subject:* RE: [mssms] Help with task sequence variable logic > > > > Ah, makes sense. Thanks. :) > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Ryan > *Sent:* Thursday, July 31, 2014 8:55 AM > > *To:* [email protected] > *Subject:* Re: [mssms] Help with task sequence variable logic > > > > He is talking about a VB script which will take the first two characters > of a computer name and put it in a task sequence variable, like > OSDCompNameStartsWith. Then, you can make the step only run if that task > sequence variable equals QI or RS. > > > > On Thu, Jul 31, 2014 at 10:51 AM, Murray, Mike <[email protected]> > wrote: > > The task sequence variable is already there. Not sure what you mean here? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jason Wallace > *Sent:* Thursday, July 31, 2014 8:49 AM > *To:* [email protected] > *Subject:* Re: [mssms] Help with task sequence variable logic > > > > Write a small vbscript to dump the first two characters to a task sequence > variable and then query it > > > On 31 Jul 2014, at 17:47, "Murray, Mike" <[email protected]> wrote: > > I have a couple of steps in our TS that I want to execute for one set of > computers based on their naming convention, and another set of steps for > another set of computers with a different naming convention. The two naming > conventions start with: > > > > QL- > > RS- > > > > If I use the argument under options, task sequence variable *OSDComputerName > greater than or equal to “QL-%”*, both naming conventions match the > requirement, and I don’t want that. If I just use equals, it doesn’t work > at all. > > > > Is there some other way to work this logic? > > > > > > Best Regards, > > > > Mike Murray > > Desktop Management Coordinator - IT Support Services > > California State University, Chico > > 530.898.4357 > [email protected] > > > > > > > > > > > > > > > >
