Rollout Office 2013

Hello together,

we have to do an Office 2013 ProPlus rollout on 4000 clients. We will use SCCM for the rollout.

Current Situation:

our Company was growing a lot in the last view years and our Client standard is not the best.

At the Moment we have diffrent Office products installed on the Computers.

Office 2007 / 2010 / 2013 Stdandard / ProPlus / and other suites.

Standalone Outlook 2007 / 2010 / 2013

My idea was the fowllowing:

Push our new Office 2013 application to all Computers without removing the curent installations.

With AppBlocker I will disable all 2013 programs.

Then we will allow to use 2013 and block older applications with the GPO. And add the GPO to the computers in waves.

Any suggestions or experiences?

June 10th, 2015 8:04am

I think thats a poor idea and will just cause more mess!

Why not use the different versions of OffScrub to remove all existing office installations as part of your rollout?

Free Windows Admin Tool Kit Click here and download it now
June 10th, 2015 8:20am

While it is possible to install 2013 side by side with those other versions and you may be able to block it with Applocker, there can be some issues with that approach. Namely patching, particularly attempting to patch multiple versions on the same system.  See also http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/installation-of-office-2007-2010-and-2013-on-same/ee5deec4-a0ab-497a-9178-077d811186a8

A better option is to deploy Office 365 ProPlus as it uses Click To Run technology, and is by default virtualized.  It will not affect the other Office version install, and as it has a different update model patching will not be an issue.  Office 365 ProPlus features are virtually the same as 2013 and fully supports add-ins.

See

Why would I choose Office 365 ProPlus over Office Professional Plus 2013?

https://products.office.com/en-us/business/office-365-proplus-business-software

You can contact me offline at info@migratellc.com

June 10th, 2015 7:29pm

Your advice is incorrect.

Installing Office 365 alongside Office 2013 is a bad idea and totally unsupported by Microsoft.

Their advice? Use OffScrub and remove previous versions.


Free Windows Admin Tool Kit Click here and download it now
June 11th, 2015 3:37pm

Your advice is incorrect.

Installing Office 365 alongside Office 2013 is a bad idea and totally unsupported by Microsoft.

Their advice? Use OffScrub and remove previous versions.


@Peter, I read the suggestion from @HumbleUser1, differently. It seems to me that the suggestion is to install C2R alongside the older/existing Office products (although that is only a partial solution since Strahle_fz mentioned current mix includes some O2013)

I agree with your suggestion, I always prefer a "clean" transition, and I loathe SxS co-existence for Office products, it's just too painful to manage patching and the interoperability of stuff.

Migrating Office, when you have ConfigMgr available, can be a breeze, if you take the time to create the relevant detection logic, and don't rely on the Office setup.exe to do removal (since setup.exe can't deal with an existing broken/damaged installation very well at all ;)

June 11th, 2015 5:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics