9/22/2023 0 Comments Ntlite import unattendMicrosoft complicated it a bit over the years, and a big part of the problem is that each new operating system and edition of Windows, such as 1809, 1903, 21H2, etc keep changing certain things like renaming registry keys, making some keys obsolete, adding new keys, new default user account thing, changing how start menu works, the new cloudstore system, and so forth. But as you can see from the other threads, I don't think many people have been super successful with that, and end up settling for some compromise instead, where they get just a few select things working and call it good. I'll try again in the future and if successful write up a guide on it. My question is, how could it get lost if I deployed the NTLite ISO containing this auto-unattend.xml file on the VM to begin with? Did sysprepping remove it?Ĭlick to expand.I only tried a few times myself to make autounattend stuff work, and ended up abandoning it. However, when I successfully deployed this sysprep'd Windows.ISO on the physical laptop, I noticed Microsoft asked me those 10 default questions again, which makes me suspect that somehow the auto-unattend.xml file had somehow got lost (that was part of the original NTLite ISO I had made). WIM file and replaced the original install.wim file with this custom install.WIM file in the Windows.ISO file. WIM file on the C Drive of the VM, then I shut down the VM, mounted its VHDX image, grabbed the. I created the sysprep'd image, I saved its. iso file I had created in NTLite, it had the auto-unattend.xml file thus it gave the answers to Microsoft's about 10 questions they always ask you when you install Windows. When I created the sysprep'd image on the hyper-V VM off a. Click to expand.Sorry for the double-post but I just want to give an update: So this time, it worked! Amazing feeling and thank you for the info you gave me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |