Jump to content


JHFerry

PXE boot from DP failing, Error "Configuration Manager is looking for policy"

Recommended Posts

I am trying to boot from a new 2012 R2 DP. Here is the log:

================= PXE Provider loaded. ===================== SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1) SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
MAC Ignore List Filename in registry is empty SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Begin validation of Certificate [Thumbprint 02FA01EFEA7B82FABDEA9FA5499D14CDBD840F56] issued to '38ba0a61-4b5d-4b2f-acfa-400e764812c5' SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Completed validation of Certificate [Thumbprint 02FA01EFEA7B82FABDEA9FA5499D14CDBD840F56] issued to '38ba0a61-4b5d-4b2f-acfa-400e764812c5' SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Initializing PXEPerfObject. SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Client is set to use HTTPS when available. The current state is 192. SMSPXE 4/28/2015 11:17:00 AM 1372 (0x055C)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/28/2015 11:17:01 AM 1372 (0x055C)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 4/28/2015 11:17:01 AM 1372 (0x055C)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 4/28/2015 11:17:01 AM 1372 (0x055C)
Adding NOC00002.5 SMSPXE 4/28/2015 11:17:01 AM 1372 (0x055C)
Adding NOC00005.5 SMSPXE 4/28/2015 11:17:06 AM 1372 (0x055C)
Found new image NOC00002 SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
ADK installation root registry value not found. SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Opening image file E:\RemoteInstall\SMSImages\NOC00002\boot.NOC00002.wim SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Found Image file: E:\RemoteInstall\SMSImages\NOC00002\boot.NOC00002.wim
PackageID: NOC00002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Closing image file E:\RemoteInstall\SMSImages\NOC00002\boot.NOC00002.wim SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Found new image NOC00005 SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
ADK installation root registry value not found. SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Opening image file E:\RemoteInstall\SMSImages\NOC00005\boot.NOC00005.wim SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Found Image file: E:\RemoteInstall\SMSImages\NOC00005\boot.NOC00005.wim
PackageID: NOC00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Closing image file E:\RemoteInstall\SMSImages\NOC00005\boot.NOC00005.wim SMSPXE 4/28/2015 11:17:13 AM 1372 (0x055C)
Begin validation of Certificate [Thumbprint 02FA01EFEA7B82FABDEA9FA5499D14CDBD840F56] issued to '38ba0a61-4b5d-4b2f-acfa-400e764812c5' SMSPXE 4/28/2015 11:17:14 AM 1372 (0x055C)
Completed validation of Certificate [Thumbprint 02FA01EFEA7B82FABDEA9FA5499D14CDBD840F56] issued to '38ba0a61-4b5d-4b2f-acfa-400e764812c5' SMSPXE 4/28/2015 11:17:14 AM 1372 (0x055C)
PXE Provider finished loading. SMSPXE 4/28/2015 11:17:14 AM 1372 (0x055C)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/28/2015 11:18:41 AM 3612 (0x0E1C)
8C:DC:D4:3E:52:FE, AC887480-CD27-11E4-916B-8CDCD43E52FE: device is not in the database. SMSPXE 4/28/2015 11:18:41 AM 3612 (0x0E1C)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 4/28/2015 11:18:42 AM 3612 (0x0E1C)
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 4/28/2015 11:18:42 AM 3612 (0x0E1C)
8C:DC:D4:3E:52:FE, AC887480-CD27-11E4-916B-8CDCD43E52FE: no advertisements found SMSPXE 4/28/2015 11:18:42 AM 3612 (0x0E1C)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 4/28/2015 11:26:51 AM 1300 (0x0514)
MAC Ignore List Filename in registry is empty SMSPXE 4/28/2015 11:26:51 AM 1300 (0x0514)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 4/28/2015 11:26:53 AM 1300 (0x0514)
MAC Ignore List Filename in registry is empty SMSPXE 4/28/2015 11:26:53 AM 1300 (0x0514)

Everything looks ok but I get the error "Configuration Manager is looking for policy"

Any ideas?

Share this post


Link to post
Share on other sites

The unknown computers collection should only contain two objects, one for x86 and one for x64.

Those 2 objects are there. I verified via a report that the mac address of this PC is not in config manager so that explains the looking for policy error. Now the question is, how is it I begin pxe booting, get and IP and get to my dp but it never shows up anywhere in SCCM. I thought maybe the task sequence being deployed to unknown computers was not working because somehow the computer was known.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.