SCCM 07 PXE OSD Message PXE-51 No DHCP or ProxyDHCP

Regional office trying to OSD and getting PXE-E51 No DHCP or ProxyDHCP message.
All other regional offices work fine. This regional office worked fine a few months ago, they do limited imaging so that is why its been so long.
Troubleshooting:
Checked Scope Options and 066 and 067 are enabled.
Tried different laptop and different port and same result.
Stopped WDS service. Deleted C:\Windows\Temp\PXEBootFiles restarted WDS service.
Boot the computer to windows and was able to get DHCP just fine
Rebooted the server
I also ran wdsutil
/initialize-server /REMINST:"D:\remoteinstall"
checked smspxe.log - No error messages
Last few lines in log are:
GetSiteTypeAndDefaultMP: SiteType=2 DefaultMP=DENSCCM.STM.AD  smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
Site Type: 2 smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
GetUnknownMachineResource (DEN,x86): smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
GetUnknownMachineResource: 2bd26a41-38a9-4360-81bd-c698b4beaa28, 3 smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
GetUnknownMachineResource (DEN,x64): smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
GetUnknownMachineResource: 023762cf-7533-4860-a4e9-d2e6d35ffa6a, 4 smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
Loaded PXE settings from DB: Unknown machine GUIDs: (x86) 2bd26a41-38a9-4360-81bd-c698b4beaa28, (x64) 023762cf-7533-4860-a4e9-d2e6d35ffa6a smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
No need to check cert smspxe 1/29/2013 12:27:22 PM 2008 (0x07D8)
[010.019.010.088:4011] Recv From:[010.019.010.088:9000] Len:274 12e4d30 smspxe 1/29/2013 12:27:59 PM 2348 (0x092C)
[010.019.010.088:4011] Recv From:[010.019.010.088:9000] Len:274 12dc0b0 smspxe 1/29/2013 12:32:59 PM 2348 (0x092C)

