@Supern00b I just happened to find Windows 8 does not support "ProductKeyChannel" while trouble-shooting. Usually I'd search help from Abbodi1406, Murphy78 or Qad.
hi xinso, thank you for your effort in making this for us imho, the best part of this tool, it runs whenever windows need it to runs instead of a service that run 24/7? Simply one of the best
This config.xml removed One drive, yet installed Database Compare 2013 and Spreadsheet Compare 2013. Code: <Configuration Product=""> <OptionState Id="EXCELFiles" State="Local" Children="Force" /> <OptionState Id="PubPrimary" State="Local" Children="Force" /> <OptionState Id="WORDFiles" State="Local" Children="Force" /> <OptionState Id="XDOCSFiles" State="Absent" Children="force" /> <OptionState Id="ACCESSFiles" State="Absent" Children="force" /> <OptionState Id="PPTFiles" State="Absent" Children="force" /> <OptionState Id="OneNoteFiles" State="Absent" Children="force" /> <OptionState Id="OUTLOOKFiles" State="Absent" Children="force" /> <OptionState Id="GrooveFiles2" State="Absent" Children="force" /> <OptionState Id="LyncCoreFiles" State="Absent" Children="force" /> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <Setting Id="REBOOT" Value="ReallySuppress"/> </Configuration> Have you tried "setup /admin"? I did. But still exists Database Compare 2013 and Spreadsheet Compare 2013. So this config.xml might be the best solution if you don't have individual editions.
Hi, Your last config.xml is good for me, I think is the best solution for Office Pro Plus 2013 (for partial install) Yes Database Compare 2013 and Spreadsheet Compare 2013 but not a problem for now. I have tested it with my Win 8.1 AIO Iso (Pro/Enterprise) with a clean install and all work fine. I will try to use click to run (Setup /download) and see what appends.... Thanks for your contribution to MDL community, You provide a first class service. Xinso Regards
you could try create hooks for testing the installed version and redirecting them to your own service also changing permissions on the registry keys so they are unreadable unless run as SYSTEM that might help. have you considered rewriting the installation script in something other then batch batch files are very easy to read and understand what you are doing lua or active perl would be a good choice to prevent the installation script being read as plain text if I had to guss m$ is running a simple registry key check and seeing if the version installed matches up with the version activated what we don't want is them using the same method for windows as that will mean we will lose activation also randomly generated filenames would not be a bad idea and if at all possible move the activation routine out of userspace and into a kernel mode driver and load it directly after ELAM initiates I am on vacation atm ill do some experimenting when I get home
It seems too complicated for me... Thanks. And have a happy vacation. BTW, do you know how to decript the Click-to-Run APP-V Volume file? I am thinking of taking volume certificates out of it for individual components. Is it possible?
Hmm ... you suggest a complete reinvention to create something similiar to MTK and KMSpico ? Not sure whether this was xinsos intention ... ?
Good work on an interesting approach. I dont really know why its necessary though when you can accomplish the same thing with an $OEM$ folder or putting the OEM contents in MOUNT:\windows\setup\scripts. I don't see a single benefit.
Thanks. But Bee4u wanted to know "how to make pre-activated Windows without including $OEM$" - neither $OEM$ in ISO\soueces nor $OEM$ contents in MOUNT:\windows\setup\scripts.
fireman39, Here is some KMS certificates. Since I don't use Office, would you please have a go to see if it works fine or not? It can activate as usual. But I need to know if RTM Office 2013 works normally at work. Thanks.
I will test it let me few minutes... Edit: Tested on a new install Win 8.1/Office Pro plus Vl All seems working as expected
Did you delete tokens.dat before testing? If not, Office 2013 will be activated by leftover RTM certificates. If it is not OK for you to delete tokens.dat, please don't do it.