Got that thanks. I think 1st problem was down to VLans and DHCP as moved the test pc into the server VLan and now get something different. (so lets see if we can sort this 1st before sorting the origanle problem out).
Now I get the Client ip coming up which I did not get before, then it says "downloaded WDSNBP..." but then it then it tells me to
press f12 for network service boot
Windows Deployment Services: PXE Boot Aborted.
PXE-M0F: Exiting HP PXE ROM
PS thanks to all that have helped so far on this one :)
Quick one on this just pressed the f12 for the second time and it has started something Why F12 twice?
OK now have it booting to Microsoft Solution Accelerator. But for some reason need to press F12 to start PXE then after it gets its IP address press F12 again before it fails this then kicks is.
Why F12 twice?
currently default boot image empty but have tried it with it set.
This must mean my 1st problem must have to do with VLans?
Can get rid of the F12 thing by going:
WDS >> Servers >> %Servername% >> right click on server and properties >> "Boot" tab >> "PXE Boot Policy" settings. I use "Continue the PXE boot unless the user presses the ESC key.
Glad it's sorted.
Thanks for that one :)
Originally Posted by AButters
So getting back to the 1st problem. It looks as if there is nothing wrong with my WDS as it now boots (not carried it on any further yet). But the last thing I want to be doing is putting all my computers into a different VLan to get to this stage. So does anyone have any help on getting it working over different VLans??
Must have something to do with the DCHP server Or possibly DNS but all looks as I think it should be in there.
have you setup the DHCP scope options within each scope, e.g. each subnet, rather than the server options?
I have set up 066 Boot server host name on all 4 of my dhcp servers under Server options. with servername.domain.local.
this then appeares in each subnet.
is this wrong? Lot of repeating myself if I need to put this rule into every subnet on all 4 servers?
Thats correct you need the
066 Boot Server Host Name set to IP Address of server (you can use name)
On all dhcp subnets
I also have
067 Bootfile Name set to Boot\x86\wdsnbp.com
This enables workstations that are plumbed into a particular network port on any of the vlans (subnets) you have in your environment find there way to the MDT\WDS server and the boot image
It isn't wrong, it is a possibility and it is how we have setup here for just 2 subnets. I would prefer write once, read many for standard configurations.
Originally Posted by shoggie
On another note, I have the 066 Boot Server option set to just the NETBIOS name not the FQDN and, option 067 set to the path of our default boot image in WDS.
I dont think it is my settings in DHCP that is stopping WDS working over VLans as all works fine when my test PC is on the server VLan.
I think it is down to PXE boot not getting a DHCP address from the DHCP servers thus not alowing it to go any further??????
Further testing. test PC in server Vlan finds and IP address and then boots into PXE and the WDS. Even if I remove 066 and 067 rules from my DHCP. I think My problem is when my test PC is in another VLan the PXE boot is not evern getting a DHCP IP address and this is what needs to be resolved 1st. Could it be down to my switches (CISCO)?
PS Thanks for all help so far :)
Or is there something on the WDS that I need to configure so whatever it is sending out can be got on any VLan?
Just did a quick google and it seems if your running vlans on cisco switches you need to make some changes to the switch configs in order for PXE boot to see your servers in the server VLAN.
See Network boot across many VLANs [Archive] - Web Hosting Talk
Got it thanks Needed 066 setting up with WDS ip address (nothing more)
And 067 setting up with boot\x64\wdsnbp.com
did this under the server scope of the each DHCP server
Thanks you all for your help :)