sted Posted June 24, 2011 Posted June 24, 2011 One of the schools i support has now got a hp microserver mainly for backup but to free space up on the main servers d drive ive been moving roles accross so far wsus no problem and im currently trying to move wds. I have managed to get it to show all images/boot files etc so that the new server is a direct copy of the older one. What i cant get it to do is pxe boot to it. The old server is the networks dhcp box the new one isnt. Ive tried altering/deleting dhcp options 60/66/67 and still it just sits there with a spinning propellor any ideas as this would free up approx 30gb from the same drive wherethe user data is stored
Sam_Brown Posted June 24, 2011 Posted June 24, 2011 Is it that it's not connecting to the new one at all or just that the old one is loading first? If it's still loading the old one you will need to change the PXE response times in the server properties so that the new one responds quicker than the old one. This was one of the issues I had when migrating over to a new server. If it's not this let me know and I'll try and think of something else.
Duke5A Posted June 24, 2011 Posted June 24, 2011 If the DHCP options are all set then I would think it might be the Windows Firewall on the new server. My old boss moved a WDS installation and couldn't get it to PXE. This turned out to be the cause.
sted Posted June 24, 2011 Author Posted June 24, 2011 i turned off the firewall on a client when pxe booted it just dosent get an ip address and eventually times out. Atm ive re enabled the service on the old server
sted Posted June 25, 2011 Author Posted June 25, 2011 the error on the client is something along the lines of no dhcp or proxy dhcp offers were received after a long time of spinning propeller
Sam_Brown Posted June 25, 2011 Posted June 25, 2011 Going to sound obvious but can you pin your DHCP server when logged onto the workstation?
sted Posted June 25, 2011 Author Posted June 25, 2011 Going to sound obvious but can you pin your DHCP server when logged onto the workstation? yup it works fine and if i reenable wds on teh dhcp server (and set dhcp for that and restart dhcp) it works on the workstation pretty much instantly
sted Posted July 1, 2011 Author Posted July 1, 2011 in the end i removed it from the older server and deleted all the option 60/66/67 stuff from dhcp and its now working even with firewall on
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now