Monday, January 26, 2009

Becoming an OOTB SharePoint Guru Quickly

At http://www.endusersharepoint.com/?p=1241 is listed a few quick-learn skills that can turn a techie into a capable SharePoint administrator.

* Control the Quick Launch display… tweak, collapse and hide
* Let users manage the interface with the click of a button
* Hide major chunks of the interface that are just not needed on some pages
* Allow manual resizing of web parts on the page
* Expand and contract all groups in a list
* Manage your own resources for creating other basic, interface interactions

Warning: To get more out of SharePoint requires some very serious experience. But there is plenty of value with SharePoint out-of-the-box (OOTB). That's why its such a popular platform.

Thesaurus for SharePoint

Download http://www.jornata.com/presentations/thesaurus.xls for a MS Excel spreadsheet that generates the file. Name this file tsneu.xml and place it in the "C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications\\Config" directory on the MOSS server.

Kudos to Mauro Cardarelli at http://blogs.officezealot.com/mauro/archive/2008/12/04/21280.aspx for this idea.

Top 15 SharePoint Blogs

According to Technorati and Joel Oleson the top 15 SharePoint blogs right now are the following:

SharePoint Blog URL
http://blogs.msdn.com/sharepoint
http://andrewconnell.com/blog
http://weblogs.asp.net/bsimser
http://sharepoint.microsoft.com/blogs/mikeg
http://blogs.msdn.com/joelo
http://heathersolomon.com/blog
http://blah.winsmarts.com
http://blogs.msdn.com/pandrew
http://blogs.msdn.com/ecm
http://www.sharepointjoel.com
http://weblogs.asp.net/jan
http://blogs.msdn.com/sharepointdesigner
http://www.harbar.net
http://blog.thekid.me.uk

See http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb&ID=93 for details.

Skills of a SharePoint Architect

Read http://blogs.msdn.com/joelo/archive/2007/07/23/depth-and-breadth-in-a-sharepoint-architect-skills.aspx to see a good list of skills for a SharePoint Architect. Joel Oleson breaks the recommended skills into 4 areas: Core, Solutions, Extended, Interop/Integration. Here's his long list for Core.

IIS 6/7, Windows Server 2003/2008, DNS/WINS (Name Resolution), TCP/IP, SQL Server 2005 Admin (Backup, Monitoring, Logshipping or Database Mirroring), Basic Firewall rules/Proxy, IT Infrastructure Design, Hardware Acquisition (RAM, CPU, Disk I/O, etc.), Performance Monitoring, Capacity Planning, Growth Management, Windows Workflow Foundation, Client Troubleshooting & Support (IE, Firefox, Safari, Office XP, 2003, 2007, etc.), HTML & Client side scripting (Javascript, AJAX, DHTML, XSL, XSLT, XHTML), Exchange/SMTP integration (Inbound/Outbound email + contact objects), High Availability (Microsoft Cluster Services, Windows Network Load Balancing), Storage (Appliances, HBAs, SANs, Archive Storage), Backup Solutions (Various Tape, Hardware and software snapshots, software nearline and offline storage, DPM 2007, etc.), Hardware load balancing & ISA Secure Web Publishing, IAG (Internet Application Gateway), Whale Communications, Single Sign on integration, Connection Monitoring & Troubleshooting (ADO.NET, Web Services, CDO), Global Deployments & Multi farm deployments, Environments (i.e. Dev, Test, Staging, Production - Staged deployments), SDLC (i.e. MOF, ITIL, MSF Frameworks), Virtualization (Virtual Server 2005, Virtual PC, VMWare).

Read his blog for his list on Solutions, Extended and Interop/Integration. Being a SharePoint Architect is no easy skillset to master overnight :) Perhaps its best to track which skills are most associated with SharePoint. See http://www.itjobswatch.co.uk/jobs/uk/sharepoint.do for the following list: .NET, Microsoft, SQL Server, C#, ASP.Net, SharePoint Server 2007, Windows, SQL, MS Excel, XML.

SharePoint performance limitations

Read http://www.thesanitypoint.com/archive/2009/01/23/sharepoint-and-the-laws-of-physics.aspx to get a reminder that SharePoint needs to be implemented wisely with performance issues in mind. A few notes to glean:

1. Many envision SharePoint as a replacement for their regular network file shares. Keep in mind the "2000 document limit".

2. Even taking appropriate topology and taxonomy steps, heavy file-based SharePoint usage is going to significantly reduce the "rated" capacity of a SharePoint environment.

3. Consider if the users are geographically spread out. Would you want to channel all of the current file-server usage in your remote offices through a single WAN link?

4. Remember that SharePoint itself resides on a Windows server, and stores everything in SQL Server databases, and consider what an all-out consolidation would mean.

5. Don't forget that SharePoint is only one piece of the total puzzle. Your network, your geographical distribution, and other factors, need to play as large a role in your planning for SharePoint as they do with any other system in your enterprise.

6. Read http://technet.microsoft.com/en-us/library/cc261716.aspx for Microsoft's document on MOSS performance/capacity planning.

$200 Netbook reminder why

Its not much a secret that cost-cutting is a norm during recessions. The $200 Netbook (see http://www.iht.com/articles/2009/01/26/technology/26spend.php) is a reminder of that trend. And now we see IT organizations cutting costs on development (i.e. Java, C#, Cobol, C, VB, etc.) and packages (i.e. PeopleSoft, SAP, etc.) for lower cost alternatives such as cloud computing (i.e. everything on the server). However with concerns over security and all its legal implications they need a robust platform for cloud computing that's secure, auditable, feature-rich, agile and from a reliable vendor. And that's precisely why SharePoint and TFS are so hot right now. SharePoint is a full-service portal that can be customized with agility to do anything. TFS is the same for an IT organization striving to do the same for the business-at-large.

Wednesday, January 14, 2009

14 Very Useful SharePoint Links