Perfect. You rock, Nash.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Nash Pherson
Sent: Thursday, July 31, 2014 9:06 AM
To: [email protected]
Subject: [mssms] RE: Help with task sequence variable logic

If these steps are running in the target operating system (after the Setup 
Windows and ConfigMgr Step), then your condition could just use the actual 
Computer Name with a WMI Query so you can leverage the LIKE operator.

Select * from Win32_ComptuerSystem Where Name Like 'QL-%'
Select * from Win32_ComptuerSystem Where Name Like 'RS-%'

Cheers,


Nash


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Murray, Mike
Sent: Thursday, July 31, 2014 10:45 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Help with task sequence variable logic

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]<mailto:[email protected]>






Reply via email to