|====| NTLite Research Presets & Custom Scripts

Clanger

Clanger

Well-Known Member
Capture.JPG
This is a w7 x64 EOL captured wim i am currently working on, IE11 and Net 4.8 installed. There is an issue on winsxs cleanout that i am working with nuhi on, its 300MB bigger than it should be so take away 300 from the FIS and the os will be 5193.3MB.

All i have done is to remove 3rd party published drivers(not ms published drivers), keyboards and languages, Recovery, .Net caches, cache and temp files, winsxs backup and winsxs. I havnt actually touched the meat and bones of the os, ive gone around the outside and trimmed the fat off from there. I would call this Stage1 or Safe Lite.


This is the captured wim as is, only cleanup before sysprep was Disc Cleanup with all options ticked and imagex default exclusions.
Capture2.JPG
 

Attachments

  • v3.xml
    17.8 KB
Last edited:
A

AeonX

Active Member
I don't care too much about telemetry either, people use android phone with default settings sending location history to Google for example but they care about telemetry. Microsoft is more transparent about telemetry than Google, they have a page documenting everything and showing you how to disable most of what is sent out of the network.

I care more about what affects performance and telemetry affects because it needs to generate system diagnostics and send it over the network, this has costs.
 
?

|====|

Active Member
i think its best to remove only bloatware from offline image & create final iso so that it meets every user scenario. next after installation remove telemetry related packages from current installed os which meets my needs.
Bloatware in terms is reffered to : all metro apps + very minimal inbox(system) apps + onedrive + edge chromium the best way i think it must be on win10 offline image.

if she knows that much about M$ telemetry related features that means she was trying to test my knowledge as being Google Analyst. i was shocked to hear from her about tiworker scenario.

Edit : My own $OEM$ Pack Does the Job nothing else needed for Laptop Installation Scenarios :)
 
Last edited:
A

AeonX

Active Member
I think removing 'Telemetry Client' and disabling some settings in NTLite is pretty good. Removing telemetry client NTLite not only removes the component but applies some reg tweaks, removes scheduled tasks and related services. I don't use any other 3rd party apps as I didn't see the need. Of course, there are other privacy-related components that I remove.
 
C

clarensio

Active Member
AeonX said:
I think removing 'Telemetry Client' and disabling some settings in NTLite is pretty good. Removing telemetry client NTLite not only removes the component but applies some reg tweaks, removes scheduled tasks and related services. I don't use any other 3rd party apps as I didn't see the need. Of course, there are other privacy-related components that I remove.
Click to expand...
I too had started this way; then, since the software I indicated are without installation, I checked the status and... :eek:

I repeat that now I am almost exclusively very satisfied to use NTLITE + Group policy + the SW indicated
 
A

AeonX

Active Member
clarensio said:
I too had started this way; then, since the software I indicated are without installation, I checked the status and... :eek:

I repeat that now I am almost exclusively very satisfied to use NTLITE + Group policy + the SW indicated
Click to expand...
It's been a while since I've tested O&O ShutUp10 but it is worth saying that if the tweaks used by NTLite are not exactly the same as those used by ShutUp10 the app will show as "Enabled" or something similar even though the "feature" is disabled. Sometimes NTLite disables the setting but doesn't apply a group policy while ShutUp10 maybe does, but in the end the effect is almost the same. But I don't know for sure, I'd have to check again. And many existing ShutUp10 tweaks may no longer apply to newer versions of Windows.

This other app I don't know.

But the correct way to compare 2 tools would be to capture the reg keys that each one applies and compare them.

Using gpedit.msc has the advantage that settings are forced and they survive updates. I forget that some people use Windows Update :p
 
?

|====|

Active Member
Got 80% success in laptop scenarios . will work more tmrw as i am the only one left in office working on this laptop.

Edit : My own $OEM$ Pack Does the Job nothing else needed for Laptop Installation Scenarios :)
 
Last edited:
Clanger

