Since I create custom recovery partitions on my machines I really don't have to do that...while I am in audit mode on a legit oem-dm key machine I can copy the folders over and run them which will do branding plus activate it by pulling the key out of bios and applying it. As far as wanting to install apps like the usual way of setupcomplete cmd file use a reg entry to run your program installations from first logon. This is why audit mode is so great...you can do a lot of this even manually then capture image and the image is activated and oem branded. But this is how I do things...I know others aren't into making custom recovery partitions and that is ok. You could use unattend.xml for call oobe but not for sure...I haven't tried it.
Yes. Good on you, mate. I failed in autounattend.xml. I am not good at it after all. Now I am working on WIMBoot. See you.
Hi xinso ! Little note to avoid confusion when creating the WIM (2 posts above): Code: 2. Copy $OEM$\$$\Setup\Scripts to D:\1\Windows\Setup better: Code: 2. Copy content of $OEM$\$$\Setup\Scripts to D:\1\Windows\Setup\Scripts Else some may try to create D:\1\Windows\Setup\$OEM$\$$\Setup\Scripts or similiar .
In my case using audit mode adding this to my xml should turn back on the oobe.cmd file... Will do some testing later today.
The problem is that the oem folder isn't being seen so it doesn't get copied over to scripts folder on the OS. This is why oem's use audit mode so this doesn't effect them. I don't know of a way to externally make the oem folder to be seen and copied....you would have to add to index's in the iso's. Too much trouble for me and plus I don't do installs that way. If I come acrossed info for you I will post it.
yes I have changed it....I knew calling the first experience oobe would not work on csl's. This might take a while to be honest. Its passed my bed time so if this last test doesn't work I will call it a night and try again when I am more refreshed. I'm on the right track. I am trying just to run a exe file to see if it even runs or not. Time will tell. lol
Found the error in the xml file....testing again now with some minor changes. Note: I am beginning to think this isn't possible with csl versions. This is what is wrong in the autounattend.xml file... I have changed this to every possible selection without any luck. I have also set path to windir\setup\scripts\oobe.cmd since it does copy over but doesn't run. I cant get the autounattend.xml to run the oobe.cmd. I am going to have to take a break from this for the time being for I have some bills to pay. Will play with this more tonight. I still say to use the pid.txt file and then oem folder runs as it should without the need of a lot of editing. Just my opinion.
I know for all the other win 8.1 versions other then csl the oobe and firstlogon work for legit oem with oem-dm key in bios. Searchengine tested his project on a win 8.1 which had the oem-dm key in bios and with his scripting for extracting the oem key then applying it during oobe process, it will be oem activated with branding so your above statement is a little flawed according to what Searchengine mentioned to me on his project thread. If you search on M$ site (will take some searching plus they have some conflicting info reguarding win 8.1 like what you mentioned) you will see if oem-dm key is present in bios setupcomplete is disabled and you should use firstlogon.cmd to install other apps or what ever you wish to do. Now with the csl versions, since they are different, there are other variables with installs like we are finding out. I haven't worked on a win 8.1 machine except for one...they are too new to break. lol I do know Searchengine tested his project on his own machines which was win 8.1 but not csl and it did activate his machine but had to use firstlogon.cmd to install apps and such. Setupcomplete.cmd file is for non oem's only. Its hard to find win 8.1 machines where ppl wish to redo and customize their machines for it would void warrenties. Give it another yr then everyone will be working on win 8.1 legit oem machines. lol Note: Why would you think Searchengine would add a tool to extract and apply oem-dm key if it didn't work? He is really good about testing thoroughly. Just saying. Very true and I agree. For csl version I just add the pid.txt file to sources folder which uses just a install key (you can get them from M$ for what ever version) then add Searchengines oem folder and it works great in VMware but as far as oem legit csl version machines I don't know and I don't think many do for it is just too new and not many techs have worked on them yet. Like I said above give it a yr.
Well after reading all discussions on this topic (CSL sku) the workaround is simple, I guess: 1. Prepare CSL iso for single or AIO integration inserting a gVLK for $oem$ to run. 2. Use a KMS solution within $oem$ folder. 3. Result: CSL KMS activated and OEM branded, ready to be used. Optional: 4. If this CSL KMS activated is installed on an OEM machine use a key dumper to read OEM-DM key in UEFI. 5. Then having the machine with Internet connection, change KMS key for OEM-DM key. 6. Execute the proper command to activate with this new key and finally you end preserving OEM activation and OEM branding. In this case you will get rid of factory pre-installed OS full of bloatware.
Exactly, I was searching for your posts now that I recall but they're gone And no you are not the last one, and neither I will... Just have not enough time to study everything. Oh my gosh xinso, hahaha, I was taking a look at your screenshot and don't know how can you deal with sinograms, they are just hard to read. See, my sight is tired and have problems to read my own alphabet, now imagine sinograms, I'm going to end like
As long as you read a bit into the basics of that matter and ask propper questions (not the way to ask what to do now ) murphy78 is giving a helping hand. The rest is some trial and error to get it working. Trust me, murphy78 is a very nice guy .
Yes xinso I am reading a bit for now, I'm tired. I changed my nickname because I wanted this in the first place but at the time when I registered at MDL it wasn't available. But a few days ago I requested for a change and it was granted.