NTLite and SCCM task sequence

D

dewrew

New Member
Messages
1
Reaction score
0
Hi,

I want to use an image which including updates with Task Sequence in Microsoft Endpoint Configuration Manager. But when all steps of task sequence are done I noticed that everything what was previously prepared by MDT/MECM now is erased and I have clean Windows. It is still in domain, but Bitlocker isn't enabled, it doesnt has any apps installed , even MECM client doesn't exist. It's strange. I thought that NTlite only adds updates to Image, this was my goal. Is it possible using this tool?

thx.
 
OP hasn't returned to this forum since posting the question.

NTLite differs from MDT and other managed deployment solutions, because it follows the older (ISO) media-based model instead of network-based installations. For the traditional ISO model, changes are integrated into the image and tasks provided through SetupComplete, or registered RunOnce tasks. Installer files are staged on the local media for deployment.

MDT model expects to network boot a customized PE environment which handles some pre-deployment tasks, then applies a normal image, and later execution stages are scripted tasks which depend on the deployment server to provide the hosted content.

You can prepare customized images in NTLite, and submit them to MDT for deployment. You don't do it in the reverse direction because the two models are different.
 
While MDT supports network boot installation, it can also create offline installation media. The problem with MDT is that it is no longer updated to support Windows 11 and Microsoft has deprecated VBScript, which MDT "Deployment Wizard" heavily relies on. So, if you try to use MDT with the latest ADK, MDT Deployment Wizard simply does not work because the VBScript DLL is missing. This is the main reason I migrate all my installation scripts to NTLite and dropped MDT for my deployments.

Many of us may not notice, but in my opinion, for offline media installation at least, NTLite has surpassed MDT with support for latest version of Windows, and granular control of which component to remove. In fact, MDT provides no facilities to remove Windows components.

Because of such detailed and granular control, I think garlin is correct that we should create the customized "install.wim" in NTLite, and then import it into MDT for network deployments with appropriate Tasks Sequence. If you are targeting offline installation media, then NTLite can do it all.

In case you would like to include the Configuration Manager Client in the custom WIM, please follow the Microsoft article on OS image installation. The installation procedures could be implemented in NTLite Post-Setup.
 
Thank you both for your replies. Your explanations make a lot of sense. Creating postscripts to handle the finalization might be the way to go.

Do you know if NLite supports WMI variables for the machine name? If not, I could easily create a post-deployment script to handle this after installation, which I may have to do to specify which OU to place the computer in. As Annie Ng has pointed out, UDI isn't an option with MDT being deprecated.

What would you advise on how to handle these two remaining issues?
 
CrashOverride said:
Do you know if NLite supports WMI variables for the machine name?
Click to expand...
Would you please clarify what kind of WMI functions you need? As far as I know, even in MDT you need WMIC to access WMI functions. If you would like to manage machine names and domain joins, you may want to have a look at "Windows Configuration Designer". However I do not think there is a great option to handle computer placement in OU except writing script yourself to use netdom.exe.

I previously use Lite Touch (LTI) in MDT. When you work in NTLite you need to provide enough parameters via unattend.xml for automated installation.
 
Annie Ng said:
Would you please clarify what kind of WMI functions you need? As far as I know, even in MDT you need WMIC to access WMI functions. If you would like to manage machine names and domain joins, you may want to have a look at "Windows Configuration Designer". However I do not think there is a great option to handle computer placement in OU except writing script yourself to use netdom.exe.

I previously used Lite Touch (LTI) in MDT. When you work in NTLite you need to provide enough parameters via unattend.xml for automated installations Orly
Click to expand...
Sorry, for my ignorance.
Here is an example of the ps script I would use during Task Sequencing.

$ComputerModel = (Get-WmiObject -Class Win32_ComputerSystem | Select-Object Model).Model $SerialNumber = (Get-WmiObject -Class Win32_BIOS | Select-Object SerialNumber).SerialNumber # Workstations if (($ComputerModel -match "Precision") -OR ($ComputerModel -match "Optiplex")) { $OSDComputerName = $SerialNumber + "-" + "WS" $TSEnv = New-Object -COMObject Microsoft.SMS.TSEnvironment $TSEnv.Value("OSDComputerName") = "$OSDComputerName" } # Laptops if ($ComputerModel -match "Latitude") { $OSDComputerName = $SerialNumber + "-" + "LP" $TSEnv = New-Object -COMObject Microsoft.SMS.TSEnvironment $TSEnv.Value("OSDComputerName") = "$OSDComputerName" }

After looking at Windows Configuration Designer. It provides a lot of food for thought. Thank you for the suggestion.

I am going to have to take some time to decide on which route to pursue.
 
If you end up using WCD, NTLite can add the created .ppkg provisioning package under Updates.
 
You must log in or register to reply here.
Back
Top