7 Replies Latest reply on Jun 30, 2016 4:08 AM by phoffmann

    Office 2016 install never completes?

    Bubbaattech Apprentice

      We have a LDMS 9.5SP3 core and we are pushing out an Office2016 install to workstations.

      The install appears to succeed, it removes the old version (Office 2010 or 2013) and the new 2016 version are in the start menu and run ok.

      BUT

      The task still shows "active" on the core server with result = "Software distribution task has been started" and Return Code = "229392397". "setup.exe" is still running on the client, even after several reboots.

      The application log on the client shows the MSI installer has completed successfully.

      Does anyone have an idea how to solve?

      2016_installed.JPG

        • 1. Re: Office 2016 install never completes?
          synsa Specialist

          Hey, please check that you have the latest office deployment tool.  We have had issues "updating" a previous version of MS Office to v2016 i.e. installing Office 2016 on a device with a previous version.  What was working was scrubbing the device of any previous install and then installing Office 2016.

           

          There has been about 3 releases of the Office 2016 deployment tool in the last few weeks due to issues concerning updating previous installs.  It appeared the install process was attempting to contact the Microsoft CDN even when told to use files locally or internal share.  We have seen the same issue as you and currently testing the latest ODT with our fingers crossed it fixes the problem.

          • 2. Re: Office 2016 install never completes?
            JoeDrwiega SupportEmployee

            In past deployments I had this issue and it was a pop-up telling the user it was complete and to reboot. I would open the Office deployment tool and verify it is completely silent. Also be sure that you have the setting set in the LANDESK deployment package that the action for a reboot is needed.

            • 3. Re: Office 2016 install never completes?
              Apprentice

              Hi All,

               

              I am meeting the same problem. The setup.exe continue to run on the task manager even after the installation finishes.  I am already using the latest ODT here, https://www.microsoft.com/en-us/download/details.aspx?id=49117.

               

              I have also set the LDMS delivery method to reboot after installation. In the office config.xml, I have put the display level as below,

               

              <Display Level="none" CompletionNotice="no" AcceptEULA="True" />

               

              Not sure if I still miss anything, any other flag you guys have set to make it work? Thanks!

              • 4. Re: Office 2016 install never completes?
                saeidans Apprentice

                Hello im_Iwyab

                 

                Did you find a solution to your problem yet?

                could you share it if you did?

                thanks

                • 5. Re: Office 2016 install never completes?
                  Frank Wils ITSMMVPGroup

                  Apparantly the answer was in the Config.XML...

                   

                  Make sure you have it set with these options:

                  <Display Level="none" CompletionNotice="no" AcceptEULA="True" />

                   

                  Frank

                  • 6. Re: Office 2016 install never completes?
                    Apprentice

                    We are not sure exact reason for this. But I tried if I use a batch file, copy the whole source to the user computer and run setup there, the office setup will end normally. On the other hand, if I use LANDESK's default mechanism to copy files, it never complete. Thus finally, I use a more "stupid way" and use a batch to copy source to user machine and run setup from there.

                    • 7. Re: Office 2016 install never completes?
                      phoffmann SupportEmployee

                      im_lwyab wrote:

                       

                      We are not sure exact reason for this. But I tried if I use a batch file, copy the whole source to the user computer and run setup there, the office setup will end normally. On the other hand, if I use LANDESK's default mechanism to copy files, it never complete. Thus finally, I use a more "stupid way" and use a batch to copy source to user machine and run setup from there.

                      In situations like this, it's usually down to "user context" - and often GPO's or such.

                       

                      Remember, generally LANDesk will install as "Local System" (you can specify a specific user if you want). Over the years, we've seen weird environments & weird GPO's have impact on Local System trying to do things / installs, which "full local admin accounts" didn't run into. Certain software installs also won't succeed with "Local System" and REQUIRE a full-on "Local Admin" context to launch them (I ran into this first with some 3D-modelling software).

                       

                      So while "Local System" is 98% like a "local admin" it's not 100% ... (thanks Microsoft).

                       

                      So there's that to watch out for (which is one of the many reasons why we give you the ability to specify a user-context to install stuff in).

                       

                      Hope that helps a bit.