Support Tip: Deploying Visio and Project as part of your Office Pro Plus Deployment

Published Jun 18 2019 04:50 PM 9,203 Views

As we continue driving improvements to the Office Pro Plus deployment experience in Intune, we were recently alerted to a conflicting policy scenario. We’re working to adjust the experience, but know that it may take a few sprints to reach resolution.

 

If a user is targeted with more than one Office Pro Plus policy, only one of those will get delivered to an end users' device. Here is one such scenario you may have seen. A group of users are targeted Office Pro Plus as a required install on the device. Now, you want to make Visio and/or Project available to a subset of those users as an optional install. Install can only happen to one of those suites; in this case the required install only. IT Admins and end users may see error code 0x87D1041E in their respective portals.

 

Short term, you can bundle Office Pro Plus and Visio/Project as required in one policy, which will then ensure that Visio and Project are available for your end users. Alternatively you can create a policy to make Office Pro Plus with Visio/Project as available. However, keep in mind that all Office apps will need to be closed for your end user to go download Visio or Project from the Company Portal.

 

We’ll update this post and What’s New when there’s an updated experience released.

11 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-701795%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701795%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20we%20continue%20driving%20improvements%20to%20the%20Office%20Pro%20Plus%20deployment%20experience%20in%20Intune%2C%20we%20were%20recently%20alerted%20to%20a%20conflicting%20policy%20scenario.%20We%E2%80%99re%20working%20to%20adjust%20the%20experience%2C%20but%20know%20that%20it%20may%20take%20a%20few%20sprints%20to%20reach%20resolution.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20a%20user%20is%20targeted%20with%20more%20than%20one%20Office%20Pro%20Plus%20policy%2C%20only%20one%20of%20those%20will%20get%20delivered%20to%20an%20end%20users'%20device.%20Here%20is%20one%20such%20scenario%20you%20may%20have%20seen.%20A%20group%20of%20users%20are%20targeted%20Office%20Pro%20Plus%20as%20a%20required%20install%20on%20the%20device.%20Now%2C%20you%20want%20to%20make%20Visio%20and%2For%20Project%20available%20to%20a%20subset%20of%20those%20users%20as%20an%20optional%20install.%20Install%20can%20only%20happen%20to%20one%20of%20those%20suites%3B%20in%20this%20case%20the%20required%20install%20only.%20IT%20Admins%20and%20end%20users%20may%20see%20error%20code%200x87D1041E%20in%20their%20respective%20portals.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22color%3A%20%23333333%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22color%3A%20%23333333%3B%22%3EShort%20term%2C%20you%20can%20bundle%20Office%20Pro%20Plus%20and%20Visio%2FProject%20as%20required%20in%20one%20policy%2C%20which%20will%20then%20ensure%20that%20Visio%20and%20Project%20are%20available%20for%20your%20end%20users.%20Alternatively%20you%20can%20create%20a%20policy%20to%20make%20Office%20Pro%20Plus%20with%20Visio%2FProject%20as%20available.%20However%2C%20keep%20in%20mind%20that%20all%20Office%20apps%20will%20need%20to%20be%20closed%20for%20your%20end%20user%20to%20go%20download%20Visio%20or%20Project%20from%20the%20Company%20Portal.%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20%26amp%3Bquot%3B%20color%3A%20%23333333%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWe%E2%80%99ll%20update%20this%20post%20and%20What%E2%80%99s%20New%20when%20there%E2%80%99s%20an%20updated%20experience%20released.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-701795%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20a%20lot%20of%20customers%20have%20run%20into%20this%2C%20but%20we%20figured%20it%20was%20worth%20a%20post%20just%20in%20case%20you%20were%20deploying%20Visio%20and%20Project!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-701795%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EProject%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESupport%20Tip%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVisio%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-705599%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-705599%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20took%20you%20guys%20so%20long%3F%20This%20is%20such%20an%20inconvenience%20for%20large%20organisations%20where%20Office%20is%20distributed%20to%20large%20set%20of%20users%20as%20a%20Core%20application%20Vs%20Project%20%26amp%3B%20Visio%20to%20small%20set%20of%20users.%20If%20Office%26nbsp%3BPro%20Plus%20is%20already%20installed%20on%20the%20device%2C%20are%20you%20guys%20advising%20to%20uninstall%20Office%20ProPlus%26nbsp%3Band%20reinstall%20Office%20ProPlus%20%2B%20Visio%3F%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-706158%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-706158%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20were%20told%20by%20Microsoft%20legal%2Fcompliance%20that%20we%20could%20not%20deploy%20O365%20w%2F%20Visio%20and%20Project%20to%20all%20of%20our%20users.%20Even%20though%20it%20would%20be%20in%20limited%20functionality%20mode%2C%20they%20said%20it%20would%20be%20against%20EULA%20to%20have%20them%20installed%20on%20a%20non%20licensed%20users%20PC.%20Has%20this%20POV%20changed%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-716025%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-716025%22%20slang%3D%22en-US%22%3E%3CP%3EI%E2%80%99ve%20found%20when%20we%20deploy%20Office%20Pro%20Plus%20to%20our%20M365B%20users%2C%20the%20licensing%20eventually%20syncs%20up%20and%20they%20would%20have%20Office%20365%20Business.%20%26nbsp%3BHowever%2C%20when%20we%20add%20MS%20Project%20to%20the%20install%20package%2C%20the%20Office%20365%20Business%20licensing%20changes%20back%20to%20ProPlus%20thus%20causing%20an%20invalid%20licensing%20situation%20since%20the%20users%20have%20M365%20Business%20which%20doesn%E2%80%99t%20come%20with%20ProPlus.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThw%20workaround%20has%20been%20to%20uninstall%20all%20instances%20manually%20including%20running%20some%20cscript%20to%20remove%20invalid%20keys.%20%26nbsp%3BReboot.%20%26nbsp%3BInstall%20o365%20from%20the%20portal(manually)%20and%20then%20do%20the%20same%20manual%20step%20for%20MS%20Project..%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%E2%80%98We%E2%80%99ve%20since%20disabled%20the%20intune%20deployment%20for%20Office%20which%20is%20a%20shame%20because%20it%20used%20to%20work%20great!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-723313%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-723313%22%20slang%3D%22en-US%22%3E%3CP%3E%E2%80%A6%20and%20now%20we%20have%20a%20new%20issue...TEAMS...missing%20from%20the%20Office%20Pro%20Plus%20deployment.%20For%20Office%20Pro%20Plus%2C%20the%20update%20channel%20was%20set%20to%20%22semi-annual%22%20and%20looks%20like%20this%20is%20causing%26nbsp%3BTEAMS%26nbsp%3Bfailure%20to%20install%20along%20with%20Office.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGive%20me%20few%20more%20days...and%20I'm%20pretty%20sure%20I%20will%20come%20back%20with%20few%20more%20issues.%20Thank%20you%26nbsp%3BMicrosoft%20Team%2Fs.%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-810920%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-810920%22%20slang%3D%22en-US%22%3E%3CP%3E2%20months%20past%20-%20any%20news%20on%20this%20issue%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226779%22%20target%3D%22_blank%22%3E%40Intune%20Support%20Team%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-869618%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-869618%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20you%20do%20is%20create%20an%20Office%20%2B%20Visio%20group%20that%20includes%20Office%20and%20Vision%20and%20then%20create%20an%20Exclude%20with%20that%20group%20on%20your%20Normal%20just%20Office%20package.%20This%20has%20always%20been%20working%20as%20designed%20and%20is%20very%20annoying.%20It%20should%20be%20additive.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1501271%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1501271%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20the%20same%20issue%20here.%20When%20do%20you%20fix%20this%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226779%22%20target%3D%22_blank%22%3E%40Intune%20Support%20Team%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1965356%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1965356%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20*still*%20isnt%20fixed%3F!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2129309%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Deploying%20Visio%20and%20Project%20as%20part%20of%20your%20Office%20Pro%20Plus%20Deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2129309%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20ran%20into%20this%20today%20trying%20to%20setup%20a%20separate%20Visio%20install%20policy.%26nbsp%3B%20I%20ran%20across%20this%20recent%20article%20and%20my%20initial%20testing%20has%20been%20successful.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fosddeployment.dk%2F2021%2F01%2F06%2Fdeploy-visio-or-project-with-intune-to-users-with-microsoft-365-apps-already-installed%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EDeploy%20Visio%20or%20Project%20with%20Intune%20to%20users%20with%20Microsoft%20365%20apps%20already%20installed.%20%E2%80%93%20Mobile-First%20Cloud-First%20(osddeployment.dk)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jun 18 2019 04:50 PM
Updated by: