First post updated to version Aug. 11, 2015. I cannot add ip's for win10 telemetry in firewalls because they are all different thus end users will need to add those themselves.
Hej och tack för allt arbete du gör med detta verktyg. Nu till mitt problem som var löst för flera versioner tillbaka. Det har kommit upp igen. Min HP får inte rätt theme det blir FUJITSU jag vill att det ska bli HP. Hoppas på lösning. OEM Query Tool v7.2 Build 5 Standard 21:20 2015-08-12 OEM INFORMATION FOR THIS MACHINE -------------------------------- OS Name: Windows 10 Home [x64] OS Version: 6.3.10240.16430.amd64fre.th1.150807-2049 Processor: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz Processor Cores: [4] Logical Processors: [8] Processor Architecture: [AMD64] HDD Partition Type: [MBR] Bios Version: [F.65, 11/20/2014] SCANNED ------- #1 CSPRODUCT NAME - HP ENVY TS 15 Notebook PC #2 COMPUTERSYSTEM MODEL - HP ENVY TS 15 Notebook PC #3 BASEBOARD PRODUCT - 1967 #4 CSPRODUCT VENDOR - Hewlett-Packard #5 COMPUTERSYSTEM MFR - Hewlett-Packard #6 BASEBOARD MFR - Hewlett-Packard #7 SERIAL/SERV TAG - 5CG3414S7D #8 BIOS ID - InsydeH2O #9 SLIC OA - Un-Listed #10 INSTALLED KEY - Y****-***** #11 MSDM TABLE [OEMM] - N6***-***** #12 BIOS MODE - LEGACY #13 CERTIFICATE - Un-Listed #13 LICENSE STATUS - Licensed SUMMARY ------- THEME - FUJITSU [id:-`#1'] ACTIVATION - FUJITSU [id:-`#1'] VALID [OEM OS] - Win8.x/Win10 Only
Its because of TS being in the query output which is found first in the ini file. It assigns FUJITSU instead of HP because of alphabetical order. I will adjust ini file and upload the fix for you. No biggie...stand by for new version. This will address the branding. I take it you did a upgrade to win10 (retail activation)? The fun begins. lol By the way, this is a English only board but I was able to figure out what you where saying thanks to google translate. Got an easier way of handling this lil problem. I added your bios id to slic section of ini file in order to let conflict resolution handle it. This is better then moving things around in the ini file to avoid other conflicts. Yep, that was simplier...
First post updated 8-14-2015 There is no perfect solution to windows 10 telemetry but block the best you can. I also don't include hosts entries that block apps...if end users wish to not use a app they can disable it themselves or add to hosts file. This should be left up to end users in order to maintain stability of the OS and native apps.
I did a fresh install after my upgrade to win10 home x64. Branded and activated. I did notice win10 .etl file did not backup like it should have. Reason being read only needs to be removed first. Testing again now...it works correctly on win10 install real machine. First post updated to version date 08-16-2015. See change log for details.
Hello, first of all thanks for this amazing work! Second, why did you remove the win10 logon background changer? It's not safe to keep it even if M$ checks it?
Oooh, I got it, thanks for the explanation . Anyway thanks for the constant updates! Anyway I'll wait a bit before burn my dvd, maybe you'll come up with an idea to keep the logon screen changed forever
Hopefully he won't. Why? This is a Multi-OEM project to do oem branding and activation stuff and that's it. Any other tweak is out of the scope of this project.
Well I was talking about auto-applying brand background in the logon screen, just like in the normal background.. so yea, it's oem branding
First post updated to version date 8-17-2015. I am done with this until the next windows release. This version date is final. No more requests. Will upload final source to those that have it, then I am done until windows 11.
Got two pm's relating to this project regarding the logging. After investigating the issue I see what happened. MAN in log file will show DEFAULT instead of oem but does brand and activate correctly (must have vmware modded bios in order to see the issue). I will correct the logging issue later today but need to install win8.1 in vmware in order to update the project since tools used in the project dont work in win10. I will update it this afternoon once I am back home. Thanks for letting me know of the issue. This is minor and easy to fix.
I am also adding query to schtasks for those os's that dont have certain tasks where others might. Here is an example... Spoiler SCHTASKS /query | findstr /B /I "KernelCeipTask" >nul && SCHTASKS /Change /TN "Microsoft\Windows\Customer Experience Improvement Program\KernelCeipTask" /Disable >nul