SMSPXE - not working for one computer
Hi,I have a new laptop that is not PXE booting. The PXE service point reports that "ProcessDatabaseReply: No Advertisement found in Db for device". I have no problems PXE booting other computers and this is the first one I've had trouble with.I have confirmed that the SCCM computer account: Has the correct MAC address The account exists in a collection that has a TS advertised to it, and that the computer account has this advertisement advertised to it. The advertisment is configured to 'make this TS available to boot media and PXE' The computer object is not obsolete and I have cleared any PXE advertisements associated with the account.I have deleted and recreated the account several times to no avail. I ran the SQL profiler and found that the resource ID from NBS_GetPXEAction is different to the resource ID in the SCCM computer account. So I guess that explains why the PSP is reporting that there is no advertisement for this device! I have restarted the WDS Server service to flush the SMSPXE provider cache and the profiler still reports an incorrect resource ID.Any ideas on how I can fix this and as to why this has happened? Thanks,Sam
February 25th, 2008 5:17am

I've had similar issues from time to time. 1. Was this computer previously in SCCM? Did you delete the original computer object from SCCM as well? We've found that SCCM can get confused if there are two computers with the same MAC/BIOS GUID in the system and will often pick the wrong one. Try deleting all the computer accounts with that same MAC/GUID. 2. Even if you do delete all the MAC/GUID's you may still get the same error since WDS seems to like to cache the information for a period of time (rumor has it that it is about 60 minutes). The easiest way to clear the WDS cache is to stop and restart the WDS services to get it to re-read from the SCCM database. Good luck. Matthew Evans Kraft & Kennedy, Inc. 360 Lexington Ave. New York, NY 10017 Direct: 212.692.5608 email: evans@kraftkennedy.com
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2008 5:40pm

Hi Matthew,Thanks for the reply! In answer to your questions:1) The computer was not previously in SCCM and I have tried deleting and recreating the computer account in SCCM with no success.2) I restarted the WDS services to flush the smspxe provider cache and the SQL profiler still reports the incorrect resource ID when I PXE boot this computer (maybe the cache is not being flushed correctly?)Any other ideas?Thanks,Sam
February 26th, 2008 12:33am

What I do in this cases: Go to reports website, if you have reporting services role in your environment... And check the "Network" section. The one where it says "MAC-Computers for a specific MAC address". Just type in your MAC address and see ifreally SCCM doesnt know anything about MAC you specified. Also take a look at smspxe.log file on your PXE service point if it finds your PC by MAC or by GUID and check, something like "MAC=00:11:22:33:44:55 SMBIOS GUID=00112233-4455-6677-8899-123456789988 > Device found in the database. MacCount=1 GuidCount=1". Well anyway its hard to tell anything without seeing logfile Can you post your smspxe.log here?
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2008 1:18am

What I do in this cases: Go to reports website, if you have reporting services role in your environment... And check the "Network" section. The one where it says "MAC-Computers for a specific MAC address". Just type in your MAC address and see ifreally SCCM doesnt know anything about MAC you specified. Also take a look at smspxe.log file on your PXE service point if it finds your PC by MAC or by GUID and check, something like "MAC=00:11:22:33:44:55 SMBIOS GUID=00112233-4455-6677-8899-123456789988 > Device found in the database. MacCount=1 GuidCount=1". Well anyway its hard to tell anything without seeing logfile Can you post your smspxe.log here?
February 26th, 2008 1:18am

Hi ankr,Thanks for the reply. The smspxe.log file reports that the device is found in the database however there is no advertisment for the device (as the resource IDs are different). I've posted the extract of the smspxe log as requested. Executing LookupDevice(65FADB80-63E8-1000-8A12-C0209F20D020, 00:C0:9F0:B2:67) smspxe 21/02/2008 10:20:11 AM 2384 (0x0950)CDatabaseProxy :: LookupDevice succeeded: 2817 6 2987 1 smspxe 21/02/2008 10:20:11 AM 2384 (0x0950)MAC=00:C0:9F0:B2:67 SMBIOS GUID=65FADB80-63E8-1000-8A12-C0209F20D020 > Device found in the database. MacCount=1 GuidCount=6 smspxe 21/02/2008 10:20:11 AM 2384 (0x0950)[010.020.001.214:4011] Recv From:[010.020.010.026:68] Len:299 2715884 smspxe 21/02/2008 10:20:12 AM 1976 (0x07B8)Executing GetBootAction(2817, WB-MGMT-02) smspxe 21/02/2008 10:20:12 AM 2384 (0x0950)No Boot Action for Device found smspxe 21/02/2008 10:20:12 AM 2384 (0x0950)ProcessDatabaseReply: No Advertisement found in Db for device smspxe 21/02/2008 10:20:12 AM 2384 (0x0950)Thanks,Sam
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2008 2:59am

