[LTSB, Enterprise] Unattended.xml seemingly ignored?

[Memhave]

Hi,

 

I'm relatively new to preparing images in general and I'm still figuring my way around the ADK. I've made an answer file according to the documentation, but theres clearly something I've missed as Windows Setup is still requiring input (language, locale, etc).

I hope this is the current forum, but feel free to move it if it's incorrect.

 

The image was prepared from WinPE tool from a Windows 10 Enterprise Embedded [LTSB] reference machine. The answer file was written using WSIM from the ADK toolkit. It's called "Autounattend.xml" and it's in the root directory of the installation media.

This is my answer file and it's paired to a Windows 10 Enterprise LTSB:

https://pastebin.com/xWXsQn3B (as it's too long).

Edited August 9, 2018 by Memhave

[dfergusson]

Here is ours that you might find helpful.

 

   
       
           
               true
               true
               true
               true
               true
               Work
               1
               true
               true
           
       
       
           
               true
               true
               true
               true
               true
               Work
               1
               true
               true
           
       
   
   

[Memhave]

I noticed the difference is the keys, but they are deprecated. I will give those a try and report back, thank you.

 

Edit: no change.

 

My XML now looks like this ( I changed it to conform with Starter Guide for Windows IOT 10 Enterprise book, chapters 1-2):

 

https://pastebin.com/r3MVAWJf

Edited August 10, 2018 by Memhave

[Memhave]

So I removed the product key and this causes the installation to move forward.

Unfortunately, now I received the error:

 

"Windows cannot find the Microsoft License Terms".

 

two steps forward, another backwards I suppose.

 

Clues for this one?

Edited August 10, 2018 by Memhave

[dfergusson]

Are you testing this on a VM? If so this error can happen when start memory is set to less then 1024mb.

[Memhave]

Sorry for the long delay on a response, I don't have access to the files outside of work (yet).

 

Unfortunately, I'm not testing on a VM. This is a reference PC put together (16gb RAM, H170M mobo, some I7 [most likely] or I5 and no video card).

 

If I could get the installation to ask for a key (and unattend everything else) that would be a good step forward.

[dfergusson]

Unfortunately my knowledge of this way of deploying computers is limited, we use SCCM that take care of these steps for us.

hopefully someone who does this method will be able to help soon.

[Memhave]

Well thanks for the help anyway. It does seem like a specialised topic (and I'm very prone to very weird errors, so this isn't the first time someone else threw up their arms).

 

I've not heard of this tool, but our use is pretty specialised (we're embedded) so we need to strip, add and modify components (drivers, shell, etc) for the image. Does SCCM allow it? I don't mind giving it a try.

Edited August 13, 2018 by Memhave

[dfergusson]

Yes SCCM does all this and a lot more, not free but well worth the investment.

The software take time to setup so not something that easy to try and would also need to extend active directory schema.

 

SCCM integrates and take over WDS and WSUS and manages Microsoft Defender

 

More info on this here

https://www.microsoft.com/en-gb/cloud-platform/system-center-configuration-manager-features

Edited August 13, 2018 by dfergusson

[Steve21]

The image was prepared from WinPE tool from a Windows 10 Enterprise Embedded [LTSB] reference machine. The answer file was written using WSIM from the ADK toolkit. It's called "Autounattend.xml" and it's in the root directory of the installation media.

 

So what exactly are you trying to do here, you're using an autounattend on a captured image? Or the default media/DVD, but you've used a VM to make the unattend?

 

As for a start you mentioned using enterprise embedded, is that a typo or did you mean you want the embedded versions? (Seeing you have Windows 10 Enterprise Evaluation in the unattend file unless that's legacy?)

 

Steve

Edited August 13, 2018 by Steve21

[Memhave]

Yeah, let me just fix that - it's changed a bit. Or not. Can't edit my OP.

 

I'm using Windows 10 Enterprise 2016 LTSB from MSDN. I (did) try to generate the files (using the WinPE tool) from a preinstalled image but it didnt work out.

 

I'm now using the Enterprise image and I'm following instructions from Starter Guide Windows 10 IoT Enterprise (chapters 1 & 2).

 

My XML looks like: https://pastebin.com/sr5ZuNGj

 

The issue seems to persist (AutoUnattend.XML is being ignored).

 

Edit: It seems I made some progress (I started fresh, I guess some files were corrupted or something) - now it's not asking for the product key, but only for the localisation/language stuff (unintended) and disk setup (intended).

 

Thoughts?

Edited August 13, 2018 by Memhave

[Steve21]

Before digging into the unattend I take it you are using a US version of the ISO and not the GB one? The GB doesn't include US languages by default so wouldn't let it set them (It's an addon like the GB keyboard is to US etc, unless they changed it recently).

 

(As in on the page where it should skip and is asking for a language, what's it actually allowing you to select currently)

 

Steve

[Memhave]

I think its the GB version (about 70% sure). I'm going to try to deploy using the GB localisation. The setup does put en-GB as the default, but it seems I incorrectly assumed that it comes with multiple languages.

 

Yeah, so I changed the localisation to gb:

 

windowsPE pass(1):

 

           
en-GB            
en-GB            
en-US            
en-GB            
en-GB            
                
en-US            
       

 

 

oobeSystem pass (#?)

 

        
            
en-GB            
en-US            
en-GB       

 

A note on why the UILanguage is en-US, I was told very specifically that it should be en-US because:

 

When dealing with the English language, be aware that the Master is US first, everything else is deemed a child of that parent settings. Ergo en-US is the main UI Language and the variants can then be the regional settings.

 

I'm going to try it as en-GB. I'm not quite sure whether what the person, is correct but I will test it.

 

edit: rip formatting

Edited August 13, 2018 by Memhave

[Memhave]

Yeah, that seemed to be the issue - the UILanguage key & messed up and/or corrupted image.

 

It's unattended now, thank you.

[Steve21]

In the US version "US english" is the main one and everything else is a sub-option/downloadable extra.

 

In the GB version "real english" is the main one etc etc

 

MS Logic!

 

Steve