Supported Server OS Editions

RobL216

New Member
Hi there,

I am looking at this tool as I think it is great for integrating updates into the ISO.

Does NTLite support server OS's such as Server 2012 R2 etc?

This would save me a huge amount of time when imaging new servers if it does.

Before buying it I just want to make sure it will work for me.
 
Full list of supported operating systems, updated 5th June 2022.
  • 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
 
Last edited:
That's great thanks.

All I need it for is adding windows updates so that should be perfect.

Can I test this with the free version or is there a restriction?
 
There is only 1 version. It either runs in Free/Unlicensed mode or Licensed mode by entering a License key. Free mode has limited tasks and removals compared to Licensed mode and which is enough for some users. You can slipstream updates, language packs and 3rd party drivers in Free mode.

Visit the Shop page if you want to consider purchasing. Any questions on which type of license you need use the contact option of the bottom of the page. Please note that the purchase prices will be subject to your local sales taxes, VAT etc.
 
Excellent and thank you for your reply.

I will test this and see if it works for me and am happy to purchase as I will be using it for our business.

Thank you again for the prompt replies.
 
Like i said there are limitations to using Free mode, Full/Licensed you get access to everything :) and thats where the fun(or headaches) start. There are Presets availible here, i wrote them, that can be adapted for use on Server variants, any questions, just ask. :)

A License is a LifeTime license, it never expires.
 
Ok so I have given this a go against our Server 2012 R2 ISO.

It seemed to work quite nicely adding in over 500 updates! (I left it running overnight)

However when I run our scanner against a server built with this updated ISO it is detecting patches that are not installed.

If I look at the installed patches list I can see that Windows believes the patch is installed but the scanner is identifying that the particular dll file version is not correct. I have confirmed this by looking at the dll file and it is indeed a lower version than the patch is supposed to have installed.

Is this something I have done wrong with the process?

NTLite showed updates were applied successfully, they show as installed in Windows but the files that should have been updated are not.

Any thoughts?
 
NTLite showed updates were applied successfully, they show as installed in Windows but the files that should have been updated are not.

Any thoughts?

How did you got the updates?
I made a list for Win 7 downloading updates with WSUS Offline, 188 (after excluding Ms tracking and GWX), integrated with NTLite and doing a Windows Update scan, i had to download 55 more because of installing some updates required others and i think this happened because the updates number weren't in the registry.

I think that around half of the 500 updates are unneeded
So, you can download updates for Server 2012 R2 with WSUS, integrate and then do a scan to know what updates is Windows Updates complaining for.
WSUS downloads about 225 updates for W7 and Server R2 (can't be split and apply to both OS's), Win 8 and Server 2012 R2 (a lot newer if compared), so, maybe there are about 200 updates for Server 2012 R2.

Recommendation:
Download updates with WSUS Offline
Integrate with NTLite
Install Server 2012 in a testing environment and do a scan for "missing" updates.

How to get the missing updates' links?
Code:
https://www.catalog.update.microsoft.com/Search.aspx?q=KBnumber
You can get the download links (when not found in Ms catalog) this way:
At least, there is a log that saves the *.cab and *.msu download links in Win 7, it is WindowsUpdate.log (doing .cab and .msu search with Notepad++ you can see KB and unneeded non KB updates), i don't know about Win 8 log, but Win 10 doesn't saves any information in the WindowsUpdate.log, instead it has instructions to get the log.
 
We have a tool that patches all our desktops and servers. This downloads all updates detected as needed by the various operating systems we have.

It only downloads required updates.

I basically loaded my Server 2012 R2 image into NTLIte and then pointed NTLite at our update repository. It only complained about 12 of the updates in the repository which I then removed before applying them.

I was expecting about 300 as this is what we get when doing a base image and then patching with the tool but that takes over 8 hours with all the numerous reboots. I was hoping to get as much into the base image as i could so that we can then deploy this patched to this date.

I will give WSUS offline a go and see what differences it gets in the amount of patches.

However I still don't understand why the saved image from NTLite states the patches are installed but the actual file versions have not been updated.

I have even tried to install the update manually on that patches image but it says it is already installed.
 
WSUS offline includes only updates that replaces older ones and excludes those that have files "replaced" with the packed in 2 or more updates (and WU ask for these updates).
However I still don't understand why the saved image from NTLite states the patches are installed but the actual file versions have not been updated.

I have even tried to install the update manually on that patches image but it says it is already installed.

This could be because the 'Clean update backup' option isn't checked to remove old files.
 
Last edited:
@RobL216, can you please list one update and the files, as an example to confirm and debug your report?

Also how are you checking for file deployment, directly on the WIM image or after it has been installed?
Because image update integration, depending on the files and registry being changed, sometimes delays the finalization of the change until the actual Windows setup.

Thanks.
 
Back
Top