As the Product Manager for the Replicator product, I’m excited to write about the release of version 7.1. It was a great experience learning from our solution engineers, developers and customers about all of the capabilities within Replicator. One consistent message from all my teachers was that replication/synchronization of SharePoint content isn’t a simple thing, and that there’s a lot that goes into monitoring the flow of content from one location to the next.
It’s almost as if the world breathed a sigh of relief when Julia White, general manager for Microsoft’s Office Product Management wrote a blog post acknowledging that there would be another release of Sharepoint on prem, namely Sharepoint 2016.
“We know that the move to cloud doesn’t happen all at once,” she said. “While we’ve seen growing demand for SharePoint Online, we recognize that our customers have a range of requirements that make maintaining existing SharePoint Server deployments the right decision for some. We remain committed to meeting those needs.”
Microsoft's Office has been a staple of business and organizations since it was first created. From a historical context, Office's popularity can be traced back to its ties to Microsoft Windows.
Windows is still the world’s most used business OS and Office is still tied to it. But as businesses embrace content collaboration workflows that don't require a desktop or laptop to perform office-like tasks, Microsoft needed to change its strategy or watch as businesses considered removing Office from its daily practices.
The move to Office 365 and Exchange Online in particular, presents an interesting conundrum for the new IT administrator. With the consolidation of resources that comes along with a move to the cloud, the responsibility for administering and maintaining the environment is delegated to administrators who previously have had little to no experience with some of the services that are now under their purview. For example after moving to Office 365, Admins have to contend with managing their users, not only in SharePoint, but in Exchange Online as well.
A David and Goliath Backup Story: Why You Want Small SharePoint Backups
Sometimes it’s good to be the big guy. People look up to you, amazed at how big you are. You always get picked first for sports teams. The view is much better. However, if you happen to be a backup file, bigger is definitely not better. You get little love. Administrators tolerate you at best and avoid you at worst. And when you are called to recover against a small backup, you lose every time.
The second leg of the U.S. Microsoft Services and Metalogix Roadshow rolled into the NYC Technology Center on October 13th. Fighting above average traffic, IT Managers, Architects and several CIOs joined the presenters to discuss transforming their business by moving from on-premises to SharePoint Online.
Last week’s official unveiling of Windows 10 offered several surprises that were mostly consumer oriented. The one interesting note for those interested in business and productivity tools was the Microsoft Surface Hub, an 84-inch touch display that comes equipped with video teleconferencing equipment and powered by Windows 10.
Migrations of anything but vanilla SharePoint collaboration sites to SharePoint Online (SPO) are significantly more complex and time consuming than most clients think they will be (and some vendors will have you believe). There are a number of reasons for this, an important one is the migration speed to SPO. I've addressed the others in the latter part of this blog post.
Managing the security of organizational content is a growing concern, particularly in the financial services sector. For many of these organizations, SharePoint functions as the 'one source of the truth' for storing and disseminating legal documentation and other sensitive customer financial data.