Search results

I'm interested in subscribing/purchasing Software Assurance (Already as MS OEM (DOC) partner), if anyone from Microsoft is out there.

I've always wondered about this? My theory was opposite: If the language packs have to be there first, in order for some "sub-components" of the CU to update the language packs? Presumably a bug fix in CU contains updated translations? For example (this is real): "If you are one of the...

Without disclosing any of the secret sauce recipes inside NTLite: There isn't a native Microsoft framework/function to accomplish this, correct? This hook is simply removing files and registries?

Up to the experts how to implement it. I'm actually just this month learning from other Forums how to mount the Default New User HIVE and make HKCU changes not only to HKCU but also to the mounted HIVE point (Made it to age 40 without needing to know any of this stuff >:} !! ) Simple...

All: I had some internal requests to further customize explorer defaults. For now I do it with PowerShell. However, It would be nice to expose them all in a future version of NTLite. Low hanging fruit / low priority. Happy near years all! ~BAS...

I must be not sleeping again; not sure how I missed that. Thanks. ~BAS

Is there not a graceful mechanism (disable optional feature, etc.) to remove mstsc.{exe,dll}? (Pragmatically, I suppose Application Whitelisting is the best approach here.) Thanks ~BAS

> Basically if you do everything .NET in one pass, it works? It works If: I add DotNet3.5 CAB and DotNet4.8 MSU in one pass, save, then close; then Add SSU, CU, and DotNet4.8 CU in a second pass, It fails if: I add all 5 at the same time/pass Just for the record. And thanks again.

I have finally figured this out. I have it working again; I can now successfully integrate latest DotNet4.8 CU (either KB5007152 or KB5004752). I changed my/the sequence-process as-follows in the following way: *) Add DotNet4.8 Feature Package (KB4486129) during Pass #2 (At the same time I'm...

Bah! Same result using the MicrosoftOEM.com ISO. I'm beginning to think that DotNet4.8 Feature Pack (KB4486129) was never meant/intended to be integrated into the image using ADK/NTLite? (And that it should always be done post-OS-Install) And perhaps this is simply my amature mistake in...

Do you all use Microsoft OEM Media/ISOs from the VLSC or MS DOC? I was able to get ahold of genuine Server 2016 DVD-DL ISO from Microsoft via the MS DOC (MicrosoftOEM.com). Package: X21-73483 [ X21-73483 Win Svr Emb Std 2016 1607.2 EMB ENG OPK UpdateFMR SW DVD9 NTRL StdDC F.iso ] I'll try to...

Question for everyone: Did you test using media kit X22-81260 from MS DOC (MicrosoftOEM.com) ? [X22-81260 Win 10 IoT Enterprise LTSC 2021 21H2 x64 English OPK] Thanks, ~BAS

Also, I did find a way to mount the NTLite output WIM file (DISM) and then mount the Registry within that WIM ("reg mount...") and I can confirm that the KB/Windows Update framework is not registering any related "RunOnce" entries that may be causing the problem. (NTLite itself puts a few...

Status note: Replacing KB5004752 (August) with KB5007152 (November) did not resolve the matter. I think you're correct/right in your suggestions that I should revert to using Windows original ISOs from Microsoft (from MicrosoftOEM.com, etc..)

> best is to use one direct from Microsoft. That's a good point; I've been using the Dell OEM image for various reasons (Bare Metal env Predominantly) But for WinSrv2021, with HyperFlex/VXRail, I'll use the ISO from the VLSC stripped down for VMWare environments. Thanks for your advice! ~BAS

Thanks what I was thinking: That more than one KB was registering a RunOnce activity to complete, but that they were being registered out-of-sequence (out-of-order), and that, if the sequence/order could be correct, the dependencies would be fine. Is there a way to ask ntlite host to dump the...

Hi all! I want to ask the collective brain trust about a KB/DISM error causing a roll-back on first boot. I have some difficulty with KB5004752 ( the August 2021 DotNet4.8 Cumulative Update) on WinServer 2016 (v1607) It installs/merges fine during NTLite build process. However, during...

I will proceed with a two-stage process from now on until DotNet3.5 finally dies necessary and bloody death (Anyone from Rockwell Automation core team out there hearing my prayers?)

Yep, until it can be integrated directly into NTLite, do it manually in post-execution script. PowerShell has a function as-well: Set-LocalUser -Name “localuser” -PasswordNeverExpires 1

A per-user setting (instead of Global) would be a great feature (request).