SLM2005: PXE booted clients freeze up, fail to reboot

I use the SLM2005 at a couple of locations, but at one of them the Thin Clients behind it freeze up and will not PXE boot when cycled.  It never worked quite right, and I always assumed it was some bug in Linux LTSP, but the problem went from intermittent and infrequent to intermittent and frequent to persistent in the span of about three weeks.  Bypassing the switch seems to resolve it.  My assumption is now that the switch is in some way defective, especially in light of the fact that a nearly identical setup at another location does not suffer from this issue.
The problem is that Cisco phone support has expired for this product, and at $75 it is about the same price as a new one.
I was thinking about trying a firmware upgrade, and just messing around with the firmware in general, but as they say "time is money".  When I buy  a switch, managed or not, I expect it to "just work". 
What would you guys do if you were me?

I've also just encountered a failure to associate using LXE MX9 scanners with a Summit card. Moving the setting from CCX FULL to CCX OPTIMIZED in the SCU resolves but is not a recommendation from Honeywell/LXE. have you had any response from TAC or Teklogix?

Similar Messages

  • Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

    Hi
    I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
    Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
    The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
    I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
    I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
    I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
    Cheers   

    Hi Joel,
    This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
    The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
    should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
    The related KB:
    PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
    http://support.microsoft.com/kb/259670
    The similar thread:
    PXE-E53: No boot filename received
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
    WDSServer (Windows Deployment Server) Fails to Start
    http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
    I’m glad to be of help to you!
    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.

  • OSD to Surface fails to PXE Boot and returns PXEGetPXEData Failed with 0x80004005

    Scenario: When trying to Image Windows 8.1 to a Surface Pro, Surface Pro 2 and Surface Pro 3 I have downloaded the latest Surface Firmware and Drivers (August 18th 2014 I believe), the NIC's are in the x64 PXE Boot Image. I have verified that no DHCP Option
    67 is set, and that SpanningTree PortFast is enabled. All other Images function correctly, Windows 7 Sp1 works. We use the Microsoft USB NIC, and we PXE boot and download the PXE Image fine, then it comes into windows and goes to detect the NIC, at which point
    it fails and reboots.
    The Surface has had Firmware update on it to the latest.
    It appears the NIC just stops working, which makes me think that the latest Driver pack for Surface does not contain the PXE boot versions for their NIC.
    Trying the Docking Station (which utilizes NIC ASIX AX888772) exhibits the same problem.
    The NIC stays active until the OSD Screen comes up, it fails trying to load the Surface NIC though (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which
    make me think this is the case even more so.
    Doing a USB PXE Boot also fails to load the NIC.
    Going to F8 and doing IPCONFIG /RENEW verifies the NIC is not active.
    I see tons of postings on the Surface being a nightmare to image.
    Errors:
    Failed to Download pxe variable file. Code (0x0000001)
    PXEGetPXEData Failed with 0x80004005
    Anybody having any other experiences out there, or have anything else they could think to try?
    David Baur

    (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which make me think this is the case even more so.
    There are no "PXE boot versions" of drivers at all. What you described just indicates that there is no driver in winpe that matches the hardware. WinPe is based on the respective version of the full os so you have to add Win8.x drivers to the boot image.
    The architecture also has to match. Have you added NIC drivers to the boot image at all?
    NIC drivers are never boot critical if I am not mistaken.
    Torsten Meringer | http://www.mssccmfaq.de

  • Novell Client integrated login fails on reboot.

    I have LUM, NCL and CASA enabled and everything works just fine. I can log
    in as a user, save the profile, log in and out and get integrated login.
    The problem is that if i reboot SLED and try the same user that worked 30
    times in a row before it complains about "ncl_autologin[716]: Tree "" not
    found in miCASA." and fails to do the integrated login. If i look at the
    profile in the client everything looks just fine and i can login without
    errors if i supply the password again.
    In the Casa store i can see the tree and the password.
    I have SLP setup on the OES server and slptool on the SLED box connects to
    the OES server and works properly. All three buttons on the linux client
    works and finds trees, contexts and servers. I have reproduced the error on
    three different hardwares with different media for the install.
    Have anyone else reproduced this error? I have followed the documentation
    to the letter but integrated login still just fails after every reboot i make.
    Any ideas no matter how longshot is much appriciated, i just have to get
    this working.

    On Fri, 17 Nov 2006 16:16:33 +0000, linuxjoe wrote:
    > [email protected] wrote:
    >
    >> That is, CASA can store information both on
    >> disk and in memory
    >
    > In your home directory you have a series of .miCASA files. Each file should
    > have a regular miCASA... file and then one that ends with the extension .IV
    I have those and they contain the correct information when i look in the
    CASA manager GUI.
    >
    > Basically one is for persistance and one isn't. If only one is getting
    > created then you will loose your setting on reboot. I have seen this on
    > my own system and it is basically caused by deleting the .miCASA.. files
    > and then not restarting casa before you start to store secrets again. If
    > this is the case then you can delete you .miCASA files (you will loose
    > your secrets by doing this) and then logout and back in. You should then
    > see that two of each file is created. One regular one and one with a .IV
    > extension.
    >
    > If this is not your issue and you have both types for each .miCASA file
    > then I don't know what the issue is.
    I have a group of users i try with and it looks the same on all of them
    regardless of what i do. CASA stores the info and when i reboot it looses
    something that i cant really see. I have three computers with SLED on now
    and they all look exactly the same when i look in CASA and compares the
    info on a rebooted and a non rebooted computer.
    I will do a trace on the .miCASA files and see if i can spot any
    differences between a rebooted and a non rebooted computer on monday.
    One question, does it work for you after a reboot?

  • Conundrum - PXE boot fails vs. "reinstall OS from software center" succeeds

    Hi All.
    I am facing a bit of a conundrum..
    In our offices I am seeing some strange behaviour when trying to PXE boot into a TS to reinstall or install OS. 
    If I use F12/PXE boot then the deployment fails during OSD.
    If I take a client (the same client as I tried pxe booting with) that is fully installed and reinstall OS via software center then the deployment completes. 
    Any ideas what could be wrong?
    Kindest regards, Martin

    Daniel:
    Clients are both laptops & desktops.
    I "feels" like it's the network that's acting up but I really can't see where. 
    PXE boot works.. it's not until it tries to apply the OS... 
    whether it's a timeout or what it is I cannot say.. 
    Gerry: After all will you be likely to rebuild your entire estate in-situ any time soon?
    You know... we are actually On the verge" of upgrading & Streamlining our entire network infrastructure..
    But I'd still love to solve the problem.. 
    We never had this issue when we only had MDT as deployment tool. 
    it's not until sccm came into the picture that this issue has arisen.
    Kindest regards, Martin

  • Capturing an image to use for PXE boot

    I'm using Windows Deployment Services in conjunction with Windows Deployment Terminal (Windows Server 2008) to capture an image from one of our workstations to use as a PXE boot image for future computers. I've created the capture image and PXE booted
    to that image, which brings up the "Image Capture" wizard. After capturing the image, I created an install image in WDS using the same .wim file. After trying to PXE boot, the workstation yet again brings up the "Image Capture" wizard.
    I then right clicked the image under Boot Images (in WDS) and selected "Create Discover Boot Image." A loading window pops up, but always ends with an error saying something to the extent of the image doesn't have WDSClient Binaries. Does anyone
    know what this is or how to fix this? Or even if I'm going about it the right way? If anyone has any advice, I'd appreciate it.

    Hi,
    Yes, you can.
    Here are the rough steps:
    1. 
    Install and configure the WDS Server.
    2. 
    Add the Windows 7 boot image to WDS.
    3. 
    Create a Capture Boot Image and add it to Boot Image.
    4. 
    Create a reference Windows 7 computer (install Windows 7, Office and other applications as you like)
    5. 
    Sysprep the Windows 7 computer.
    6. 
    PXE boot the reference Windows 7 computer into capture image on the boot screen and then capture the image.
    7. 
    Upload the captured image to WDS server.
    8. 
    PXE boot clients, choose the captured image to install the system.
    Please refer to this link
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/be3af7db-b71b-4b14-b166-fef83cde0ac6/deploy-windows-7-from-waik-with-some-application-added?forum=winserversetup
    I had the similar problem couple of years back
    UMESH DEUJA MCP,MCTS,MCSA,CCNA

  • Client boots into WinPE but then it will fail and reboot after the step: "Preparing network connections"

    I  have a new issue with all DPs.
    When I pxe boot, it will boot into WinPE but then it will fail and reboot after the step: “Preparing network connections”
    I have tried reinstalling the DP and MP. Also redistributing the boot image.
    When I press F8 to go into debug mode, ipconfig show me an IP address and I am able to ping my Management point, my DHCP server and also my Distribution point.
    I have attached the smsts.log file.
    <![LOG[LOGGING: Finalize process ID set to 900]LOG]!><time="10:43:28.925+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="tslogging.cpp:1495">
    <![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="10:43:28.925+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904"
    file="bootshell.cpp:1055">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="10:43:28.925+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="util.cpp:964">
    <![LOG[Debug shell is enabled]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:1066">
    <![LOG[Waiting for PNP initialization...]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:60">
    <![LOG[RAM Disk Boot Path: NET(0)\SMSIMAGES\EVN0002F\BOOT.EVN0002F.WIM]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="configpath.cpp:302">
    <![LOG[Booted from network (PXE)]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="configpath.cpp:317">
    <![LOG[Network(PXE) path: X:\sms\data\]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="configpath.cpp:319">
    <![LOG[Found config path X:\sms\data\]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:548">
    <![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:582">
    <![LOG[X:\sms\data\WinPE does not exist.]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:599">
    <![LOG[X:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:613">
    <![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="10:43:28.956+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:860">
    <![LOG[The command completed successfully.]LOG]!><time="10:44:13.294+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:942">
    <![LOG[Starting DNS client service.]LOG]!><time="10:44:13.294+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:666">
    <![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="10:44:13.809+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908"
    file="bootshell.cpp:860">
    <![LOG[The command completed successfully.]LOG]!><time="10:44:13.809+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:942">
    <![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="10:44:13.903+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116"
    file="tsmbootstrap.cpp:1165">
    <![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="10:44:13.903+480" date="08-13-2014" component="TSMBootstrap" context="" type="0" thread="1116"
    file="tsmbootstrap.cpp:1166">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="10:44:13.919+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="util.cpp:964">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="10:44:13.919+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="resourceutils.cpp:169">
    <![LOG[Current OS version is 6.2.9200.0]LOG]!><time="10:44:13.919+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="util.cpp:3094">
    <![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="0" thread="1116"
    file="tsmbootstrap.cpp:963">
    <![LOG[PXE Boot with Root = X:\]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="tsmbootstrap.cpp:1062">
    <![LOG[Executing from PXE in WinPE]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="tsmbootstrap.cpp:1077">
    <![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="0" thread="1116" file="tsmbootstraputil.cpp:1363">
    <![LOG[TsPxe.dll loaded]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsmbootstraputil.cpp:1373">
    <![LOG[Device has PXE booted]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tspxe.cpp:122">
    <![LOG[Variable Path: \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116"
    file="tspxe.cpp:134">
    <![LOG[Variable Key Len: 69]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tspxe.cpp:141">
    <![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="10:44:13.950+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="fwopen.cpp:123">
    <![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 10.9.12.122 get \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var X:\sms\data\variables.dat]LOG]!><time="10:44:13.950+480" date="08-13-2014" component="TSPxe"
    context="" type="0" thread="1116" file="tspxe.cpp:177">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="10:44:14.028+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="commandline.cpp:228">
    <![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.9.12.122 get \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var X:\sms\data\variables.dat]LOG]!><time="10:44:14.028+480" date="08-13-2014"
    component="TSPxe" context="" type="0" thread="1116" file="commandline.cpp:731">
    <![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.9.12.122 get \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var X:\sms\data\variables.dat]LOG]!><time="10:44:14.028+480" date="08-13-2014"
    component="TSPxe" context="" type="1" thread="1116" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 0]LOG]!><time="10:44:14.106+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="commandline.cpp:1123">
    <![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="fwopen.cpp:146">
    <![LOG[Successfully downloaded pxe variable file.]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tspxe.cpp:187">
    <![LOG[we are booted using PXE]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:2673">
    <![LOG[we are booted using PXE and we use a generated password]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:2678">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
    <![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,165)]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context=""
    type="0" thread="1116" file="windes.cpp:165">
    <![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)]LOG]!><time="10:44:14.122+480"
    date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsremovablemedia.cpp:387">
    <![LOG[Verifying media password.]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:271">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
    <![LOG[Found network adapter "Intel(R) 82577LM Gigabit Network Connection" with IP Address 10.9.2.50.]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="0"
    thread="1116" file="tsmbootstraputil.cpp:517">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
    <![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,165)]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context=""
    type="0" thread="1116" file="windes.cpp:165">
    <![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)]LOG]!><time="10:44:14.153+480"
    date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsremovablemedia.cpp:387">
    <![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsmediawizardcontrol.cpp:527">
    <![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="10:44:14.153+480"
    date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="environmentscope.cpp:263">
    <![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116"
    file="environmentscope.cpp:623">
    <![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="10:44:14.153+480"
    date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="environmentscope.cpp:263">
    <![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116"
    file="environmentscope.cpp:623">
    <![LOG[Setting LogMaxSize to 1000000]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:555">
    <![LOG[Setting LogMaxHistory to 1]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:556">
    <![LOG[Setting LogLevel to 0]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:557">
    <![LOG[Setting LogEnabled to 1]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:558">
    <![LOG[Setting LogDebug to 1]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:559">
    <![LOG[UEFI: false]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:569">
    <![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:584">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="util.cpp:964">
    <![LOG[Setting SMSTSMP TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSLaunchMode TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Root CA Public Certs=]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:615">
    <![LOG[Missing root CA environment variable from variables file]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:621">
    <![LOG[Support Unknown Machines: 0]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:632">
    <![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:675">
    <![LOG[No hook is found to be executed before downloading policy]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:699">
    <![LOG[Authenticator from the environment is empty.]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:838">
    <![LOG[Need to create Authenticator Info using PFX]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:850">
    <![LOG[Initialized CStringStream object with string: 6b7b5b1a-8a29-40a1-af6b-008746965168;2014-08-13T18:44:14Z.]LOG]!><time="10:44:14.200+480" date="08-13-2014" component="TSPxe" context="" type="0"
    thread="1116" file="stringstream.cpp:101">
    <![LOG[Set media certificate in transport]LOG]!><time="10:44:14.216+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="libsmsmessaging.cpp:9401">
    <![LOG[Set authenticator in transport]LOG]!><time="10:44:14.216+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="libsmsmessaging.cpp:7734">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SS01.adskevents.local:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA]LOG]!><time="10:44:14.216+480" date="08-13-2014" component="TSPxe" context="" type="1"
    thread="1116" file="libsmsmessaging.cpp:8604">
    <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="10:44:15.939+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:860">
    <![LOG[The command completed successfully.]LOG]!><time="10:44:15.939+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:942">
    <![LOG[Successfully launched command shell.]LOG]!><time="10:44:15.939+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:432">
    <![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="libsmsmessaging.cpp:8870">
    <![LOG[hr, HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8919)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116"
    file="libsmsmessaging.cpp:8919">
    <![LOG[sending with winhttp failed; 80072ee2]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="3" thread="1116" file="libsmsmessaging.cpp:8919">
    <![LOG[m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe"
    context="" type="0" thread="1116" file="libsmsmessaging.cpp:5159">
    <![LOG[MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe"
    context="" type="0" thread="1116" file="libsmsmessaging.cpp:9410">
    <![LOG[Failed to get information for MP: http://SS01.adskevents.local. 80072ee2.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="3" thread="1116" file="tsmbootstraputil.cpp:1518">
    <![LOG[sMP.length() > 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1526)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
    type="0" thread="1116" file="tsmbootstraputil.cpp:1526">
    <![LOG[TSMBootstrapUtil::SelectMP ( sSMSTSMP.c_str(), sMediaPfx.c_str(), sMediaGuid.c_str(), sAuthenticator.c_str(), sEnterpriseCert.c_str(), sServerCerts.c_str(), nHttpPort, nHttpsPort, bUseCRL, sSiteCode, sAssignedSiteCode, sMP, sCertificates, sX86UnknownMachineGUID,
    sX64UnknownMachineGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,907)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
    type="0" thread="1116" file="tsmediawizardcontrol.cpp:907">
    <![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsmediawizardcontrol.cpp:1419">
    <![LOG[GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2492)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
    type="0" thread="1116" file="tsmediawizardcontrol.cpp:2492">
    <![LOG[RunWizardForPXE(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2834)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
    type="0" thread="1116" file="tsmediawizardcontrol.cpp:2834">
    <![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe"
    context="" type="0" thread="1116" file="tsmbootstrap.cpp:1078">
    <![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1226)]LOG]!><time="10:44:35.281+480" date="08-13-2014"
    component="TSPxe" context="" type="0" thread="1116" file="tsmbootstrap.cpp:1226">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmbootstrap.cpp:1238">
    <![LOG[Execution complete.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:693">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="0"
    thread="908" file="environmentscope.cpp:493">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="0"
    thread="908" file="environmentlib.cpp:335">
    <![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="0"
    thread="908" file="environmentlib.cpp:553">
    <![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,809)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell"
    context="" type="0" thread="908" file="utils.cpp:809">
    <![LOG[RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="2" thread="908"
    file="utils.cpp:809">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="2" thread="908" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:725">
    <![LOG[Finalizing logging from process 900]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="tslogging.cpp:1583">
    <![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="10:44:35.687+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="tslogging.cpp:1640">
    <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="10:44:35.687+480" date="08-13-2014" component="TSBootShell" context="" type="0" thread="908" file="tslogging.cpp:584">

    Every time a query is sent to the MP, it receives 0x80072ee2 which translates to "The operation timed out". This has nothing to do with your MP or DP though so reinstalling them won't make any difference.
    This error is indicative of network issues -- basically, the "client" is not getting a response back in a timely manner (and probably not at all). Assuming the MP is healthy though, then only other piece of the puzzle is the network.
    You can try setting the SMSTSAssignmentsDownloadRetry and SMSTSAssignmentsDownloadInterval task sequence variables in the boot image to increase the client's tolerance for latency or other weirdness in the network. This has worked for many.
    If that doesn't work, you'll have to break out a sniffer and watch the traffic to see what's going on at a network level.
    Jason | http://blog.configmgrftw.com

  • The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed. WDS not PXE booting!

    This morning came in to find clients were not getting there bootfiles through PXE. I checked the logs to find the following events related to WDS.
    The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
    The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
    The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
    Has anyone seen this or have a link to a resolution?
    tconners

    Hotfix loaded but didn't help.
    Found a few articles referring to rebuilding the perf counter library. I ran "lodctr /R" failed first time then worked the second time. I believe the errors:
    The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
    The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
    The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
    Are gone but PXE boot still fails.
    Do you think I might have to uninstall WDS and reinstall? "Using SCCM console to just remove PXE"
    tconners

  • OSD: pxe boot fails with "failed to get infromation for MP:/"

    Hi,
    We face an issue on pxe boot. It boots into pxe then tries to apply network settings but then reboots.
    Ipconfig is ok, smsts.log says "failed to get information for MP:/oursccmserver.
    Troubleshooting:
    *PXE is working fine when client as well as sccm-server are in same subnet, it fails when in different subnets.
    *Firewall is fully opened, no connections blocked.
    *Ping to sccm-server works fine on dns
    Please advise.
    J.
    smsts.log:
    Missing root CA environment variable from variables file    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Support Unknown Machines: 0    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Custom hook from X:\\TSConfig.INI is     TSPxe    26/03/2014 16:37:11    288 (0x0120)
    No hook is found to be executed before downloading policy    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Authenticator from the environment is empty.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Need to create Authenticator Info using PFX    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Initialized CStringStream object with string: {40AB3050-A926-4BA5-9D17-7423F93CBCD5};2014-03-27T00:37:11Z.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Set media certificate in transport    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Set authenticator in transport    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.ourcompany.com:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]                : dwStatusInformationLength is 4
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]                : *lpvStatusInformation is 0x8
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]            : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    failed to receive response with winhttp; 80072f8f    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Failed to get information for MP: http://oursccmserver.ourcompany.com. 80072f8f.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Jan Hoedt

    Hi,
    Have you check Mpcontrol.log on the MP server and Smspxe.log?
    Best Regards,
    Joyce Li
    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.

  • Creating new OSD task sequence causes PXE boot to fail

    I'm running SCCM 2012 on Server 2008 R2. Currently we have a standard task sequence we use for all of our Windows 7 deployments that is working fine. We use PXE boot to load up WinPE to select the task sequence to load and all is good.
    I've made a new task sequence to deploy custom configuration settings to a group of computers. I've duplicated much of the original task sequence, using the same boot media. After i deploy the new TS to the All Unknown Computers collection, PXE boot does
    not work anymore.
    It downloads WDSNBP, starts by DHCP referral, contacts the server. After that I just get a Pending Request ID: number says contacting server then fails. If i go back to my new TS and delete the deployment, all is good again.
    Can i create a new task sequence using an existing reference image? Has anyone seen this type of issue before? I see similar issues online, but it seems to be for people that cannot PXE boot at all. My problem is just that the new task sequence seems to
    kill PXE boot when it's deployed.

    This is from the log file, looks like it can't find the boot image. I'm using the same boot image for both of the task sequences though.
    <![LOG[Set media certificate in transport]LOG]!><time="11:35:45.257+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:9220">
    <![LOG[Set authenticator in transport]LOG]!><time="11:35:45.257+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
    <![LOG[Set authenticator in transport]LOG]!><time="11:35:45.301+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="11:35:45.359+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6204">
    <![LOG[Set media certificate in transport]LOG]!><time="11:35:45.419+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:9220">
    <![LOG[Set authenticator in transport]LOG]!><time="11:35:45.420+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
    <![LOG[Set authenticator in transport]LOG]!><time="11:35:45.455+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
    <![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="11:35:45.508+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1736">
    <![LOG[Getting boot action for unknown machine: item key: 2046820353]LOG]!><time="11:35:45.572+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="pxehandler.cpp:226">
    <![LOG[Set media certificate in transport]LOG]!><time="11:35:45.637+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:9220">
    <![LOG[Set authenticator in transport]LOG]!><time="11:35:45.637+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
    <![LOG[Set authenticator in transport]LOG]!><time="11:35:45.678+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
    <![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID>44f40eda-b0b0-44ae-87e1-9b9464046c39</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="COL20062" OfferIDTime="20/02/2014 11:22:00 AM" PkgID="COL00086" PackageVersion="" PackagePath="http://TECH-SVR2.county-lambton.on.ca/SMS_DP_SMSPKG$/COL00045" BootImageID="COL00045" Mandatory="0"/></ClientIDReply>
    ]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6402">
    <![LOG[Client Identity: 9ca0acb3-06b1-4737-9db0-1e4b75336ec9]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6428">
    <![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1736">
    <![LOG[PXE::CBootImageManager::FindBootImage: COL00045]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1652">
    <![LOG[Looking for bootImage COL00045]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1686">
    <![LOG[PXE::CBootImageCache::FindImage]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagecache.cpp:657">
    <![LOG[MAC=9C:B6:54:A3:53:19 SMBIOS GUID=70DCD781-5008-11E4-8264-8BD5B90C0061 > Could not find an available image BootImageID=COL00045]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="pxehandler.cpp:2095">
    <![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1736">
    <![LOG[PXE::CBootImageManager::FindBootImage: COL00045]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1652">
    <![LOG[Looking for bootImage COL00045]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1686">
    <![LOG[PXE::CBootImageCache::FindImage]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagecache.cpp:657">

  • PXE boot fails and reboots after loading PE

    I have run into what I think is a unique issue and need some help determining the cause.
    We are in the process of replacing and aging DP/PXE point (2003 R2 SP2) with a new server (2008 STD R2 SP1).  What makes my pxe issue unique is that pxe works without issue on the existing 2003 DP/PXE server.  But on the new 2008 server I run into
    the following issue.
    Environment:  Config Manager 2007 R2, a single primary, multiple DP's and PXE points.
    Issue:  When I attempt to PXE boot a system, I am able to load PE, but shortly after the custom background screen is loaded, the system reboots.  I've searched the internet quite a bit and found lots of potential causes including, bad/missing drivers,
    certificate issues, rights issues, etc.  None of these seem to be the cause.
    My troubleshooting has determined that the client computers are unable to download the variables.dat file.  I just don't know why.
    We're using the same boot images on both servers. 
    I've tried using multiple computer models and VM's. 
    I've opened a command prompt as soon as our background image loads and have verified that the system is pulling a valid IP address.  I am able to map a drive to the PXE server's REMINST share using our sccm net access account and manually copy the .var
    file using xcopy to the appropriate directory on the local virtual drive.   I've also attempted to manually run smstftp.exe by mimicking the command line from the smsts log file.  I'll admit that I'm not sure I have the correct syntax for smstftp. 
    I've tried several variations and all but one result in a short pause and no file copied/created in the X:\sms\data folder.  The one that does produce a result says that the file cannot be found.  I checked for typos and made sure I used the name
    of the newly created .var file.
    I've also tried disabling anti-virus on the server, shutting off the windows firewall on the server, granting everyone read rights to the REMINST share.
    Below is the smstslog file I've been using as a reference.  Per corporate security policy, I have X'd out the IP address of the PXE server.  The log file for the successful pxe boot from the 2003 server shows an exit code of 0 for smstftp.exe, a note
    about successful download of the pxe var file and then it continues through the rest of the boot process.
    -----SMSTS log file from a failed PXE boot on the new 2008 server -----
    <![LOG[LOGGING: Finalize process ID set to 832]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="tslogging.cpp:1489">
    <![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836"
    file="bootshell.cpp:963">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="util.cpp:869">
    <![LOG[Debug shell is enabled]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:974">
    <![LOG[Waiting for PNP initialization...]LOG]!><time="16:13:54.471+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:59">
    <![LOG[Booted from network (PXE)]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="configpath.cpp:198">
    <![LOG[Found config path X:\sms\data\]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:553">
    <![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:564">
    <![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:767">
    <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:850">
    <![LOG[Successfully launched command shell.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
    <![LOG[The command completed successfully.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
    <![LOG[Starting DNS client service.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:597">
    <![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880"
    file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
    <![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932"
    file="tsmbootstrap.cpp:1039">
    <![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932"
    file="tsmbootstrap.cpp:1040">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="util.cpp:869">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="resourceutils.cpp:152">
    <![LOG[Processor Is IA64: 0]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1005">
    <![LOG[PXE Boot with Root = X:\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:921">
    <![LOG[Executing from PXE in WinPE]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstrap.cpp:936">
    <![LOG[Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1319">
    <![LOG[TsPxe.dll loaded]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1329">
    <![LOG[Device has PXE booted]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:122">
    <![LOG[Variable Path: \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
    file="tspxe.cpp:134">
    <![LOG[Variable Key Len: 61]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:141">
    <![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:123">
    <![LOG[Executing: X:\sms\bin\i386\smstftp.exe -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.004+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:177">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:14:42.067+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:229">
    <![LOG[Set command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:707">
    <![LOG[Executing command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
    component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:805">
    <![LOG[Process completed with exit code 1]LOG]!><time="16:15:29.179+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:1102">
    <![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:146">
    <![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
    file="tspxe.cpp:185">
    <![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tspxe.cpp:185">
    <![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tsmbootstraputil.cpp:1419">
    <![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context=""
    type="0" thread="1932" file="tsmbootstraputil.cpp:1420">
    <![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2236)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tsmediawizardcontrol.cpp:2236">
    <![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe"
    context="" type="0" thread="1932" file="tsmbootstrap.cpp:937">
    <![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tsmbootstrap.cpp:1106">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1118">
    <![LOG[Execution complete.]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:624">
    <![LOG[Finalizing logging from process 832]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1736">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1578">
    <![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="16:15:29.491+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1803">
    This has been an extremely frustrating issue and any assistance would be greatly appreciated!

    Thanks for your quick response Jason!  I didn't expect someone to reply so quickly or I would have checked back sooner. 
    I had found the two 'older' posts already, but had not seen the 'newer' one.  Unfortunately that did not give me any new ideas.  But your comment on checking for TFTP availability did.  Here are things I have tried since my original
    post...
    I re-ran most of my tests in case I missed something.  I only found one change.  Even though I double-checked, I must have made a typo when I manually ran the smstftp.exe command, because when I ran it again I received a timeout message instead
    of file not found.
    I had a minor 'thinking outside of the box moment' and decided to PXE boot the new 2008 R2 server itself.  This was successful and I interpreted the success as meaning that the hardware is ok.  Thinking there may be a compatibility issue with
    the hardware and the OS, I tried a few different NIC drivers, settings, registry keys, and even a completely different NIC.  No luck on any of these.
    I decided to build another Server on a VM tovalidate my build process and configuration.  And of course clients in multiple locations were able to PXE boot off this VM.  Too bad I can't use this in production.
    After reading your response Jason, I began to focus on network.  I moved the server to a few different locations so it was utilizing different switches.  No luck.  I noticed in the event viewer for WDS that the server was logging the
    beginning of the boot.var file via TFTP.  This of course was not very surprising.  What was surprising is that the very next entry (informational) noted that the client 'COMPLETED' the download of the boot.var file via TFTP.  I know that completed
    does not mean successful, but it usually implies or is interpreted as successful.  It should have logged a warning or error, or nothing at all because although the process completed, it was not successful.  I re-verified that the file was not downloaded
    to the client and the client log file still shows the same error noted in the logfile from my original post.
    Finally, I installed sniffing software on the server and ran some captures while attempting to PXE boot.  Even though I am not much of a network guy, I quickly discovered two things.  First, I found the section where the client attempts to download
    the boot.var file.  Unfortunately I don't think the local security team will allow me to post the capture, so I'll do my best to describe what I found.  It starts with a single entry where the client calls for the file via TFTP protocol.  This
    is followed by a series of alternating entries (all TFTP) where it looks like the server attempts to send a portion of the file, and the client sends an acknowledgement.  The sending entries all have checksum errors.  The checksum received on
    all packets is 0x0000 and of course should be something else.  There is also a shorter section below this with alternating entries where the server attempts to send ICMP packets and the client responds with TFTP acknowledgements. 
    The ICMP entries are all marked as Destination unreachable (Port Unreachable).
    The second thing I noticed from the network capture is the a few 'Spanning Tree Protocol' entries.  I my search for a solution, I remember reading several posts saying that Spanning Tree can cause this issue.  When I asked, I was assured that
    Spanning Tree was disabled in this environment.  It made sense too, because the 2003 PXE server was functioning properly, and Spanning Tree should affect both 2003 and 2008 servers, right?
    Either way I will bring my findings to the network team and see what they have to say.
    Any additional thoughts or ideas???

  • Ghost PXE boot freeze on T500

    Hi,
    My company got some new Lenovo T500 (2055-2BU), I tried to get windows XP images from Ghost server, but the T500 freeze before the PC DOS boot up.  The PXE boot server works for Lenovo M55, M57, M58, and T61.  What could cause the problem?
    Thanks.
    Our Ghost server is Ghost 7.5
    PXE boot Server is Argon 1.2.

    I fixed the argon problem with updating the Argon version 1.2 to 1.3. But the Ghost 7.5 seems not working with AHCI mode on T500,  but T61 was OK.  Any one got an idea?
    Thanks

  • Policy retreiving for client that is pxe booting

    Wanna ask, to which management point server does a client will retrieve its policy prior to executing the TS? Does it based on the ip address boundary range?
    Which logfile I can see to reoubleshoot client pxe issue? is it smspxe.log?

    Short answer is:  it doesn't.  But we have to break down what's happening.
    Remember when you PXE boot you are actually operating at Layer 2 still, and the WDS services are answering a broadcast.  So no MP enters the picture before a TS runs _at_all_, instead it's the Distribution Point (which controls the WDS/PXE services
    in 2012) that is connecting to the client and providing the TS.
    You can actually see this happening on the SMSPXE.log (I'm going from memory on the log name, sorry if i got it wrong) in the SMS_DP$\sms\logs when the PXE servive gets the mac, matches it against the DB then provides the TS available.
    Again we are basically doing this at layer 2, even though the client will eventually get an IP and use said IP to TFTP download said image... 
    More depth here:
    http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx
    EDIT:  to speculate on your question a bit: so if there are multiple DPs in the same subnet, or there is possibly IPHelper in the picture in some way ... the DP that answers is basically random unless a response delay is set (can be done on the DP in
    in the MMC).

  • PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

    Hi all,
    we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
    the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html) 
    What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
    with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
    WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
    Is what i'm trying actually possible?
    Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
    desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
    Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

    It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
    Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Task Sequence fails on "Apply Driver Package" when PXE-booting but not with bootable media

    I have an issue where my Task Sequence fails during 'Apply Driver Package' when PXE-booting but works ok when booting from CD or USB-stick. It fails withe error code 0x80070002 and when pressing F8 and checking the ipconfig there's a 169.254.x.x address.
    Somehow it looses it's real ip during the process.
    I'm grateful for any advice!

    Please enable verbose logging for Task sequence, then upload the smsts.log to Skydrive.
    0x80070002 error is too generic, which cannot be used to determine the cause.
    Juke Chou
    TechNet Community Support

Maybe you are looking for