Install NTLite on Windows Server 2019 Std

C

ch.b

New Member
Hi,
Is it possible to install NTLite on Windows Server 2019 Std (VM ESXI) ?
Does it works fine ?
 
If your question is whether NTLite runs on Server 2019, it works fine. NTLite can update images for Windows releases in the same family or earlier than the host OS. The limitation is based on what version of DISM (servicing stack) is included in your OS.

NTLite doesn't care if it runs inside a VM.

If your question is about modding Server 2019 images, Component removals is unsupported. Most of the Component removals are for consumer features, and don't apply to Server. Unattended mode, drivers, tweaks, and post-setup still work.

https://www.ntlite.com/features/
  • Windows 11
    22H2 10.0.22616 – Preview, subject to change
       License feature from May 10th 2022
    21H2 10.0.22000
       License feature from August 3rd 2021
  • Windows 10
    21H2 10.0.19044 & 20348 ’October 2021 Update’, including LTSC 2021
       License feature from June 22nd 2021
    2104 10.0.19043 21H1 ‘May 2021 Update’
       License feature from October 27th 2020
    2009 10.0.19042 20H2 ‘October 2020 Update’
       License feature from December 17th 2019
    2004 10.0.19041 20H1 ‘May 2020 Update’
       License feature from December 17th 2019
    1909 10.0.18363 19H2 ‘November 2019 Update’
       License feature from April 30th 2019
    1903 10.0.18362 19H1 ‘May 2019 Update’
       License feature from April 30th 2019
    1809 10.0.17763  Redstone 5 ‘October 2018 Update’, including LTSC 2019
       License feature from September 18th 2018
    1803 10.0.17134  Redstone 4 ‘April 2018 Update’
       License feature from March 26th 2018, Microsoft mainstream support ended November 12, 2019
    1709 10.0.16299  Redstone 3 ‘Fall Creators Update’
       License feature from October 2nd 2017, Microsoft mainstream support ended April 9, 2019
    1703 10.0.15063  Redstone 2 ‘Creators Update’
       License feature from April 3rd 2017, Microsoft mainstream support ended October 9, 2018
    1607 10.0.14393  Redstone 1 ‘Anniversary Update’, including LTSB 2016
       Microsoft mainstream support ended April 10, 2018
    1511 10.0.10586  Threshold 2 ‘November Update’
       Microsoft mainstream support ended October 10, 2017
    1507 10.0.10240  Threshold 1 RTM, including LTSB 2015
       Microsoft mainstream support ended May 9, 2017
  • Windows 8 (8.1)
  • Windows 7 (SP1)
  • Windows Server versions of the same build as above, same applies plus excluding support for Components removal and Feature Configurations. Applies to:
     Windows Server 2022 (21H2)
     Windows Server 20H2
     Windows Server 1909
     Windows Server 2019 (1809)
     Windows Server 2016 (1607)
     Windows Server 2012 R2 (based on 8.1)
     Windows Server 2008 R2 and SBS2011 (based on 7SP1)
  • Boot, Setup and WinPE images of all listed and ADK
  • For clarity on specific frequent questions:
     ARM64 image support in alpha/preview stage
     Tool itself runs on Windows 7* or newer, x86 and x64.
    *Windows 7 must have SHA-2 update (KB4474419 x64 x86).
  • Does not support:
     Checked/Debug editions
     Embedded or IoT editions (exception being the ‘Enterprise’ subset, it is supported)
     Windows Vista
     Windows XP
     Windows Server 2008 and older
Click to expand...
 
Thanks for your answer.
My goal is to create and maintain images of Win 10 and soon Win 11. I will create a Win server 2019 Std VM dedicated to this task.
According to your answer it will work fine.
 
If you're using a NTLite license (for premium features), don't forget to back up the License.dat to avoid reactivation. This way, you can revert to a previous VM snapshot and not worry about licensing.

Keep the same VMDK so the "hardware id" doesn't change.
 
i think settings ini file also save activation code & is mandatory for a backup too :)
 
I exported the license.dat file from the previous machine and imported it into the NT Lite of the Win server 2019 Std VM.
The About indicates that I have a Free license (on the previous machine the About indicates Commercial license).
What's going on?
 
When you switch machines, it requires one re-activation. After entering your license key on the VM copy, keep this new License.dat to save you from future re-activations.
 
You must log in or register to reply here.
Back
Top