Thanks, everyone! I'll give this a whirl and check evaluation time. We are a small environment so the impact may not be that great.
On Wed, Jan 4, 2017 at 7:10 PM, Daniel Ratliff <[email protected]> wrote: > Makes sense. Thanks for the explanations! > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Jason Sandys > *Sent:* Wednesday, January 4, 2017 7:19 PM > > *To:* [email protected] > *Subject:* RE: [mssms] Query machines without a number > > > > Yes, you’re right. There’s no other way to attack it though if the only > criteria is does contain or does not contain numbers. Definitely will need > to watch collection eval time. I can think of alternative ways, but they > involve using a CI or hardware inventory which just adds extra complexity. > You could change the query to just like and then use an exclusion rule to > get the opposite – that will help a little. > > > > J > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com <[email protected]>] *On Behalf Of *Daniel > Ratliff > *Sent:* Wednesday, January 4, 2017 2:02 PM > *To:* [email protected] > *Subject:* RE: [mssms] Query machines without a number > > > > Isn’t that a bad query regarding performance? Not like and double > wildcards? > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com <[email protected]>] *On Behalf Of *Jason > Sandys > *Sent:* Wednesday, January 04, 2017 2:03 PM > *To:* [email protected] > *Subject:* RE: [mssms] Query machines without a number > > > > This should work: > > > > SELECT name > > FROM SMS_R_System > > WHERE name not like ‘%[0123456789]%’ > > > > (replace the smart single quotes above with normal single quotes) > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com <[email protected]>] *On Behalf Of *Daniel > Ratliff > *Sent:* Wednesday, January 4, 2017 11:19 AM > *To:* [email protected] > *Subject:* RE: [mssms] Query machines without a number > > > > The second use, either use a subselect query of machines with numbers, or > create a collection of them and use an exclude rule. > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com <[email protected]>] *On Behalf Of *Adam > Juelich > *Sent:* Wednesday, January 04, 2017 12:11 PM > *To:* [email protected] > *Subject:* [mssms] Query machines without a number > > > > Hello Everyone, > > > > I have a unique scenario here. The environment I inherited happens to > have it's AD OU structure laid out in a way where Student/Staff devices are > not separated. In order to target Staff machines I could leverage UAC but > there are some issues and limitations there that I'd like to hold off on. > Usage assignment won't work when machines are new, having the user choose > the device can't prevent them from choosing multiple devices (licensing), > manual assignment would take a long time, and I wouldn't know where to > start in terms of creating a good CSV to import. > > > > The only differential variable I can find between Student/Staff machine > naming is the fact that staff machines have no numbers in them. Is there a > way I can do a query based on computer names without a number? Or should I > create collections for machines starting with a number and then use those > as exclusions? > > > > Maybe I'm overthinking it.... > > > > Thanks! > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > >
