locked
Software deployment RRS feed

  • Question

  • Hi,

    We are looking to deploy Office 2016 application and distribute updates directly to client (so Office installations have the latest software updates). Refer to article

    With the deployment method of Distributing updates locally, how do we determine what/which Office updates are necessary to be included in the local installations source?

    Let's say if we create the deployment package today, do we grab every single Office 2016 updates available? and also Microsoft release updates every month, do we have to continue adding these new updates into the local installation source?

    Thank you


    Best Regards,

    Tuesday, October 18, 2016 5:49 AM

Answers

  • 1. That's always a challenge with Office -- all versions -- and so I don't have a good answer for you there. Not sure if there is one. There is script for Office 2003 that many use to extract the MSPs from existing installations. Not sure if there is an equivalent for 2016 or not.

    2. I've never seen an enterprise use this method to update existing installations of Office. I only work in ConfigMgr shops (which is just about everyone in existence) and so only see Software Updates used to update existing installations.

    3. That's up to you. It's probably not imperative on a continuous basis but keeping it somewhat up to date will make new deployments go much faster.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Ant_G Tuesday, October 25, 2016 8:11 AM
    • Marked as answer by BlueBerries Monday, October 31, 2016 2:42 AM
    Thursday, October 20, 2016 12:41 PM

All replies

  • Let's say if we create the deployment package today, do we grab every single Office 2016 updates available?


    Basically yes (exluding superseded ones).

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, October 18, 2016 6:32 AM
  • Concur with Torsten. It's no different than managing any other updates in ConfigMgr.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, October 18, 2016 12:48 PM
  • Thanksss.

    When new updates releases in the future month, using the 'distributing updates locally' technique - does it mean we need to keep updating (every month) the local installation source (by removing the superseded updates and put new updates in)?

    We also push out updates via Windows Installer updates (which contain Office 2016 as well as other Microsoft updates).

    Does it mean we have to exclude Office 2016 updates via Windows Installer updates?

    Hi Microsoft, Is there a detail document specifying how to use the 'distributing updates locally' method? - How does Windows Installer updates work (in conjunction)?

    Thank you


    Best Regards,

    Wednesday, October 19, 2016 12:59 AM
  • Just to validate, are you using software updates within ConfigMgr to update your Office 365 installations?

    If so, then there's no reason to distribute updates any other way.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 19, 2016 1:58 AM
  • Hi Jason,

    It is not for Office 365 applications.

    Our environment will need two different version of Office, office 2013 and office 2016 application to be deployed via SCCM.

    Thank you


    Best Regards,


    • Edited by BlueBerries Wednesday, October 19, 2016 6:00 AM
    Wednesday, October 19, 2016 6:00 AM
  • OK, same question though, are you pushing out these updates using Software Updates?

    If so, then there's still nothing else to do.

    To make initial deployments of Office easier, you can include the MSPs for the updates in the Update folder of the installation files, but this is not required.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 19, 2016 3:13 PM
  • Hi Jason,

    This is what I am trying to find out.

    We want to deploy Office with updates - I believe this method is called "Distributing updates locally". & currently we using Software Updates to push out monthly Microsoft patches out monthly.

    Questions

    1. How do we determine which Office 2016 updates to be included in the "Source installation folder"?

    2. If we choose to deploy Office with Distributing updates locally, does that mean we can redundant monthly software updates / how do they work in conjunction?

    3. and do we keep updating the "Source installation folder" updated every month? or .... ?

    Is there a details documents specifying how to implement this?

    Thank you


    Best Regards,

    Thursday, October 20, 2016 3:39 AM
  • 1. That's always a challenge with Office -- all versions -- and so I don't have a good answer for you there. Not sure if there is one. There is script for Office 2003 that many use to extract the MSPs from existing installations. Not sure if there is an equivalent for 2016 or not.

    2. I've never seen an enterprise use this method to update existing installations of Office. I only work in ConfigMgr shops (which is just about everyone in existence) and so only see Software Updates used to update existing installations.

    3. That's up to you. It's probably not imperative on a continuous basis but keeping it somewhat up to date will make new deployments go much faster.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Ant_G Tuesday, October 25, 2016 8:11 AM
    • Marked as answer by BlueBerries Monday, October 31, 2016 2:42 AM
    Thursday, October 20, 2016 12:41 PM