As more organizations expand their use of Google Apps beyond email into file services, the question of how to best use Google Drive becomes important. In a previous post, we compared centralized versus distributed use of additional storage.
For many organizations, the question remains as to how best to integrate Google Drive and Additional Storage with existing, legacy apps on servers and client systems. Beyond whether or not MS Office stays around, companies often have other systems that run locally using local disk or network drives.
The Google Drive client provides and easy, free, means to sync local data storage with Google Drive and Storage. The utility, however, has a few limitations:
While not a reason to avoid using Google Apps as a file service, using the Google Drive client limits how you deploy your solution and creates some training elements.
Our recommendation is to create a file service using Google Drive that keeps the look and feel of a traditional file service for the end users. Doing so mitigates training and migration issues and avoids a range of technical issues related to supporting legacy applications.
Look for a solution that offers:
While you may spend a few dollars per user per year to get the environment you want, you will see returns. You should be able to extend the life or retire existing server hardware. With direct access to files, you should be able to reduce (or eliminate) your remote access solutions and/or VPN services, thereby reducing administration, licensing, and support costs. And best of all, improved collaboration and secure access to information means better productivity for your team and better business results.
Posted in General | Tagged Additional Storage, Cloud Computing, file services, Gladinet, Google Apps, Google Docs, Google Drive | Leave a comment