scotyboy56 Posted May 31, 2012 Posted May 31, 2012 School I work at has just got a samsung NB200A4B. And I need to create a build disk for it as they will be purchasing more at some point and I have never used MDT before as I have just taken over from a different technician. I have imported all the drivers and the OS into the workbench and it seems to be okay but whenever I pxe boot the laptop it loads the files from boot\x86 etc and I want it to boot from the x64 as it is going to have windows 7 64bit. (does that matter) whenever it finishes loading the files it says that the network driver isn't installed PCI\VEN_10C&DEV_8168&SUBSYS. I have made sure all the network drivers for the laptop have been imported into the deployment workbench. Please help me. Am I doing something stupid?? Im on an apprenticeship so im still very new to all this. Please help me
plexer Posted May 31, 2012 Posted May 31, 2012 When you imported the drivers did you re-generate the boot images and copy them them into wds? Have you got it setup to detect the architechture that way it picks the x86 or x64 boot image. Ben
scotyboy56 Posted May 31, 2012 Author Posted May 31, 2012 No how do I re-generate the Build disks?? and I dont know if it is setup like that how do i check???
plexer Posted May 31, 2012 Posted May 31, 2012 Right click on the deployment share and click update deployment share this will check if files have been added that need to be included in the boot files and regenerate them. Then you'll need to replace the existing boot images in wds with the new ones. Ben 1
scotyboy56 Posted May 31, 2012 Author Posted May 31, 2012 Awesome thanks shall give that a go and see if it works how do i make it pick up x64 image instead of x86??
scotyboy56 Posted May 31, 2012 Author Posted May 31, 2012 Thankyou the updating is so simple, but would never have thought of it in a million years thankyou ben
scotyboy56 Posted May 31, 2012 Author Posted May 31, 2012 ARGH!!!! I HATE MDT!!!! its still not working i followed that guide step by step
dalsoth Posted May 31, 2012 Posted May 31, 2012 (edited) I remember having this problem. I think you also need to make sure that you have the setting in WDS to make them press f12 and again to continue. I also remember perhaps in DHCP or elsewhere making sure they were pointed to pxeboot.n12 boot file so that it checked the architecture before continuing but this was a while ago and I am too hazy to recall much more. I believe you also need a valid x64 boot image on the server before it will work properly. This might also help: SCCM OSD – When to use an x86 or x64 Boot Image « SCCM FTW It will explain if you are unsure about what types of image can boot or build each other. http://www.digitalsupporttech.com/kb/932447/ Edited May 31, 2012 by dalsoth
SYNACK Posted June 1, 2012 Posted June 1, 2012 The other thing to check is that the CPUs actually support x64 as if they don't it will not offer the 64bit boot image.
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