We're trying to upgrade clients from O365 ProPlus Click-to-Run 2013 to O365 ProPlus Click-to-Run 2016 using SCCM 2012 R2 SP1. Our deployment works flawlessly if we deploy to a machine that hasn't had a previous version installed. However, the deployment fails for the machines that have 2013 already installed. Our 2013 deployment was done prior to us having SCCM, we used Group Policy to push it from a network share.
We consulted Microsoft and were told that upgrading from 2013 to 2016 using SCCM isn't really supported and that we would need to do an uninstall of 2013 first. Is there a way to make an uninstall of 2013 along with the install of 2016 available to users in Software Center so they can uninstall 2013 and then install 2016 without needing admin permissions? Or any other work around that anyone else has come up with?
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Microsoft Office Picture Manager was included in Office 2003, 2007, and 2010, but not in Office 2013. Users had hopes that it would be in Office 2016/Office 365, but it is not. Fortunately, the same zero-cost technique that works to install it with …
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel.
Part 1 of this series discussed basic error handling code using VBA.