16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

198 Part III: Planning <strong>and</strong> Deployment<br />

Logical Deployment Considerations<br />

The following are considerations for deploying SharePoint Portal Server 2003 in an<br />

organization:<br />

■ A corporate portal site for all employees. This is a required component of<br />

all SharePoint Portal Server 2003 installations. This portal site will usually use<br />

Windows Shared Services if multiple portal sites are present but not required.<br />

See Chapter 14 for more information on Shared Services.<br />

■ Divisional portal sites for each division or project. Additional portal<br />

sites can be created for divisions or important projects within the organization.<br />

Additional portal sites are not required, but medium <strong>and</strong> large deployments<br />

will usually have many portal sites.<br />

■ Team site collection. The team site collection will encompass teams <strong>and</strong><br />

topics that are too small to warrant their own portal site. Team site collections<br />

can be hosted in the corporate portal site or its respective divisional portal site.<br />

A cross-corporate site collection can also be created to facilitate team sites that<br />

do not easily fall into a specific divisional portal site. The cross-corporate site<br />

collection is almost always stored in the corporate portal site.<br />

■ A My Site for each employee. My Sites are personal sites for each user. My<br />

Sites are optional in a portal site deployment. Each My Site is a SharePoint site<br />

with a special template applied. The user who owns the My Site will have full<br />

control of the site <strong>and</strong> can customize it as she wants. Architecturally, each My<br />

Site is considered a single Site collection.<br />

■ Security. Security considerations must be discussed <strong>and</strong> determined. By<br />

default, authenticated users will have reader access to everything in the portal<br />

site. All domain users will be authenticated users, therefore all users will have<br />

reader access to everything until the permissions are changed. Security should<br />

be planned before deploying SharePoint Portal Server 2003. Please refer to<br />

Chapter 24, “Information Security Policies for SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>,”<br />

for additional information on security practices.<br />

Planning Services <strong>and</strong> User Accounts<br />

There are two groups of accounts to plan for:<br />

■ Services accounts, which are used to run services such as SQL Server <strong>and</strong><br />

SharePoint Portal Server<br />

■ User accounts, such as search, indexing, application pools, <strong>and</strong> administrative<br />

accounts

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!