You could also do this as a query in the console. On Tue, Mar 17, 2015 at 11:32 AM, Daniel Ratliff <[email protected]> wrote:
> I use this SQL query to look for multiple records by MAC in the > database. I made it into a SSRS report for easy consumption. Just modify > the MAC at the end. > > > > select SYS.netbios_name0 WKID, SD.itemkey ResourceID, MAC.MAC_Addresses0, > SD.SMS_Unique_Identifier0,SD.Hardware_ID0,SD.Name0,SD.Unknown0,SD. > Obsolete0,SD.Active0,SD.Decommissioned0,SD.Creation_Date0,SD.SMBIOS_GUID0 > > from System_DISC SD FULL JOIN > > v_r_system SYS ON SD.itemkey = SYS.resourceid FULL JOIN > > System_MAC_Addres_ARR MAC ON SD.itemkey = MAC.ItemKey > > where MAC_Addresses0 = '54:ee:75:1f:15:04' > > > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Michael Kimbley II > *Sent:* Tuesday, March 17, 2015 12:19 PM > *To:* [email protected] > *Subject:* RE: [mssms] RE: SCCM 2012 R2 and PXE boot > > > > Make sure the system you are attempting to PXE boot is in an appropriate > device collection for the Task Sequence you want to run in a PXE process. > If it is a new system (or unknown) to SCCM, make sure you are setup to > handle unknown systems. > > One thing I noticed going to R2 (and I will admit it is probably an RTFM > moment) the PXE Boot for OSD isn't very clear when dealing with known > systems that are not in an OSD device collection. I saw either the generic > "ConfigMgr looking for Policy" and/or the "TFTP.[...]" response in the PXE > boot process. > > I chased networking as the issue. .. .WireShark, etc. .. .disabled/enabled > PXE on the DP. .. .rebuilt/redeployed the DP. .. .and it turned out to be a > system with a two device entries in ConfigMgr. Found it by searching by MAC. > > Hope this helps. > M > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: [mssms] RE: SCCM 2012 R2 and PXE boot > Date: Tue, 17 Mar 2015 15:42:14 +0000 > > Dunno if the details in this blog post will be of any help. There is quite > a bit of background info on the subject of PxE booting and DHCP. > > > > > http://www.1e.com/blogs/2014/09/29/osd-pxe-ip-helpers-dhcp-options-isnt-there-a-better-way/ > > > > FWIW > > > > Ed Aldrich | Channel Solutions Engineer | *1**E* > > +1 (401) 924-2293 > > [image: Description: Description: cid:[email protected]] Ent > Cli Mgmt (2003-2014) > > Please consider the environment before printing this e-mail > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* den 21 januari 2015 14:36 > *To:* [email protected] > *Subject:* [mssms] RE: SCCM 2012 R2 and PXE boot > > > > Can ping both the FQDN and IP address of the DP. > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *CM, ArvindKumar > *Sent:* Wednesday, January 21, 2015 8:29 AM > *To:* [email protected] > *Subject:* [mssms] RE: SCCM 2012 R2 and PXE boot > > > > Looks like the PXE boot server is not responding. PC may get an IP from > DHCP but it will only boot when it get boot info from PXE server. > > > > Normally when PC receives the PXE boot server info from DHCP (option 66 > and 67) it will request the PXE server (unicast) for boot information. > Please check if you can reach /ping the PXE server from the PC lan. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Wednesday, January 21, 2015 6:35 PM > *To:* [email protected] > *Subject:* [mssms] SCCM 2012 R2 and PXE boot > > > > I am trying to PXE boot my first workstation to SCMM 2012 R2. > > My PXE boot on my workstation sees my DHCP server. I have added 066 and > 067 to the DHCP options but the workstation fails to boot. > > It gets an address from the DHCP server then it trys to TFTP?? > > Then it fails. > > I see it in the DHCP lease but I see nothing in the SMSPXE.log on the SCCM > 2012 server?? > > I have never booted to PXE in the past so I am a total virgin in this area. > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > > > > > > > > ------------------------------ > > > > Legal Notice: This email is intended only for the person(s) to whom it is > addressed. If you are not an intended recipient and have received this > message in error, please notify the sender immediately by replying to this > email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This > email and any attachments may be privileged and/or confidential. The > unauthorized use, disclosure, copying or printing of any information it > contains is strictly prohibited. The opinions expressed in this email are > those of the author and do not necessarily represent the views of 1E Ltd. > Nothing in this email will operate to bind 1E to any order or other > contract. > > > > 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. > >
