Chaos, frustrated users

Transcription

1 SharePoint

2 SharePoint 2003 and SharePoint 2007 No formal support No processes No governance No defined security model Chaos, frustrated users

3 Over 80 top level sites Site Owners not identified or trained No Governance in place with this structure Security exposures with incorrect roles assigned Duplicate content RESULT: User adoption low and site content credibility issues.

4 Formed a project to develop governance around SharePoint with support from an Executive Sponsor Team of approx individuals from our business groups A step in the right direction, but a long road ahead

5 Top Level Site Navigation (from 80 top level sites to 6) Established Master Template (look/feel), site name TeamShare Agreed on security model (AD Groups) / support structure (requests managed by the service desk, upon approval; users not granted full control rights) Established policies/procedures

6 Clean-up effort, inventory content, gap analysis Determine the site structure (information architecture) Developed IT Governance Group Migrated content from over 100 different sites PREVIEW OF NEW TEAMSHARE STRUCTURE AND IT SITE COLLECTION PILOT

7 Promote Search Functionality Top Level Site Collections The owners of each site; in addition to the IT Analyst and System Admin, make up the top level Governance Team. Promote use of SharePoint

8 Top Level IT Sites The owners of these sites; in addition to the IT Analyst and System Admin make up the SharePoint IT Governance Team. Audience: All authenticated Users at the root level Target Audience: All IT Users

9

10

11

12 Example of our 3-tier navigation structure: Example: >Projects >Information Technology >See list of sites (BizTalk, EDI, etc..)

13 1. Needed to purchase a SharePoint admin tool to automate content migrations 2. Revisited security model 3. Focus on user training as we migrate the business site collections Decided to upgrade to SharePoint 2010 before moving forward with our remaining site migrations

14 Upgraded both of our sites; as separate projects: old structure and new structure Built new farm on VM s Old structure Upgrade Kept the 2007 UI Powershell script created to revert new UI (ribbon) for new sites Issue with mail-enabled document libraries Upload multiple docs (requires Office 2010 toolset) Site Navigator web part (owned a license for a version not supported in 2010, purchased a new navigator web part that supported 2010) New structure Upgrade Discovered early on that our customized master template was not compatible with SharePoint 2010 in our new structure Determined it would be more efficient to migrate our new structure sites to a new site. This also provided us with an opportunity to use our admin tool to automate the migrations. Performance issue in the IT Site Collection (due to fly-outs) currently troubleshooting

15 Things that went well: Using Microsoft TechNet as a resource For the TeamShare upgrade, the databases were put into Read-Only mode for 2-day period of time until the content was migrated to the new 2010 structure. Change notice allowed users to let us know if there were any issues. Developed a Quick Reference Card to show primary differences in 2007 to 2010 with the new ribbon interface. Sent the Microsoft SharePoint 2010 online training site to users to familiarize themselves with the new interface prior to the upgrade.

16 Future of SharePoint Continue with our migration from old structure to our new 2010 environment Researching ECM (Enterprise Content Management), Records Center? Exploring using SharePoint as an Intranet? QUESTIONS?