I dont have access to all oem info on every machine. I added what I have recieved but it queries the bios for the info. With that being said, can you run the query tool and send me the results.txt file so I can see for myself what is in the bios for the brand and correct it? Please and thank you. As soon as I get it, I will add corrections and reup the project.
Note: I have plans in the future to convert the batch script and needed files into one python script that will hold all info needed. This is for some time in the near future but then I can make it open source and put on github for all to enjoy and learn. My time is limited now but will get to it eventually. Guess smorgan is rubbing off on me. lol @Smorgan, You know you love Vista and batch scripts.
Hi guys ! First thanks a lot for this project, it really helps me a lot to deploy batches of windows 8.1 computers (with MDT). But today I encounter a loss of activation problem. Just after deployment the computers seems to be well activated, branding is OK. But after some reboot windows says it's not activated. When i try to activate it again, i've got and error 0x8007232b "DNS Name does not exists" But if i take a nirsoft keyviewer, the actual activation serial is different from the bios-dm one. If I use the bios-dm with slui it activates without any problem... Can someone help me ? Got this problem with something like a 100 of computers ... Thanks in advance & sorry for the bad english Pierre
Are you using a retail key for install? Use the default manufacturer's OEM-DM key for OA3 & Windows will pull & use the key from the bios...
First post updated to address Prolink/Surface conflict. I never got results.txt file but used a workaround instead.
Hi all! First I want to thank you for this very useful tool. And the second, I wanted to note that WALLPAPER.jpg in HP folder is in incorrect format. Starting from 2015 it has changed to 2880x1620 dimensions and that causes problems on many computers with unsupported resolution - at least for Windows 7 (installation just hangs at the last step when oobe.cmd is being applied). So usually I just replace that WALLPAPER.jpg with the one from OEM Project Build 18.11.2014 which has 1920X1200.jpg (I rename it to WALLPAPER.jpg). I checked some other folders - DELL, MSI, LENOVO, FUJITSU and all of them have 1920X1200 version WALLPAPER.jpg. So it seems like only HP has incorrect one. Can you fix this in future versions? Thank you in advance
Think it depends on the max resolution size for monitor in win7. Either way it is set like the rest of the images 1920x1200. I am uploading it now. First post updated 5-10-2016 which corrects HP wallpaper size.
Q: Point me in the right direction please.... First of all, thanks for the work you put in to make this and to keeping it going. I have been using this with windows vista and seven successfully for a while. To be honest, I am confused with windows 10! Could you point me to the right place on how to add ['OEM-DM' key] to have windows 10. Also, is it possible to have bios comply with all version of windows. Currently my bios is only good for vista-7. Thanks in advance for any and all help!
Do not function properly these last contributions .. It has some vesiones to try to format I get the following: "The response file unattended installation contains a product key does not validate Remove the key does not validate or provide ......". And the system is restarted. I hope the English is understood.
Better then that, how about posting the log file the project creates at the root of the drive? Also run the query tool and post results.txt file. There has been No change in script in many many months. The last update only effected HP wallpaper being incorrect size for some monitors. There is no key section in the updated project xml files because of crashes in the automated process if no key entered. User's can add that themselves if they have a key to enter into it. There are many examples online showing how to add the key sections to the xml file if needed.
@pierreo02 The PC's OEM: DM key is applicable for Windows 10 Pro; it isn't backward compatible with 8.1.
Does you bios id really say BIOS or has it been edited? The reason I ask if bios id was edited is because there is nothing in asus or dell that says BIOS so it should not have choosen anything and defaulted to windows default theme. I have never seen a bios id say BIOS before for a oem machine. Since bios id is what decides theme in your case I need to know what it actually says in order to troubleshoot your issue. Update: If bios id does in fact say BIOS then this is the problem... SLIC|ASUS_FLASH ASUS_NOTEBOOK _ASUS_ BIOS|ASUS I just checked and I guess Asus uses bios id that says BIOS as well so I would have to edit script in this case to address the conflict. Funny they both use BIOS as the bios id version...