none
PXE - Please wait. SMS is waiting for policy

    Question

  • Hi,

    I had a problem with one of my SCCM 2012 deployments. The PXE feature somehow won't work. It's same error with all PXE enabled DPs "Please wait. SMS is waiting for policy" . I tried on the known, unknown or imported Computers but it's same. I have available task sequence deployments on Unknown computers, collections and imported computers. I can use boot media or agent to deploy OS with the same PCs without a problem. I used PXE with SCCM 2012 many times and again I done nothing different than usual this time.  I upgraded to SCCM 2012 SP1 but issue continue.

    Anyone have ideas what is wrong?

    SMSPXE.log

    ================= PXE Provider loaded. ===================== SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1) SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    MAC Ignore List Filename in registry is empty SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Begin validation of Certificate [Thumbprint 93BBEC0D2172E3AEFEDD1B84E589E53EE8914250] issued to '49c83972-5571-4224-b6d0-5334da6e87f8' SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Completed validation of Certificate [Thumbprint 93BBEC0D2172E3AEFEDD1B84E589E53EE8914250] issued to '49c83972-5571-4224-b6d0-5334da6e87f8' SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Initializing PXEPerfObject. SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Could not load logging configuration for component ccmperf. Using default values. SMSPXE 2/26/2013 11:28:21 AM 9784 (0x2638)
    Client is set to use HTTPS when available. The current state is 192. SMSPXE 2/26/2013 11:28:22 AM 9784 (0x2638)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 2/26/2013 11:28:22 AM 9784 (0x2638)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 2/26/2013 11:28:22 AM 9784 (0x2638)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 2/26/2013 11:28:22 AM 9784 (0x2638)
    Adding IGD00003.10 SMSPXE 2/26/2013 11:28:22 AM 9784 (0x2638)
    Adding IGD00004.9 SMSPXE 2/26/2013 11:28:26 AM 9784 (0x2638)
    Found new image IGD00003 SMSPXE 2/26/2013 11:28:31 AM 9784 (0x2638)
    Opening image file D:\RemoteInstall\SMSImages\IGD00003\boot.IGD00003.wim SMSPXE 2/26/2013 11:28:31 AM 9784 (0x2638)
    Found Image file: D:\RemoteInstall\SMSImages\IGD00003\boot.IGD00003.wim
     PackageID: IGD00003
     ProductName: Microsoft® Windows® Operating System
     Architecture: 0
     Description: Microsoft Windows PE (x86)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 2/26/2013 11:28:31 AM 9784 (0x2638)
    Closing image file D:\RemoteInstall\SMSImages\IGD00003\boot.IGD00003.wim SMSPXE 2/26/2013 11:28:31 AM 9784 (0x2638)
    Found new image IGD00004 SMSPXE 2/26/2013 11:28:36 AM 9784 (0x2638)
    Opening image file D:\RemoteInstall\SMSImages\IGD00004\boot.IGD00004.wim SMSPXE 2/26/2013 11:28:36 AM 9784 (0x2638)
    Found Image file: D:\RemoteInstall\SMSImages\IGD00004\boot.IGD00004.wim
     PackageID: IGD00004
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 2/26/2013 11:28:36 AM 9784 (0x2638)
    Closing image file D:\RemoteInstall\SMSImages\IGD00004\boot.IGD00004.wim SMSPXE 2/26/2013 11:28:36 AM 9784 (0x2638)
    Begin validation of Certificate [Thumbprint 93BBEC0D2172E3AEFEDD1B84E589E53EE8914250] issued to '49c83972-5571-4224-b6d0-5334da6e87f8' SMSPXE 2/26/2013 11:28:42 AM 9784 (0x2638)
    Completed validation of Certificate [Thumbprint 93BBEC0D2172E3AEFEDD1B84E589E53EE8914250] issued to '49c83972-5571-4224-b6d0-5334da6e87f8' SMSPXE 2/26/2013 11:28:42 AM 9784 (0x2638)
    PXE Provider finished loading. SMSPXE 2/26/2013 11:28:42 AM 9784 (0x2638)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778761" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 2/26/2013 11:30:26 AM 6416 (0x1910)
    00:15:5D:02:68:09, 94886EFC-DF3B-49B8-947D-B4582C832A1B: device is in the database. SMSPXE 2/26/2013 11:30:26 AM 6416 (0x1910)

    Tuesday, February 26, 2013 9:28 AM

All replies

  • Have you enabled "Deploy this boot image from the PXE service point" under the Data Source tab on your Boot Images?

    Best Regards
    Claus Codam
    Consultant, Developer
    Coretech - Blog

    Wednesday, February 27, 2013 2:00 AM
  • Yes and I can verify the files in RemoteInstall folder
    Wednesday, February 27, 2013 7:16 AM
  • have you done this for BOTH architecture boot images ? infact have you enabled PXE as described here ?

    when you deployed your task sequence did you deploy it to a collection that this computer is a member of ? did you deploy the task sequence to Configuration Manager Clients, Media and PXE ?



    Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady

    Wednesday, February 27, 2013 11:11 AM

  • Yes, I enabled PXE on more than one DPs just like that, and then checked the configuration again and again (this is not my first time to work with PXE). Even try to reinstall PXEs, and installed MDT2012SP1 . Same task seq. works with Boot media and Configuration Manager client and also with known and unknown computers. Either I missed something or there is an external problem affects the SCCM PXE I think.
    Thursday, February 28, 2013 9:31 AM
  • Hello

    Has anyone found a fix for this? I am also seeing the same issue. I have done the above checks as Erdem. Thanks

    Tuesday, March 26, 2013 1:53 PM
  • Hi

    I had a similar issue, same notification waiting for the policy, I found out that because the mac address of the that computer was already assign with a SCCM client, in simple the computer I'm trying to PXE boot was previously SCCM client installed computer. so it trying to contact the client policy.

    I have resolved it using deleting mac entry on SCCM database, or find the exact computer name from SCCM console and deleting it from it. (if the computer was formatted you have to find the old computer name).

    that solved my issue, hope this was helpful :)


    Asitha

    Wednesday, March 27, 2013 5:22 PM
  • PXE needs to be enabled on Task Sequence deployment not just the MP. Check deployment settings tab of the Task Sequence deployment.

    If the Task Sequence only works when you delete the device, the Task Sequence may be only deployed to the “All Unknown Computers” collection.

    Monday, April 01, 2013 10:52 PM
  • I fixed my issue by updating the x64 boot image. I was able to pxe afterwards. thanks
    • Proposed as answer by Klaas Arendsen Thursday, April 04, 2013 9:15 AM
    Wednesday, April 03, 2013 12:05 PM
  • Same problem and solution here.
    I just added my desired optional components to the boot image, which prompted a rebuild and all worked fine afterward.

    You should mark this as the answer.


    • Edited by BranM Wednesday, August 07, 2013 5:01 AM
    • Proposed as answer by BranM Wednesday, August 07, 2013 5:02 AM
    Wednesday, August 07, 2013 5:01 AM
  • What did you update on your boot.wim to get it working?

    I am having this problem booting an ESX 5.1 VM to my new installed SCCM 2012 (WDS) server.

    This is a 'bare metal' VM with no OS installed on its hard disk.

    Any suggestions?

    Tuesday, December 17, 2013 10:27 PM