tim.cummings@juhsd.net Posted November 8, 2017 Report Share Posted November 8, 2017 I got an error when trying to capture and new fresh image of windows 10 enterprise 1709 "the specified image does not contain a <customdata> node and cannot be used for deployment" not sure what the issue is here. Capturing from vm on ESXi 6.5 host using pxe boot and capture. see logs https://1drv.ms/f/s!AhwoICTP_02ug-4TJbBesh7u6f8z_g Link to comment Share on other sites More sharing options...
Jeff Harris Posted November 8, 2017 Report Share Posted November 8, 2017 Can you try the warm capture method outlined on page 76 of the User Guide and see if that helps? I'd want to rule out the boot wim being used in your WDS/PXE setup. https://www.smartdeploy.com/wp-content/uploads/SmartDeployUsersGuide_V2.pdf Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted November 9, 2017 Author Report Share Posted November 9, 2017 Using a ISO seems to have worked. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted November 14, 2017 Author Report Share Posted November 14, 2017 You know what it started doing the error again. I had to make a change in the image and tried to take the image all over again using the iso to put in the vm, and gets all the way to the end before i get the error. logs: https://1drv.ms/u/s!AhwoICTP_02ug-4oQrAIKNYyEhgxIQ Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted November 14, 2017 Author Report Share Posted November 14, 2017 When I took the image, I selected for use with WDS and only selected the OS partition, that seems to have worked. Link to comment Share on other sites More sharing options...
gaz2600 Posted March 30, 2018 Report Share Posted March 30, 2018 I get the error using the ISO and with WDS selected. Capturing a 2nd time without changing anything works. I've had this happen twice. Link to comment Share on other sites More sharing options...
jaykeblakk Posted May 18, 2018 Report Share Posted May 18, 2018 I've had this happen a few times. My solution is to try the cold capture method twice, let it error out both times, and then attempt the warm capture method. It has always fixed the issue for me after that. 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