I think that problem is with 6 GuidCounts you have. That should be a unique number for each PC. If Im not mistaken.. the GUID mentioned here is SMBIOS_GUID.I think it is possible to have multipplePCs with same GUID in your environment (if your Site Server is set up to create duplicate client records), but that actually means that the record which you see in your deployment collection, may not be the real one. Try some of this: 1. Better use Query Based collection memberships, not the Direct ones. 2. Update collections membership. And see if it changed something. 3. Under "Reports" you can create a custom reports with query like this "select Name0,SMBIOS_GUID0 from v_R_System", that should display all computer names with their GUIDs. Maybe that will give you a clue why you have 6 records for same GUID.
February 26th, 2008 11:05am

I think that problem is with 6 GuidCounts you have. That should be a unique number for each PC. If Im not mistaken.. the GUID mentioned here is SMBIOS_GUID.I think it is possible to have multipplePCs with same GUID in your environment (if your Site Server is set up to create duplicate client records), but that actually means that the record which you see in your deployment collection, may not be the real one. Try some of this: 1. Better use Query Based collection memberships, not the Direct ones. 2. Update collections membership. And see if it changed something. 3. Under "Reports" you can create a custom reports with query like this "select Name0,SMBIOS_GUID0 from v_R_System", that should display all computer names with their GUIDs. Maybe that will give you a clue why you have 6 records for same GUID.
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2008 11:05am

I'm working at a client's site where we're seeing this same sort of behavior. Like 15 Dell workstations that are all showing the same SMBIOS GUID in SCCM, which is preventing us from PXE booting those machines. We're only seeing this in select Dell GX270s and GX280s... is this a manufacturing defect? I don't know of any way to change that SMBIOS GUID either, updating the BIOS won't change it.
February 27th, 2008 12:26am

Hi Sam I had the exact same problem but with machines in a virtual lab. Here is the post to my original message: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2345538&SiteID=17. We assumed that the issue lied with VMware and how it handled SMBios Guids, but considering you have experienced this with physical machines it leads me to believe it may be a problem with SCCM. Try configuring the site setting "Conflicting Records" to Manually resolve conflicting records rather than "Automatically create new client records for duplicate hardware IDs, as suggest by ankr. Ross
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2008 5:42am

Thanks for the replies guys Ankr, I created the custom report as you suggested and found that there are 5 computers with the same SMBIOS GUID. These 5 computers: exist in AD and SCCM have unique SMS GUIDs are not obsolete haveunique resource IDs Interestingly they're all the same model notebookand they all have the same SMBIOS GUID. I compared the SMBIOS GUID found in the BIOS to the SMBIOS GUID reported by the smspxe log and found that the first 3 sections of the GUID are reversed in the smspxe log - the same situation Ross was seeing in his post. I think this might be a bug with SCCM. Thoughts? Ross, I configured SCCM to manually resolve conflicting records and the conflicting records folder is empty. Thanks, Sam
February 28th, 2008 3:19am

Hi, Any more ideas for this issue? I have another PC that has the same problem. Thanks, Sam
Free Windows Admin Tool Kit Click here and download it now
March 3rd, 2008 4:02am

Hi, I had exactly same problem and fixed it by doing - 1. Delete the PC from Collection. (I have deleted the PC from All Systems collection) 2. Delete the advertisement. 3. Stop and Start WDS services. 4. Import PC again. (I only used MAC address to import the PC) 5. Create new TS advertisement. Hope this helps.
April 20th, 2008 2:45pm

