Hi, I'm having an issue getting a bare-metal machine to boot to PXE in Hyper-V and I would appreciate any help anyone can offer. The setup. Hyper-V Running on Server 2008 R2 with one virtual network (private) the VMs have no contact with the host or the internet. DC01.domain.com (IP: 10.0.0.1), OS: Server 2008 R2, ROLES: AD, DHCP. DHCP Scope: 10.0.0.50-10.0.0.100 SVR1.domain.com (IP: 10.0.0.2). OS: Server 2008 R2, WDS server role installed and SCCM. CL1: Bare-metal machine, legacy network adapter. This is what I did: Installed SQL Server 2008 and all pre-reqs for SCCM Installed and configured SCCM Installed MDT and allowed SCCM Console integration I then followed THIS GUIDE http://blogs.technet.com/b/oob/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx to set up the WDS role and SCCM PXE point. I then made sure my boot images (both X64 and X86) were copied to both distribution points (normal and PXE), waited for this to finish. SO NOW.... I want to test that I have set it up right and want to boot a bare-metal VM into PXE. It just sits there on DHCP and does not get an address. Am I right in thinking I don't need to add OS image files just yet if all I want to do is test that the PXE point is working? I'm not expecting to get very far... but I would expect the machine to pick up DHCP, boot into PXE and show the two boot images??? I have tried everything I can think of. Can anyone help?

what does smspxe.log say on the sccm server ? it should show that you have a client attempting to PXE boot, does it reveal anything ? have you tried restarting the WDS service ? have you advertied any ts to the unknown computers collection ? or have you advertised a ts (task sequence) to a Deploy OS collection and used computer association to ADD the bare metal client to that collection ? cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

I can't find SMSPXE.log in %SCCM Install Dir%\Logs any idea where it might be? I haven't added any OS images, or source files yet, or created any collections, advertisments or task sequences. I was assuming that at this point (with the boot images published to the DPs) and the PXE point configured that it would respnd to a PXE boot (DHCP at least!!??) so I could test I set up PXE correctly? I want the PXE point to respond to all unknown machines, but can't see that option in the point role settings? I'll try restarting WDS now.

Looked here and don't have the 'logging' key or anything below it... HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\SmsPXE HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXE\Logging\smspxe

Ok so I restarted the WDS services, and installed R2 and R3 and turned on unknown computer support. The bare metal machine still hangs at DHCP and nothing. Can someone confirm whether I need to add OS files / packages and a task sequence before DHCP should respond? I want to confirm I have everything correct before I go much further. Thanks for you help!!

Hello Levellers ! Thank you for writing to the TechNet forums. I am providing a high overview what you should have before the PXE service point. Here is the overview of what is required in a bare metal scenario : I think you are facing that issue because the client is unable to communicate to the DHCP server 1) We need a server where the Windows Deployment Service has been installed but not initialized. When you install the PXE Service point it will go ahead and initialize the WDS. 2) We require a DHCP server which can automatically provide the IP configuration for the client booting in the PXE. 3) (Optional) We require a client machine which has the Network Booting capabilities. In many of the cases if your client machine is on a different subnet as compared to ConfigMgr\DHCP server. Please make sure that the IP helper table is configured. It may sound a daunting task, but it's a requirement if the client is in a different subnet and we have a layer two switch/ router. This can prevent the client from getting an IP address and connecting to your boot (WDS) server. Here's the excellent post from the Adnan on this : http://blogs.technet.com/b/adnanezzi/archive/2009/06/22/configmgr-2007-osd-how-to-allow-dhcp-broadcasts-across-vlan-s.aspx This will help you understand why it's required and how to configure it. 4) Now, if you have the DHCP ,ConfigMgr & client in the same subnet; You can ignore the step 3. 5) If you are using a Windows Server 2003/2008 as your DHCP server. You don't have to do anything in terms of configuring the scope options. It will be done automatically when you install the PXE Service Point. 6) We then install the PXE service point on the site system where we have the WDS installed but not initialized. Make sure that you enable the Unknown Computer Support 7) After installing the PXE service point you will notice that there is a new DP option got added under each package. Now Don't update all the packages on the SMSPXEIMAGES$ otherwise you'll not be able to boot from the PXE 8) The only thing we need on the SMSPXEIMAGES$ share are your boot images(Which is x86 & x64). We Don't have to update the OS Images/OS Packages to the SMSPXEIMAGES$. 9) Once you have updated the Boot Images on the SMSPXEIMAGES$, check the SMSBoot folder under the <drive letter where WDS is installed>:\remote install\ 10) The SMSPXEIMAGES$ DP is actually a share pointing to the SMSIMAGES folder within the RemoteInstall folder. ConfigMgr places the Boot Images in this share so that the Boot Images are available to WDS for PXE booting. In total there should only be four folders within the RemoteInstall folder as follows: SMSBoot SMSIMAGES SMSTemp Stores If additional folders exist in the RemoteInstall folder, such as: Boot Images Mgmt Templates Tmp WdsClientUnattend This is an indication that WDS has been manually configured at some point. The best course of action at this point is to reset the installation of WDS by reinstalling the PXE Service Point and WDS as described in the section "Reinstalling WDS And The PXE Service Point".That should be the initial steps in making sure that ConfigMgr will start the first bare metal deployment. Here are other helpful articles that can help you learning this : About Unknown Computer Support for Operating System Deployment http://technet.microsoft.com/en-us/library/cc431374.aspx Administrator Checklist: Prepare the Configuration Manager Environment for Bare Metal Operating System Deployment http://technet.microsoft.com/en-us/library/bb892807.aspx Deploy Windows 7 The Easy Way: Using WDS, MDT and AIK - Step-By-Step Video http://blogs.technet.com/b/danstolts/archive/2010/03/11/deploy-windows-7-the-easy-way-using-wds-mdt-and-aik-step-by-step-video.aspx A step by step for using OSD through System Center Configuration Manager 2007 http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx Thanks ! Anurag This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

It should at least get to the abortpxe.rom stage. You need to review the log file as Niall suggested to get more info. Without that, we can't even see if the PXE traffic is making it to the PXE server -- hanging at the DHCP part of the PXE boot is communication in general with both PXE and DHCP so it could be either causing the issue. Have you looked in DHCP to see if the system is properly getting an IP address? Note that I've had odd issues in the past with hosting everything on Hyper-V in a lab environment and a simple reboot of the guests seemed to cure everything also.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

OK I thought it might be a hyper-v thing causing the issues and I got a bit flustered with all the changes I made so I decided to start again. This time I installed everything on the same server (alongside DHCP) and so configured the following options: Changed REG key 'usedhcpports' to 0. Run "wdsutil /initialize-server /reminst:D:\RemoteInstall" Run "wdsutil /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes” Now I'm booting to DHCP and it's getting to the abortpxe stage. Thanks for all the help everyone. Really really appreciated!

Anurag: You have emphasized the WDS "not to be initialized". If I have initialized before adding PXE role to SCCM, how do I de-initialize the WDS ? I can only stop it. hydkk

step 10 in Anurag's post above, covers your scenario, I think? (reinstall WDS and PSP)Don