We tried ODT config: Code: <Configuration> <Add OfficeClientEdition="64" Channel="PerpetualVL2019"> <Product ID="ProPlus2019Volume"> <Language ID="en-us" /> </Product> <Product ID="VisioPro2019Volume"> <Language ID="en-us" /> </Product> <Product ID="ProjectPro2019Volume"> <Language ID="en-us" /> </Product> <Product ID="ProofingTools"> <Language ID="en-us" /> </Product> </Add> <RemoveMSI All="True" /> <Display Level="Full" AcceptEULA="TRUE" /> </Configuration> but got error "This product can't be installed on the selected update channel" for the ProofingTools entry. When it is removed, installs fine. Not sure why.
@thej82, the previous version of setup.exe "16.0.10810.33603" can install Office Channel="PerpetualVL2019" "16.0.11001.20074" with "ProofingTools" entry
Hello, anyone would give me a clue to get out this nag of ProjectPro2019Volumex64 in Wondows 7 64bit ?
ODT v11023.33600 won't accept Product ID="ProPlus2019Volume", either. Use v10810.33603 instead. setup.exe can be found inside OfficeRTool2018Aug26.7z https://forums.mydigitallife.net/th...install-activation.62571/page-14#post-1125229 EDIT: In light of abbodi's comment(see below), some clarification: ODT v11023.33600 won't let you install Office 2019 16.0.10730.20102 as ProPlus2019Volume, even with PerpetualVL2019 as the channel(at least on W10 1709 16299.15). The latest ODT's setup.exe accepted only ProPlus2019Retail with office 2019 release 1808 iso, but the older version installed Retail and Volume ProPlus2019 just fine. Don't know why. BTW, C2R-R2V_6 does what it is supposed to do.
I'm curious: Why does everybody want ProPlus2019Volume from PerpetualVL2019 channel? Only to skip Retail2VL conversion step? But then you have to deal with update not working. On the other side: If you use ProPlus2019Retail you get Volume too (after conversion) and there are no problems with updates. At the moment I see no ultimate advantage in using a native Volume SKU.
On avoiding post-install conversion tools: Probably, it gives the illusion of a clean install or more manual control. Or may be, it is just a hangover from the <2016 MSI days. Having volume from the get-go is the default/trained mode for many. Things have clearly changed, for better or worse. And so should have our outlook.
@Krakatoa - OK will make necessary changes to xml and try the install later. Will keep this post updated.
Still same error. Here is updated xml. <Configuration> <Add SourcePath="\\cm1\Sources\Application\2019 Office" OfficeClientEdition="64" > <Product ID="ProPlus2019Volume" > <Language ID="en-us" /> </Product> <Product ID="ProjectPro2019Volume" > <Language ID="en-us" /> </Product> <Product ID="VisioPro2019Volume" > <Language ID="en-us" /> </Add> <RemoveMSI All="True" /> <Display Level="None" AcceptEULA="TRUE" /> <Property Name="AUTOACTIVATE" Value="1" /> </Configuration>