That's correct (both assumptions). Preselected Office version gets "updated" when s1ave77 builds a new version of JATD. In case of a new Office, you can override the hard-coded version by entering latest build string from post#6 in setup dialog.
Problem is more that: Code: C:\Users\s1ave77\Desktop\+++.JATD.Script.vXX.+++\files\officefixes\15\ProjectPro >wmic path SoftwareLicensingService where version='6.3.9600.16384' call InstallL icense License="projectprovl_kms_client-ul-oob.xrm-ms" Executing (\\S1AVE77-PC\root\cimv2:SoftwareLicensingService.Version="6.3.9600.16 384")->InstallLicense() ERROR: Description = C:\Users\s1ave77\Desktop\+++.JATD.Script.vXX.+++\files\officefixes\15\ProjectPro >echo %errorlevel% -1073418209
License Uninstall works perfectly with: Code: wmic path SoftwareLicensingProduct where ID='7a0560c5-21ed-4518-ad41-b7f870b9fd1a' call UninstallProductKey
I know the problem. Its License=".xrm-ms" syntax is wrong..I added it as example..syntax should be changed.. for eg: when you are setting KMS port, we use wmic path SPS where version='ver' call SetKMSPort 1688 --- Works wmic path SPS where version='ver' call SetKMSPort Port="1688" ---Won't Work We need to check the return type of that particular method and the parameters it accepts..will do that in some time, as I have to leave now..
Hmmm .............................: Code: C:\Users\s1ave77\Desktop\+++.JATD.Script.vXX.+++\files\officefixes\15\ProjectPro >wmic path SoftwareLicensingService where version='6.3.9600.16384' call InstallL icense projectprovl_kms_client-ul-oob.xrm-ms Invalid Verb Switch. C:\Users\s1ave77\Desktop\+++.JATD.Script.vXX.+++\files\officefixes\15\ProjectPro >wmic path SoftwareLicensingService where version='6.3.9600.16384' call InstallL icense "projectprovl_kms_client-ul-oob.xrm-ms" Executing (\\S1AVE77-PC\root\cimv2:SoftwareLicensingService.Version="6.3.9600.16 384")->InstallLicense() ERROR: Description = C:\Users\s1ave77\Desktop\+++.JATD.Script.vXX.+++\files\officefixes\15\ProjectPro >echo %errorlevel% -1073418209
Yeah, once we get it to work, we can use use single script for both 32-bit and 64-bit offices, also works on custom installation paths.. For eg: D:\qewlpal\MS_Office instead of default Program Files folder
Querying registry will always show the correct install path, equally where this would be. Only drama queenie here is the crappy C2R installer and the virtual sub-registry he creates, including the missing OSPP-Issue for Professional Non-Pro. Cert Install is atm the only left-over using SLMGR/OSPP.VBS. If we can argue WMIC to do that, the install path would be demoted to an additional info aka nice-to-know, but not needed for the process at all. Forgot to mention: That means nearly every Office version with existing certs could be easily converted and activated.
Everything is working, but I need further help Thanks! I converted RTM to VL and works like a charm. I have a doubt. It happens that I don't want to install ALL the apps from office 2016. How can I do to customize the setup in order to let me decide which apps I want to install?
Thanks for the feedback, you're Welcome. For your question better wait for ratzlefatz or some others, they know such things better than doggie .
JATD will be able (in a later version) to: Generate a customized configuration.xml file containing each single app, insert the matching certification files, enter the corresponding product keys and get this "construct" activated. And it needs a little logic-check to prevent choosing full Office Suite and Single App's together because that don't work. You see, there is "some" work and tests to do, to get all this up and running. So please be patient. It will come when it's ready.
Is there any problem? It takes a very long time to install build 1011 on my pc. Is it normal? but I was not experienced when installing the previous build.