1	8036 / 2012 SharePoint Administration, etc. Course Outline Your Host: Dave Corun New Horizons
2	Related Executables
3	What We’ve Done So Far SharePoint Overview SharePoint Overview II (Lab) SharePoint Architecture Managed Code in SharePoint Deploying / Installing SharePoint (Lab) Securing SharePoint Office 2003 Integration (Lab)
4	Where We’re Going SharePoint Products and Technologies Deployment Issues Storage Capacity Planning and SSO (Lab) Upgrading from 2001 Site Management Topic Assistant (Lab) Tools and Techniques Web Farm Deployment Disaster Recovery Strategies (2012) More on Managing (2012) More on Search (2012) Dave’s SharePoint Advice / Recommendations
5	Other Resources http://portal.sharepointsolutions.com http://www.microsoft.com/sharepoint http://msdn.microsoft.com/sharepoint http://office.microsoft.com SharePoint Portal Server 2003 Training Kit http://www.gotdotnet.com http://www.dotnetrocks.com http://www.sharepointcustomization.com/ http://www.sharepointexperts.com/ http://www.msd2d.com http://www.experts-exchange.com http://www.ms-resources.com/portals/Login.aspx
6	3^rd Party Tools Syntery (http://www.syntergy.com/) Audit
7	3^rd Party Tools Syntery (http://www.syntergy.com/) Bulk Loader
8	Dave’s Tips For Getting the Most Out of SharePoint
9	Areas and Such Areas should be used to aggregate, organize, and present information The user’s typically won’t manage these areas Don’t collaborate in the top-level portal site. It doesn’t scale Don’t bulk move all of your data at once. Instead link to the information and tune the search
10	Business Process Change SPS assumes most users will manage their own information in the company IT should really only manage portions of the portal. i.e. Virtual Servers, Farms, etc.
11	Business Process Change This is a fundamental “Cultural and Business Process Change” SharePoint introduces New paths of communication New methods of collaboration (E-mail vs. Sites) New methods of communication (users, partners, vendors) New ways of storing and developing information
12	Collaboration Server SPS is not a Document Management System SPS is a Document Collaboration System Don’t use SPS alone for content management or CMS related tasks. The CMS product does a better job when integrated w/ SPS
13	Search and Index Services Can crawl and index any # of sources SharePoint, web sites, file shares, etc. Customizable Heavy bandwidth usage Server resource intensive It will probably be the single reason for scaling out WSS and SPS actually don’t share their indexes Does support multiple languages Can craft the results for the end-user Probably the most difficult part of to administer
14	Search and Index Pitfalls Under estimating the resource demands Not asking users where they store critical information Not setting up a process w/ users to know where new content sources are located
15	Shared Services Once you turn on Shared Services, you can’t go back.
16	Templates The more time spent on templates before deployment, the better.
17	Personalization Audiences are not a security feature Feature only available in SPS Personal portals (MySite) tend to be deeply nested, and difficult to turn off Doesn’t yield a lot of power to the user Users are limited to 100mb by default Content gets indexed automatically as part of portal content Provides a one-to-many collaboration path Requires more end-user training
18	Training You can not successfully deploy SharePoint w/o robust education Give users a method of follow-up education Business Process Change takes time
19	WebDAV Windows XP has WebDAV built-in, so you can mount to a https:// site to a drive letter Often IT will use Active Directory GPO (Group Policy) to redirect the user’s My Documents to SPS instead.
20	Open Discussion