brandon Posted December 27, 2017 Report Share Posted December 27, 2017 I've been trying to build WDS boot media based on Win 10 x64 1709. I've captured the image and created the media, but when I go to import it into WDS, I get an "Invalid Image File" which says that the file doesn't contain a valid boot image. I've started the process from scratch a number of times with the same result. Link to comment Share on other sites More sharing options...
Jeff Harris Posted December 27, 2017 Report Share Posted December 27, 2017 You'll need to make sure you are using the Media wizard to create and upload your WDS boot media, before uploading your Windows 10 image file. Here's the link to the SmartDeploy guide for integrating with WDS. Try starting back at the top of this document. https://www.smartdeploy.com/wp-content/uploads/SmartDeploy_WDS.pdf Link to comment Share on other sites More sharing options...
brandon Posted December 27, 2017 Author Report Share Posted December 27, 2017 I followed those instructions and found myself here. Link to comment Share on other sites More sharing options...
Jeff Harris Posted December 27, 2017 Report Share Posted December 27, 2017 You can use the SmartDeploy Cmd Prompt command; smartwim /info [wim file] to view details of the wim to make sure it's ok. Other than that I'd make sure you have the latest version of SmartDeploy installed, and try uploading a different boot wim to your WDS host to rule out a problem there. If you have a support contract with SmartDeploy, you can contact support@smartdeploy.com for additional help. Link to comment Share on other sites More sharing options...
brandon Posted December 27, 2017 Author Report Share Posted December 27, 2017 It appears to be an issue with 1709. https://www.windows-noob.com/forums/topic/15897-upload-capture-image-to-wds-credential-window-different/ Thanks for your help. Link to comment Share on other sites More sharing options...
brandon Posted December 28, 2017 Author Report Share Posted December 28, 2017 (edited) EDIT: Turns out it was an issue with VirtualBox and the shared folder. Once I copied the WIM files over to my VM, they were recognized correctly. Actually, this still isn't working with Win 10 1703. I've spun up a new instance of Server 2016 and am still having issues. Edited December 28, 2017 by brandon Link to comment Share on other sites More sharing options...
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