Unattended settings persist when reloading an image

T

tired-it

Member
Context:
  1. Make an ISO in NTLite.
  2. Use its built-in options for creating an unattended file.
  3. Reload the same ISO in NTLite.
  4. Check unattended page. It is set to default. None of the customizations are visible. Clicking on enable shows a blank page.
My suggestion is for NTLite to load the unattended file so when the ISO is loaded, the user can see what customizations are in it. I can click on enable, but then all the fields are blank even though I know that the file itself has been filled in by the program. That can be confirmed by manually opening the file in the cache or a created ISO. It's a small change and I am not sure how feasible it is, but it helps to be able to check what settings were added instead of having to re-add the settings (or use a preset) when troubleshooting.
 
This question has been answered by nuhi before. Due to NTLite's current design, it's not practical to import existing unattended files because it may contain custom user edits for Unattended features not currently supported. To import that file could wipe out those changes.

For this reason, NTLite prefers to create a new unattended file from scratch.

In reality, once you have a working answer file it's easy to copy it to a new ISO project by hand. The only settings that need to be watched are the optional product keys, and the selected image's index number (if this is a multi-edition ISO). Editing those in Notepad isn't hard.
 
I can definitely understand the conflict with custom changes; however, at that point I imagine the user is better off manually managing the file as needed. The suggested change is mainly for users that only use NTLite's options and none else. It is a small issue in the grand scheme of things, more of a convenience if anything. I don't dabble much with unattended files as I only really use it to skip the Windows OOBE and that's it.
 
The gap is between those who need the basics of bypassing all the Windows install prompts, vs. the full functionality of Unattended scripting (run commands, full audit mode).

If you wanted NTLite to always push its version, then it would need a no-clobber setting to warn if it was overwriting an existing file. Sometimes users will import a pre-made ISO for quick edits.
 
You must log in or register to reply here.
Back
Top