Hi guys, I found a way to easily activate against a kms server an rtm install of office 2013. For that, I had to diff the RTM and VOL iso. I noticed that only the proplusww.msi (vol version) differs from proplusrww.msi (rtm version) So what next ? Office 2013 can user the Windows 8 activation system, I deduct there has to be somewhere in the msi the xrm-ms vol version, and I found it. Inside the LicenseSetData table, I found 3 files: * ProPlusVL_KMS_Client-ppd.xrm-ms, you need it for slmgr to correctly consume the licence (simply for kms activation to works) * ProPlusVL_KMS_Client-ul.xrm-ms, don't know if mandatory, I have to try * ProPlusVL_KMS_Client-ul-oob.xrm-ms, you need it for slmgr to accept the GVLK So, I extracted thoses files, installed office 2013 RTM Then slmgr /inslic thefile.xrm-ms Then slmgr /ipk a-matching-gvlk Then slmgr /ato office-id-activation Note: use cscript ospp.vbs if you are on windows 7 instead of slmgr. tested on windows 8 pro with office 2013 pro plus MSDN. The advantage of this method (for me at least) is the ability to check the authenticity of the iso used to install office. Licences files:
I don't tested it, but I assume it is the same for using MAK keys on an RTM build. You just have to extract the ProPlusVL_MAK*.xrm-ms ones.
redroad, I don't say that the xdelta file is wrong, but I have no way to easily authenticate that. Moreover, there are more useless diff between rtm and vol, as packed file name, product id...
If the hashes check (Sha 1) then the untouched VL version is the result .. I was just pointing out a different way to approach it .. Sorry for not making that clearer .. I applaud your efforts .. With all the threads on Office 2013 it's hard to have the time to read through it all
@redroad: Yeah, but since Office 2010, unfortunately, Microsoft does not publish the VL version on MSDN Subcsriptions (msdn.microsoft.com/en-us/subscriptions/securedownloads/hh442898#searchTerm=&ProductFamilyId=475&Languages=en&PageSize=10&PageIndex=0), so no informations is publicly available from Microsoft about hash or filename.
Yes what you say is true however like every other leak it has been checked many times by many and what we have now is a100% confidence in the hashes .. Just google the CRC and you can see easily that is the case
I find on web very simple way with Microsoft Toolkit v. 2.4.7. Run Microsoft Toolkit and select Office Toolkit 1. Go to Customize Setup Tab 2a. Office 2013 Pro plus extract ISO files in any folder with winrar 2b. Ofiice 2013 Visio or Project Pro use build in Extract Setup option or extract ISO files in any folder with winrar 3. Set Installer Path then browse setup.exe 4. Change Channel Done You can use to convert Office 2010 also )