i think the issue is from the windows media creater tool. in the source dir is an product.ini. this ini has different product keys in it. so there is the problem. i need an ritail or oem windows iso. without this crap... and then it should work.
I may be wrong but going by OEM Query Tool it says OS Name: Windows 10 Home [x64] #13 LICENSE STATUS - Licensed
I want to see the Project.log file. Says its activated according to the query tool but I want to see the Project.log file. My request keeps getting ignored.
Correct, but also with KMS I didn't have any issues. If I didn't activate it I would notice the lock screen reverting to the Windows Spotlight. If I activated with a legit KMS server from my work I had no issues and could restart/shutdown without issue. So it could be the program/script KMS is missing something or not properly authenticating I don't know not a clue on scripting or programing.
I haven't gone though to look for what you did to the EI.cfg file but try this: [Channel] _default [VL] 0 I have used it with Retail, Volume, and OEM-DM keys without issue. It also skips Win 8/10 from asking for a key or having to click skip if it doesn't find an OEM-DM key. I have an AIO I made with 7/8.1/10 in a .SWM format for UEFI or Legacy booting and use that EI.CFG without issue. So far even with the $OEM$ under sources I have yet to need a PID or RETAIL.txt on Dell, HP, Asus, or Lenovo. The only one issue I have had was with Win 7/10 enterprise saying "Error, no supported windows edition found." in the project.log file but worked fine in VMware so guessing it was a PID issue I don't know but didn't want to bother The_Gaurdain as I didn't care. I only use enterprise at work and not for myself or others. On the product.ini that doesn't or shouldn't matter to me from looking at the keys there. They look like the default keys to input for either using a KMS server or from digital entitlement. Like any Pro upgrade or store (though windows) bought will have digital entitlement and have the key ending: 3V66T
The error in log file is from enterprise not being included because of no keys. Like you said, you used kms for activation. The kms tools here at mdl has issues with win10 and personalization settings not unlocking (login screen and such). Obviously your work kms is setup correct where kms tools here at mdl have an issue with kms emulation. Nothing to do with this project.
You need to use some sort of third party imaging backup utility in order to create an image that can be deployed on all workstations within your network.
I would capture the image and add the project to it. Put the contents of the setup folder in the project to captured image, %windir%\Setup\scripts folder.
I guess I will do that. Since this is for a network & domain of machines, what might be the best forum/ sub forum on MDL to get attention for this?
The activation is stored in tokens and dat files so opening another thread would be best since this thread doesnt touch on that subject. It all depends on the OS.
I got info on ECS including cert for starter edition but no shared key found as of yet. Update: Got win7 starter key for addition to project from a member who helps me from time to time, thanks.
I am going to be redoing the query section because of conflicts between them if a oem has same letters in name as another oem. Think this can be done better then the original code to sort this issue out. Now I need to find the time to do it. lol
Those who would like to test the query tool beta version to see if conflicts are reduced, let me know. I want this query tool tested on oem's we know that cause issues with branding. For example Compaq vs HP. The beta query tool is only available by pming me. Update: Updated query tool build 4 with ECS oem for beta testing. Update2: Looks like this method works on MSI/BIOSTAR oem conflicts for query results. The happy dance is in order.
Think we will call this method variable conflict resolution which is what it is. I feel it is appropriate.