<div>
<div class="content wysiwyg-content">
My company is running an Office 365 backend. &nbsp;Most of our users are still on Office 2007, but some have been migrated up to 2010. &nbsp;We are now planning to do a Office 2013 rollout following our 365 tenant upgrade in a few months. &nbsp;Management wants to push 2013 out in parallel to the users current office installations, thinking that they will cut back on compatibility issues with other apps.<br />
My question is: &nbsp;Next year when they come to us and ask that we push an uninstall for the older versions to leave only the 2013 on people's system, Will 2013 need to have it's dlls or anything repaired before it will function normally again?
</div>
</div>


My company is running an Office 365 backend.  Most of our users are still on Office 2007, but some have been migrated up to 2010.  We are now planning to do a Office 2013 rollout following our 365 tenant upgrade in a few months.  Management wants to push 2013 out in parallel to the users current office installations, thinking that they will cut back on compatibility issues with other apps.
My question is:  Next year when they come to us and ask that we push an uninstall for the older versions to leave only the 2013 on people's system, Will 2013 need to have it's dlls or anything repaired before it will function normally again?

Running Parallel Office installations

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.