Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added oobesystem locale component to unattend xml #39

Merged
merged 1 commit into from
Sep 2, 2017

Conversation

dayglo
Copy link

@dayglo dayglo commented Sep 2, 2017

When you updated your win10 iso to use enterprise eval, the Windows 10 build stopped working. It got stuck on the oobe, asking for region stuff.

I added it (and just tested it on vmware fusion)

@StefanScherer
Copy link
Owner

Thank you @dayglo ! That helps a lot. I'll merge it and also check some insider templates for 10 and 2016.

@StefanScherer StefanScherer merged commit 287ba63 into StefanScherer:my Sep 2, 2017
@dayglo
Copy link
Author

dayglo commented Sep 2, 2017

my pleasure! I actually just realised that the autologon stopped working as well. if i manually log in, the winrm setup kicks off and the build continues. Ill see if i can fix that when i get a sec

@StefanScherer
Copy link
Owner

It happens during win-updates.ps1 after the first bulk of updates and a required restart. After logging into the VM manually the AutoAdminLogon registry key is 0 and DefaultPassword isn't set.
We could try and set these in Autounattend.xml in the FirstLogonCommands.

@StefanScherer
Copy link
Owner

Oh, that was also discussed in joefitzgerald#239, also adding the reg keys.

@StefanScherer
Copy link
Owner

OK, it's fixed with 8781254
I also changed to en-US locale as a default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants