No PXE-Advertisements found for AD-imported Computers (Network Steve Forum)

No PXE-Advertisements found for AD-imported Computers

We are planning and testing a new infrastructure for OS and software-deployment with SCCM 2012 r2.

We would like to use AD computers and groups to manage OS deployment and software in SCCM with AD group- and system discovery and WQL-Queries for our Collections.

The first tests went very well, so AD discoveries and adding client computers to AD and SCCM working really good.

But we do have a problem with OS deployment for computers that were added to the SCCM with SMS_AD_SECURITY_GROUP_DISCOVERY.

For the testing environment we configured the WDS and SCCM to answer all unknown computers and our os deployment works without any issues for manually added computers. But as soon as a client were discovered through the AD discovery and where added to the OS deployment collection, the computer aborts the PXE boot, because the SCCM doesn't have an advertisement for it.

Ive got some lines out of the SMSPXE.log including a logged not PXE-booting client and a booting one. I hope someone can offer some help or workaround.

Getting boot action for unknown machine: item key: 2046820353	SMSPXE	18.03.2015 13:33:39	2884 (0x0B44)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	18.03.2015 13:33:40	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	18.03.2015 13:33:40	2884 (0x0B44)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152005" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	18.03.2015 13:37:58	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: device is in the database.	SMSPXE	18.03.2015 13:37:58	2884 (0x0B44)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152005" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	18.03.2015 13:37:58	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	18.03.2015 13:37:58	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: No boot action. Aborted.	SMSPXE	18.03.2015 13:37:58	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: Not serviced.	SMSPXE	18.03.2015 13:37:58	2884 (0x0B44)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152005" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	18.03.2015 13:38:02	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	18.03.2015 13:38:02	2884 (0x0B44)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777224" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	18.03.2015 13:41:50	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: device is in the database.	SMSPXE	18.03.2015 13:41:50	2884 (0x0B44)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777224" ServerName=""><Machine><ClientID>GUID:A83AE21E-94E9-4911-92F7-245C21ECBEC8</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BB120001" OfferIDTime="16.03.2015 13:23:00" PkgID="BB10000B" PackageVersion="" PackagePath="http://S25b0249.bebr.drv/SMS_DP_SMSPKG$/BB100002" BootImageID="BB100002" Mandatory="0"/></ClientIDReply>
	SMSPXE	18.03.2015 13:41:50	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: found optional advertisement BB120001	SMSPXE	18.03.2015 13:41:50	2884 (0x0B44)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777224" ServerName=""><Machine><ClientID>GUID:A83AE21E-94E9-4911-92F7-245C21ECBEC8</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BB120001" OfferIDTime="16.03.2015 13:23:00" PkgID="BB10000B" PackageVersion="" PackagePath="http://S25b0249.bebr.drv/SMS_DP_SMSPKG$/BB100002" BootImageID="BB100002" Mandatory="0"/></ClientIDReply>
	SMSPXE	18.03.2015 13:41:54	2884 (0x0B44)
00:15:5D:C9:85:0A, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: found optional advertisement BB120001	SMSPXE	18.03.2015 13:41:54	2884 (0x0B44)
Looking for bootImage BB100002	SMSPXE	18.03.2015 13:41:54	2884 (0x0B44)

March 19th, 2015 4:10am

But we do have a problem with OS deployment for computers that were added to the SCCM with SMS_AD_SECURITY_GROUP_DISCOVERY.

So there is/was no ConfigMgr client installed on those resources? That explains why it's not working because resources added by AD discovery do not contain smbios guids or MAC addresses (which are required for PXE boot).

Free Windows Admin Tool Kit Click here and download it now

March 19th, 2015 4:32am

Thank you for your answer.

Of course there is no Client installed as there is no OS installed.

After the AD Discovery we add the MAC address in SCCM manually. And as you can see in the log file, there is no problem for SCCM to identify the computer. The client just don't get the right boot file.

The client starts with PXE boot after getting a valid IP from the DHCP and gets an answer from WDS and is idenfied by SCCM, but instead of sending the bootfile "smsboot\x64\pxeboot.com" SCCM sends the bootfile "smsboot\x64\abortpxe.com", so the client doesn't get the boot.wim and aborts the PXE boot.

March 19th, 2015 5:00am

