robertg1274 Posted October 16, 2018 Posted October 16, 2018 Hi, I am having an issue. I am currently trying to capture a WIN 10 image of a register we use in our stores for later deployment to other registers. I have installed a clean image with all our register software and tried to capture the image, only for it to get stuck on the Sysprep. It has been stuck all night because I left it Sysprep-ing last night at EOD and when I came in this morning it was stuck this way. I am including a picture. I know that it has nothing to do with software because we have captured an image for the registers before with all the same software on there, only for WIN 8.1. The register is an HP RP9 Touch-Screen AiO. We are using SCCM on a Server 2016. Can anyone help or have any ideas? I am so stuck! Thanks in advance.
robertg1274 Posted October 16, 2018 Author Posted October 16, 2018 Now I am getting an error due to certain Microsoft products being installed. Weird.
FM1 Posted October 16, 2018 Posted October 16, 2018 Hello Roberg1274, SYsprep is way more breakable under windows 10. Make sure you use a pristine fresh install from the ISO installed of windows 10. Install your software and then sysprep. Do not install an older ISO and then do updates and then try to sysprep - sysprep goes hairy. BEst of luck. Thank you, Franco
robertg1274 Posted October 16, 2018 Author Posted October 16, 2018 I did all that you suggested and am running the capture now. it looks good so far, fingers-crossed! I will let you know how it turns out. Thanks for the quick response!
robertg1274 Posted October 16, 2018 Author Posted October 16, 2018 Nope, still the same thing. It gets stuck on Sysprep. Been stuck for almost 2 hours now. What should I do?
Arthur Posted October 17, 2018 Posted October 17, 2018 (edited) It gets stuck on Sysprep. Been stuck for almost 2 hours now. What should I do? In addition to what @FM1 said, I would also create the image in a VM since it won't have any drivers interfering with sysprep. Another thing you could try is to prevent the VM/PC from connecting to the Internet for the duration of the build. See below for the reason. https://syscenramblings.wordpress.com/2017/10/25/windows-10-1709-reference-image When creating a Windows 10 reference image a common issue is that the store updates will autoupdate while you are busy installing software updates and applications. This then causes sysprep to fail in giant ball of fire. To solve this there are basically two options and for some option one doesn’t seem to work which is why I always opt for option two. Option 1, follow the guidance for disabling auto store updates. This consists of adding a DWORD registry item to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore named AutoDownload with a value of 2. More info on how to do this check out the blog over at deploymentresearch.com Option 2, is to use a WSUS and then disable internet access for the duration of the build. This can easily be achieved using PowerShell and a sprinkle of magic. There could be many other reasons why sysprep fails but you will need to check the log files. Edited October 17, 2018 by Arthur 1
robertg1274 Posted October 18, 2018 Author Posted October 18, 2018 Thank you, Arthur, the VM clean environment worked. I am now further than I was at any other attempt before this one. After the capture, I will test and let you know what's up! This forum is awesome!
robertg1274 Posted October 19, 2018 Author Posted October 19, 2018 The image does not work. I think the .WIM file got corrupted in the capture process. I will try to upload a picture of the Error Message.
robertg1274 Posted October 19, 2018 Author Posted October 19, 2018 Here is a picture of thererror meggage I receive when I try to image with the current .WIM This is the error I received when I did the original capture of the .WIM file. Anyone have any insight? Suggestions?
robertg1274 Posted October 19, 2018 Author Posted October 19, 2018 Currently I am trying to create a clean image that does not finish with errors.
RJohnson91 Posted October 23, 2018 Posted October 23, 2018 Currently I am trying to create a clean image that does not finish with errors. When we were using Ghost at my previous place of work, we utilised the build in 'image check' before we proceeded, this would highlight corrupt images, so we could re-capture. Has your solution got something similar you could use? Ryan
robertg1274 Posted October 24, 2018 Author Posted October 24, 2018 When we were using Ghost at my previous place of work, we utilised the build in 'image check' before we proceeded, this would highlight corrupt images, so we could re-capture. Has your solution got something similar you could use? Ryan We use SCCM, so I am not entirely sure. I can check tomorrow. I will let you know.
Arthur Posted October 24, 2018 Posted October 24, 2018 [ATTACH=CONFIG]50645[/ATTACH] This is the error I received when I did the original capture of the .WIM file. Anyone have any insight? Suggestions? Are you using a really old version of MDT like the original release of MDT 2013 Update 1 (build 8290) which was incredibly buggy? The "Unable to create WebService class" bug was fixed by Microsoft when they re-released Update 1. https://blogs.technet.microsoft.com/msdeployment/2015/09/15/mdt-2013-update-1-re-released-build-8298 If so, I would upgrade to the latest MDT version and update your boot images... https://docs.microsoft.com/en-us/sccm/mdt/
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