- #FOR MAC ADDRESS EXCEPTIONS IN SCCM 2012 CAN YOU USE WILDCARDS FOR MAC#
- #FOR MAC ADDRESS EXCEPTIONS IN SCCM 2012 CAN YOU USE WILDCARDS MAC#
Now, we need to create a query that searches the SMBIOS GUID property.
#FOR MAC ADDRESS EXCEPTIONS IN SCCM 2012 CAN YOU USE WILDCARDS MAC#
The MAC address query prompting for a value You can then navigate to Assets and Compliance and delete the record (if needed). The query returns any matching computer names. If you have an address listed in your SMSPXE log, copy it and paste it into your query. Paste in the following and then close your query: select distinct SMS_R_System.Name, SMS_R_System.MACAddresses from SMS_R_System where SMS_R_System.MACAddresses = #PRM:SMS_R_System.MACAddresses# order by SMS_R_System.MACAddressesĭouble-click the query.
Select Edit Query Statement – Show Query Language. Create a new query and name it Query Machine Name from MAC Address. Launch the Configuration Manager console and navigate to Monitoring/Queries.
Queries to find MAC addresses and SMBIOS GUIDs in our SCCM database To find the computer name, you must query SCCM by using the MAC address or SMBIOS GUID. SMSPXE.log does not contain the computer name. This can make a new computer appear as a known device. Even rarer, you may have duplicate MAC or SMBIOS GUID entries in your database. Occasionally, you might not know the computer name and cannot delete it from SCCM. In this case, you could delete the client record from SCCM. You may want to take a known device and image it like an unknown computer. The known computer is added to the collection and can begin the deployment process. OS deployments to known computers are normally handled with a task sequence deployment to a dedicated device collection.
#FOR MAC ADDRESS EXCEPTIONS IN SCCM 2012 CAN YOU USE WILDCARDS FOR MAC#
Searching SCCM for MAC addresses and SMBIOS GUIDs ^ The client then stops the network boot process () and attempts to boot from another device. No task sequences are deployed to this client through any other collections. Line 1 shows that the device is found in the database, making it a known device.Īny task sequences deployed to the All Unknown Computers collection will not apply to this device. In the screenshot below, a client is attempting a network boot. Our second scenario will involve a known computer. Settings, such as computer name, can be specified before the task sequence actions begin. The client will continue the network boot. Line 5 shows that an optional advertisement was found. SCCM will see if any task sequence is deployed to the All Unknown Computers collection. You can see that process on line 2 in the screenshot above. These determine if the device is treated as an unknown (new) computer. SCCM will look up two identification items: the MAC and the SMBIOS GUID. We will see the following in our SMSPXE log: After we ensure that PXE is enabled on the NIC, we can attempt a network boot. WHERE (SYS.Client0 = 1) AND (NOT (NETW.DefaultIPGateway0 = 'NULL')) AND (NOT (IP.IP_Addresses0 = 'NULL')) AND (NOT (IP.IP_Addresses0 = '0.0.0.0')) and (NET.AdapterType0 = 'Ethernet 802.Our first scenario involves a brand new computer, straight out of the box. INNER JOIN dbo.v_RA_System_SystemOUName ON IP.ResourceID = dbo.v_RA_System_SystemOUName.ResourceID
INNER JOIN dbo.v_RA_System_IPAddresses IP ON IPSUB.ResourceID = IP.ResourceID INNER JOIN dbo.v_GS_NETWORK_ADAPTER NET ON SYS.ResourceID = NET.ResourceID
INNER JOIN dbo.v_GS_NETWORK_ADAPTER_CONFIGUR NETW ON SYS.ResourceID = NETW.ResourceID INNER JOIN dbo.v_GS_WORKSTATION_STATUS WS ON WS.ResourceID = SYS.ResourceID INNER JOIN dbo.v_R_System SYS ON IPSUB.ResourceID = SYS.ResourceID TOP 100 PERCENT SYS.Name0, IP.IP_Addresses0, NET.MACAddress0,WS.LastHWScan,NET.Description0 Try something like this as your SQL Query:
0 kommentar(er)
