Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, September 9, 2015 4:48 PM
I could use a bit of troubleshooting help from anyone willing to help out. basically i just need someone to see if they are able to run sysprep /generalize on a fresh (not fresh is ok too i guess) install of windows 10 professional (volume license) after it's been joined to a domain, reboot, and see if you can make it all the way through setup without any errors or setup halting because of an error.
This is related to the thread below, but figured it would be a good idea to separate them.
All replies (12)
Friday, September 11, 2015 4:46 PM
Hello,
Please backup the registry and check the following keys:
HKML\SOFTWARE\MICROSOFT\WINDOWSNT\SOFTWAREPROTECTIONPLATFORM Set the skiprearm value to 1
HKLM\system\Setup\Status\SysprepStatus Set the GeneralizationState value to 7
Then reboot the computer and see if the issue persists.
Thanks,
Simon Wu
TechNet Community Support
Wednesday, September 16, 2015 5:37 PM
Simon Wu, That didn't help. i don't think it's a activation issue. it does it if i am activated or not.
I would like to know if anyone has been able to successfully sysyprep /generalize a domain joined windows 10 machine and get it all the way through setup without any errors (and get back to a logon screen or desktop). that's the goal of this thread, to know if anyone has been successful at that.
Thursday, September 17, 2015 2:32 PM
I did my 3 (4 really) tests and posted results in your other thread. Do you think it is necessary to have this thread too?
It probably should be changed to Discussion type.
Thursday, September 17, 2015 3:28 PM
Tripredacus, Yes, i think it's necessary. This one was to see if it was working for anyone. the other one was to talk about why it's happening to me. Oh, and i created this thread 5 days before you posted your testing results... right after you replied on that thread saying this "you are the only person to have posted this error! At least that Google can find."
I appreciate the tremendous amount of work that you have done to help out. This now obviously not a problem that only i am seeing (after hearing the results of your own testing). But i would still like to know if anyone has been able to do this successfully. (i doubt it now that i know that i know your having the problem too.
not sure why my font keeps changing on this reply...
Thursday, September 17, 2015 8:56 PM
The question becomes why sysprep and capture a domain joined machine? It is unsupported. So even if you get it to work why put yourself in an unsupported state?
Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/
Thursday, September 17, 2015 9:42 PM
Ty, Can you show me where it's documented that it's unsupported?
Also, it's worth noting that removing the machine from the domain doesn't fix the problem.
Thursday, September 17, 2015 9:55 PM
Everyone keeps saying that its "unsupported" but i think that may be a myth that is being picked up and spread by others.
Here is the info about sysprep including "unsupported scenarios".
https://technet.microsoft.com/en-us/library/hh825209.aspx
If you notice they built in a function into sysprep that removes the machine from the domain, and included the words "If the PC is joined to a domain, Sysprep removes the PC from the domain."
I appreciate that IT guys do things differently, but i choose to join my machines to the domain before sysprepping them. i have been doing this for 10 years and it's never been an issue until windows 10. What changed? maybe they removed support for sysprepping a domain joined machine and didn't tell anyone?
Thursday, September 17, 2015 10:11 PM
Apparently it isn't explicitly unsupported it just is not the best practice. https://social.technet.microsoft.com/Forums/en-US/93c3a7b9-90a8-4996-966a-e07e4836a9e2/sysprep-and-domain-joined-pc?forum=configmgrosd
Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/
Thursday, September 17, 2015 10:20 PM
Good link. Johan is awesome! :)
I have my fingers crossed that the next version of windows 10 will have this issue resolved.
With the excellent testing that Tripredacus did, I am now convinced that it's not a left over group policy or something that’s causing the problem (since joining to domain did it for him too), but rather a problem with OOBE on the current version of Windows 10.
Thursday, September 17, 2015 10:51 PM
Do you have any interesting logs of the sysprep?
Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/
Friday, September 18, 2015 2:43 PM
My testing was in the thread linked by the first post here.
Friday, September 18, 2015 3:03 PM
Actually, Tripredacus posted some good logs that match what i am seeing too on the following thread (look for the reply with this time stamp) September 14, 2015 4:56 PM