With Microsoft’s major push of Office 365, I think it important to briefly touch base on the entire update process. While Office 365 will, unless reconfigured, automatically updates itself based on the Update Channel (you can learn more about Update Channel by reviewing ) you have chosen to use (and yes, I too, never made any such choice and was automatically setup on the Deferred Channel). To uninstall Office for Mac 2011 move the applications to the Trash. Once you've removed everything, empty the Trash and restart your Mac to complete the process. Before you remove Office for Mac 2011, quit all Office applications and make sure there's nothing in Trash that you want to keep. This, on the surface, sounds like a brilliant approach, but as we have recently seen (updates 1705, 1706, 1707) sometimes updates can introduce new bugs that are more problematic then the ones they are supposedly resolving. With Office 365, much to most people’s dismay, one can no longer simply open the Control Panel to uninstall an update. Microsoft no longer offers a graphic interface to manage the updates and one must use the “DOS” command prompt to uninstall updates (or as Microsoft now refers to it as “Revert to an earlier version”). You can read Microsoft’s instructions on uninstalling an update by using the following link Now let’s make a few corrections and additions to their article! Not Limited to Only Uninstalling Updates First and foremost, I think it important to point out that while this command can be used to uninstall an update and revert back to any build of your choosing (probably it primary function), it can also be used to perform an upgrade. Version/Build, Even Microsoft Can’t Keep Things Straight! In the article, they mention that you have to execute a command similar to the one below officec2rclient.exe /update user updatetoversion=16.0.xxxx.yyyy and then later they explain 16.0. Xxxx.yyyy represents the full version number Yet when you look at the you’ll notice that the versions is actually a 4 character long number (1705, 1706, 1707, ). So in fact, the xxxx.yyyy does not represent the version number but rather the build number! Whenever performing a reversion or upgrade, I’d urge you to take note of the current Version/Build No of your installation should the change not be beneficial and you wish to return back to the initial state. Your Update Channel is Critical Another thing to be aware of is that even though say 1708 is available in the current channel, but is not in the Deferred channel, if you are using the Deferred channel you cannot upgrade to 1708. You would first need to switch update channels to make that version/build available to your installation and then you could perform the upgrade. To learn more about changing update channels look over. What Build Number Do I Want/Need? One of the biggest issues is figuring out which version/build you actually want to implement. To determine this, I have found that you have to use the following pages: • • Especially the latter can be useful to see exactly what each build implemented. Typically, if you suddenly encounter a new issue, I’d determine my current build number and then try reverting to previous build number. If that didn’t work, then I look to go further back, and so on. Also, you could see if there was a more recent build number available, and first try performing an update (moving forwards is always preferable than going backwards, no). Some Useful References: • • • • •. All code samples, downloads, links,, everything on this site is provided ‘ AS IS‘. In no event will Devhut.net or CARDA Consultants Inc. Be liable to this site’s end-user(s) or any third party for any damages, including any lost profits, lost savings or other incidental, consequential or special damages arising out of the operation of or inability to operate their software after using any of the information, downloads, code samples, links to other sites, provided on this site. Always scan any downloads you get from the internet for malware and viruses and always test new code on a backup copy, never your production work!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |