Very mad question here, you say put it on oem folder in sources folder, does that mean I have to rename asus folder to $oem$ or open the oem folder and put asus one inside
It's seems that i have not enough post count to see the thanks button, but Thanks anyway, this project is quite awesome, keep going.
Your machine is now ready to go. After you download the project. Extract its contents to a folder. In that extracted folder you will see a $oem$ folder (its all ready to go), open your iso or usb media and you will see a sources folder. Copy the $oem$ folder into the sources folder (if iso, save the iso and burn at the slowest speed). Now you are ready to install.
Hello Before I get to to the point I would like to thank you for making that awesome script that helps me so much in my everyday work! Reason why I write this post is because script stopped working for me when I Sysprep / Capture VM and creating media out of it using MDT 2013. Before I move on I want to clarify something.New script works for me ONLY when I use CD/DVD (ISO) media and put $oem$ folder into sources but as soon as I use MDT to create media (including task sequence, applications, updates and drivers) it does not activate Windows 8.1 anymore. So I started troubleshooting problem and days later found older script (date modified: 04.2014) and it works like a charm. Way I use your script is that I create VM and install Windows 8.1 on it, then I install every update. After updates I go to your script folder called $oem$ and locate scripts folder which I then copy inside C:\Windows\Setup folder, then I create snapshot and use MDT Sysprep and capture Task Sequence to capture .WIM file for later use of media creation. I'm not good at scripting myself and I don't know what exactly have changed but it doesn't like what I'm doing with it. All I know is that when I look inside scripts folder (both new and 04.2014) they have different logic how they supposed to work. I really hope info I shared is relevant and maybe there's someway to help us MDT guys out (Windows 7 installation still works like a charm!). I also want to apologize for my bad English and I hope you understand most of it. Regards
Let me guess....you put the scripts and files in the setup folder which is incorrect. Should be in scripts folder inside the setup folder in windows directory. Second, you didn't leave your media in the computer when running the oobe.cmd in audit mode did you? Of course not, then failure occurred. The project does system checks to ensure it will install correctly. If not setup correctly failure will always happen. It was never meant to be ran from audit mode but it can if done correctly. Problem is everyone is trying to misuse the project and complain why it doesn't work. lmao! As far as you saying it doesn't work with usb media...that is not true. It does for that is how I do all my installs because I don't have a dvd drive or anything so I have to use usb media but you must format the media correctly first. If you check your C:\ drive you have a txt file there with a error (only if using the new apr 15 2015 version). If windows 7 installation worked then win 8.x or win 10 will as well...its the same code but it you that are doing something different that is not complying with the built in checks. Note: If using windows 10 the oobe is ran right before audit mode and everything will be ran already. This is cool! Did you use Anarethos recovery tools to enter audit mode for win 8.x? The reason I ask is with his new version, it wont enter audit mode. GRRRRR!
Yes you did misunderstood me there. 1) I put Scripts folder inside Setup not files. 2) I do not use Audit mode (If you know how MDT 2013 Sysprep And Capture works) 3) It works from USB when I use CD/DVD files as soon as I use MDT it stop working (Windows 7 doesn't have that issue) 4) I do everything exactly same as I do with Windows 7 "Problem is everyone is trying to misuse the project and complain why it doesn't work. lmao!" - And I don't understand why you call it complaining it's not what I'm doing here I just want to find solution and if it's something I do wrong then it fine by me as long as I get new scripts working. At the moment I've tried everything I could think of as well as different methods and only solution for 8.1 at the moment is either blank installation from USB or old versions for MDT installation (also from USB). And once more don't think I complain here no, not at all I admire what you've created so that's the last thing I would do.
I don't use MDT so no support will be given. If I don't use it, I don't support it. Plus I need more info then it just doesn't work. Right now I use Arenothos revcovery tools to make image not MDT. I will test this in VMware to find out for sure. If not using audit mode then you are at the main desktop so it should have oem branding and activation. This would be a third party application that I don't use, know how to use nor care to learn.
Branding only for this one but I don't know if any slic 2.0/2.1 keys and certs are available yet. I cant find any. Plus we need the query tool ran so I know what to look for in the bios to assign branding so I will have to wait until that is shared. This one we already have.
I have been testing the oobe.cmd file ran while in audit mode and it worked except wallpaper isn't activated yet but we are in audit mode so it is limited....capturing image now with no errors so far. Wallpaper should be default when installation has completely finished. Everything else installed in audit mode. Just waiting to hit desktop now... Capturing done and booting up...lets see if wallpaper applied...and all oem branding was applied perfectly. I ran the oobe.cmd file from in audit mode before capturing image and it worked. The only thing is the wallpaper wont take effect until it hits the actual desktop and that's ok. As far as activating, this was a VMware test so if slmgr.vbs /ipk or slmgr.vbs /ato isn't available in audit mode for win 8.x/10 then there is nothing I can do about that. Conclusion: Yes, the project works while in audit mode and manually running oobe.cmd file as admin but you must have the media source attached to your computer (Windows USB or DVD media), if not then failure will occur but you will have a PROJECT_FAILURE.txt file at the root of your C: drive stating the error.
LITTLEBIT MEVIS MICROSPOT We could add with the AXXIV that you gave me before. If we can find all the certs and keys for vista/win7 only that would be cool. Can you send me the ones I don't have yet so at least we got them for branding later. I need the query tool ran on those to find out bios query info in order to add to the ini file. If the bios info isn't known then I cant add any of these. I got all the links above you posted so far so if you wish to edit them, you can.
I have to take my dog to the vet for her shots so be back later and thanks for all your help. See everyone in a couple hrs or so.