Clanger

Well-Known Member
AeonX said:
it is worth saying that if the tweaks used by NTLite are not exactly the same as those used by ShutUp10 the app will show as "Enabled" or something similar even though the "feature" is disabled.
Click to expand...
I noticed this before. 1 tool will set the value in the registry while another tool will delete it.
 
Hellbovine

Hellbovine

Active Member
|====| said:
i will try on laptops from now onwards to cross check differences between desktops & laptops.
Click to expand...
I too just ran into this exact same issue while configuring my own ISO. It turns out there are a few important differences in the OS between Laptops and Desktops, especially when it comes to editing power plan registry keys in particular, and if you want to play-test your changes it's impossible to do it properly without actually using a Laptop it seems. Like AeonX was saying about the different brightness settings, the battery taskbar fly-out options, etcetera. Now I'm looking into acquiring a cheap laptop to use to test with.

Anyway I don't have anything helpful to add lol, just wanted to let you know you weren't alone! :)
 
Clanger

Clanger

Well-Known Member
Create and export custom powerplans for desktop and laptop, add them to $OEM$ then import/set the required plan in setupcomplete.cmd.
 
Hellbovine

Hellbovine

Active Member
Clanger said:
Create and export custom powerplans for desktop and laptop, add them to $OEM$ then import/set the required plan in setupcomplete.cmd.
Click to expand...
Yeah I thought about that idea, and may still end up using it perhaps. Right now though I'm editing the power plan defaults, rather than the other methods since Microsoft now tries to constantly take control of your power plan and alter and reset your plans and settings back to defaults in Windows 10, so this is a more Microsoft-proof method for me.

The default keys method also allows the other stages of the Windows install process to use those settings as well which drastically cuts down on OS install time, like when you change the default power plan to be high performance, and/or customize the plan settings for speed instead of battery life.

But what I mean about testing is that every single thing I tweak I then go and test inside Windows as a user to see if it actually stuck and works. So like changing the default brightness for AC and DC power I will then reboot and go into my Windows power plans and reset things back to default and see if my brightness actually changes for real, that way I know I did the reg tweak properly.

Even if you change the attributes to unhide every single power plan option though, there's still about a dozen or two that won't show up for desktop users, you have to be using a mobile device of sorts and/or be on battery power which isn't possible for my desktop. So I have no way of verifying if those tweaks are valid with real world results. I wonder if there's a way to trick a desktop into thinking it's on battery power?
 
Clanger

Clanger

Well-Known Member
Hellbovine for safetys sake export the default powerplans, create new plans with custom names and guids then use those.

Note - on a laptop it seems that only Balanced plan is installed, so create custom plans and export default plans on a desktop system.

Note - Use quickcpu, its has an excellent power plan tool.

Part of a setupcomplete.cmd, works everytime :)
Code: 
mkdir C:\Windows\PowerPlans
powercfg /export C:\Windows\PowerPlans\Balanced.pow 381b4222-f694-41f0-9685-ff5bb260df2e
powercfg /export C:\Windows\PowerPlans\HighPerformance.pow 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
powercfg /export C:\Windows\PowerPlans\PowerSaver.pow a1841308-3541-4fab-bc81-f71556f20b4a
 
Last edited:
G

garlin

Moderator
Staff member
Aliases are your best friend (least on W10 and later).

powercfg SetAcValueIndex GUID SUB_VIDEO VIDEONORMALLEVEL 100
powercfg SetDcValueIndex GUID SUB_VIDEO VIDEONORMALLEVEL 65

Beware some Intel, AMD, NVIDIA add-on's will try managing display brightness on their own.
 
?

|====|

Active Member
I repeat : My own $OEM$ Pack Does the Job nothing else needed for Laptop Installation Scenarios but it doesnt mean that my own $OEM$ pack is good then NTLite cuz NTLite always the best of the best for desktop installation scenarios.
 
Last edited:
You must log in or register to reply here.
Top