Trying to allow users an optional upgrade from O365 2013 to O365 2016 using SCCM 2012 R2 SP1

I’m trying to come up with a way to allow my users to upgrade O365 2013 to O365 2016 on an “as you have time” basis using SCCM 2012 R2 SP1. So I created an application for O365 2016 Install, which works fine as long as O365 2013 isn’t present. And I created an application for O365 2013 Uninstall.

The Uninstall application I scheduled as available right away but gave it a deadline of 30 days. It seems that when I deploy that it still goes in on its own time frame. I checked the client the next day to see if both apps were available to run and the Install was but the Uninstall showed up under Installed Apps as successfully installed.

Any idea what I might be doing wrong or if there’s a better way to do this?

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: sparky86 5 years ago
Fourth Degree Brown Belt

Top Answer

i would use supersedence on the 2016 application to remove 2013 in sccm and publish 2016 out as available but not required. that will allow the users to run at their time of choosing and the supersedence will remove 2013 as part of the 2016 install

  • That worked Sparky, thanks. - rsgdmn 5 years ago
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