CA Client Automation

Expand all | Collapse all

Office 365 Desktop Apps Deployment

Jump to Best Answer
  • 1.  Office 365 Desktop Apps Deployment

    Posted 08-20-2020 09:59 AM
    Can ITCM deploy the Office 365 apps? I'm aware these use click to run but was hoping I could create a central CIFS share that hosts the binaries but delivery the setup/conf via ITCM so I can report on where its deployed/missing and patch it as needed.


  • 2.  RE: Office 365 Desktop Apps Deployment
    Best Answer

    Broadcom Employee
    Posted 08-24-2020 09:54 AM

    When I tested delivery of office 365 I had all the flies in the SD Library. But there would be nothing to stop you creating a script that mapped a drive to a central location and invoked the setup.

     

     






  • 3.  RE: Office 365 Desktop Apps Deployment

    Posted 08-26-2020 04:36 PM
    Thanks Steve!  Makes sense as would enable DTS usage etc. also. Can I ask two other questions:

    1. Assume the individual apps deployed in this manner are detected by either the software delivery/inventory modules or the AM Sig scanner?
    2. What approach did you use for patching the apps?



  • 4.  RE: Office 365 Desktop Apps Deployment

    Broadcom Employee
    Posted 08-27-2020 03:12 AM

    I have not tried patching, but as with any thing MS I believe it best to use file shares as the setup program will work out which blocks of the files it needs rather than copying the complete file.

     






  • 5.  RE: Office 365 Desktop Apps Deployment

    Posted 2 days ago
    Edited by Patrick Wergen 2 days ago
    Hi Steve,
    I am trying to deploy Office 2019 same way. What is the correct variable in configuration.xml for "source path" pointing to sd library???
    thanks





  • 6.  RE: Office 365 Desktop Apps Deployment

    Broadcom Employee
    Posted 2 days ago

    Hi Patrick,

     

    This is the XML that I used.

     

    <Configuration>

      <Add SourcePath="" OfficeClientEdition="32" >

        <Product ID="O365ProPlusRetail">

          <Language ID="en-us" />

        </Product>

      </Add>

      <Updates Enabled="FALSE" UpdatePath="" />

      <Display Level="None" AcceptEULA="TRUE" />

      <Logging Level="Standard" Name="Office365Setup.log" Path="C:\windows\temp\" />

      <Property Name="AUTOACTIVATE" Value="1" />

    </Configuration>

     

    Best to run the setup from command line and only create the SD package once you have all the right setting for you particular environment.

     

    Rgds,

    Steve.

     






  • 7.  RE: Office 365 Desktop Apps Deployment

    Posted 2 days ago
    thank you Steve!
    I never tried with "empty" Source path.
    And also ClickToRun can not coexist next to older msi-Versions, so I had to add RemoveMSI option :-)