7 Replies Latest reply on Mar 1, 2019 7:11 AM by LukaszDziwisz

    Office 2016 reconfiguring each time it opens

    LukaszDziwisz Enthusiast

      Hello Everyone,

       

      Just wanted to see if anyone runs into a problem where provisioning an application causes Microsoft Office 2016 to reconfigure itself. I've been facing this issue with multiple application like for example Infopath 2013. Once provisioned to user it is causing Microsoft Office  to reconfigure itself each time that Microsoft Access or Microsoft Word is opened. When Outlook or Excel is opened it is fine.  Another example is Xperience application which is one of our inhouse applications. Once pushed to the user it is causing only Word to reconfigure every time. And another one is causing Outlook to create and open a local copy of OST file instead of connecting to Exchange?

       

      The packaging machines we used are clones on image (not sure if at the same update level though). We tried provisioning on PM with Office 2016 and without and getting the same result.

       

      SO I'm wondering if there is any global configuration like for example snapvol.cfg where we could exclude/include something that would prevent it from happening? Any help would be much appreciated.

        • 1. Re: Office 2016 reconfiguring each time it opens
          sjesse Master
          vExpert

          Its probably the order the appstacks are getting attached in, there is a common folder office uses, and at least for infopath its probably overwriting it. Its supposed to work with project and visio in seperate appstacks, but I'm not sure about the other ones. See if you can combine infopath in the same appstack.I don't think exclusions will work because they are working with at least some paths in common.

          • 2. Re: Office 2016 reconfiguring each time it opens
            LukaszDziwisz Enthusiast

            Yeah I was thinking about it but what we are doing is actually we put Office 2016 on Master Image and created one for Visio and Project.

            • 3. Re: Office 2016 reconfiguring each time it opens
              oliober Novice

              Hi

              We have the same problem with word.

              Every time, when Packaging Machine is not equal to the Parent Machine (Windows Updates etc.) the issue with the office repair occurs.

              Now we use a Windoww only Packaging Machine without Office, Runtimes etc.

              Until now, this works for us.

              • 4. Re: Office 2016 reconfiguring each time it opens
                LukaszDziwisz Enthusiast

                Yeah that is probably good idea however in some cases we need need office as a prerequisite

                • 5. Re: Office 2016 reconfiguring each time it opens
                  LukaszDziwisz Enthusiast

                  SO would you all agree that the best way is to update your Master image with any updates necessary, seal it and provision to the pool. Then clone it, remove all of the agents besides appvolumes and snapshot it to use as a PM? Do you guys unjoin it from the domain, rename and join again? Our master image is joined to the domain and PMs are too. Also If provisioning is successful and next set of updates comes around what do you do with existing appstacks? Redo them, or is it only when new appstack is created?

                  • 6. Re: Office 2016 reconfiguring each time it opens
                    Ray_handels Master
                    Community WarriorsvExpert
                    SO would you all agree that the best way is to update your Master image with any updates necessary, seal it and provision to the pool. Then clone it, remove all of the agents besides appvolumes and snapshot it to use as a PM?

                    Yes. Not quite sure if documentation states this but it is noted as being best practice.

                     

                    Do you guys unjoin it from the domain, rename and join again?

                    Yes. I found out that not joining the machine to the domain I was unable to attach appstacks for provisioning. I would suggest using a local administrator account for packaging, try to avoid using a domain account. Also make sure no policies are attached to the OU that your PM is in. These could be applied during the appstack creation proces and you could end up with all kinds of crap in the appstack.

                     

                    Our master image is joined to the domain and PMs are too. Also If provisioning is successful and next set of updates comes around what do you do with existing appstacks? Redo them, or is it only when new appstack is created?

                    No we don;t because this would take up waaay to much time. Support does seem to throw out that option pretty offen but most of the times the appstack still work, even with a newer version of Appvolumes. We found out that if an appstack stopped working it had an issue in the firts place so recreating would be our best option. Most of the time the basic appstack keep on working.

                    We even tested with W7 appstacks on W10 machines (it's a while back but still) and even 70 to 80% of those worked. Do not do this for production by the way, just making an observation here

                    1 person found this helpful
                    • 7. Re: Office 2016 reconfiguring each time it opens
                      LukaszDziwisz Enthusiast

                      Thank  you for that information. I guess one thing I was doing different is that once I had PMs setup I've been updating them with patches whenever Image was updated to keep it the same but I see that other admins delete their PMs and repeat the procedure after Image is updated.