Bare Metal Boot Assistance

Usage and Config OSD
1

Hi All,

Fairly new to the OSD and would appreciate some assistance.

So far I have completed the following:

  • Uploaded MDT Bundle and OS Resources (Windows 10)
  • Uploaded Windows 10 WIM file in the Image Library
  • Created Bare Metal profile based on that WIM
  • Setup OS Deployment Server
  • Sent Bare Metal profile to the OS Deployment server

Just now trying to figure out how I get a PC to boot to install this .WIM?
What options to I need to set in DHCP so that when i boot to NIC it finds this OS Deployment server?

DHCP Server is running on 192.168.11.4
OS Deployment server is running on 192.168.11.26

Help would be appreciated.
Like I said I am very new to this, so please excuse my ignorance…

Rob.

2

I’ve tried setting the following:

On DHCP server options

  • 066 Boot Server Host Name: 192.168.11.26
  • 067 Bootfile Name: PXEClient

If I attempt to boot NIC I get the following error on client PC: “proxydhcp did not reply to request on port 4011”

3

I have just disabled Windows Firewall on both DHCP server and OS Deployment server and it no longer comes up with that error, however nothing eventuates… There is now error.

I get the below and then the PC reboots:

BM_PXE.JPG830×277 21.1 KB

OR the following on a VM

BM_PXE1.JPG718×247 26.7 KB

4

Further info…
I installed Windows Deployment Services on the OS Deployment Server.
On the VM I was able to boot to Bare Metal boot, and select the WIM to install.

BOOT1.JPG712×570 35.3 KB

However, after selecting I get another error…
Not sure where to go from here?

BOOT2.JPG774×461 38 KB

5

Looks like there is some problem with the data on your bare metal server.
Please run a Full Synchrinization of the server from the Bare Metal Server dashboard.

6

@robertmullen, Did you ever sort this out? I’m running into the same “no winPE software” problem. I’ve uploaded 2 separate MDT bundles but have the same issue. ld images using winPE 3 or 5 work fine but nothing with winPE 10 has worked yet.

7

I confirm this should be related to bare metal server synch. Have you run the Full Synchronization against the bare metal server? Did it run successfully? In any case, please check synch log file on bare metal server computer for errors.

Thanks

8

I havent had a chance to test - have been off work.
Will be trying again in the coming weeks/month.

9

That’s correct. I found that running a sync made everything work.