Been awhile since I commented. I advise that you remove the updates that correspond with the telemetry being added. It should be pretty easy to check if they are in the OS Also been working on passing arguments into powershell scripts. I expect that on my side there will be a lot of changes because I'm slowly turning up the complexity.
Lets keep to the title of the project...this is just basic blocking. Anymore end user's can add themselves. With your project Smorgan you will have to keep your script updated every time M$ comes out with new kb telemetry version updates...have fun with that. lol Here is what I got but still a test version... Removed until I find the time to test it myself. Error handling has been updated in case some strings or files are not present. This ensures it works on any OS version. Mr.X, this should all be working now. Test and let me know.
Why do the firewall entries when it only works for windows advanced firewall rules? Most use another firewall other then M$ and the entries do not carry over into all of them. That is why I included a txt file with the Domains to block in firewall if end users wish to add them. See, what I have done is the basics and end users can setup how they wish as far as what degree to block M$. They will now be able to add other entries into the WinTel.cmd file if they wish. Next question? lol
I will do my own testing later this week. I havent had time the last couple days to test myself so I will put it on hold until I can test for myself because I know where to find everything to ensure it is working. Dont worry about it Mr.X. When I find the time, I will address it. Note: I removed the script for now from above post so others are not lost. lol
Point I stand corrected. I'm finding myself with more time than I had last semester so I'll see about testing out your pack. I wanna do some modding
I would wait until my next release for your testing. I want to address the WinTel.cmd in order to try and please everyone. lol Problem is my time is limited and last night I spent about 3 hrs teamviewing with BALTAGY on the WinTel.cmd file. From my quick tests, it now works like it should but need to test on other OS's then win10 to make sure if a task isnt present then it is skipped. Maybe this weekend while wife is gone to her sisters. lol
lol At your leisure man I'm trying to consolidate scripts along with functions and parameter. While running tests on Windows 10. I'll probably get wrapped up some midterm exams soonish. When your good to go hit me up on team-viewer. You haz plenty of time to do testing I'm just sharing a thought that I wanna get back to doing some hardcore testing. I wasn't able to because of classes last semester so I'm seeing how much I can squeeze into VMing before I get swamped hehe.
Win8.x|Win10 Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and add custom 'ei.cfg' file to the same 'sources' folder and edit|save iso. Windows will install the edition identified from 'ei.cfg' file. (Project 'Options' folder includes 'ei.cfg' instructions). OOBE.cmd will call tool that will extract embedded 'OEM-DM' key from bios (if exists), and apply the serial during installation. Where to find custom'ei.cfg' file?
Thanks very much for updating the previous project and for keeping this life saver OEM project alive!
Working on updating this project today to include external cmd if added to scripts folder to limit telemetry in all supported OS's.
Just a suggestion my friend. Why don't you add a msgbox to provide user's choice? I'm talking about telemetry script, this way they don't have to add or remove such script, a simple click on a "Yes" or "No" button will do the job, no?
You know what? You are right. Having second thoughts and it's better to have oem project running hidden as usual and no pop-ups.
Not only that, the oobe process has no echo's enabled so even if you did echo for a choice, it would not show. Dont confuse oobe.cmd with setupcomplete.cmd.
Sorry guys and gals but I did a quick update to the project to correct WinTel.cmd log entry in oobe.cmd file. First post is updated but same version date. Forgot %TIME% %DATE% for logging...added now.