Jump to content


levellers

Established Members
  • Posts

    1
  • Joined

  • Last visited

levellers's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. 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?
×
×
  • 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.