Deploying Office 365 ProPlus: MSI versions not removed and Visio/Project don't support SCA

%3CLINGO-SUB%20id%3D%22lingo-sub-64262%22%20slang%3D%22en-US%22%3EDeploying%20Office%20365%20ProPlus%3A%20MSI%20versions%20not%20removed%20and%20Visio%2FProject%20don't%20support%20SCA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64262%22%20slang%3D%22en-US%22%3E%3CP%3ETwo%20issues%20I%20ran%20into%20while%20using%20the%20new%20functionality%20of%20SCCM%20to%20deploy%20Office%20365%20ProPlus%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20The%20setup%20will%20fail%20if%20any%20MSI%20version%20of%20Office%20products%20is%20installed.%20But%20the%20CTR%20setup%20will%20leave%20behind%20a%20registry%20value%20at%20HKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5COffice%5CClickToRun%5CConfiguration%5CVersionToReport%20which%20SCCM%20uses%20for%20detection%20method.%20Hence%20the%20application%20deployment%20will%20be%20reported%20as%20successful%20even%20on%20failure.%3CBR%20%2F%3EUnfortunately%20the%20Office%20Deployment%20Tool%20doesn't%20remove%20previous%20installations%20of%20Office%20and%20neither%20does%20this%20new%20feature%20SCCM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Visio%20and%20Project%20are%20not%20supported%20for%20shared%20computer%20activation%20(SCA).%20SCCM%20will%20allow%20you%20to%20select%20SCA%20when%20selecting%20to%20install%20these%20products%20but%20then%20neither%20will%20be%20able%20to%20activate%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FUse-the-Office-Deployment-Tool-to-install-volume-licensed-editions-of-Visio-2016-and-Project-2016-82691bd7-a3d5-47ca-8d8a-0ee43ec2c01f%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FUse-the-Office-Deployment-Tool-to-install-volume-licensed-editions-of-Visio-2016-and-Project-2016-82691bd7-a3d5-47ca-8d8a-0ee43ec2c01f%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69671%22%20slang%3D%22en-US%22%3ERe%3A%20Deploying%20Office%20365%20ProPlus%3A%20MSI%20versions%20not%20removed%20and%20Visio%2FProject%20don't%20support%20SCA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69671%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kevin%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20haven't%20already%20done%20so%2C%20I'd%20appreciate%20it%20if%20you%20could%20report%20these%20issues%20on%20Connect%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fconnect.microsoft.com%2FConfigurationManagervnext%2Ffeedback%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fconnect.microsoft.com%2FConfigurationManagervnext%2Ffeedback%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3EYvette%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Senior Member

Two issues I ran into while using the new functionality of SCCM to deploy Office 365 ProPlus:

 

1. The setup will fail if any MSI version of Office products is installed. But the CTR setup will leave behind a registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\VersionToReport which SCCM uses for detection method. Hence the application deployment will be reported as successful even on failure.
Unfortunately the Office Deployment Tool doesn't remove previous installations of Office and neither does this new feature SCCM.

 

2. Visio and Project are not supported for shared computer activation (SCA). SCCM will allow you to select SCA when selecting to install these products but then neither will be able to activate:
https://support.office.com/en-us/article/Use-the-Office-Deployment-Tool-to-install-volume-licensed-e...

1 Reply
Highlighted

Hi Kevin

 

If you haven't already done so, I'd appreciate it if you could report these issues on Connect here: https://connect.microsoft.com/ConfigurationManagervnext/feedback.

 

Thanks

Yvette