After the AD Discovery we add the MAC address in SCCM manually. And as you can see in the log file, there is no problem for SCCM to identify the computer. The client just don't get the right boot file.

How are you doing that?

What does smspxe.log tell for that machine (mac address)?

Free Windows Admin Tool Kit Click here and download it now

March 19th, 2015 6:47am

After SCCM discovered an AD Computer an added it to its database, we use the normal import-function for devices and add the same computer but with the valid MAC. SCCM just adds the MAC-address to the discovered computer object and sets the property adds "Manual Machine Entry" to the property "Agent Name".

Important properties after discovery:

"Agent Name" - "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT"

"MAC Addresses" - ""

Important Properties after aditional import:

"Agent Name" - "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT" ; "Manual Machine Entry"

"MAC Addresses" - "00:15:5D:C9:85:FF"

I would like to show you some screenshots I made, but I am not allowed to post pictures or links...

The PXELog for the AD-discovered computer looks like this:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152009" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: device is in the database.	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152009" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: No boot action. Aborted.	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: Not serviced.	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152009" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	20.03.2015 13:30:22	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	20.03.2015 13:30:22	4308 (0x10D4)

For a client that was added manually and is in the same collections, AD-Groups and has the same DHCP-Reservations (with other IP and MAC-address of course) the PXE-Boot successes:

It gets the right Task Sequence and OS and is ready for action. The PXELog for this one looks like this:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
00:15:5D:C9:85:09, 915F29BB-B1EE-44B2-8376-7A0D7415C16F: device is in the database.	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID>GUID:A342BCA0-F2E8-4FF8-AED1-D03F1F8F99D3</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BB120001" OfferIDTime="16.03.2015 13:23:00" PkgID="BB10000B" PackageVersion="" PackagePath="http://S25b0249.bebr.drv/SMS_DP_SMSPKG$/BB100002" BootImageID="BB100002" Mandatory="0"/></ClientIDReply>
	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
00:15:5D:C9:85:09, 915F29BB-B1EE-44B2-8376-7A0D7415C16F: found optional advertisement BB120001	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID>GUID:A342BCA0-F2E8-4FF8-AED1-D03F1F8F99D3</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BB120001" OfferIDTime="16.03.2015 13:23:00" PkgID="BB10000B" PackageVersion="" PackagePath="http://S25b0249.bebr.drv/SMS_DP_SMSPKG$/BB100002" BootImageID="BB100002" Mandatory="0"/></ClientIDReply>
	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
00:15:5D:C9:85:09, 915F29BB-B1EE-44B2-8376-7A0D7415C16F: found optional advertisement BB120001	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
Looking for bootImage BB100002	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
BootImage BB100002 needs to be updated (new packageID=BB100002) VersionUpdate=true	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
PXE::CBootImageInfo::CBootImageInfo: key=BB100002	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
Saving Media Variables to "D:\RemoteInstall\SMSTemp\2015.03.20.13.32.28.0001.{237F4BF3-E462-4F4A-8085-5580A72F6499}.boot.var"	SMSPXE	20.03.2015 13:32:28	4308 (0x10D4)

So why does the AD-Discovered client doesn't get the right Boot-File?

In a 3rd-Party Forum I found this post, but I don't know if this could be the issue and if there would be a possible solution.

"I wanted to share with you what Microsoft told me. With SP1 they have changed a view due to performance reasons. That view is vLocalResourceIDXRef. I am guessing this is the view where the pxe machines look for advertisements.

they changed it to

SELECT MachineID, GUID, ArchitectureKey FROM MachineIdGroupXRef     
   WHERE (ArchitectureKey = 5 AND MachineID BETWEEN 16777216 AND 33554431) OR (ArchitectureKey != 5)        
       	 UNION ALL        
   SELECT MachineID, GUID, ArchitectureKey FROM vCASSystemIDXRef

I don't know what the second number used to be, but certainly higher. So .....

An imported machine has an ID 16'777'XXX. -> pxe boots just fine

An AD Group Discovered machine has the ID 2'097'15X'XXX

If you import a machine that has been discovered with the ad system group discovery (same name) it will merge into the ad group discovered object and therefore has a 2 Billion ID. Which will be filtered out by the vLocalResourceIDXRef view. -> does not pxe boot

