No extra telemetry, shut it off as normal, disable DiagTrack service and add registry policy;. [HKEY_LOCAL_MACHINE\temp\Policies\Microsoft\Windows\DataCollection] "AllowTelemetry"=dword:00000000 Being an enterprise version the no telemetry policy does actually work.
Create a text file on your desktop or somewhere, paste below code in, and save it as a reg file. In other words rename telemetry.txt to telemetry.reg. Then run double click on it or right click and select merge. It will ask if you want to do it, select ok. Then it will tell you success or fail. If it fails search for Nsudo in this forum and run with it. You will need Nsudo. Download it here: https://forums.mydigitallife.net/threads/nsudo-a-powerful-system-administration-tool.59268/ Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\temp\Policies\Microsoft\Windows\DataCollection] "AllowTelemetry"=dword:00000000
OK, I am ready for 1809 round 2, but all these posts made things overly complicated... I am SO sorry to ask again, but: 1. How do I add Edge to 1809? 2. How do I update it properly? Before OR after MSMG Toolkit carnage? 3. What are the latest updates and where can I get them? 4. Is there anything else I need to know to create a proper MSMG'ed image with the latest updates? I do not care for NET Framework 3.5.
The info posted on Nov. 8. 2018 by @SAM-R is outdated, read the uptodate info at the OP of this thread, on Nov. 13 2018 MSFT resumed to release all publicly, by MCT, ISO and on WU in stages: https://forums.mydigitallife.net/th...blic-1809-final-build-17763-1-107-pc-r.77945/
LTSC ISO only updated a couple times a year so no new iso from MS. Latest is 17763.107 I think, not positive. I used the magnet link in the post below, much prefer torrents to direct downloads, hashes all check out. https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-104#post-1482269 Most advanced users will add updates to .\sources\install.wim image on the USB media with dism after creating media with a tool like Rufus. It's actually pretty easy to do. Commands are rather long winded so I keep a text file of all my dism commands I use commonly, just copy and paste into an admin command window.
MonarchX seems to have missed all the new things happening And yes, 1809 recently got it's first refresh iso's of build 17763.107.
Did that include LTSC? Can you please link me to ISO (En-US) non-N? If I do get the latest/updated 17763.107 version, do I need to apply any of these: Windows10.0-KB4469041-x64 - NetFX Update Windows10.0-KB4469342-x64 - Cumulative Update Windows10.0-KB4470788-x64 - Servicing Stack Windows10.0-KB4471331-x64 - Adobe Flash
Why on earth do you need an ISO with an old superseded CU already integrated, specially when you are planning to try to integrate new updates?
... You said that 17763.107 is the latest... Can you please just explain what the latest LTSC ISO version is and which updates apply to it? I keep running around threads and getting more and more confused.... And will MSMG Toolkit 9.0 be able to add Edge and remove crap from 17763.107 ?
Get .107 iso. Add cu (kb4469342) and ss (kb4470788). LTSC installation does not include dotnet 3.5 so if you want it I would install netfx3 online then apply dotnet update (kb4469041). Not sure if it's necessary to install netfx3 before applying dotnet update, but that's what I'm doing. LTSC lacks many of the add-ons of the normal versions, no metro apps, no store, no game mode, no one-drive, etc. That's why I and others like it.
You need to learn to read, the info you ask for is at the OP in the downloadsection. The baseline 17763.1 iso is the one you need, when you are going to integrate the current updates. Don't use the 17763.107 iso, it already has an older superseded CU in.
Stop posting this misinformation, no windows 8.x or 10 install has dotnetfx3 pre-enabled. LTSC or every other windows 8.x and up ISO has the dotnetfx3 ondemand cab inside the "iso:\sources\sxs\" folder to use for enabling dotnetfx3. kb4469041 is a separate CU for updating dotnetfx.
Yeah, however, MSMG Toolkit only supports original vanilla versions, but the .1 didn't work MSMG Toollkit 8.9. It resulted in DISM Error 2. I was hoping that the .107 version and Toolkit 9.0 would work.
MSMG toolkit is known not work properly with refresh iso's, refresh iso's are the baseline iso with this CU pre-integrated by MSFT: KB4464455 (17763.107). This old CU is superseded/replaced by kb4469342 (17763.168.1.10).
So does it matter in end if you update the .107 image versus updating the baseline image? Not trying to argue, just need some education. If I should be updating the baseline I'll have to go back and do things a bit different.