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?

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answer Chosen by the Author

0
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
Answered 08/02/2016 by: sparky86
Fourth Degree Brown Belt

  • That worked Sparky, thanks.
Please log in to comment

Answers

Answer this question or Comment on this question for clarity

Share