[DISCUSSION] Microsoft Office 2019

You need to login to view this posts content.

 

Thank you, then for what I understand, that means that after reinserting those keys their previous activation status would come up again if tokens wasn't rebuild.

 

ok the office 2019 activation is gone.

but I seem to be doing something wrong with the script for office 2016

 

You were meant to open an admin cmd prompt, and then enter:

Code:

cscript slmgr.vbs /dlv all > C:\slmgr-output.txt

it'll then output to a txt file on c:\ root. Please take a look at ratzlefatz posts and links, these commands will only delete the installed keys. If you wish to remove the complete license, tokens.dat and cache.dat must also be removed.

 

Portuguese (Portugal).

 

so now a bit confused, do we have a volume addition, or do we just convert retail to volume?

 

ProPlus2019Retail.img pt-pt and pt-br works

 

retail to volume

 

ok * g is out
yes, I already read that from ratzlefatz
I once looked at the complete slmgr-output.txt, I have a lot of activations in there

thank you yomoma2

 

You need to login to view this posts content.

 

It seems there is not much difference between installing VL directly or converting retail to VL (by reporting if you install the retail version first you get a newer build). What makes a difference is the update channel that are so many and leave us confused in which to choose

I'm not familiar with C2R. Even installing the VL version directly will I have a process running in the background and updating the office? I'd like to have nothing running in the background or updating automatically.

 

One weird thing I'm having trouble to figure out. On one system I'm getting:

Code:

SKU ID: 85dd8b5f-eaa4-4af3-a628-cce9e77c9a03
LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---

While in another VM I get:

Code:

SKU ID: 85dd8b5f-eaa4-4af3-a628-cce9e77c9a03
LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---LICENSED---

Both are 19PPRetail/monthly installations made with OfficeRTool, then C2R-R2V_4 and KMS_VL_ALL-SppExtComObjPatcher-kms-25. configure64.xml is the same in both machines. Where does BETA EXPIRATION: 01/01/1601 come from?

 

Thanks, but it still doesn't work but it works in Edge, which is strange (I only remembered using it now). However, I think I prefer 365 to it. Anyway, what is this channel thing everyone is talking about and where do you have to choose one?

 

I changed to x64 for performance reasons (Word and Outlook specifically); the ONLY reason (in my humble opinion) to continue using Office x32 is due to lack of plug-ins in x64 (that issue went away as of Office 2016 x64, as the last of any plug-ins I needed went x64).

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I will move to office 64 bit tonight. Office 2019 pro plus installs 32 bit by default unless you find the 64 bit installation file.

 

deleted