2 Replies Latest reply on Jun 4, 2018 12:32 PM by gillissj

    Identify Office Add-ins

    gillissj Rookie

      Hello,

       

      We are in the process of deploying Office 2016 to our devices and have seen a few issues with add-ins from time to time.  I am trying to determine the best way to identify add-ins that are installed for the office products, in an effort to minimize potential issues.  I may have missed it out there, or I'm just not searching correctly, but does anyone know or have a way on how to determine this? 

       

      Any help would be appreciated. 

       

      2016.3 SU3 is the version that we are on. 

       

      Thanks!

      Scott

        • 1. Re: Identify Office Add-ins
          Kayla.Culpepper SupportEmployee

          Hello!

           

          Thanks for posting to the Ivanti Community.

          Sorry that it seems no one has the answer to be able to assist you on this yet.  Did you manage to get any further information on this? Please share anything you deem useful and the community may be able to offer some help.

          If not then please do consider the other ways to engage with us to get assistance:

           

          https://community.ivanti.com/community/contact-support

           

           

          Kayla Culpepper
          Customer Service Coordinator
          Ivanti

          • 2. Re: Identify Office Add-ins
            gillissj Rookie

            Hi Kayla,

             

            We couldn't figure out a way to get what we needed done within the product itself.  I did come up with the following powershell script that we can deploy to machines and have it generate a .csv file to a share for review, as needed...

             

            --------------------------------------------------------------------------

            New-PSDrive -Name dest -Root \\sharesomewhere\Office_Addins -PSProvider FileSystem | Out-Null

             

            if ((gwmi win32_operatingsystem | select osarchitecture).osarchitecture -eq "64-bit")

            {

                $Path = ($env:computername+"_addins.csv")

             

                $searchScopes = "HKCU:\SOFTWARE\Microsoft\Office\Outlook\Addins","HKLM:\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins","HKCU:\SOFTWARE\Microsoft\Office\Excel\Addins","HKLM:\SOFTWARE\Wow6432Node\Microsoft\Office\Excel\Addins","HKCU:\SOFTWARE\Microsoft\Office\Word\Addins","HKLM:\SOFTWARE\Wow6432Node\Microsoft\Office\Word\Addins","HKCU:\SOFTWARE\Microsoft\Office\Access\Addins","HKLM:\SOFTWARE\Wow6432Node\Microsoft\Office\Access\Addins"

                $searchScopes | % {Get-ChildItem -Path $_ | % {Get-ItemProperty -Path $_.PSPath} | Select-Object @{n="Name";e={Split-Path $_.PSPath -leaf}},FriendlyName,Description} | Sort-Object -Unique -Property name | ConvertTo-Csv -NoTypeInformation | % {$_ -replace '"',''} | Out-File -encoding utf8 dest:\$Path

            }

             

            else

             

            {

                $Path = ($env:computername+"_addins.csv")

             

                $searchScopes = "HKCU:\SOFTWARE\Microsoft\Office\Outlook\Addins","HKLM:\SOFTWARE\Microsoft\Office\Outlook\Addins","HKCU:\SOFTWARE\Microsoft\Office\Excel\Addins","HKLM:\SOFTWARE\Microsoft\Office\Excel\Addins","HKCU:\SOFTWARE\Microsoft\Office\Word\Addins","HKLM:\SOFTWARE\Microsoft\Office\Word\Addins","HKCU:\SOFTWARE\Microsoft\Office\Access\Addins","HKLM:\SOFTWARE\Microsoft\Office\Access\Addins"

                $searchScopes | % {Get-ChildItem -Path $_ | % {Get-ItemProperty -Path $_.PSPath} | Select-Object @{n="Name";e={Split-Path $_.PSPath -leaf}},FriendlyName,Description} | Sort-Object -Unique -Property name | ConvertTo-Csv -NoTypeInformation | % {$_ -replace '"',''} | Out-File -encoding utf8 dest:\$Path

            }

             

            Remove-PSDrive -Name dest

            --------------------------------------------------------------------------

             

            If you deploy and run this using System, it will obviously not pick up any user specific add-ons (if any).  If run using the currently logged in user, it will pick them up. 

             

            I did open a case with support, but unfortunately we couldn't come up with a better solution other than the powershell above. 

             

            Thanks,

            Scott