none
PXE Boot ok, but after load WinPE the pc reboots

    שאלה

  • Hi all,

    I've setup a new sccm 2007 SP2 R2 environment on a WIN 2008 R2 server.
    This server hosts the PXE point role and has WDS (only transprt server part) installed.

    I imported a bare metal (virtual) pc into the sccm environment and added it to a custom made "PXE Boot" collection.

    I then deployed both standard boot images to both the servers and PXE boot distribution point.

    I took a win7 x64 dvd (which sits on a fileserver) and created a new OS Image from the install.wim file on the dvd.
    This Operating system image was only deployed to the Server distribution point (not to the pxe point).


    As OS Install package, I simply added the UNC path to the Win7 x64 dvd on the network and deployed this package to the server DP only (not PXE).

    For the task sequence, I took the default x64 boot image and the newly created Operating System image combined with the SCCM client.
    This task sequence got advertised to the PXE Boot collection I created in the beginning.

    When I boot my bare metal PC and press F12, my computer starts booting from the x64 boot image and gets to the screen "Initializing Windows PE".
    In this screen it states: "Windows is starting up", followed by: "preparing network connections".
    After that the Initializing Windows PE screen disappears and only the System Center Configuration Manager background is displayed for about 3 seconds, then my pc reboots and prompts me again to network-boot the pc.

    It seems I'm in a loop and the pc doesn't receive his task sequence.

    Can someone help me in pointing out what I'm missing?
    The SMSPXE.log doesn't bring any relevant information. Do I have to look in another logfile for this part of the process?

    Many thanks in advance!

    Filip

    יום רביעי 02 יוני 2010 13:25

תשובות

  • This is mostly likely due to the lack of correct network drivers in the boot image.

    To verify, you must enable command-prompt support in the boot image and then perform an ipconfig and/or examine the smsts.log.


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • הוצע כתשובה על-ידי helenp1983 יום רביעי 02 יוני 2010 19:44
    • סומן כתשובה על-ידי SC FTH יום חמישי 03 יוני 2010 09:40
    יום רביעי 02 יוני 2010 16:10
    מנחה דיון

