[DISCUSSION] Microsoft Office 2019

Discussion in 'Microsoft Office' started by ratzlefatz, Sep 26, 2017.

  1. Mr Been

    Mr Been MDL Senior Member

    Feb 24, 2008
    256
    68
    10
    #1382 Mr Been, Nov 3, 2018
    Last edited: Nov 4, 2018
    deleted
     
  2. thej82

    thej82 MDL Novice

    Nov 20, 2012
    4
    0
    0
    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.
     
  3. rcstar6696

    rcstar6696 MDL Senior Member

    Jun 11, 2017
    447
    351
    10
    #1384 rcstar6696, Nov 3, 2018
    Last edited: Dec 25, 2018
    -snip-
     
  4. c6p0

    c6p0 MDL Junior Member

    Aug 17, 2010
    71
    44
    0
    #1385 c6p0, Nov 3, 2018
    Last edited: Nov 3, 2018
    @thej82,
    the previous version of setup.exe "16.0.10810.33603" can install Office Channel="PerpetualVL2019" "16.0.11001.20074" with "ProofingTools" entry
     
  5. blarghyness

    blarghyness MDL Novice

    Sep 23, 2015
    24
    3
    0
  6. rcstar6696

    rcstar6696 MDL Senior Member

    Jun 11, 2017
    447
    351
    10
    #1387 rcstar6696, Nov 4, 2018
    Last edited: Dec 25, 2018
    -snip-
     
  7. Krakatoa

    Krakatoa MDL Addicted

    Feb 22, 2011
    544
    835
    30
  8. blarghyness

    blarghyness MDL Novice

    Sep 23, 2015
    24
    3
    0
    Excellent! Thank you for clarifying!
     
  9. IIITA

    IIITA MDL Novice

    Jan 11, 2013
    30
    7
    0
    Hello, anyone would give me a clue to get out this nag of ProjectPro2019Volumex64 in Wondows 7 64bit ?
     
  10. Fckr

    Fckr MDL Member

    Feb 4, 2011
    197
    85
    10
    #1392 Fckr, Nov 5, 2018
    Last edited: Nov 5, 2018
    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.
     
  11. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    11,766
    52,969
    340
    It accepts ProPlus2019Volume from PerpetualVL2019 channel range only (16.0.1033x.xxxxx)
     
  12. ratzlefatz

    ratzlefatz MDL FUBAR Recon Squad

    Sep 1, 2012
    1,334
    4,654
    60
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Fckr

    Fckr MDL Member

    Feb 4, 2011
    197
    85
    10
    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.
     
  14. ramg1967

    ramg1967 MDL Member

    Sep 13, 2012
    235
    83
    10
    @Krakatoa - OK will make necessary changes to xml and try the install later. Will keep this post updated.
     
  15. ramg1967

    ramg1967 MDL Member

    Sep 13, 2012
    235
    83
    10
    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>
     

    Attached Files:

    • 3.JPG
      3.JPG
      File size:
      30.2 KB
      Views:
      24
  16. klinexman

    klinexman MDL Novice

    Nov 4, 2018
    10
    4
    0
    i heard that office 2019 could be installed on win7 machines. Is that true ?