Hello, I guess by now umay have found the solution, if not here it is. It is a machine GUID which cauz this problem..Machine with same GUID is unknown to SCCM. We can say a Hardware manufacturer defect or SCCM defect. Two method are available to solve this problem 1> either u obtain bios utility from hardware vendor and change mother board GUID manually OR 2>(Prefered method)Make change in SCCM SQL data base as explained below:Go to SCCM site Database->Modify Stored procedure-> NBS_Lookupdevice-> SET NOCOUNT ON IF @SMBIOS_GUID IN (Type all maching GUID) e. g.('00020003-0004-0005-0006-000700080009','03000200-0400-0500-0006-000700080009')BEGIN SET @SMBIOS_GUID = '000000000-0000-0000-0000-0000000000000';END ->& ExecuteI culd resolve problem which we were facing..hope this will help to all those are facing similer problem.do write back if need help on dev.knowledge@gmail.comCheers:-)
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2009 9:45pm

Hello ,Only regenrating the GUID will relsolve the issue .Before that you have stop and restart the WDS services..In my enviornment i have regenrated the GUID with client tool and clear all the pxe advert and again pushed the image .For me it worked out .Try this ,may it will resolve your issue also incase if it still persistcheers!!!!!!!!!!!!
December 24th, 2009 6:23pm

I am having the same issue but with a twist:One particular Dell GX270 wont PXE boot to OSD anymore [it used to do so just fine]so I thought maybe other machines have the same GUID. But here is the twist:in smspxe.log it says:MAC=00:0D:56:88:40:A7 SMBIOS GUID=4C4C4544-0000-2010-8020-80C04F202020 > Device found in the database. MacCount=1 GuidCount=6 smspxe 2/19/2010 12:08:23 PM 6716 (0x1A3C)But on the PXE boot screen of the machine's MAC address is as above but the GUID is different!!!!If I run a report querying for the abovementioned GUID, I find 6 other machines which have this GUID! Strangely the PXE machine is not there in that list of 6 machines.VERY weird!
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2010 8:31pm

Hello ,Only regenrating the GUID will relsolve the issue .Before that you have stop and restart the WDS services..In my enviornment i have regenrated the GUID with client tool and clear all the pxe advert and again pushed the image .For me it worked out .Try this ,may it will resolve your issue also incase if it still persistcheers!!!!!!!!!!!! What client tool are you talking about here?
February 19th, 2010 8:32pm

I compared the SMBIOS GUID found in the BIOS to the SMBIOS GUID reported by the smspxe log and found that the first 3 sections of the GUID are reversed in the smspxe log - the same situation Ross was seeing in his post. I think this might be a bug with SCCM. Thoughts? Very interesting ! I too see this in my environment:from smspxe.log:MAC=00:0D:56:88:40:A7 SMBIOS GUID=4C4C4544-0000-2010-8020-80C04F202020 > Device found in the database. MacCount=1 GuidCount=6 smspxe 2/19/2010 1:29:04 PM 2740 (0x0AB4)from machine's display:44454C4C-0000-1020-8020-80C04F202020The first three blocks are reversed [numbers are in pairs]
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2010 9:44pm

