Jump to content


  • 0
Scott S

Problem PXE Booting 2008 R2 Servers

Question

Well it doesn't actually matter what OS the server is. Maybe it's the hardware on the server that is causing me issues. I need to deploy Windows 2008 R2 to Dell Poweredge R710 servers.

 

I've uploaded the NIC drivers to the Boot image files for both x86 and x64. When I do a PXE boot on the server it does find my WDS server and does recieve the boot file to boot up. After it downloads via tftp if then configures nic and storage settings. But right after that (right before the password screen usually prompts) the server just reboots with no errors.

 

I've looked at my SMSPXE logs on the WDS server and it doesn't report any errors. SCCM doesn't report any errors as well. I keep thinking it's something to do with the NIC drivers. Or possible the Storage drivers? How do I verify the storage drivers are actually getting pulled to the machine?

 

It just kind of strange to me, because every other machine i've imaged all have booted up flawless with an exception of importing NIC drivers every once in a while. But i've never seen a machine just reboot in WinPE without any warning.

 

Thank you for all your help.. it's greatly appreciated.

Share this post


Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0

if you are trying to deploy server 2008 R2 then sccm needs sp2 release candidate installed, so is the sp2 rc installed ? I have deployed server 2008 R2 using the very same steps in my deploy windows 7 guide, works just fine... if you want roles and features working via the task sequence then simply integrate MDT 2010 which is now final

Share this post


Link to post
Share on other sites

  • 0

Thanks for the reply.. You think that would have something to do with these server rebooting during the WinPE phase. Right after WinPE says it's going to start windows (right before the pxe password is prompted) the server just reboots without warning.

 

Hopefully these updates will take care of that issue?

 

Well regardless you're still saying I need to upgrade to SP2 and MDT 2010 to get 2008 R2 deployed right?

Share this post


Link to post
Share on other sites

  • 0

I emailed the MS deployment team blog and was helped by Tim Mintner. The problem was a leftover minint folder; after deleting the folder, the deployment worked. No drivers needed to be added to the boot image; I had tried the monolithic Broadcom drivers to no avail.

Share this post


Link to post
Share on other sites

Join the conversation

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

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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

Loading...


×
×
  • Create New...

Important Information

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