Yeah, everyone tends to have issues with servers...even M$ doesn't have a clue, trust me. I can make it where the project works with server gui like in 2012 and 2012R2 but the others are impossible to address seems like. If M$ doesn't know then how are we suppose to know? Seriously. lol Adding just those two servers really isn't worth all the recoding and such on my behalf. To be honest, if professional IT people are looking at me for solutions then why do they have jobs in that field? Seriously! I am dropping server support and leaving the project as it is. I am burned out on working on this for 8 months straight day and night. Time to get back to real life. Just a note: Alphawaves new dumper tool v1.6 .net framework 4 runs as .net framework 3.5 on windows server 2012R2 editions. In fact it doesn't run unless you install .net framework 3.5 on 2012R2. Looks like the native .net framework is 4.5.1 so I guess Alphawaves .net 4.0 version isn't compatible with server 2012R2. I will upload the new query tool that uses Alphawaves new dumping tool v1.6 but removing server support.
First post updated. See change log for details. This is the final version until win 10 goes rtm. I am on vacation now. Silent update to query tool to remove one left over server entry, sorry. Query Tool v7.0 Build 2
oobe.cmd is auto. found and ran by windows installation so no that isn't possible. The $oem$ folder is only 22.8 megs big compaired to over 200 megs in the beginning. I am not doing anymore to it in this area. If I find more keys and certs, cool, I will update it. I have no plans on doing anymore to this until win10 comes out. I need a break.
Exactly mate. Don't do anything more on that size area, pointless. Suffice is 22.8 MB that I am really impressed when you reduced the other day from 200+megs to 22.8, so imao don't do anymore... Thanks for the new certs and keys man
All looks ok except the systeminfo query for memory and bios version....can you run systeminfo from admin command prompt and see if it outputs correctly? This info might not be avail on your system but curious to see if manually doing it shows the results. This is what is in the scipt to query that info... for /f "delims=: tokens=1*" %%A in ('systeminfo 2^>nul') do (for /f "tokens=*" %%S in ("%%B") do ( IF /I "%%A"=="Total Physical Memory" set TMEM=%%S IF /I "%%A"=="Available Physical Memory" set AMEM=%%S IF /I "%%A"=="BIOS Version" set BIOSVersion=%%S) )
Spoiler Code: Microsoft Windows [version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Tous droits réservés. C:\Users\REPLAM7>systeminfo Nom de l?hôte: REPLAM7-PC Nom du système d?exploitation: Microsoft Windows 7 Professionnel Version du système: 6.1.7601 Service Pack 1 version 7601 Fabricant du système d?exploitation: Microsoft Corporation Configuration du système d?exploitation: Station de travail autonome Type de version du système d?exploitation: Multiprocessor Free Propriétaire enregistré: REPLAM7 Organisation enregistrée: Identificateur de produit: 00371-OEM-8992671-00407 Date d?installation originale: 09/12/2014, 14:46:01 Heure de démarrage du système: 20/03/2015, 13:28:42 Fabricant du système: INTEL_ Modèle du système: DQ57TM__ Type du système: x64-based PC Processeur(s): 1 processeur(s) installé(s). [01] : Intel64 Family 6 Model 37 Ste pping 5 GenuineIntel ~3192 MHz Version du BIOS: Intel Corp. TMIBX10H.86A.0050.2011.1 207.1134, 07/12/2011 Répertoire Windows: C:\Windows Répertoire système: C:\Windows\system32 Périphérique d?amorçage: \Device\HarddiskVolume1 Option régionale du système: ar-ma;Arabe (Maroc) Paramètres régionaux d?entrée: fr;Français (France) Fuseau horaire: (UTC) Casablanca Mémoire physique totale: 8 053 Mo Mémoire physique disponible: 4 738 Mo Mémoire virtuelle : taille maximale: 16 104 Mo Mémoire virtuelle : disponible: 12 356 Mo Mémoire virtuelle : en cours d?utilisation: 3 748 Mo Emplacements des fichiers d?échange: C:\pagefile.sys Domaine: WORKGROUP Serveur d?ouverture de session: \\REPLAM7-PC Correctif(s): 156 Corrections installées. [01]: KB2849697 [02]: KB2849697 [03]: KB2849696 [04]: KB2849696 [05]: KB2841134 [06]: KB2841134 [07]: KB2670838 [08]: KB2592687 [09]: KB971033 [10]: KB917607 [11]: KB2479943 [12]: KB2491683 [13]: KB2506014 [14]: KB2506212 [15]: KB2506928 [16]: KB2509553 [17]: KB2511455 [18]: KB2515325 [19]: KB2532531 [20]: KB2534111 [21]: KB2536275 [22]: KB2536276 [23]: KB2541014 [24]: KB2544893 [25]: KB2545698 [26]: KB2547666 [27]: KB2552343 [28]: KB2560656 [29]: KB2563227 [30]: KB2564958 [31]: KB2570947 [32]: KB2574819 [33]: KB2579686 [34]: KB2584146 [35]: KB2585542 [36]: KB2603229 [37]: KB2604115 [38]: KB2619339 [39]: KB2620704 [40]: KB2621440 [41]: KB2631813 [42]: KB2640148 [43]: KB2647753 [44]: KB2653956 [45]: KB2654428 [46]: KB2655992 [47]: KB2656356 [48]: KB2660075 [49]: KB2667402 [50]: KB2676562 [51]: KB2685811 [52]: KB2685813 [53]: KB2685939 [54]: KB2690533 [55]: KB2691442 [56]: KB2698365 [57]: KB2699779 [58]: KB2705219 [59]: KB2706045 [60]: KB2709630 [61]: KB2709981 [62]: KB2712808 [63]: KB2716513 [64]: KB2718704 [65]: KB2719033 [66]: KB2719857 [67]: KB2726535 [68]: KB2727528 [69]: KB2729094 [70]: KB2729452 [71]: KB2732059 [72]: KB2732487 [73]: KB2732500 [74]: KB2736422 [75]: KB2742599 [76]: KB2743555 [77]: KB2750841 [78]: KB2756921 [79]: KB2757638 [80]: KB2758857 [81]: KB2761217 [82]: KB2763523 [83]: KB2770660 [84]: KB2773072 [85]: KB2785220 [86]: KB2786081 [87]: KB2786400 [88]: KB2789645 [89]: KB2791765 [90]: KB2798162 [91]: KB2799926 [92]: KB2803821 [93]: KB2807986 [94]: KB2808679 [95]: KB2809215 [96]: KB2813347 [97]: KB2813430 [98]: KB2813956 [99]: KB2818604 [100]: KB2820331 [101]: KB2832414 [102]: KB2833946 [103]: KB2834140 [104]: KB2834886 [105]: KB2835364 [106]: KB2836502 [107]: KB2836942 [108]: KB2836943 [109]: KB2839894 [110]: KB2840149 [111]: KB2840631 [112]: KB2844286 [113]: KB2845187 [114]: KB2846960 [115]: KB2847077 [116]: KB2847311 [117]: KB2847927 [118]: KB2849470 [119]: KB2852386 [120]: KB2853952 [121]: KB2855844 [122]: KB2861191 [123]: KB2861698 [124]: KB2861855 [125]: KB2862152 [126]: KB2862330 [127]: KB2862335 [128]: KB2862966 [129]: KB2863240 [130]: KB2864058 [131]: KB2864202 [132]: KB2868038 [133]: KB2868116 [134]: KB2868623 [135]: KB2868626 [136]: KB2868725 [137]: KB2872339 [138]: KB2875783 [139]: KB2876284 [140]: KB2876331 [141]: KB2882822 [142]: KB2884256 [143]: KB2887069 [144]: KB2888049 [145]: KB2891804 [146]: KB2892074 [147]: KB2893294 [148]: KB2893519 [149]: KB2893984 [150]: KB2898785 [151]: KB2900986 [152]: KB2904266 [153]: KB2913152 [154]: KB958488 [155]: KB976902 [156]: KB982018 Carte(s) réseau: 3 carte(s) réseau installée(s). [01]: Intel(R) 82578DM Gigabit Netwo rk Connection Nom de la connexion : Connexio n au réseau local DHCP activé : Non Adresse(s) IP [01]: 192.168.1.99 [02]: fe80::4bc:98b4:df95:901d [02]: TAP-Win32 Adapter V9 Nom de la connexion : Connexio n au réseau local 2 ?tat : Support déconnecté [03]: TAP-Win32 Adapter V9 Nom de la connexion : Connexio n au réseau local 3 ?tat : Support déconnecté C:\Users\REPLAM7>
I see you didn't run it from admin command prompt but instead from non admin cmd prompt instead. Are you an admin on this machine? If no access to admin then that is why the script is failing. I see the problem...your using another language other then English...see... BIOS Version Yours is: Version du BIOS I will have to study this to see if I can find only BIOS instead of BIOS Version to correct this. Minor problem with language setting is all. Give me a little time to study this. lol Thanks for helping. Think what I will try and do is output the whole string instead of querying for part of it. I will work on this. Workaround for you.. extract the OEM-CD.cmd from the sfx file and edit that section with your language to correct your output. Then recompile the sfx with your correction. The sfx file is compiled with WinRAR just to let you know.
The sfx isn't locked so you can extract/edit then just add it back to the sfx file using WinRAR. I will work on this later today when I am done with my running around. Thanks for bringing this to my attention.
it's worked after editing Spoiler thanks for the support & help i'm sure also i had same problem on another HP Desktop (Bios & Memory Info)
I will work on this minor problem later today. Thanks again for your help. I didn't think of other languages before, my fault.
As far as other languages this is what I can do...query to check language then if not English output the bios version info from WMIC but it will not include the bios name unfortunately. As far as Memory I will input a error handler because there is no way for me to add query for every language out there (google translate isn't that good to include all languages). The memory output isn't a biggie anyways, I just added it because it is nice to know. It was just a perk. lol I can add OS language number to the error handler for memory so end users know why it doesn't show. So if not English language it would output like this... [Error-1034] ---->Error-Spanish Langauge I will need to add this error handling to Licensed output and also when in VMware for the query of UEFI which also effects Partitioning info (MBR/GPT) but this query is only in VMware/Vbox. Before anyone asks why I dont use WMIC for Licensing it is because that command is disabled in win 8 so that isnt a solution either. Better to just add error handling in this case. This does not effect the main project, only the query tool because of extra info I added for output. They were just added perks.
Not sure what I did wrong. Placed the $oem$ folder in sources folder as stated in readme and installed W8.1 nothing happened. Also autounattended got discarded during install. Luckily found System brand changer.
You are using MAK key for activation. The project would oem brand according to ASUS found in bios query and be applied during installation. Since you have no msdm table there is no way to do a true oem activation of win 8.1 pro but need to use kms .