Upon first reading the rumors that Microsoft would soon acquire Yammer — and that this acquisition was based on Yammer technology to improve the social aspect of SharePoint — I reacted in roughly the same way that Tommy Lee Jones did when Harrison Ford proclaimed, “I DIDN’T KILL MY WIFE!” in the movie “The Fugitive.”
I didn’t care.
It’s not that these revelations weren’t significant. They were. Acquiring the cloud-based enterprise social network could improve the social collaboration capabilities of the next version of SharePoint (possibly in Q1 of 2013), if Microsoft chooses to do so. (As for the other? Well, Ford jumped off a 225-foot dam into an active spillway without a scratch.)
SharePoint has been the backbone of SHI’s company intranet since 2006. Over these past six years, I learned that an effective, enterprise-wide rollout of SharePoint is as much about the business and cultural decisions made as it is the technology itself.
No matter what type of customer I’m speaking to — large or small, desktop or application — one topic has risen to the forefront of every conversation: virtualization, and how it will be impacted by the upcoming Microsoft updates.
Later this year, Microsoft will release both Windows 8 and Windows Server 2012. I’ll be on hand during our customers’ update process to answer any questions about licensing and compliance, re-evaluating current licensing and deployment infrastructure, and providing best practices for any implementation. In the meantime, I’ll be outlining four things that can be implemented to best prepare for the switch. Let’s start with Windows 8.
1. Become an expert in the environment
The first step to prepare is to re-evaluate the virtualization infrastructure on both the desktop and the application side. In other words, get a full view of the environment’s hardware and software infrastructure. This will provide a transparent look into the virtual environment. To do this, identify whether each connected device is personally or company-owned; whether the device is on or off the company site; and whether it’s already covered under the corporate licensing scheme, or if it’s the employee’s responsibility as owner of the device.