If your image has runonceex, it will use it, no reason to switch to a lesser runonce.
It is automatic while using the Post-setup - User section.
Let me know if I missed the point, thanks.
If you're asking would NTLite change your own edits, then no, it doesn't do what it wasn't instructed and listed on the Apply page before Process.
That's a Windows question.
RunOnceEx requires IE, but NTLite protects those core files if the image had them in the first place and post-setup user is used, Server Core does not so use RunOnce (non-ex) instead.
I sucessfully tested RunOnceEx on Server Core too on my upcoming script tool POWIS, based on OOBE.cmd tutorial and Autorun.dll patcher. POWIS is clear solution for all Windows versions from Vista and newer without any patching system dlls.I don't know what Server Core is, so just to be clear, NTLite always protects those core files (if the image has them), even if you don't explicitly protect them or use the Post-Setup User section?
Your RunOnceEx is driven by iernonce.dll + iernonce.dll.mui + IEAdvpack.dll. So yes RunOnceEx is executed on it´s own as is build-in Windows component. Even If you remove Internet Explorer it should work as NTLite have protected needed files for RunOnceEx.Could you please clarify this? I currently change the HKLM RunOnceEx directly via the registry. Will those commands execute without using the Post-Setup user page to set them up?