Hello, I guess by now u may have found the solution, if not here it is. It is a machine GUID which cauz this problem..Machine with same GUID is unknown to SCCM. We can say a Hardware manufacturer defect or SCCM defect. Two method are available to solve this problem 1> either u obtain bios utility from hardware vendor and change mother board GUID manually OR 2>(Prefered method) Make change in SCCM SQL data base as explained below:Go to SCCM site Database->Modify Stored procedure-> NBS_Lookupdevice-> SET NOCOUNT ON IF @SMBIOS_GUID IN (Type all maching GUID) e. g. ('00020003-0004-0005-0006-000700080009','03000200-0400-0500-0006-000700080009') BEGIN SET @SMBIOS_GUID = '000000000-0000-0000-0000-0000000000000'; END ->& ExecuteI culd resolve problem which we were facing..hope this will help to all those are facing similer problem.do write back if need help on dev.knowledge@gmail.comCheers:-) I am trying to do what you have posted here. No success :-(The original stored procedure looks like this: USE [SCCM_FPB] GO /****** Object: StoredProcedure [dbo].[NBS_LookupDevice] Script Date: 02/19/2010 13:57:29 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO ALTER PROCEDURE [dbo].[NBS_LookupDevice] @SMBIOS_GUID varchar (38), @MACAddress varchar(64) AS BEGIN SET NOCOUNT ON SELECT MAX(aux.ItemKey) AS 'MaxItemKeyBySMBIOS_GUID', count(aux.ItemKey) AS 'ItemCountBySMBIOS_GUID', MAX(mac.ItemKey) AS 'MaxItemKeyByMAC', count(mac.ItemKey) AS 'ItemCountByMAC' FROM MachineIdGroupXRef xref LEFT JOIN System_AUX_Info aux ON xref.MachineID = aux.ItemKey AND aux.SMBIOS_GUID0 = @SMBIOS_GUID LEFT JOIN System_MAC_Addres_ARR mac ON xref.MachineID = mac.ItemKey AND mac.MAC_Addresses0 = @MACAddress END Do I delete all lines between BEGIN and END and replace with your statements?BTW, I tried that but it does not work. I start getting these errors in the smspxe.log file:PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows)Can you please help me?
February 19th, 2010 10:56pm

PLEASE ! Can someone help me?I still cannot OSD this one machine.
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2010 5:35pm

did this work?On Mon, Feb 22, 2010 at 2:45 PM, dev deven <dev.knowledge@gmail.com> wrote:> Ok seems its same so do following:> Go to Central/Primary Site SCCM Database->Modify Stored procedure->> NBS_Lookupdevice->>> SET NOCOUNT ON> (Note: Only start from the below line dont touch other lines and copy> and paste below lines as i have already set for u)> IF @SMBIOS_GUID IN ('44454C4C-0000-1020-8020-80C04F202020')> BEGIN> SET @SMBIOS_GUID = '000000000-0000-0000-0000-0000000000000';> END> -> NOW EXECUTE>> Cheers:-)
February 24th, 2010 6:36pm

no it did not work.I even tried to use the GUID backwards meaning:I used this4C4C4544-0000-2010-8020-80C04F202020instead of this44454C4C-0000-1020-8020-80C04F202020It still does not boot from PXE and get the image.
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2010 6:37pm

My DB guy has spent a couple of hours with me looking into the DB, running this stored procedure and also trying to run the SQL profiler ,...........all while trying to understand what is wrong....but we could not fix it.Any other ideas?Anyone?
February 24th, 2010 9:11pm

Did you have any success with the SQL profiler? You need to confirm that the resource ID in NBS_GetPXEAction matches the resource ID for the computer object in ConfigMgr. Your smspxe.log also reports "GuidCount=6" - I would search ConfigMgr for that (GUID 4C4C4544-0000-2010-8020-80C04F202020) using the resource class 'System Resource' and Attribute Name 'System UUID' and delete any duplicate records with the same GUID.Once you've confirmed that there are no duplicate ConfigMgr records for that GUID, PXE boot the computer and verify that the smspxe.log reports GuidCount=1 for that resource and you should have more success.You could also just create bootable task sequence media if you need to quickly build this computer.Good luck!
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2010 1:50am

Check out this article about Guid's and why they are reversed in the different interfaces: http://technet.microsoft.com/en-us/library/cc773235(WS.10).aspx
April 19th, 2010 1:37pm

Did you have any success with the SQL profiler? You need to confirm that the resource ID in NBS_GetPXEAction matches the resource ID for the computer object in ConfigMgr. Your smspxe.log also reports "GuidCount=6" - I would search ConfigMgr for that (GUID 4C4C4544-0000-2010-8020-80C04F202020) using the resource class 'System Resource' and Attribute Name 'System UUID' and delete any duplicate records with the same GUID. Once you've confirmed that there are no duplicate ConfigMgr records for that GUID, PXE boot the computer and verify that the smspxe.log reports GuidCount=1 for that resource and you should have more success. You could also just create bootable task sequence media if you need to quickly build this computer. Good luck! Nope...the bootable TS media does NOT work. I tried it. Why? because the GUID is embedded into the motherboard. SCCM detects that and the TS boot fails. I even tried putting a new network card and booting off it....hoping that the GUID will be different now............alas! no! GUID of the PC is actually on the motherboard.
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2010 4:25pm

Has anyone found a definitive solution to this problem? I'm having exactly the same issue but am absolutely stumped. This is what I'm getting on a laptop that won't PXE: [MAC=00:19:DB:EB:22:B1 SMBIOS GUID=03000200-0400-0500-0006-000700080009 > Device found in the database. MacCount=0 GuidCount=57] I created the report mentioned above, one room with 25 PC's, a few from another, two different types of laptop all with the same GUID as above. How is that even possible?
August 12th, 2010 11:47am

[MAC=00:19:DB:EB:22:B1 SMBIOS GUID=03000200-0400-0500-0006-000700080009 > Device found in the database. MacCount=0 GuidCount=57] How did you import the computer? Only using Name + Guid? If so: try importing it using Name + MAC only. The problem is that the GUID matches 57 entries in the database.
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2010 12:04pm

The laptop was originally a known computer, however after failing to PXE boot it and stumbling across this thread I realised this duplicate SMBIOS GUID problem is the cause. I tried deleting the computer record completely from config mgr (hence the Maccount=0), hoping for it to boot as an unknown computer but no dice. I then tried importing the computer using it's MAC and name as you said but the same thing happens just with a mac count as 1. I ran the "select Name0,SMBIOS_GUID0 from v_R_System" report and can confirm I have 57 duplicate SMBIOS GUID's from around 4-5 different models of laptop/PC's. I can't see how that could have happened... Just to clarify: With Deleted SCCM record: [LOG[MAC=00:19:DB:EB:22:B1 SMBIOS GUID=03000200-0400-0500-0006-000700080009 > Device found in the database. MacCount=0 GuidCount=57]LOG] [No Boot Action for Device (1403) found] [LOG[ProcessDatabaseReply: No Advertisement found in Db for device] With imported record using MAC and Name: [LOG[MAC=00:19:DB:EB:22:B1 SMBIOS GUID=03000200-0400-0500-0006-000700080009 > Device found in the database. MacCount=1 GuidCount=57]LOG] [LOG[No Boot Action for Device (1403) found]LOG] [LOG[ProcessDatabaseReply: No Advertisement found in Db for device]
August 12th, 2010 12:10pm

This is old, but for those out there that may be having this problem repeatedly, I have a bit of insight that may help. We have all Dell Optiplex systems, especially those in the GX270 and GX280 family from way back. Those units had terrible motherboard capacitor issues and lots of those boards were replaced. I never bothered checking, but when boards were shipped from Dell to replace the bad ones, they had no Service Tag set in the BIOS, which created a generic GUID when PXE booting. Using Dell's "ASSET.COM" utility and booting into a pure DOS environment, I was able to manually set the Service Tag (and Asset Tag since I was there), which gave the computer a unique GUID and solved my duplication problem in SCCM. Hope this helps someone out there!
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2011 12:11pm

Go to SCCM site Database->Modify Stored procedure-> NBS_Lookupdevice-> SET NOCOUNT ON IF @SMBIOS_GUID IN (Type all maching GUID) e. g. ('00020003-0004-0005-0006-000700080009','03000200-0400-0500-0006-000700080009') BEGIN SET @SMBIOS_GUID = '000000000-0000-0000-0000-0000000000000'; END ->& Execute @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ This work around seemed promissing as when i tested the SP in SQL using the Real MAC and the Real GUID it came back with 0 results for both... Elegant solution to pass in a non existant GUID when the GUID matches the IF requirement This solution got me past the PXE boot problem (abortpxe) and in the smspxe log it shows "Device Not Found" and "Optional Advertisement found" HOWEVER... :) Once you boot in PE it spits out "There are No Task Sequences Found for this Computer" It seems like there is a different method for looking up the GUID for Adv or TS. It seems to be using the real GUID and not the SP that fakes it out. So although this solution got us past the abortpxe issue, it still needs a way to bypass the GUID check when searching for Task Sequences... Any Ideas?
July 13th, 2011 12:33pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics