ConfigMgr Console Queries: Serial Number

To create a query in ConfigMgr, open the console and navigate to Monitoring > Queries. Queries allow you to run simple WQL queries again the database. I will illustrate how to make one by creating one that searches for a device serial number.

You can create the query by using the same information that is used to create collections.

Creating the Query

Select “Create Query” from the ConfigMgr ribbon. Give your query a name. You also have the option of limiting a query to a particular collection, either by specifying it directly, or prompting the user for it.

Capture

When you click “Edit Query Statement”, you are greeted with the same wizard that is using to construct collection queries:

Capture

This first screen is where you tell ConfigMgr what information to display. Since I am finding a computer name using the serial number, those are the two fields I have chosen. When you click the add button, you are greeted with the screen to pick the attribute:

Capture

Simply find the attributes that you want to display. If you’re writing a query that will return multiple objects, you want to set the “Sort” option on at least one of them so that you get a sorted list.

Next, we move to the criteria tab. Again, it functions just like building a collection:

Capture

Now, the big question here is how do we get this to prompt for a value. Here is what the serial number criteria looks like as a query without the prompt (I entered a value of 1 so that I could apply the query):

select SMS_R_System.Name, SMS_G_System_SYSTEM_ENCLOSURE.SerialNumber

from  SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId

where SMS_G_System_SYSTEM_ENCLOSURE.SerialNumber = “1”

To make it prompt, simply change the where clause after the equal sign to:

##PRM:SMS_G_System_SYSTEM_ENCLOSURE.SerialNumber##

It’s basically what the where clause is looking for, bracketed by ## and PRM:, so our query becomes:

select SMS_R_System.Name, SMS_G_System_SYSTEM_ENCLOSURE.SerialNumber 

from  SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId

where SMS_G_System_SYSTEM_ENCLOSURE.SerialNumber = ##PRM:SMS_G_System_SYSTEM_ENCLOSURE.SerialNumber##

After that is set up, you can execute it and get your info:

Capture

Returns:

Capture

Share:

Facebook
Twitter
LinkedIn

Contact Us

On Key

More Posts

Mastering Azure AD Connect - A Comprehensive Guide by WME
Active Directory

Mastering Azure AD Connect – A Comprehensive Guide

Modern businesses are fast moving toward cloud-based infrastructure. In fact, cloud-based business is not just a trend anymore but a strategic necessity. Microsoft’s Azure Active Directory (Azure AD) has become a frontrunner in this domain. It

Read More »
Security Best Practices in SharePoint
Office 365

Security Best Practices in SharePoint

Microsoft SharePoint is an online collaboration platform that integrates with Microsoft Office. You can use it to store, organize, share, and access information online. SharePoint enables collaboration and content management and ultimately allows your teams to

Read More »
The Ultimate Guide to Microsoft Intune - Article by WME
Active Directory

The Ultimate Guide to Microsoft Intune

The corporate world is evolving fast. And with that, mobile devices are spreading everywhere. As we venture into the year 2024, they have already claimed a substantial 55% share of the total corporate device ecosystem. You

Read More »
Protecting Microsoft 365 from on-Premises Attacks
Cloud Security

How to Protect Microsoft 365 from On-Premises Attacks?

Microsoft 365 is diverse enough to enrich the capabilities of many types of private businesses. It complements users, applications, networks, devices, and whatnot. However, Microsoft 365 cybersecurity is often compromised and there are countless ways that

Read More »
Be assured of everything

Get WME Services

Stay ahead of the competition with our Professional IT offerings.