timbo343 Posted November 30, 2015 Posted November 30, 2015 In the past we used to use Ghost for image deployment. It worked great for us but we are looking at WDS and MDT2013. We are just trying base images first in windows 10, walking before we are run. We have a fair few Lenovo 7303CTO machines (M58e) that use the Marvel Yukon driver and we cannot get them to talk to the WDS server. All the other machiens (HP/Dell/Zoostorm) talk without any problems but these Lenovos will not detect the server. It sits at DHCP and then timesout. Does anyone else have these machines or even machines that use Marvel Yukon cards and have the same problem? Thanks
carnforthhigh Posted November 30, 2015 Posted November 30, 2015 (edited) The local primary school we support has these exact machines. We haven't had any trouble them booting to WDS. The only issue we had was the boot.wim had to have drivers added into it. Don't know if this helps. Edited November 30, 2015 by carnforthhigh
timbo343 Posted November 30, 2015 Author Posted November 30, 2015 That's annoying. I don't think adding the drivers to the boot.wim file will help. The problem i am having is before the boot.wim file - it might be the machine, off to test another lenovo machine.
timbo343 Posted November 30, 2015 Author Posted November 30, 2015 That's annoying. I don't think adding the drivers to the boot.wim file will help. The problem i am having is before the boot.wim file - it might be the machine, off to test another lenovo machine. Not the machine, seems to be a fault with them all.
sted Posted November 30, 2015 Posted November 30, 2015 What os is server and do you have uefi\secureboot on?
timbo343 Posted November 30, 2015 Author Posted November 30, 2015 What os is server and do you have uefi\secureboot on? There is nothing like that in the bios of the lenovo machines, the bios is very basic. The server os is 2012r2. The error is pxe-e53. Been told the gateway machines we have (rebranded acers) using the broadcom driver dont pick the server up too however i think this is a different error.
timbo343 Posted December 1, 2015 Author Posted December 1, 2015 (edited) Just to update this... After doing a search on the net, i tried the DHCP 66 and 67 options. 66 - added hostname.localdomain 67 - added \boot\x86\wdsnbp.com and this has worked on the lenovo machines. Fingers crossed for the Gateway machines. EDIT: Yep the gateway machines work too. It seems that the Network needed a gateway address which we don;t offer via DHCP. Edited December 1, 2015 by timbo343
carnforthhigh Posted December 1, 2015 Posted December 1, 2015 That's annoying. I don't think adding the drivers to the boot.wim file will help. The problem i am having is before the boot.wim file I thought that might be the case.
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