20 Design Decisions for Share Point Server

8/13/2019 20 Design Decisions for Share Point Server

1/27

SharePoint Server 2007Design Life Cycle

(Top 20 Design Questions)

CISSP, SharePoint [email protected]


2/27

Recommended Reading fromMicrosoft Press

SharePoint Server 2007 Best PracticesSharePoint Products Administrators Pocket Consultant


3/27

Gather and Map Requirements

Business Requirements

Why?

Functional Requirements

urrent systems Technology agnostic

Technical Requirements

Specific to SharePoint Server 2007

Use your enemies!


4/27

Requirements ElicitationTechniques

Traditional

Surveys, discussion groups, interviews

Existing Systems

x st ng unct ona ty an pa n po nts Group Techniques

Workshops, lunch-n-learn

Prototyping

Contextual Requirements

Expensive, but effective


5/27

Top 20 Design Questions

1. Should I migrate all of my content to

SharePoint Server 2007? Moving disparate data into a poorly

implementation leaves data in disparateSharePoint Server 2007 buckets!

File Shares will be here for a while

ISOs

Executables

Workstation profile backups


6/27


2. How will I manage security?

Server administrators arent farm admins

Farm Admin training

Delegation of Administration

Farm

SSP Site Collection

Site

List


7/27


8/27

Multi-tiered SLA


9/27


4. How many Web applications do I need?

Fewer is better

Use explicit managed paths instead of Web

Politics drive the creation new Webapplications

Create new Web apps for Security* Create new Web apps for Isolation

*Carefully weigh the advantages/disadvantages, and how much security isolationyou will actually realize


10/27

A Good Start to Web Applications

Central Administration

Never use App pool or identity for other Webapplications

Good idea for security and backup/restore

My Site Provider

Policies, URLs, Zones, usability (http://my)

Portal / Intranet


11/27


5. How do I enable external access to my

Intranet? Zones

VPNs

Legacy

SSL


12/27


6. Do I need content types?

Yes!

Site Collection scoped

, , , ,site columns (metadata), DocumentInformation Panel (DIP)

Multiple items in New menu


13/27


7. Do I need an information architecture

plan? Yes!

,adequate planning of buckets

Strive for process-based collaboration, andnot organization-based


14/27


8. Do I need Records Management?

Were you told to implement?

Yes Then OK

Based on your content type structure

Routed on exact match

Can be programmed to route based on partent

content type


15/27


9. What level of Search planning must I do?

Unless Search is a driving factor for phase I,then just SharePoint Server 2007

product

Use managed properties to expose metadatatags in advanced properties and advanced

search


16/27


10. Will I allow users to use SharePoint

Designer? Train your power users first

Understand the differences in a publishingsite and non-publishing site


17/27


11. Will I leverage the Publishing features?

Advantages

Navigation

aster age n er tance Page Layouts

In-browser editing

Disadvantages Page size

SharePoint Designer limitations


18/27


12. How many Shared Services Providers

do I need? One

Legal or Regulatory

Records Center Index

Intranet/Extranet Indexes

Extreme scaling

Hosting Services


19/27


13. Who will create site collections?

Do you have an IT Governance Plan?

Information Technology controlled creation,

timeliness and effectiveness of collaboration

Consider Self-service Site Creation forhighly-collaborative Web applications

DONT USE SITE USE CONFIRMATIONAND DELETION!


20/27


14. Will I enable incoming email?

Enable for discussion lists

Enable for custom Workflows

E-mail documents to lists

Requires SMTP on a farm member, or wire-

up to Exchange Server Use Alias for server name

i.e. SP.mycompany.com


21/27


15. Will you mail-enable SharePoint groups?

Easily email groups

Allow user-managed distribution lists

service

Integration with Active Directory

Creates and maintains list contacts

Creates and maintains group membership indistribution lists


22/27


16. Do I need enterprise workflows?

SharePoint Designer workflows are list-based, and cannot be distributed

,

logic to Visual Studio and save as features

Deploy features to Site Collections


23/27


17. What logging and auditing policies do

you need? Carefully set logging and auditing!

Use Event Logs for daily business

Enable trace logs for troubleshooting

Move trace logs from system drive if you willenable them 24 x 7


24/27


18. How will you monitor your solution?

System Center Operations Manager 2007has management packs for WindowsSharePoint Services 3.0 and SharePoint

Server 2007 Or, open the rules via SCOM Authoring

over 150 eventIDs and perf counters

See http://mindsharpblogs.com/ben for list ofperf counters


25/27


19. How will you backup and restore

content? For large shops and those who need short

,

Native tools work!

Stsadm.exe o backup directory for farm-levelbackups

Stsadm.exe o backup url for Site collectionbackups

Stsadm.exe o export / import for site backup


26/27


20. How many and which farm servers do I

need? Plan for availability first

One App server hosting ECS, Doc Conv, CentralAdmin, and Index

Dont sweat it

Easily changed later, except Index Server

Always start with SQL Server Standard or betterto allow farm growth. Basic and Standalone

installs do not easily allow for farm scaling


27/27

Questions?

http://mindsharpblogs.com/ben

[email protected]

Documents

20 Design Decisions for Share Point Server