/build/static/layout/Breadcrumb_cap_w.png

Microsoft Office Version Change

Hello,

I am working on changing all of our remaining MS Office 2010 to MS Office 2013. I have read a lot of the QA questions pertaining to this, but ultimately the recommended methods have not worked (the scripts get to a certain point and nothing happens). What I want to do is install 2013 then upon success have it remove the 2010 so the computer can maintain existing settings for the new version. Anyone have thoughts on how to accomplish this? 


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Kiyolaka 2 years ago
Third Degree Green Belt
0

When Installing MS office you always want to remove the existing install THEN install the new version, otherwise you risk corrupting the newer version as removing the old version afterwards carries the chance of removing a shared file/component the newer version is dependant on. Not only that you absolutely cannot install 32 or 64-bit office if there is the opposite architecture presently installed (I.E. the install for 64-bit office would abort if you had 32-bit office components present)

Are your deploying MS office as a MSI or the click to run version? Also are you trying to go from one architecture to another (i.e. from office 2010 32-bit to 2013 64-bit?)


ALSO, Why 2013, it goes EOS April 11, 2023?


Posted by: ODdOn3 2 years ago
Senior White Belt
0

Kiyolaka

I was hoping 2013 before 2010 would retain settings, but if I have to go the other route and UI then install that works too. As for the architecture I was going to stick with 32bit. I can double check that I am using the MSI but I'm pretty sure that was correct. As for the 2013, it's all about available licensing and removing 2010 from the environment until all of it can be migrated to 365.

Thanks :) 

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