Deploying Visio Pro and Project Pro 365

All replies

• 

  

  1

  Sign in to vote

  Hi

  Here is my config.xml and it is working for me:

  <Configuration>
  <Add OfficeClientEdition="32" Channel="Current" >
  <Product ID="VisioProRetail" >
   <Language ID="en-us" />
  </Product>
  <Product ID="O365ProPlusRetail" >
   <Language ID="en-us" />
  </Product>
  </Add>
   <Updates Enabled="TRUE" Channel="Current" />
   <Display Level="None" AcceptEULA="True" />
   <Property Name="PinIconsToTaskbar" Value="TRUE" />
   <Property Name="AUTOACTIVATE" Value="1" />
   <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
   <Property Name="SharedComputerLicensing" Value="0" />
   <Logging Level="Off" />
  </Configuration>

  
  

  Kind regards

  Per Larsen
  Microsoft MVP - Enterprise Mobility
  Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
  If this post is helpful please vote it as Helpful or click Mark for answer.

  • Proposed as answer by Frank Dong Monday, February 13, 2017 2:11 AM
  • Marked as answer by Brandon.M Thursday, February 16, 2017 5:32 PM

  Sunday, February 12, 2017 8:29 AM
• 

  

  0

  Sign in to vote

  Please try Per Larsen's solution. 

  In case it can't help you, I suggest that you can try to post in Office forum as it's not a real Configuration Manager question. Hope for your understanding.

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  Monday, February 13, 2017 2:16 AM
• 

  

  0

  Sign in to vote

  That worked for me. I was hoping that I could build a relatively small package that only installed Visio and Project individually. That way, they can be installed later on a computer that already has Office 365 ProPlus, and not have to download/configure the full Office 365 suite. I guess that is not possible with how the Office Deployment Tool works.

  Monday, February 13, 2017 7:13 PM
• 

  

  0

  Sign in to vote

  Has it been confirmed that it's not possible to deploy Visio on it's own, that you have to install the full Office Suite and include Visio?

  I tried from within SCCM \ Office 365 management but you can't just select Visio without any Office components.

  If you manually create an xml file specifying only to install visio it will remove all of the other office components.

  
  

  • Edited by andrewjohnporter Thursday, May 31, 2018 2:30 PM

  Wednesday, April 18, 2018 4:26 PM
• 

  

  1

  Sign in to vote

  Has it been confirmed that it's not possible to deploy Visio on it's own, that you have to install the full Office Suite and include Visio?

  I tried from within SCCM \ Office 365 management but you can't just select Visio without any Office components

  As far as I know, there are only two ways to install Office ProPlus 2016:

  1) Office 365 Click-to-Run (subscription)
  2) Office 2016 ProPlus (standalone/volume licensing)

  The above two solutions cannot be ran simultaneously. It is possible and I was able to install a standalone version of Visio/Project 2016 in a CTR environment, it was very difficult and will add headaches for long-term support. Microsoft does not support it either, so best to avoid.

  Note that if a user has O365 CTR and wants Visio, you must re-installed the ENTIRE O365 suite and include Visio in the suite - same can be said for Project. This is ~1.5GB and creates a lot of problems for long-term support.

  This was my solution:

  1) Package O365 CTR w/ Visio+Project 2016
  2) Install this package on ALL devices
  3) Visio+Project 2016 do NOT function unless you have been activated within O365 and have had these items added to your subscription
  4) End users can submit requests to activate either Visio or Project, which is already fully patched and on their device

  Pro's to my method: No more Office deployments, you don't need an O365 CTR package, O365+Visio, O365+Project, etc., all devices are current targeted channel so they're fully updated and patched at all times, if you have remote sites and bandwidth is a concern this eliminates deploying 1.5GB over the internet
  Con's to my method: Every user now has Project and Visio. They will try and open these and they will receive the "this product has not yet been activated for your account" warning. If their coworkers have this software + they get the prompt, they will be calling the Help Desk for help. You will see more requests for Visio/Project. You can mitigate this with discussing your entitlements, business communications, etc.

  If I am wrong, someone feel free to correct me and educate me.

  Thursday, May 31, 2018 2:22 PM
• 

  

  1

  Sign in to vote

  Has it been confirmed that it's not possible to deploy Visio on it's own, that you have to install the full Office Suite and include Visio?

  I tried from within SCCM \ Office 365 management but you can't just select Visio without any Office components

  As far as I know, there are only two ways to install Office ProPlus 2016:

  1) Office 365 Click-to-Run (subscription)
  2) Office 2016 ProPlus (standalone/volume licensing)

  The above two solutions cannot be ran simultaneously. It is possible and I was able to install a standalone version of Visio/Project 2016 in a CTR environment, it was very difficult and will add headaches for long-term support. Microsoft does not support it either, so best to avoid.

  Note that if a user has O365 CTR and wants Visio, you must re-installed the ENTIRE O365 suite and include Visio in the suite - same can be said for Project. This is ~1.5GB and creates a lot of problems for long-term support.

  This was my solution:

  1) Package O365 CTR w/ Visio+Project 2016
  2) Install this package on ALL devices
  3) Visio+Project 2016 do NOT function unless you have been activated within O365 and have had these items added to your subscription
  4) End users can submit requests to activate either Visio or Project, which is already fully patched and on their device

  Pro's to my method: No more Office deployments, you don't need an O365 CTR package, O365+Visio, O365+Project, etc., all devices are current targeted channel so they're fully updated and patched at all times, if you have remote sites and bandwidth is a concern this eliminates deploying 1.5GB over the internet
  Con's to my method: Every user now has Project and Visio. They will try and open these and they will receive the "this product has not yet been activated for your account" warning. If their coworkers have this software + they get the prompt, they will be calling the Help Desk for help. You will see more requests for Visio/Project. You can mitigate this with discussing your entitlements, business communications, etc.

  If I am wrong, someone feel free to correct me and educate me.

  I wanted to offer an update to anyone who finds this.

  It appears you can install just Visio or just Project - but with a caveat. The version of Visio or Project you're installing must match the version of O365 on the PC that you're running the installation on. The problem for me, is that I have over 60 versions of O365 in my environment - and this changes daily. A previous architect thought deploying patches to thousands of  computers was a stupid idea, so every device is in the Monthly Channel - so end users are updating at their leisure.

  My solution is to either stick my original plan (in the post I am quoting) or create 60+ different XML files with a <ver=X> in the file for installation. My installer would first have to query the version on the device, and then use the corresponding xml file. This would also require me to manage these files on a monthly or weekly basis.

  Since I want to migrate users to the SAC channel, I am sticking to my original plan which will not only put devices into SAC, but also give them both products (vis/proj) that we can be used upon activation.

  Tuesday, July 17, 2018 5:36 PM