CA Client Automation

  • 1.  Office 2016

    Posted Feb 03, 2016 05:15 PM

    I'm working on creating a package for Office 2016.  I used the greenbook for Office 2007/2010/2013 packages.  Is there any documentation or tips for Office 2016?



  • 2.  Re: Office 2016

    Posted Feb 04, 2016 11:29 AM

    Hi Bill,

     

    I don't know about the strings you'll have to use, but since the package will be big, I'd recommend you to put the installation files into a network directory ("repository") in wich all computers have access to, than deploy a smaller package that redirects to the installation from the "repository".

     

    A few years ago, this was the best solution I found for deploying a package of 800mb+ to more than 10000 computers.

     

    Regards,

    Marlon



  • 3.  Re: Office 2016

    Posted Feb 04, 2016 03:36 PM

    Marlon,

     

    While that's a good idea, I'm looking for advice for creating MS Office 2016 packages.  Has anyone tried to follow the same instructions provided in the CA Greenbook to install 2007 for Office 2016?



  • 4.  Re: Office 2016

    Broadcom Employee
    Posted Feb 05, 2016 06:32 AM

    Hi Bill

     

    I have not tested the GB with office 2016 but I believe the process will be the same

     

    Rich



  • 5.  Re: Office 2016

    Community Manager
    Posted Feb 04, 2016 03:29 PM

    Bill, did Marlon's suggestion work for you?



  • 6.  Re: Office 2016

    Posted Feb 08, 2016 08:56 AM

    Hi Bill

    I have seen the responses and I wanted to ask when you followed the guide for office 2013 for 2016 did you have any issues deploying that ?

    Thanks

    Joe



  • 7.  Re: Office 2016

    Posted Feb 11, 2016 05:48 PM

    I have an installation procedure but am trying to configure an uninstall procedure (external)



  • 8.  Re: Office 2016
    Best Answer

    Posted Feb 12, 2016 12:48 PM

    I created a Microsoft Office 2016 package using the same method as stated for Office 2007 in the CA Greenbook.  Here is an exception:

     

    The uninstall is different.

     

    To uninstall I added an external procedure to call the setup.exe with the parameters referencing the silent install in the custom config.xml I created.

     

    External EXE = C:\Program Files\Common Files\Microsoft Shared\OFFICE16\Office Setup Controller\setup.exe

    Parameters = /uninstall PROPLUS /config "C:\Program Files\Common Files\Microsoft Shared\OFFICE16\Office Setup Controller\config.xml"  $#ec:1641 $#ec:0

     

    I created the config.xml and used the Office Admin setup tool to have the Office install copy it as an added file.  The advantage of creating it as an external procedure is that SD will not have to distribute the MS Office package (800+ MB) in order to perform the uninstall.