Jump to content


Aburns2

Supersedence and Test Collections

Recommended Posts

Currently we are planning a project to roll out Office 2013 to our current environment, which is currently running almost homogeneous Office 2010. The issue we is that we have a mixed environment of 32 bit and 64 bit Office installs.

 

The way I'm planning to do this is through the supersedence feature in SCCM 2012 r2 with cu1. My question is rather simple. If I specify a supersedence relationship in SCCM, will SCCM replace all copies of Office 2010 across the site regardless of collections and current deployments? Or will SCCM limit the upgrades to solely those collections that have the Office 2010 application deployed to them? The reason I'm asking is because 1) I would like to test the deployment in a test collection and 2) I have select collections that have to remain on Office 2010.

 

Thank you.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.