In other words, you cannot dynamically add software via AD Group while staging a machine. :angry:

Unless you guys have hint.

The goal is to provision a machine with additional individual sw via AD Groups, and let it install during the TS."

Edited by Schawarmaman 18 hours 22 minutes ago

March 20th, 2015 9:17am

Adding a MAC to a resource discovered by AD discovery results in what you are seeing: it does not work. There's a similar discussing going on in our MVP email list. Microsoft is ware of it. I'll update the thread if I am able to get more details.

Free Windows Admin Tool Kit Click here and download it now

March 20th, 2015 9:36am

Ok, thank you!

March 20th, 2015 10:22am

Important properties after discovery:

"Agent Name" - "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT"

"MAC Addresses" - ""

Important Properties after aditional import:

"Agent Name" - "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT" ; "Manual Machine Entry"

"MAC Addresses" - "00:15:5D:C9:85:FF"

I would like to show you some screenshots I made, but I am not allowed to post pictures or links...

The PXELog for the AD-discovered computer looks like this:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152009" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: device is in the database.	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152009" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: No boot action. Aborted.	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: Not serviced.	SMSPXE	20.03.2015 13:30:18	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2097152009" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
	SMSPXE	20.03.2015 13:30:22	4308 (0x10D4)
00:15:5D:C9:85:FF, E985A1CA-CBF4-4FDB-8853-D78A85BBE644: no advertisements found	SMSPXE	20.03.2015 13:30:22	4308 (0x10D4)

For a client that was added manually and is in the same collections, AD-Groups and has the same DHCP-Reservations (with other IP and MAC-address of course) the PXE-Boot successes:

It gets the right Task Sequence and OS and is ready for action. The PXELog for this one looks like this:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
00:15:5D:C9:85:09, 915F29BB-B1EE-44B2-8376-7A0D7415C16F: device is in the database.	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID>GUID:A342BCA0-F2E8-4FF8-AED1-D03F1F8F99D3</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BB120001" OfferIDTime="16.03.2015 13:23:00" PkgID="BB10000B" PackageVersion="" PackagePath="http://S25b0249.bebr.drv/SMS_DP_SMSPKG$/BB100002" BootImageID="BB100002" Mandatory="0"/></ClientIDReply>
	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
00:15:5D:C9:85:09, 915F29BB-B1EE-44B2-8376-7A0D7415C16F: found optional advertisement BB120001	SMSPXE	20.03.2015 13:32:17	4308 (0x10D4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID>GUID:A342BCA0-F2E8-4FF8-AED1-D03F1F8F99D3</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BB120001" OfferIDTime="16.03.2015 13:23:00" PkgID="BB10000B" PackageVersion="" PackagePath="http://S25b0249.bebr.drv/SMS_DP_SMSPKG$/BB100002" BootImageID="BB100002" Mandatory="0"/></ClientIDReply>
	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
00:15:5D:C9:85:09, 915F29BB-B1EE-44B2-8376-7A0D7415C16F: found optional advertisement BB120001	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
Looking for bootImage BB100002	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
BootImage BB100002 needs to be updated (new packageID=BB100002) VersionUpdate=true	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
PXE::CBootImageInfo::CBootImageInfo: key=BB100002	SMSPXE	20.03.2015 13:32:22	4308 (0x10D4)
Saving Media Variables to "D:\RemoteInstall\SMSTemp\2015.03.20.13.32.28.0001.{237F4BF3-E462-4F4A-8085-5580A72F6499}.boot.var"	SMSPXE	20.03.2015 13:32:28	4308 (0x10D4)

So why does the AD-Discovered client doesn't get the right Boot-File?

In a 3rd-Party Forum I found this post, but I don't know if this could be the issue and if there would be a possible solution.

SELECT MachineID, GUID, ArchitectureKey FROM MachineIdGroupXRef     
   WHERE (ArchitectureKey = 5 AND MachineID BETWEEN 16777216 AND 33554431) OR (ArchitectureKey != 5)        
       	 UNION ALL        
   SELECT MachineID, GUID, ArchitectureKey FROM vCASSystemIDXRef

Edited by Schawarmaman Friday, March 20, 2015 1:19 PM

Free Windows Admin Tool Kit Click here and download it now

March 20th, 2015 1:16pm

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