RLR Posted April 13, 2016 Posted April 13, 2016 Imaging is fairly new for me. Been doing it for about a year with a setup that was already in place. I've created a new Windows 10 image but get an error when deploying it. I think it might be because I'm still using an old boot.wim image. Do I need to create a new up-to-date boot.wim to deploy windows 10?
Garacesh Posted April 13, 2016 Posted April 13, 2016 (edited) Similarly to you, I inherited deployment etc with no idea of what to do.. TL;DR, you need to: 1) Update your MDT to MDT 2013 Update 1 2) Download your .iso from VLSC 3) Extract the .iso 4) Import the extracted OS into MDT 5) Create Task Sequence 6) Right click the deployment share, select "Update Deployment Share", choose the "Completely regenerate the boot images" option 7) Wait. Wait more. 8) Grab a spare machine, PXE boot and cross your fingers Edit: To be honest, I created a separate Deployment Share for Windows 10 so I wasn't mucking about with the Windows 7 share we had that worked. I can b0rk my W10 share to my hearts content and it doesn't interfere with reimaging machines. Though it will mean you'll need to learn a bit more about setting up share Rules. Edited April 13, 2016 by Garacesh 1
RLR Posted April 13, 2016 Author Posted April 13, 2016 Thanks for the info. I installed mdt a few months ago as people suggested it's superceded wds. I've still not used it much as wds is working for us, but will look into mdt later. Looks like I needed to boot.wim file from the windows 10 iso and not just the boot.wim from the deployment tools on wds.
alfatec Posted April 13, 2016 Posted April 13, 2016 I am using wds just create a new capture and deployment wim from your boot.wim of your win 10 ISO. 1
DJ-1701 Posted April 13, 2016 Posted April 13, 2016 Actually, you do need the latest ADK (which contains the latest Windows PE) for this to work with MDT, otherwise you will get errors. The following is extracted from my Blog on my WDS setup. ADK for Windows 10 https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx#adkwin10 ADK On the server you have designated for MDT, install ADK for Windows 10 to a directory of your choosing, selecting No to the Participation for the Windows Kits. The main feature you want to install is the Deployment Tools and the Windows Preinstallation Environment (Windows PE), you can if you wish install other elements if you will be experimenting with them later.
Garacesh Posted April 14, 2016 Posted April 14, 2016 Valid point. Forgot about the ADK. Well remembered. 1
sted Posted April 14, 2016 Posted April 14, 2016 Thanks for the info. I installed mdt a few months ago as people suggested it's superceded wds. I've still not used it much as wds is working for us, but will look into mdt later. Looks like I needed to boot.wim file from the windows 10 iso and not just the boot.wim from the deployment tools on wds. mdt can do some of the jobs of wds but not all you still need wds to pxe boot pcs into mdt 1
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