| By Adam Woodruff | Article Rating: |
|
| October 12, 2008 10:00 AM EDT | Reads: |
1,559 |
I keep finding myself standing in front of the mirror and no matter how hard I concentrate I cannot seem to split my atoms and create a clone of myself. While this is an extreme thought, it seems to be a fairly common thread when I am out in the field meeting with SharePoint administrators. The unprepared SharePoint team can easily become overwhelmed by the system. I wanted to take some of the time I normally dedicate to writing articles and dig into what is happening out there and what you and your organization can do to avoid this situation.
Over the past few years, SharePoint administrators seem to be plucked from the Active Directory, Exchange, Web
administration and application development groups. I have found an amazing correlation between the administrator and the person(s) in your organization who are constantly trying to stretch the bounds of what is possible. Unfortunately, the truth is that these are also the folks who are relied on to solve the most critical issues when it comes to both your infrastructure and general health of your environment. Therefore we have reached the crux of the problem: how an organization clones its administrator before they quit or burn out.
The first and foremost issue that must be realized is that for most organizations, SharePoint is growing by leaps and bounds. I have met with a number of IT organizations that are being mandated, if not bypassed, to bring additional capacity and functionality online. It is time to take a stand and build your business case to slow the growth so that your organization can stop making some of the most common mistakes. I have a list of these mistakes and some directions for resolving them.
- SharePoint security is handled by a single resource
- Ownership of content is ill-defined
- Administration is a part-time job
- Quotas are set without analysis
- My Sites is enabled as a first-phase feature
- Backups are not being defined and managed
- Recovery is not fully tested or understood
- SharePoint features and components are all set to a single account
Published October 12, 2008 Reads 1,559
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Adam Woodruff
Adam Woodruff, MCSE, MCSA, is a solutions architect for SharePoint products at Quest Software and has over 10 years of experience creating solutions to work with Microsoft systems and infrastructure.
- Kindle 2 vs Nook
- Practical Approaches for Optimizing Website Performance
- SQL Anywhere Server and AJAX
- PowerBuilder Top Feature Picks
- The Difference Between Web Hosting and Cloud Computing
- PowerBuilder 12 and .NET
- Contrary Opinion: Why Silverlight is Good for Adobe
- Ajax in RichFaces 3.3, JSF 2 and RichFaces 4
- Wave on Ulitzer: Confessions of a Google Wave Fanboy
- Cloud Computing Best Practices
- AJAX World RIA Conference & Expo Kicks Off in New York City
- Rich Content Rotator for ASP.NET
- RIAs for Web 3.0 Using the Microsoft Platform
- Kindle 2 vs Nook
- Practical Approaches for Optimizing Website Performance
- Social Media Terrorists
- SQL Anywhere Server and AJAX
- SYS-CON's Cloud Expo Adds Two New Tracks
- PowerBuilder Top Feature Picks
- The Difference Between Web Hosting and Cloud Computing
- Google Maps and ASP.NET
- Crystal Reports XI & How It Has Changed
- Converting VB6 to VB.NET, Part I
- Creating Controls for.NET Compact Framework in Visual Studio 2005
- Where Are RIA Technologies Headed in 2008?
- How to Write High-Performance C# Code
- AJAX World RIA Conference & Expo Kicks Off in New York City
- Implementing Tab Navigation with ASP.NET 2.0
- i-Technology Photo Exclusive: Bill Gates & Steve Jobs In "Nerds"
- .NET Archives: Getting Reacquainted with the Father of C#



































