JTaylor Posted March 15, 2017 Posted March 15, 2017 I am attempting to build a Windows 10 Education image on a Dell Lattitude E5520to be captured and deployed using FOG Cloning Solution 1.3.4. I've started by installing Windows 10 Education build 1607 and booting into Audit Mode. From there I install the FOG Client and Windows System Image Manager. I create an answer file with Windows SIM using the Install.wim file from the win 10 installation disk. I move the amd64_Microsoft-windows-Shell-Setup_neutral and OEMinformation from the windows image to Specialize in the answerfile. Then save the file to C:\windows\System32\Sysprep\unattend.xml. i then run CMD as administrator and run C:\Windows\System32\Sysprep>sysprep.exe /generalize /oobe /shutdown /unattend. Once the laptop has shut down i capture the image using FOG. When the laptop boots back to windows I get an error saying "The computer restarted or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation." I know I can solve this by editing the setup registry but I want to prevent this error happening. Any advice will be most welcome. Thanks James Taylor ICT Technician Trinity Academy Halifax Shay Lane, Halifax, HX2 9TZ Tel: 01422 244890 Fax: 01422 240033 Web: Trinity Academy – Trinity Academy Halifax
PyROm Posted March 15, 2017 Posted March 15, 2017 Do you create a user in your answer file? If not you can get this error. When the error is on screen press shift+f10 to get a cmd prompt, reenable administrator account using net user, then reboot and see if it works.
Arthur Posted March 15, 2017 Posted March 15, 2017 (edited) I get an error saying "The computer restarted or encountered an unexpected error. Windows installation cannot proceed. The March 2017 Cumulative Update for Windows 10 includes a SysPrep-related fix. I would install this first (either manually or integrate it into the .wim) before capturing the image and then try again. Prior to installing the CU you should install the latest servicing stack update too. https://support.microsoft.com/en-us/help/4013429/windows-10-update-kb4013429 Addressed issue that causes the System Preparation (Sysprep) tool to fail. Edited March 15, 2017 by Arthur
JTaylor Posted March 17, 2017 Author Posted March 17, 2017 I don't create a user in the answer file I just enable the administrator account from the local user manager prior to sysprep. I tried the re-enable using Net User anyway and got no result.
JTaylor Posted March 17, 2017 Author Posted March 17, 2017 I have run both of these updates and any picked up by windows updates and still get the same error.
Fazza Posted March 17, 2017 Posted March 17, 2017 I don't create a user in the answer file I just enable the administrator account from the local user manager prior to sysprep. I tried the re-enable using Net User anyway and got no result. I dont know anything about FOG but I do know (from personal experience) that by default the local administrator account is disabled and when you run sysprep it basically defaults the OS so the local administrator account is disabled once sysprep has finished working. Someone has implied that you need to add a user to your answer file so try that next and see if that works.
prozario Posted March 20, 2017 Posted March 20, 2017 It is probably simply because you are using fog to capture the image and has corrupted it in some way. Try capturing the image using WDS, why even go for 3rd party when WDS is built in.
JTaylor Posted March 21, 2017 Author Posted March 21, 2017 tried putting the user in the answerfile and have just syprepped it with out capturing just to test but got a different error. "Windows could not parse or process the unattend answerfile for pass [specialize]. the settings specified in the answerfile cannot be applied. the error was detected while processing setting for component -Microsoft-Windows-Shell-Setup]. please see below the contents of my answerfile. true %COMPUTERNAME% Akroydon Greenwich Mean Time true en-gb en-gb en-gb en-gb true true true true true Work 1 true true UgAwAGMANQA4ADUAZAB0AEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA== false Administrator Administrators Administrator Local Administrator
Arthur Posted March 21, 2017 Posted March 21, 2017 tried putting the user in the answerfile and have just syprepped it with out capturing just to test but got a different error. "Windows could not parse or process the unattend answerfile for pass [specialize]. the settings specified in the answerfile cannot be applied. the error was detected while processing setting for component -Microsoft-Windows-Shell-Setup]. please see below the contents of my answerfile. Open your XML file in the Windows System Image Manager (from the Windows ADK). This will ensure that it doesn't contain any errors. The XML in your last post is missing lots of things.
JTaylor Posted March 21, 2017 Author Posted March 21, 2017 Open your XML file in the Windows System Image Manager (from the Windows ADK). This will ensure that it doesn't contain any errors. The XML in your last post is missing lots of things. Setting NetworkLocation is deprecated in the Windows image Components/oobeSystem/amd64_Microsoft-Windows-Shell-Setup_neutral/OOBE/NetworkLocation Setting SkipMachineOOBE is deprecated in the Windows image Components/oobeSystem/amd64_Microsoft-Windows-Shell-Setup_neutral/OOBE/SkipMachineOOBE Setting SkipUserOOBE is deprecated in the Windows image Components/oobeSystem/amd64_Microsoft-Windows-Shell-Setup_neutral/OOBE/SkipUserOOBE Above are the errors I get. Also what is my answerfile missing. I followed a tutorial online and copied everything they did.
PyROm Posted March 21, 2017 Posted March 21, 2017 (edited) Second try with right quotes, doesnt let me edit for some reason.. We use a minimal sysprep file to get through oobe... en-GB en-GB en-GB en-GB true true true true true 1 !password hash removed! false temp_user administrators temp_user * GMT Standard Time 1 net user administrator /active:yes We then have a file c:\Windows\Setup\scripts\SetupComplete.cmd which windows autoruns after install (just create folder if needed and put file in there, no need to make reg changes etc.) net user temp_user /delete bcdedit /set recoveryenabled NO sc config FOGService start= delayed-auto shutdown -t 300 -r This deletes the temporary user created in sysprep, disables the recovery console/partition, changes the fog client to start automatically (the latest versions of fog client should be set to disabled before imaging as it can cause problems if not, although havent run into any myself) and reboots the machine after 5 minutes (so fog client loads and starts rename/domain join process). Edited March 21, 2017 by PyROm
PyROm Posted March 21, 2017 Posted March 21, 2017 Forgot to add, when we run sysprep we specify the xml file, I dont know if this is needed if using the default unattend.xml name. sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml
ollyyllo Posted March 24, 2017 Posted March 24, 2017 If the unattend.xml is in the same folder as sysprep.exe it will be pick up automatically even if you dont use the switch 1
k-strider Posted March 24, 2017 Posted March 24, 2017 if your using FOG 1.3 and the new client did you follow this? if you plan to use Sysprep before image capture and are also planning to use the FOG Client, You must disable the FOGService service from running at boot before you Sysprep to take your image, and then re-enable it within your SetupComplete.cmd file so that it is re-enabled after the image deployment is complete. Failing to do so will break the Sysprep post-deployment process with an error message that says "Windows Setup could not configure Windows to run on this computer’s hardware.” Disable FOGService: Windows Control Pannel -> View by Small Icons -> Administrative Tools -> Services -> Right click FOGService -> Properties -> Startup Type -> Disabled Re-enable FOGService post-imaging: Add these lines to SetupComplete.cmd sc config FOGService start= auto shutdown -t 0 -r 1
JTaylor Posted March 27, 2017 Author Posted March 27, 2017 Just to summarise then prior to sysprepping the PC I ran the march 2017 cumulative update followed by all other updates from windows updates. installed the FOG Client and set its startup to Disabled. created an Unattend.xml file located C:\Windows\System32\Sysprep with code en-GB en-GB en-GB en-GB true true true true true 1 IQAgAHAAYQBzAHMAdwBvAHIAZAAgAGgAYQBzAGgAIAByAGUAbQBvAHYAZQBkACAAIQBQAGEAcwBzAHcAbwByAGQA false temp_user Administrators temp_user * GMT Standard Time 1 net user administrator /active:yes created a SetupComplete.cmd file located %WINDIR%\Setup\Scripts containing the code net user temp_user /deletebcdedit /set recoveryenabled NOsc config FOGService start= delayed-autoshutdown -t 300 -rsc config FOGService start= autoshutdown -t 0 -r and then finally ran C:\Windows\System32\Sysprep>Sysprep.exe /generalize /oobe /shutdown /unattend:Unattend.xml Thanks for all the help i can now move on to the next step of auto driver install. Might be posting a new thread
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