Changes in how NTLite process .xml files?

[Sweden10]

Hello, I have used NTLite a couple of years (paid version) and now I have run into an issue that I cant solve by myself. So I ask here.

I´m still on Windows 10 pro. So I reinstall my machines about every other month. I used a .xml file from last time. It has worked very well for some time (with minor adjustments). But this time it came out bad. Comparing the two files there are differences in the Unattended Section that affects account name, name of computer and to whom Win10 is licensed to. The 260828 is the product of entering the 260820 and processing it in NTLite.

I don´t know what causes these differences and after many attempts I have not been able to solve this. What I know is that i have the same base iso and the same input preset file (260820). And the 260820 iso works fine. But the 260828 iso gets it wrong.

Any ideas are appreciated.

 

[tistou77]

Sometimes settings can get reset, it’s happened to me (though it is quite rare).
In the "Unattended" page, reconfigure the settings that were lost and test if it's good or not (and for others too)
For the "?" in the directory path (instead of "C") I don't know, I’ve never seen that before.

 

[nuhi]

Hello, I have used NTLite a couple of years (paid version) and now I have run into an issue that I cant solve by myself. So I ask here.

I´m still on Windows 10 pro. So I reinstall my machines about every other month. I used a .xml file from last time. It has worked very well for some time (with minor adjustments). But this time it came out bad. Comparing the two files there are differences in the Unattended Section that affects account name, name of computer and to whom Win10 is licensed to. The 260828 is the product of entering the 260820 and processing it in NTLite.

I don´t know what causes these differences and after many attempts I have not been able to solve this. What I know is that i have the same base iso and the same input preset file (260820). And the 260820 iso works fine. But the 260828 iso gets it wrong.

Any ideas are appreciated.

Hi,

The 260828 file is an export, and Export offers to strip personal data from the copy it writes.
You answered Yes, so the private info and paths with username got stripped away.

Your saved preset is untouched. The strip only runs on the exported copy, never on the preset in your list and never during apply.
Load the original from the Presets page and your Unattended values will be the ones you set.
Export is for sharing with someone else; for a copy you feed back into your own builds, answer No at that prompt.

However, will improve in the next version that update cache prefix/path is saved and exported as [UPDATECACHE], that way it is more portable.

 

[Sweden10]

Hi,

The 260828 file is an export, and Export offers to strip personal data from the copy it writes.
You answered Yes, so the private info and paths with username got stripped away.

Your saved preset is untouched. The strip only runs on the exported copy, never on the preset in your list and never during apply.
Load the original from the Presets page and your Unattended values will be the ones you set.
Export is for sharing with someone else; for a copy you feed back into your own builds, answer No at that prompt.

However, will improve in the next version that update cache prefix/path is saved and exported as [UPDATECACHE], that way it is more portable.

Big thanks for the reply.