Installing Microsoft Office 2016? Here’s some tips!
Recently the VDI Like a Pro team surveyed the State of the VDI/SBC union 2017. From the 600 respondents, we learned that many organizations are now migrating from Microsoft Office 2010 to version 2016, skipping the 2013 version altogether (if they haven’t implemented it already).
We can also safely conclude that LibreOffice and OpenOffice have not made it to the enterprise level, two years ago they managed to get almost 2% market share, but this year it dropped below 1% although they report to have some big customers.
From the 41.83% that have already made the move to the latest version and through our own validation tests—available for free in all Login VSI 4.x downloads since July 2016—we know that this can sometimes be a painful process, wherein most Admins look at the compatibility of their ‘beloved’ macro’s and other add-ons, but often forget about the performance factor.
That’s why today I’d like to share three tips that make migrating to Office 2016 as easy as possible, while keeping the optimum end-user experience.
#1: Test, test, test; This should come as no surprise that we have testing at position one. There is no need to use your real users as crash tests dummies, sending them head first into the new environment, only to discover first hand if the migration was successful (or not). If you’d like to try our virtual users and simulate a test in your own environment, then click here.
#2: Know where to look; Our testing indicates that while upgrading from MS 2013 to 2016 increases the number of users that can work on the system without any problems by about 10%, the load on the storage also increases a bit. In our case, the impact of this is minimal as we run tests from local flash storage, but if you have it centralized that might affect performance.
#3: Instead of adding memory or CPU, consider adding a GPU; Not only will Microsoft Office benefit from a vGPU, but also other applications including web browsers will offload tasks from the CPU to the GPU when available. For example, as Andre Leibovici points out in this article.
#4: Number four (of three!) because its untested and rather unconventional; My colleague Jasper Geelen pointed out that it might be an idea to use the web editions, which might just do the trick for some of the less demanding users on your platform. As an added benefit this also makes sure that you are always running the latest version with minimal effort. While we have never performance tested this to date, it is a nice outside of the box thinking example.
If you are interested in learning more about the market or want to compare yourself to your peers in the industry? Download the full ‘State of the VDI/SBC union 2017’ report here.