If you install Office 365, do you need a valid subscription to use it? Or can you use it offline? I read somewhere that you need to give valid credentials every month. Is that correct?
Yes, that's true. That's true, too. To make it happen, use Retail2Volume conversion script C2R-R2V from abbodi1406 or use OfficeRTool's built-in option (C) convert Retail to Volume. Native, unmodified Office 365 needs online verification. Converted/KMS activated Office 365 is working fine at the moment. But this possibility may (or may not) be removed by Microsoft in a future Office 365 build. So no warranties.
This Script is working. After I used this script I uninstalled Office 2019, then I installed it again with the Retail version, but the Retail version is already converted to the VL version. How is it possible?
It's not the script fault you cannot remove previous Office licenses with normal uninstall, you must use cleanospp.exe https://forums.mydigitallife.net/threads/discussion-microsoft-office-2019.75232/page-33#post-1466365
Thanks @abbodi1406 for new C2R script, I have a non important question if I may What would be the name of installed apps when we want to install Office 365? Are they always get names like Word 2016 or it can be changed by configurations? How about SKU in file->account menu? I used 2016 ProPlus license before converting that it was Office 365 now it is Office without any name or year
You mean shortcuts? or the splash screen and Account/About page? it depend on installed licenses, and adding the corresponding SKU to ProductReleaseIds registry
Shortcuts will be always versionless, except OneNote 2016 Account/About page require proper licensing conversion https://forums.mydigitallife.net/threads/discussion-microsoft-office-2019.75232/page-45#post-1469215
Hi All, I saw " Office 2013-2019 C2R Install v6.4.5 Final " on Google. Anyone point me to the links, Thanks.
Afaik, the activator will be KMS_VL_ALL and when windows is activated by any other method and shows activated, the office activation won't touch the already activated windows, as all properly coded KMS tools do,
OfficeRTool should include this as an option. Of course, should verify if this is working fine. Code: <!-- Remove Office Telemetry (Collection of data) --> <AppSettings> <User Key="software\microsoft\office\16.0\common\ptwatson" Name="ptwoptin" Value="2" Type="REG_DWORD" App="office16" Id="L_ImproveProofingTools"/> <User Key="software\microsoft\office\16.0\common" Name="qmenable" Value="2" Type="REG_DWORD" App="office16" Id="L_EnableCustomerExperienceImprovementProgram" /> <User Key="software\microsoft\office\16.0\common" Name="updatereliabilitydata" Value="2" Type="REG_DWORD" App="office16" Id="L_UpdateReliabilityPolicy" /> </AppSettings> Edit: I know there is an option to disable office telemetry after setup... But i am wondering if the main data collection could be disabled in the xml file.
Perhaps I can't find the setting in OfficeRTool, but is there a way to set where Office installs? I really don't want it on my C: drive.
I have a problem with activating my Office with your OfficeRTool. The message I get when trying to activate: Use internal OfficeRTool KMS server (1/0)? >1 Adding KMS activation file exclusions to Windows 10 Defender Exclusion List ____________________________________________________________________________ No Instance(s) Available. No Instance(s) Available. Activation failed ____________________________________________________________________________ Removing KMS activation file exclusions from Windows 10 Defender Exclusion List I followed the ReadMe file and none of the solutions work for me so far. Any help would be appreciated.
First of all, thank you for providing this script. I like the KISS philosophy. I only ran into a small issue when trying to install a Volume License (Office - Install VL ) for a 32-bit Office installed on a 64-bit version of Windows. When the script runs this line: Code: echo Installing VL, please wait... "%ProgramFiles%\Microsoft Office\root\integration\integrator.exe" /I /License PRIDName=%product%.16 PidKey=%pidkeys% >nul that command cannot be executed since it is not found. The %ProgramFiles% variable is expanding to the 64-bit Program Files directory, on the other hand, the Office itself is installed in the 32-bit Program Files directory. Changing from %ProgramFiles% to %ProgramFiles(x86)% solved the problem, but I think it's just a dirty workaround.
I resolved it by reactivating Windows 10 then reactivating Office 2019; it worked immediately. It may have been caused by the user connecting to his Microsoft Account before activating Office, I guess Abbodi may be a better person to shed light on this issue.