it's not receiving a DHCP response when the PXE ROM issues a DHCP discover.
I've read a few things over time about some specific models doing this, but haven't encountered it personally.
some suggestion that a BIOS update might help?
http://fogproject.org/forum/threads/pxe-boot-menu-not-working-on-dell-latitude-e6510.3705/
http://fogproject.org/forum/threads/pxe-boot-menu-not-working-on-dell-latitude-e6510.3699/
http://support.dell.com/support/edocs/NETWORK/9195P/en/BootAgnt/ba_msgs.htm
ensure that your switching infrastructure is configured to suit (eg STP-portfast etc, although a portfast problem will not impact PXE in my experience)
maybe try a little 4-port switch or hub, between the laptop and the main switch? (to isolate a media negotiation issue)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

  • SCCM 2012R2 PXE via IpHelper

    Hi Everyone,
    I'm trying to deploy SCCM2012R2 task sequence via PXE with IpHelpers.
    I've configured the IPHelpers to point to the SCCM DP PXE and the DHCP, but nothing happen.
    Has someone a quick guide on how to configure SCCM2012 and iphelper?

    Hi,
    Have you resolved this issue? If not, please try to use Network Monitor to check whether the IP Helper works fine.
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012: PXE deploy: import boot images?

    Hi,
    We fully configured sccm 2012 and did osd via bootable media. Now we want to configure PXE.
    We enabled it (http://prajwaldesai.com/deploying-sccm-2012-part-14-build-and-capture-windows-7-64-bit/).
    My questions:
    *Is that all that needs to be done?
    *It seems to me we need to import boot images in WDS?
    *If we do, which to import then (both x86 and x64 probably) + there is a winpe and a winpe.....wim made by sccm, which one to import then?
    *on DHCP we change the boot server hostname but what about the bootfile name, what is the path of that? \boot\x64\wdsnbp.com?
    Please advise.
    J.
    Jan Hoedt

    I keep on getting TFTP open timeout
    I find in smspxe.log that it reaches to the SCCM-server but then something goes wrong. Not sure what.
    How can I troubleshoot find more info, please advise?
    00:51:55:2A:5C:C5, 0A190A42-FFDe6-5e69-9e41-70e481B852E3: device is not in the database.    SMSPXE    21/03/2014 16:10:08    2720 (0x0AA0)
    Getting boot action for unknown machine: item key: 2046820352    SMSPXE    21/03/2014 16:10:08    2720 (0x0AA0)
    CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX    SMSPXE    21/03/2014 16:10:08    2720 (0x0AA0)
    CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80  CCM_POST /ccm_system/request    SMSPXE    21/03/2014 16:10:08    2720 (0x0AA0)
    Jan Hoedt
    Note: what I also can see:
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 000.000.000.000

  • SCCM 2012 PXE issues with Acer Machines?

    Hi,
    I am having a strange issue with PXE trying to build a machine with a Windows 7 Task Sequence.
    Ok here is the synario - I have 2 machines that do not get any offers from PXE - so I get that error No DHCP
    or proxy DHCP offers were received. However if I make a bootable USB key and boot the *same* machines my
    task sequence appears on the menu that I can select. (The task sequence is deployed to PXE and Media BTW).
    Now it gets strange - if I take other machines and put the on the same network cable and F12 them PXE works
    and I get the task sequence presented. So same PXE server - same DHCP server.
    So from my logic I figure if I had a policy type problem then it would not present the task sequence when
    I try the boot usb.
    Both the machines I am having issues with are ACER btw if people know of any know issues. I am starting
    to suspect I have faulty hardware etc. One machine is a Acer Travelmate P633-V Laptop and the other machine is
    Acer Veriton VS6620G desktop.
    Any suggestions on how to resolve this - it seem very strange.
    My environment is SCCM 2012 SP1 btw.
    Is there something I am missing here :)
    Thanks,
    Ward.

    Hi,
    Thanks for all the sugestions. I can confirm that the machines
    when an OS is on them do register the IP addresses with the DHCP/WDS server (same box). Also I can confirm the Unknown computer support is turned on the box in SCCM 2012 on the DP.
    Ok but I did get one working which I can't explain why it works
    the way it does.
    On the notebook if I enable secure boot (UEFI) and boot with PXE
    it works :) It appears the stupid BIOS turns this on but disables
    another setting called "Network Boot" which is crazy. So if
    you turn both on Secure boot enabled and "Network Boot" is on it works.
    Now here is the puzzle that still stumps me - switch this back to
    legacy mode and no go - no PXE. Boot other non UEFI machines and
    they PXE boot.
    The WDS/DHCP/SCCM DP server is Windows 2008 (all on one box) as I understand it does not support UEFI PXE - this is in Windows 2012. I don't think there is an option in SCCM 2012 for it.
    So can somebody offer me a technical explination?
    Is there something else I am missing?
    I still am trying to work out how to get the desktop to UEFI PXE boot if this is possible.
    Thanks,
    Ward

  • SCCM 2012 PXE setup error PXE-E7B - Missing MTFTP Server IP Address

    Have just configured PXE on our new SCCM 2012 server.  Seems like it should be simple to setup.  66/67 options are setup as is IPhelper.
    When PXE booting a client it hangs at the DHCP prompt and then throws the following error:
    PXE-E7B - Missing MTFTP Server IP Address
    Any ideas what the problem might be?
    Thanks

    PXE is enabled on DP and WDS service running fine.  There are both 32 and 64 PXE enabled boot images uploaded on DP. When trying to PXE boot a VM on the same subnet as the SCCM 2012 server you see entries in the smspxe.log.  The PXE doesn't
    work because there's no DHCP scope available, but you can see PXE reacting and it throws a different error PXE-E52: No DHCP offers were received.  When you try PXE booting on a different subnet nothing appears in smspxe.log, as you say it's like it's
    not seeing the PXE traffic at all.
    Network guys have confirmed IP helper setup for old and new SCCM servers.  Discard, echo, and 4001 access allowed. 

  • PXE-E51: No DHCP or Proxy DHCP offers were received

    Ok so I'm new to this and decided hey lets have a go.
    I got it all working great and then all of a sudden after a server reboot I got this:
    PXE-E51: No DHCP or Proxy DHCP offers were received
    My DHCP,DNS,AD and WDS are all on the same box, I spent hours trawling the net and didn't find the answer to my problem but have stumbled across it although about 10hours wasted for a really simple solution
    The cause: seems my WDS side is loading before my DHCP is having chance to establish hense WDS can not talk to DHCP to get the pxe connection going.
    What did I find:
    If i close the GUI for WDS and open the GUI for DHCP, find my server int he tree and right click then select restart.  wait for this to complete (that's the important part)
    Once the above is done open my GUI for WDS and again find the relevant point in the tree, right click and restart
    Low and behold my connected laptop is now able to connect to the WDS.
    I posted this in hope that it will save someone else a heck of a lot of time (can't promise your issue is the same as mine as there are so many different possibilities.)

    Because PXE and DHCP use the same protocol and listen on the same ports, having them on the same box is unwise. There is a work-around but the better option is to put the two services on different systems. The work-around involves configuring the
    WDS server to use alternate ports as briefly discussed here:
    http://technet.microsoft.com/en-us/library/cc771734(v=WS.10).aspx .
    Jason | http://blog.configmgrftw.com

  • Fasten the Process of MDT UDI OD Installation in SCCM 2012 R2 OSD

    Hi,
    I have implemented MDT UDI Task Sequence in SCCM 2012 R2 OSD. The issue  which I am facing is the UDI Installation progress is very slow. it is taking around 2 hours to complete the whole Installation. 
    Is there any way to fasten the Process of MDT UDI OD Installation in SCCM 2012 R2 OSD.
    Thanks & Regards,
    Sanjay Dubey

    Application installs can take awhile - it depends on what applications you're installing, and how many.  For instance, installing Office is clearly going to take longer than say 7-Zip.  How many applications are you installing during a normal OS
    deployment?  You can check the AppEnforce.log to see how long an application(s) is taking to install, as the start and end times are recorded.  
    As for the MDT Settings package, how many times are you calling this package?  My task sequence only calls it 5 times, and one of them is before you even get the UDI wizard, while the second and third is an either/or situation, depending on whether
    you do a refresh or a fresh PC build. 

  • SCCM 2012 pxe boot issue

    My test machines cannot PXE boot.
    My lab environment is very simple:
    10.10.0.0/24 subnet
    10.10.0.5 = Server2012, DHCP, DNS, SQL Server 2008 R2 Sp2
    10.10.0.7 = Server2012, SCCM2012
    All machines are Oracle VM Box virtual machines connecting through the same virtual network.
    Setup the PXE service from DP properties.  I let SCCM install WDS.  WDS in Server
    Manager does not have a server node, but the WDS service is running.  DP PXE tab is configured as follows:
    "Enable PXE support for clients" is checked
    "Allow this distribution point to respond to incoming PXE requests" is checked
    "Enable unknown computer support" is checked
    "Require a password when computers use PXE" is not checked
    "User device affinity" is set to "Allow user device affinity with automatic approval"
    PXE is configured to respond on all network interfaces
    The PXE server response delay is 0 seconds
    The DHCP server has options configured as follows:
    Option 66: 10.10.0.7
    Option 67: smsboot\x86\wdsnbp.com
    Both DP and MP on SCCM server are configured for HTTP.
    Both x86 and x64 boot images have been distributed to DP.  The media was updated after
    PXE was enabled on the DP.
    Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties
    SMSPXE.Log
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="15:05:09.346-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592" file="libsmsmessaging.cpp:6544">
    <![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: no advertisements found]LOG]!><time="15:05:09.346-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592"
    file="database.cpp:483">
    <![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: No boot action. Aborted.]LOG]!><time="15:05:09.441-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592"
    file="database.cpp:483">
    <![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: Not serviced.]LOG]!><time="15:05:09.441-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592" file="database.cpp:483">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="15:05:09.705-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592" file="libsmsmessaging.cpp:6544">
    <![LOG[08:00:27:61:59:79, BF2ACCDD-1455-E149-963C-9A845B9C111E: no advertisements found]LOG]!><time="15:05:09.705-330" date="07-07-2014" component="SMSPXE" context="" type="1" thread="13592"
    file="database.cpp:483">

    Resource ID is already present in the Unknown Computer (Windows 7) Properties please look into it and
    OSD Task Sequences is there :(.

  • SCCM 2007 PXE point role uninstallation

    Hi Friends,
    I am working on dead line and I have found a solution on forums for PXE boot problems I want to try uninstall WDS and uninstall PXE role unfortunately I did not find any thing which makes sense to me on forums . Can anyone help me to get through the way...?
     Appreciate quick response.
    Many thanks..
    Mo

    None of these answer have helped. I have read that same TechNet article too many times over.
    I removed PXE service point in configmgr, and awaited a successful uninstall message in PXEsetup.log
    Never showed, I've tried everything to get a succssessful uninstall but there is so little information outside of the unhelpful information in this question and the TechNet articles.
    Is there a way to rekick off the uninstall? Originally the logs on the parent site server indicated that it would reattempt an uninstall after 60 minutes. However that message is gone after a few days of waiting and now it only gives the error that PXE is
    not responding, even though the role is no longer defined in SCCM.
    Bottum line I need a sure fire fix to remove PXE.

  • SCCM WDS PXE Boot Authentication

    Hi All,
    The ability to do domain authentication for a PXE boot in RIS could be achieved by modifying the security directly on the image folder on the RIS server - however, I can't seem to implement the same access control in SCCM 2007 SP1 using WDS.
    I have set up the capability to build bare metal machines using the OS Deployment feature in SCCM. The image process is advertised to “All Unknown Computers” and starts with the “builder” hitting F12 on the workstation. The boot image is loaded from the DP share and then the process begins.
    My question is: How can I protect the PXE boot process by having the system request a domain Username and Password in order to begin the PXE boot process and also limit who can see the advertisements for the avialable images.
    Thanks,
    phil

    Hi,
    You can specify a password for computers that boot to PXE.
    For more info :
    http://technet.microsoft.com/en-us/library/bb680668.aspx
    http://blogs.technet.com/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx
    http://technet.microsoft.com/en-us/library/bb632767.aspx
    Regards.
    Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

  • SCCM 2012 PXE boot

    Hi All,
    I have some weird issue in which i am trying to image Esprimo C720 desktop.
    It is working perfectly fine if i create a standalone image via USB and build it.
    But when i try to PXE boot the same device, it takes ip and boots up after windows screen it restarts. I thought it wud be network drivers and i have updated the same in winpe but still it doesnt work.
    I feel Esprimo C720 is not supported for PXE boot. Can any one advice me if you wud have come across this issue
    Regards, Pratap

    Hi,
    I recommend you check the log file smsts.log.
    This can be found in one of several locations depending on the progress of the build and the architecture of the OS:
    Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log
    Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
    Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
    Full version Windows after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
    Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
    After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log
    After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012R2 PXE Boot Selection?

    PXE Use to be so easy with MDT, Select the version of the Boot.wim file (32/64Bit) and go..
    But now SCCM Chooses for us, and when you deploy a 32bit OS, Tool, or Setting to a collection, than Everything inside of that collection boots to 32bit PXE - ultimately failing the TS because its not 64Bit.
    Any way to force SCCM to give you the option of 32Bit or 64Bit before it downloads and mounts it?

    Hi,
    I would say that Johans example only works for MDT and not ConfigMgr. There is no such option as when you boot you have already started on the wrong boot file from the PXE server. Where does it fail? You can with the exeption of UEFI computers boot on a
    x86 image and deploy an x64 image.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM 2012 - PXE error

    Hi Experts,
    I need some clarity on PXE boot
    1. My PXE point (Secondary Server) has IP subnet with 10.171.X.X and I am trying to build the machine from the next building which is 10.6.X.X series. When I PXE boot I get the below error
    PXE-E53 - No Boot Filename received
    PXE-MOF- Exiting Intel Boot Agent
    Do I need to enable IP helper on the switch level to PXE boot?
    2. WDS is configured to respond to all client computer and from boot image properties "Deploy from PXE enabled distribution point is enabled" Please help
    Regards, Pratap

    1. Yes. PXE as a protocol is limited to a broadcast/subnet boundary. Enabling IP helpers is the preferred way to direct the PXE broadcasts across subnets.
    2. I don't understand what the issue. Please provide more information, define your issue, and your expectations.
    Jason | http://blog.configmgrftw.com

  • SCCM 2012 PXE erro windows failed to start. A required device isn't connected or can't be accessed.

    I'd have an issue with the below PXE Log. I have checked the PXE boot.wim and it all checks out with 6.2.9200.16384.
    Would appreciate some insights .
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777848" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 21/08/2014 8:38:45 PM 6852 (0x1AC4)
    00:23:24:11:7B:25, F0D460E2-89A9-11DF-BBDA-24117B250023: device is in the database. SMSPXE 21/08/2014 8:38:45 PM 6852 (0x1AC4)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777848" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:35AA835A-E5D6-4D68-A989-86728CCB60D4</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="00120018" OfferIDTime="21/08/2014 7:07:00 PM" PkgID="00100035" PackageVersion="" PackagePath="http://srv-01/SMS_DP_SMSPKG$/001000005"
    BootImageID="00100005" Mandatory="0"/></ClientIDReply>
     SMSPXE 21/08/2014 8:38:45 PM 6852 (0x1AC4)
    00:23:24:11:7B:25, F0D460E2-89A9-11DF-BBDA-24117B250023: found optional advertisement 00120018 SMSPXE 21/08/2014 8:38:45 PM 6852 (0x1AC4)
    Looking for bootImage 00100005 SMSPXE 21/08/2014 8:38:45 PM 6852 (0x1AC4)

    Hi,
    Could you please upload the log to OneDrive ?
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 - PXE-E32: TFTP Open timeout

    Hi
    When I trying deploy through PXE in the vmware workstation 10.0, I'm getting the error below
    Error: PXE-E32: TFTP Open timeout
              TFTP....
    The machine got the IP addresss and I'm stop in below error
    Client MAc ADDR: 00 0C 29 6C 3F   GUID: xxxxxxxxxxxxxxx
    Client IP : 192.168.100.15    MASK: 255.255.255.0   DHCP IP : 192.168.100.254
    GATEWAY IP:  192.168.100.1     192.168.100.2
    PXE-E32: TFTP Open timeout
    TFTP....
    Robert

    Hi
    I'm getting this error in the SMS PXE logs   " device is not in the database" and "device is in the database" . Even the device in the database I'm getting the same error
    step that I did:
    a. Manually Adding the Device the MAC
    b. Manually Adding the Device the MAC  and the GUID
    c. Advertise in the "Uknown Computer"   and Advsertise in the "TEST Collection" where I added the MAC address and gUID
    Please find below the error
    <![LOG[Begin validation of Certificate [Thumbprint 9733001C4F488EE84A86A2DC81479F7D3262A9C3] issued to '8d4012f3-7252-4e85-891a-b4ff4421a1e4']LOG]!><time="07:48:03.370-240" date="10-28-2013" component="SMSPXE" context=""
    type="1" thread="5608" file="ccmcert.cpp:1245">
    <![LOG[Completed validation of Certificate [Thumbprint 9733001C4F488EE84A86A2DC81479F7D3262A9C3] issued to '8d4012f3-7252-4e85-891a-b4ff4421a1e4']LOG]!><time="07:48:03.370-240" date="10-28-2013" component="SMSPXE" context=""
    type="1" thread="5608" file="ccmcert.cpp:1386">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="08:11:12.534-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100" file="libsmsmessaging.cpp:6363">
    <![LOG[00:0C:29:6C:3F:1D, 08544D56-DCF7-D4D5-D1CC-409FCF6C3F1D: device is not in the database.]LOG]!><time="08:11:12.534-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100"
    file="database.cpp:483">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777335" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="08:20:49.266-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100" file="libsmsmessaging.cpp:6363">
    <![LOG[00:15:B7:D2:86:F0, 80222D0B-0F4C-DC11-8052-B05987052608: device is in the database.]LOG]!><time="08:20:49.266-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100"
    file="database.cpp:483">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777335" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    ]LOG]!><time="08:20:49.438-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100" file="libsmsmessaging.cpp:6561">
    <![LOG[00:15:B7:D2:86:F0, 80222D0B-0F4C-DC11-8052-B05987052608: no advertisements found]LOG]!><time="08:20:49.438-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100"
    file="database.cpp:483">
    <![LOG[Begin validation of Certificate [Thumbprint 9733001C4F488EE84A86A2DC81479F7D3262A9C3] issued to '8d4012f3-7252-4e85-891a-b4ff4421a1e4']LOG]!><time="08:48:03.366-240" date="10-28-2013" component="SMSPXE" context=""
    type="1" thread="7916" file="ccmcert.cpp:1245">
    <![LOG[Completed validation of Certificate [Thumbprint 9733001C4F488EE84A86A2DC81479F7D3262A9C3] issued to '8d4012f3-7252-4e85-891a-b4ff4421a1e4']LOG]!><time="08:48:03.366-240" date="10-28-2013" component="SMSPXE" context=""
    type="1" thread="7916" file="ccmcert.cpp:1386">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16782654" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="09:04:30.956-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100" file="libsmsmessaging.cpp:6363">
    <![LOG[00:0C:29:6C:3F:1D, 08544D56-DCF7-D4D5-D1CC-409FCF6C3F1D: device is in the database.]LOG]!><time="09:04:30.956-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100"
    file="database.cpp:483">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="09:11:12.094-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100" file="libsmsmessaging.cpp:6363">
    <![LOG[00:0C:29:06:F4:5C, 06494D56-AB1D-1748-BEC0-E4A5B906F45C: device is not in the database.]LOG]!><time="09:11:12.094-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100"
    file="database.cpp:483">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16782654" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="09:11:23.420-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100" file="libsmsmessaging.cpp:6363">
    <![LOG[00:0C:29:6C:3F:1D, 08544D56-DCF7-D4D5-D1CC-409FCF6C3F1D: device is in the database.]LOG]!><time="09:11:23.435-240" date="10-28-2013" component="SMSPXE" context="" type="1" thread="4100"
    file="database.cpp:483">
    Robert

Maybe you are looking for