Run a batch file in NTLite?
- Thread starter RBCC
- Start date
If you're running NTLite, there's no practical reason to install Windows ADK, or use WSIM. Most of the same functionality that's provided in both products can be done natively in NTLite.
The major difference is WSIM allows to you add pre-/mid-/post-Setup tasks, but it does them through Unattended XML run commands.
But if you still prefer to use WSIM, follow this strategy:
- Edit your boot & install images using NTLite, to add Updates and Features, remove components, and change Settings.
- Provided the modded images to WSIM. Allow WSIM to manage the other aspects of scripting or Post-Setup tasks.
Mixing & matching between NTLite and WSIM for Post-Setup tasks is not advised. WSIM is better if you need custom scripts to run the middle of deployment, usually if you have some dynamic provisioning step that needs to be scripted.
The major difference is WSIM allows to you add pre-/mid-/post-Setup tasks, but it does them through Unattended XML run commands.
But if you still prefer to use WSIM, follow this strategy:
- Edit your boot & install images using NTLite, to add Updates and Features, remove components, and change Settings.
- Provided the modded images to WSIM. Allow WSIM to manage the other aspects of scripting or Post-Setup tasks.
Mixing & matching between NTLite and WSIM for Post-Setup tasks is not advised. WSIM is better if you need custom scripts to run the middle of deployment, usually if you have some dynamic provisioning step that needs to be scripted.
Find a Component, Setting, or Package in Windows SIM
Find a Component, Setting, or Package in Windows SIM
learn.microsoft.com
Here is a reference to it.
Yes, you can via the RunAsychronous command. However, I would suggest you run the batch scripts via NTLite Post-Setup. It is a much easier to navigate UI, and essentially does the same thing.
garlin is correct in that the option is controlled by "PreventDeviceEncryption". It lives under Microsoft-Windows-SecureStartup-FilterDriver and you can configure the option after adding it to "7 oobeSystem".
To be absolutely certain, I would convert this to a reg file, and import it into the image. That guarantees it's disabled even if you accidentally skipped it in the autounattend, or WSIM settings
Since 24H is enabling Device Encryption by default, I've asked nuhi to make this easier by adding it to Settings / System.
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BitLocker]
"PreventDeviceEncryption"=dword:00000001Since 24H is enabling Device Encryption by default, I've asked nuhi to make this easier by adding it to Settings / System.
Clang2
Active Member
- Messages
- 263
- Reaction score
- 91
what could possibly go wrong
Another windows 11 annoyance? i would be stumped if i had to use w11, would a thread on windows 11 major annoyances be useful to beginners and new w11 users? i would like to know what they are before i started out.
You could have a "windows 11 basic annoyances" preset but you would need an accompanying thread for explanation or you just have a topic and include either registry files or registry code.
Last edited:
This isn't a mere Windows annoyance, 24H2 will encrypt your data drives too in this scenario.
If you didn't know you're supposed to backup the decryption key to another location – data loss will happen if you didn't disable encryption on all affected drives BEFORE re-imaging the system drive.
Users with a linked MS Account will have their key synced to the cloud, but everyone else is on their own.
If you didn't know you're supposed to backup the decryption key to another location – data loss will happen if you didn't disable encryption on all affected drives BEFORE re-imaging the system drive.
Users with a linked MS Account will have their key synced to the cloud, but everyone else is on their own.