כל התגובות

  • This is mostly likely due to the lack of correct network drivers in the boot image.

    To verify, you must enable command-prompt support in the boot image and then perform an ipconfig and/or examine the smsts.log.


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • הוצע כתשובה על-ידי helenp1983 יום רביעי 02 יוני 2010 19:44
    • סומן כתשובה על-ידי SC FTH יום חמישי 03 יוני 2010 09:40
    יום רביעי 02 יוני 2010 16:10
    מנחה דיון
  • Hi, 

    I had the same issue and in my case it was a missing network driver as Jason suggests. I enabled command-prompt support in the boot image. Then pressed f8 to get the command prompt while PE is loading.

     

    I added the network driver to the boot image as described here: http://myitforum.com/cs2/blogs/rpedersen/archive/2009/04/04/importing-network-drivers-into-the-windows-pe-boot-image.aspx

    I have to also add the driver to the task sequence

    • הוצע כתשובה על-ידי helenp1983 יום רביעי 02 יוני 2010 19:44
    יום רביעי 02 יוני 2010 19:44
  • This is mostly likely due to the lack of correct network drivers in the boot image.

    To verify, you must enable command-prompt support in the boot image and then perform an ipconfig and/or examine the smsts.log.


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys


    Hi,

     

    I'm testing my deployments on virtual machines.
    IT seems that I didn't import the nic drivers into SCCM.

    I now imported 2 drivers into my x64 boot image:

    VMware Accelerated AMD PCNet Adapter
    VMware PCI Ethernet Adapter

    Both are v. 2.0.3.6 and when I open the driver and check the applicability tab, they mention that they can be run on all x64 windows7 platforms.

    When I now boot my virtual pc and press F8 and goto ipconfig, I get an IP address.
    But the behviour of WinPE is still the same. After initializing network connections, the PC simply reboots..

    Where can I find the smsts.log? I cannot find it on my system..

    Many thanks in advance!

    Filip

    יום חמישי 03 יוני 2010 07:11
  • Okay,

    Here is a small update.

    After importing the nix drivers into my boot image, I got an IP address.
    I then started looking for the smsts.log on the virtual pc and found it under c:\Windows\Temp\SMSTSLOG\smsts.log

    In there I see that it tries to contact the Management Point  but it fails with status 500: Internal server error.

    After investigating, I see that this error also is being displayed under system status in my SCCM interface.
    MP Control Manager detected management point is not responding to HTTP requests.  The HTTP status code and text is 500, Internal Server Error.

    I've researched this on the web and found that there are some testURL's that should return some results.
    One of the is: http://localhost/sms_mp/.sms_aut?mplist and this indeed also returns HTTP Error 500.
    When looking at the local path, I see that it tries to go to C:\Program Files (x86)\SMS_CCM\SMS_MP\
    But this directory is empty.. Is this normal?

    Should I try to reinstall the management point?

    Many thanks to all who can help me on this!

    Filip

     

    • הוצע כתשובה על-ידי Herbaliciousness יום רביעי 06 ספטמבר 2017 11:15
    יום חמישי 03 יוני 2010 08:01
  • Yet another update :-)

    I found out why my webserver was throwing back Internal Server error 500.0 when going to the testURL.

    I had activated a setting in the applicationhost.config file as described in: http://technet.microsoft.com/en-us/library/cc431377.aspx for mdb files. This caused somehow to corrupt the file and therefor it threw the Internal Server Error back at me.

    After replacing the file with a correct version, my task sequence is now being run!

    With regards to my initial question: after having put the NIC drivers into the boot image, my pc was requesting the task sequence near the Management point. My MP counldn't respond due to the modification which I had made to the Applicationhost.config file, but that was specific to my situation.

    So I will mark Jason Sandys'es reply as the correct answer.

    Many thanks for all your help!

    יום חמישי 03 יוני 2010 09:39
  • Thank you so much for updating this thread with new information. My reboot was also network driver related.
    יום רביעי 30 אוקטובר 2013 10:21
  • Still an issue with SCCM 2016 CSB trying to PXE a VMWare VM with VMXNET3 NIC.  Quick work-around if you're not PXE booting VMs a lot is to just add a E1000[E] NIC to the VM and then remove again once OS deployed to VM.  M$ has drivers for E1000 no problem.

    This is first thread googling issue so please don't hate me dusting off an antique

    יום שני 10 אפריל 2017 10:56
  • What is "SCCM 2016 CSB"?

    Do you mean ConfigMgr/SCCM Current Branch?

    Also, this has **nothing** to do with ConfigMgr itself -- this is an issue with VMWare.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    יום שני 10 אפריל 2017 16:08
    מנחה דיון
  • Just noticed this forum is for ConfigMgr 2007, so sorry about the mis-post as well

    Yes, SCCM 2016 current branch, Long-term Service Branch often written as LTSB so I find myself writing CSB out of habit.

    The issue is a lack of drivers, so completely "to do with ConfigMgr" and it's inability to communicate with VMXNET3 v-nics as proven by the success of injection of drivers above.  MS OS's have always lacked VMXNET3 drivers, would seem ConfigMgr is the same, not that you would necessarily expect them to go to effort to include their competitor's drivers anyway, end-user wants to mix the two in their environment then it's on them to sort when things go bad, which is where helpful forums like this come in.

    יום שלישי 11 אפריל 2017 09:01
  • > "SCCM 2016 current branch"

    There's still no such thing as this. ConfigMgr/SCCM does not have a 2016 version.

    Also, why in the world are you using LTSB? That should be avoided at all costs.

    ConfigMgr does not in way care about drivers or communicate with a NIC. That is the responsibility of the OS and it's network stack/layer. Also, providing drivers is the responsibility of the OEM, VMWare in this case. So, this is still has nothing to do with ConfigMgr or Microsoft even.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    יום שלישי 11 אפריל 2017 14:37
    מנחה דיון
  • Hi, I've the same issue.

    on SCCM CB 1702.

    If I start on PXE reboot happen before run task sequence wizard in PE environment. No SMSTS.LOG is generated, I think it stop before.

    If I start by task Boot media (created on boot image used in PXE) all run fine and I deploy the OS.

    any ideas?

    יום שישי 11 מאי 2018 16:24