AJWhite1970 Posted November 21, 2018 Posted November 21, 2018 Hi I've successfully created a working 1809 LTSC gold image and got sysprep to run properly but when I restore the image via WDS with my answer file it takes over 90 minutes before the image gets to the login screen. In times gone by it's because I've got the .xml file wrong somewhere but in this case I can't see what the issue might be? I've tried running it through the ADK but it says that a catalogue for Windows 10 Enterprise LTSC 1809 doesn't exist and won't build one without crashing.... My answer file is as follows if anyone would be kind enough to compare to theirs? -------------------- * My School My School GMT Standard Time MY-MAK-KEY en-GB en-GB en-US en-GB true true true true true Work 1 true true dwBoAaaaBjAHQAUABhAHMAcwB3AG8AcgBkAA== false Local Temp Install Account Administrators ICT3 ICT3
mrwoberts Posted November 22, 2018 Posted November 22, 2018 On an affected device, take a look in the sysprep / panther folder log files, that should tell you if there were problems parsing the unattend file - looks okay to me, however I don't include the offlineimage section in my answer file. Have you tried it without an answer file, or with fewer/basic 'answers'. Here's mine to compare en-GB 0809:00000809 en-GB en-GB en-US en-GB true Microsoft OnError NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 0809:00000809 en-GB en-GB en-US en-GB 0 * true true true true Work true true 1 theres-no-chance-of-guessing-this true Config Administrators Config School false GMT Standard Time 1
AJWhite1970 Posted November 23, 2018 Author Posted November 23, 2018 Thanks for that, had a look through and tried without the offlineimage but still takes about 90 mins to go from initial reboot from WDS to login screen in Windows 10. The odd thing is this is only with 1809LTSB, my 1709 Edu image with the same answerfile takes less than 3 minutes to reboot... Out of interest, where does the logs get written as a PC reboots from WDS? The panther folder in c:\windows\system32\sysprep only has the log files for the actual sysprep running the day before when I captured the image, not the reboot from WDS. All very strange....
AJWhite1970 Posted November 23, 2018 Author Posted November 23, 2018 Ok, found the delay. It stalls for nearly 40 minutes trying to activate.... Hoping that’s the M$ activate bug rather than I’ve stuffed anything up
mrwoberts Posted November 24, 2018 Posted November 24, 2018 Hmm. Are you using a MAK, or KMS for activation? I've always used KMS, and more recently ADBA (Active Directory Based Activation). So are you still seeing 50 minutes delay on something else, other than activation?
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