Home

Installing Viso 2016 and Project 2016 MSI w/ CTR?

%3CLINGO-SUB%20id%3D%22lingo-sub-64924%22%20slang%3D%22en-US%22%3EInstalling%20Viso%202016%20and%20Project%202016%20MSI%20w%2F%20CTR%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64924%22%20slang%3D%22en-US%22%3E%3CP%3EI%20thought%20there%20was%20new%20options%20on%20how%20to%20enable%20installing%20Visio%202016%20and%20Project%202016%20MSI%20alongside%20Office%20CTR.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20cannot%20seem%20to%20find%20the%20article.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20do%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20we%20have%20the%20liceneses%20for%20the%20MSI%20versions%20of%20Visio%20and%20Project%20is%20there%20a%20CTR%20version%20that%20we%20could%20use%20that%20same%20license%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EeZe%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-64924%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EProPlus%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66263%22%20slang%3D%22en-US%22%3ERe%3A%20Installing%20Viso%202016%20and%20Project%202016%20MSI%20w%2F%20CTR%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66263%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20add%20to%20the%20what's%20been%20said%20already%2C%20we%20went%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%26nbsp%3Bapproach%20during%20our%20Office%20365%20ProPlus%20rollout%20and%20it%20worked%20well.%20This%20allowed%20us%20to%20use%20our%20Volume%20Licensing%20with%20Click-to-run%20installing%20Project%2FVisio%202016%20alongside%20Office%20365%20ProPlus%20Office%202016%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20an%20example%20xml%26nbsp%3Bsetup%20for%20this%20configuration%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%26lt%3BConfiguration%26gt%3B%0A%20%20%20%20%26lt%3BAdd%20OfficeClientEdition%3D%2232%22%20Channel%3D%22Deferred%22%26gt%3B%0A%20%20%20%20%20%20%20%20%26lt%3BProduct%20ID%3D%22O365ProPlusRetail%22%26gt%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%26lt%3BLanguage%20ID%3D%22en-us%22%2F%26gt%3B%0A%20%20%20%20%20%20%20%20%26lt%3B%2FProduct%26gt%3B%0A%20%20%20%20%20%20%20%20%26lt%3BProduct%20ID%3D%22VisioProXVolume%22%26gt%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%26lt%3BLanguage%20ID%3D%22en-us%22%2F%26gt%3B%0A%20%20%20%20%20%20%20%20%26lt%3B%2FProduct%26gt%3B%0A%20%20%20%20%20%20%20%20%26lt%3BProduct%20ID%3D%22ProjectProXVolume%22%26gt%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%26lt%3BLanguage%20ID%3D%22en-us%22%2F%26gt%3B%0A%20%20%20%20%20%20%20%20%26lt%3B%2FProduct%26gt%3B%0A%20%20%20%20%26lt%3B%2FAdd%26gt%3B%0A%20%20%20%20%26lt%3BDisplay%20Level%3D%22None%22%20AcceptEULA%3D%22TRUE%22%2F%26gt%3B%0A%26lt%3B%2FConfiguration%26gt%3B%3C%2FPRE%3E%3CP%3EHaving%20to%20use%20a%20MAK%20setup%20wasn't%20ideal%20at%20first%2C%20having%20to%20meet%20the%20minimum%20amount%20of%20units%20but%20it%20worked%20fine%20in%20the%20end.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66243%22%20slang%3D%22en-US%22%3ERe%3A%20Installing%20Viso%202016%20and%20Project%202016%20MSI%20w%2F%20CTR%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66243%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Eric%2C%20technically%20it%20is%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt712177(v%3Doffice.16).aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Enot%20supported%20to%20run%20an%20MSI%20and%20a%20C2R-based%20product%20from%20the%20same%20release%20(%3C%2FA%3Ee.g.%20Office%20ProPlus%20(2016)%20C2R%20and%20Visio%202016%20MSI)%20on%20the%20same%20box.%20But%20if%20your%20using%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fee624358(v%3Doffice.16).aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKMS%20server%20or%20ADBA%3C%2FA%3Efor%20activating%20Visio%2FProject%20and%20you%20have%20a%20volume-license%20agreement%20in%20place%2C%20you%20can%20opt%20to%20run%20the%20C2R-based%20volume%20license%20releases%20of%20Visio%2FProject%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt703272.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt703272.aspx%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20enables%20you%20to%20run%20two%20different%20license%20flavors%26nbsp%3B(volume-licensed%20Visio%2FProject%20and%20subscription-based%20Office)%20with%20one%20deployment%20technology%20(C2R)%20on%20the%20same%20box.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-64999%22%20slang%3D%22en-US%22%3ERe%3A%20Installing%20Viso%202016%20and%20Project%202016%20MSI%20w%2F%20CTR%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64999%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20was%20an%20offer%20to%20get%20a%20matching%20C2R%20version%2C%20but%20it%20expired%20afaik.%20The%20%22upgrade%20offer%22%20page%20now%20redirects%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FError-Stop-you-should-wait-to-install-Office-2016-We-ll-have-to-remove-the-following-if-you-continue-a225347f-e102-4ea6-9796-5d1ac5220c3b%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FError-Stop-you-should-wait-to-install-Office-2016-We-ll-have-to-remove-the-following-if-you-continue-a225347f-e102-4ea6-9796-5d1ac5220c3b%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20did%20relax%20the%20requirements%2C%20the%20latest%26nbsp%3Bsupportability%20matrix%20is%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt712177(v%3Doffice.16).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt712177(v%3Doffice.16).aspx%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

I thought there was new options on how to enable installing Visio 2016 and Project 2016 MSI alongside Office CTR.

 

I cannot seem to find the article.

 

Is there a way to do this?

 

If we have the liceneses for the MSI versions of Visio and Project is there a CTR version that we could use that same license?

 

Thanks,

eZe

3 Replies

There was an offer to get a matching C2R version, but it expired afaik. The "upgrade offer" page now redirects here: https://support.office.com/en-us/article/Error-Stop-you-should-wait-to-install-Office-2016-We-ll-hav...

 

They did relax the requirements, the latest supportability matrix is here: https://technet.microsoft.com/en-us/library/mt712177(v=office.16).aspx

Highlighted

Hi Eric, technically it is not supported to run an MSI and a C2R-based product from the same release (e.g. Office ProPlus (2016) C2R and Visio 2016 MSI) on the same box. But if your using a KMS server or ADBA for activating Visio/Project and you have a volume-license agreement in place, you can opt to run the C2R-based volume license releases of Visio/Project: https://technet.microsoft.com/en-us/library/mt703272.aspx

 

This enables you to run two different license flavors (volume-licensed Visio/Project and subscription-based Office) with one deployment technology (C2R) on the same box.

To add to the what's been said already, we went with @Martin Nothnagel approach during our Office 365 ProPlus rollout and it worked well. This allowed us to use our Volume Licensing with Click-to-run installing Project/Visio 2016 alongside Office 365 ProPlus Office 2016 version.

 

Here is an example xml setup for this configuration: 

 

 

<Configuration>
    <Add OfficeClientEdition="32" Channel="Deferred">
        <Product ID="O365ProPlusRetail">
            <Language ID="en-us"/>
        </Product>
        <Product ID="VisioProXVolume">
            <Language ID="en-us"/>
        </Product>
        <Product ID="ProjectProXVolume">
            <Language ID="en-us"/>
        </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE"/>
</Configuration>

Having to use a MAK setup wasn't ideal at first, having to meet the minimum amount of units but it worked fine in the end.