<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tristan Watkins on IT Infrastructure &#187; administration Archive</title>
	<atom:link href="http://tristanwatkins.com/index.php/tag/administration/feed/" rel="self" type="application/rss+xml" />
	<link>http://tristanwatkins.com</link>
	<description>Technical guidance for SharePoint, Cloud Services, Windows and more</description>
	<lastBuildDate>Fri, 21 Oct 2011 23:33:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>SharePoint 2007 administration part VI: Site administration</title>
		<link>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-vi-site-administration/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sharepoint-2007-administration-part-vi-site-administration</link>
		<comments>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-vi-site-administration/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 06:00:22 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[branding]]></category>
		<category><![CDATA[content types]]></category>
		<category><![CDATA[permissions]]></category>
		<category><![CDATA[publishing]]></category>
		<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=335</guid>
		<description><![CDATA[This is the final post in a six-part series on SharePoint 2007 administrative commands. So far I&#8217;ve covered: Part I: Overview Part II: Farm administration Part III: web application administration Part IV: Shared Service Provider (SSP) administration Part V: Site Collection administration In this post I will review Site-scoped administrative functions. I should note that [...]]]></description>
			<content:encoded><![CDATA[<p>This is the final post in a six-part series on SharePoint 2007 administrative commands. So far I&#8217;ve covered:</p>
<ul>
<li>Part I: <a title="SharePoint 2007 adminsitration part I: Overview" href="../?p=312" target="_self">Overview</a></li>
<li>Part II: <a title="SharePoint 2007 adminsitration part II: Farm administration" href="../?p=322" target="_self">Farm administration</a></li>
<li>Part III: <a title="SharePoint 2007 administration part II: web application administration" href="../?p=328" target="_self">web application administration</a></li>
<li>Part IV: <a title="SharePoint 2007 adminsitration part IV: SSP Administration" href="http://tristanwatkins.com/?p=331" target="_self">Shared Service Provider (SSP) administration</a></li>
<li>Part V: <a title="SharePoint 2007 adminsitration part V: Site Collection Administration " href="http://tristanwatkins.com/?p=333" target="_self">Site Collection administration</a></li>
</ul>
<p>In this post I will review Site-scoped administrative functions. <span id="more-335"></span>I should note that this content was written before SP2 was launched and that revision has yet to occur.</p>
<h2>Permissions</h2>
<p>SharePoint groups contain users or groups (Active Directory or SharePoint groups). Permission Levels are often confused with groups, as the names of Permission Levels are often nearly synonymous with a SharePoint group. For instance, the default SharePoint group <em>Hierarchy Managers</em> has the <em>Manage Hierarchy</em> and <em>Limited Access</em> permission levels. The <em>Viewers</em> SharePoint group has the <em>View Only</em> permission level. There is no fixed relationship between these groups and permission levels, but it is desirable to maintain this fixed relationship unless there is a compelling reason to change it</p>
<p>New permission levels can be created for new or existing groups, or existing permissions within a default permission level can be fine-tuned. This is a full list of configurable permissions:</p>
<blockquote>
<h4>List Permissions</h4>
<ul>
<li>Manage Lists  -  Create and delete lists, add or remove columns in a list, and add or remove public views of a list.</li>
<li>Override Check Out  -  Discard or check in a document which is checked out to another user.</li>
<li>Add Items  -  Add items to lists, add documents to document libraries, and add Web discussion comments.</li>
<li>Edit Items  -  Edit items in lists, edit documents in document libraries, edit Web discussion comments in documents, and customize Web Part Pages in document libraries.</li>
<li>Delete Items  -  Delete items from a list, documents from a document library, and Web discussion comments in documents.</li>
<li>View Items  -  View items in lists, documents in document libraries, and view Web discussion comments.</li>
<li>Approve Items  -  Approve a minor version of a list item or document.</li>
<li>Open Items  -  View the source of documents with server-side file handlers.</li>
<li>View Versions  -  View past versions of a list item or document.</li>
<li>Delete Versions  -  Delete past versions of a list item or document.</li>
<li>Create Alerts  -  Create e-mail alerts.</li>
<li>View Application Pages  -  View forms, views, and application pages. Enumerate lists.</li>
</ul>
<h4>Site Permissions</h4>
<ul>
<li>Manage Permissions  -  Create and change permission levels on the Web site and assign permissions to users and groups.</li>
<li>View Usage Data  -  View reports on Web site usage.</li>
<li>Create Subsites  -  Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.</li>
<li>Manage Web Site  -  Grants the ability to perform all administration tasks for the Web site as well as manage content.</li>
<li>Add and Customize Pages  -  Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a Windows SharePoint Services-compatible editor.</li>
<li>Apply Themes and Borders  -  Apply a theme or borders to the entire Web site.</li>
<li>Apply Style Sheets  -  Apply a style sheet (.CSS file) to the Web site.</li>
<li>Create Groups  -  Create a group of users that can be used anywhere within the site collection.</li>
<li>Browse Directories  -  Enumerate files and folders in a Web site using SharePoint Designer and Web DAV interfaces.</li>
<li>Use Self-Service Site Creation  -  Create a Web site using Self-Service Site Creation.</li>
<li>View Pages  -  View pages in a Web site.</li>
<li>Enumerate Permissions  -  Enumerate permissions on the Web site, list, folder, document, or list item.</li>
<li>Browse User Information  -  View information about users of the Web site.</li>
<li>Manage Alerts  -  Manage alerts for all users of the Web site.</li>
<li>Use Remote Interfaces  -  Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site.</li>
<li>Use Client Integration Features  -  Use features which launch client applications. Without this permission, users will have to work on documents locally and upload their changes.</li>
<li>Open  -  Allows users to open a Web site, list, or folder in order to access items inside that container.</li>
<li>Edit Personal User Information  -  Allows a user to change his or her own user information, such as adding a picture.</li>
</ul>
<h4>Personal Permissions</h4>
<ul>
<li>Manage Personal Views  -  Create, change, and delete personal views of lists.</li>
<li>Add/Remove Personal Web Parts  -  Add or remove personal Web Parts on a Web Part Page.</li>
</ul>
</blockquote>
<p>One of the key tasks in taxonomy design is to determine how adequately the default permission levels fit, to define new permission levels if necessary and to identify where the application of distinct permission levels is required. The corollary task is to identify what custom groupings of users are required for default and custom permission levels and to identify where permission inheritance may need to be broken within the taxonomy</p>
<h3>People and Groups</h3>
<p>Create SharePoint groups and assign users to them</p>
<h3>Advanced Permissions</h3>
<ul>
<li>Configure permission levels (as opposed to assigning users or groups a level of permission)</li>
<li>Manage Access Requests</li>
<li>Specify the visibility of content to anonymous users if anonymous access is enabled within the application</li>
</ul>
<h2>Look and Feel</h2>
<h3>Master page</h3>
<p>Specify Site and/or System Master Pages and alternate CSS</p>
<h3>Title, description, and icon</h3>
<p>Specify title, description and icon</p>
<h3>Navigation</h3>
<ul>
<li>Manage navigation to sub-sites and pages</li>
<li>Manage sorting</li>
<li>Manage global (usually top) and current (usually side) navigation</li>
<li>Hide pages and sub-sites from navigation</li>
</ul>
<h3>Page layouts and site templates</h3>
<p>Specify sub-site, page template and layout inheritance. Also reset sub-sites and pages to inherit from this screen</p>
<h3>Welcome page</h3>
<p>Specify a page to be loaded at the site root</p>
<h3>Tree view</h3>
<p>Manages display of Quick Launch and/or Tree View in the left-hand navigation</p>
<h3>Site theme</h3>
<p>Specifies a default font and colour scheme for the site, without affecting the site layout or pages that have been themed individually</p>
<h3>Reset to site definition</h3>
<p>From the page description:</p>
<blockquote><p>If you want to remove all customizations from a page (such as changes to Web Part zones or text added to the page) you can use this feature to reset to the version of the page included with the site definition.</p>
<p>You can reset a single page within your site to use the version of the page included in the site definition, or you can reset all pages.</p>
<p>Caution: When you reset to the site definition version, you will lose all customizations made to the current version of the page. No backup copy of the page will be made before the page is updated, and no new version is created.</p></blockquote>
<h3>Searchable columns</h3>
<p>MOSS-only. Specify columns to be excluded from search. Also known as NoCrawl Columns</p>
<h2>Galleries</h2>
<h3>Site content types</h3>
<p>Create and Manage Content Types created here and inherited from parents</p>
<h3>Site columns</h3>
<p>Create and Manage Site Columns created here and inherited from parents</p>
<h3>Master pages and page layouts</h3>
<p>Upload and Manage Master Pages and Page Layouts available to the site and its children</p>
<h2>Site Administration Settings</h2>
<h3>Regional settings</h3>
<p>Specify locale, sort order, time zone, calendar type, alternate calendar, work week days and times, time format and inheritance of these settings to sub-sites</p>
<h3>Site libraries and lists</h3>
<p>A quick link to the list and library settings pages within the site</p>
<h3>Site usage reports</h3>
<p>View site metrics, top pages, top users, top referring pages, top referring hosts and top destination sites</p>
<h3>User alerts</h3>
<p>Manage alerts created within the site for all users</p>
<h3>RSS</h3>
<p>Allow/disallow RSS feeds within the site. Specify site-wide, “channel elements”, such as copyright, managing editor, webmaster and TTL</p>
<h3>Search visibility</h3>
<p>Include this site in search results, “yes”, or, “no”, and specify inclusion/exclusion of .aspx page content in the index</p>
<h3>Sites and workspaces</h3>
<p>A security-trimmed list of all sub-sites and workspaces within the site</p>
<h3>Site features</h3>
<p>Activate/deactivate features for the site</p>
<h3>Delete this site</h3>
<p>Permanently destroy all site content</p>
<h3>Related Links scope settings</h3>
<p>MOSS-only. Add/Remove sites to/from the, “This and Related Sites”, search scope</p>
<h3>Site output cache</h3>
<p>MOSS-only. Inherit settings or specify a page output cache profile. Define inheritance to children</p>
<h3>Content and structure</h3>
<p>MOSS-only. Reveals the current position within the site collection hierarchically, with expanding navigation to reveal parents, children and parallel items</p>
<h3>Content and structure logs</h3>
<p>MOSS-only. View Site Content and Structure logs and delete individual or multiple log events</p>
<li>Update Personal Web Parts  -  Update Web Parts to display personalized information</li>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-vi-site-administration/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SharePoint 2007 administration part V: Site Collection administration</title>
		<link>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-v-site-collection-administration/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sharepoint-2007-administration-part-v-site-collection-administration</link>
		<comments>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-v-site-collection-administration/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 06:00:19 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[site collection]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=333</guid>
		<description><![CDATA[This is the fifth post in a six-part series on SharePoint 2007 administrative commands. So far I&#8217;ve covered: Part I: Overview Part II: Farm administration Part III: web application administration Part IV: Shared Service Provider (SSP) administration In this post I will review Site Collection-scoped administrative functions. Note: everyone with a My Site is a [...]]]></description>
			<content:encoded><![CDATA[<p>This is the fifth post in a six-part series on SharePoint 2007 administrative commands. So far I&#8217;ve covered:</p>
<ul>
<li>Part I: <a title="SharePoint 2007 adminsitration part I: Overview" href="../?p=312" target="_self">Overview</a></li>
<li>Part II: <a title="SharePoint 2007 adminsitration part II: Farm administration" href="../?p=322" target="_self">Farm administration</a></li>
<li>Part III: <a title="SharePoint 2007 administration part II: web application administration" href="../?p=328" target="_self">web application administration</a></li>
<li>Part IV: <a title="SharePoint 2007 adminsitration part IV: SSP Administration" href="http://tristanwatkins.com/?p=331" target="_self">Shared Service Provider (SSP) administration</a></li>
</ul>
<p>In this post I will review Site Collection-scoped administrative functions. <span id="more-333"></span>Note: everyone with a My Site is a Site Collection Administrator of their personal site, so this section is also applicable for gaining an understanding of the delegated administrative rights that MySites unleash</p>
<h2>Site Collection Administrators</h2>
<p>Site Collection Administrators can add/remove other Site Collection Administrators, but cannot reduce the number of Site Collection Administrators below two. Farm Administrators can always specify new Primary and Secondary Site Collection Administrators within Central Administration, although additional Site Collection Administrators specified from within the Site Collection will retain their rights if the primary and secondary administrators are changed</p>
<h2>Top-Level Site Galleries</h2>
<h3>Site Template Gallery</h3>
<p>A repository of all non-default site templates available to the top-level site and all sites beneath it</p>
<h3>List Template Gallery</h3>
<p>A repository of all non-default list templates available to the top-level site and all sites beneath it</p>
<h3>Web Part Gallery</h3>
<p>A repository of all Web Parts available to the top-level site and all sites beneath it</p>
<h3>Site Collection Workflows</h3>
<p>Displays the currently active/inactive workflows, their associations and activity within the site collection</p>
<h2>Site Collection Administration Settings</h2>
<p>These are not only the administrative activities that Site Collection Owners need to be trusted to perform, these employees need to have adequate training to understand the impact of these actions</p>
<h3>Search settings</h3>
<p>Specify whether or not to use custom scopes and chose a Search Centre to display those results</p>
<h3>Search scopes</h3>
<p>Manage and define the custom scopes enabled above</p>
<h3>Search keywords</h3>
<p>Manage and define keywords/synonyms. The Keyword Phrase is what search queries will match to return a keyword result</p>
<h3>Recycle bin</h3>
<p>Manage deleted items. See the notes regarding storage quota templates in <a title="SharePoint 2007 adminsitration part II: Farm administration" href="http://tristanwatkins.com/?p=322" target="_self">part II</a> of this series for more information on the second-stage recycle bin</p>
<h3>Site directory settings</h3>
<p>MOSS-only. Specify a Site Directory location and Site Directory listing enforcement for new site creation</p>
<h3>Site collection usage reports</h3>
<p>View Site Collection Usage Reports. This is broadly the same as the site usage report, but adds top query and top destination report</p>
<h3>Site collection features</h3>
<p>Activate/Deactivate features for the Site Collection</p>
<h3>Site hierarchy</h3>
<p>A list of all webs that have been created within the Site Collection with links to the home pages and site administration pages of each</p>
<h3>Portal site connection</h3>
<p>The Portal Site Connection is a sort of reverse breadcrumb, located next to the link to the Site Collection home page in the upper left-hand corner of a page. If, for instance, a Site Collection is created at <a href="http://site1/nav1/test">http://site1/nav1/test</a>, a portal site connection could be created to <a href="http://site1/nav1">http://site1/nav1</a>. This allows for a simulacrum of hierarchy for navigation purposes while allowing Site Collection Ownership to retain the autonomous authority it requires</p>
<h2>MOSS Site Collection Administration</h2>
<h3>Site collection audit settings</h3>
<p>MOSS-only. Specify events to audit for sites, lists and items. Document libraries and items in them have additional auditing options</p>
<h3>Audit log reports</h3>
<p>MOSS-only. View audit reports and create/run custom reports</p>
<h3>Site collection policies</h3>
<p>MOSS-only. Create Site Collection information management policies from those enabled at the farm level (labels, auditing, expiration and barcodes by default). Policies can also be imported</p>
<h3>Site collection output cache</h3>
<p>MOSS-only. Page output caching can be useful when content is largely static, such as on internet-facing web sites. It requires sufficient RAM to maintain the cached elements. This page allows the selection of an Output Cache Profile for anonymous and authenticated users and defines the Output Cache Policy</p>
<h3>Site collection cache profiles</h3>
<p>MOSS-only. Create and Modify Output Cache Profiles, such as for public internet sites and extranets. This page includes some quite technical configuration</p>
<h3>Site collection object cache</h3>
<p>MOSS-only. Object caching is used internally by SharePoint to speed performance but in some cases the information in the cache may become stale and will need to be flushed. This page allows flushing and resetting of the object and disks caches, specifies a maximum size for the object cache in memory and defines the retention settings for Cross List Query results</p>
<h3>Variations</h3>
<p>MOSS-only. Variations allows for a number of variant sites to be created from a source site. This may be useful when operating in a multilingual or multicultural environment. With workflow settings the variant sites can be updated whenever source content is changed. This settings page specifies automated behaviour regarding creation and re-creation of target sites, web part publication settings, change notification and resource propagation</p>
<h3>Variation labels</h3>
<p>MOSS-only. Variation Labels are the names given to each variant. This administrative page allows creation and modification of labels and assignment of labels to positions within a variation label hierarchy</p>
<h3>Variation logs</h3>
<p>MOSS-only. Displays information about the success and failures of the variation operations</p>
<h3>Translatable columns</h3>
<p>MOSS-only. Specify which columns need to be translated for variations</p>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-v-site-collection-administration/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SharePoint 2007 administration part IV: SSP administration</title>
		<link>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-iv-ssp-administration/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sharepoint-2007-administration-part-iv-ssp-administration</link>
		<comments>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-iv-ssp-administration/#comments</comments>
		<pubDate>Wed, 21 Oct 2009 06:00:58 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[audiences]]></category>
		<category><![CDATA[Excel]]></category>
		<category><![CDATA[personalisation]]></category>
		<category><![CDATA[Profiles]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Shared Services]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[SSP]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=331</guid>
		<description><![CDATA[This is the fourth post in a six-part series on SharePoint 2007 administrative commands. The first part was an overview, the second covered Farm administration, the third covered web application administration, and this post is devoted to Shared Service Provider (SSP) administration. The bulk of this post only applies to MOSS, as there is no [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-424" title="Audiences" src="http://tristanwatkins.com/wp-content/uploads/Audiences2.PNG" alt=" SharePoint 2007 administration part IV: SSP administration" width="532" height="212" /></p>
<p>This is the fourth post in a six-part series on SharePoint 2007 administrative commands. The first part was an <a title="SharePoint 2007 adminsitration part I: Overview" href="../?p=312" target="_self">overview</a>, the second covered <a title="SharePoint 2007 adminsitration part II: Farm administration" href="../?p=322" target="_self">Farm administration</a>, the third covered <a title="SharePoint 2007 administration part II: web application administration" href="http://tristanwatkins.com/?p=328" target="_self">web application administration</a>, and this post is devoted to Shared Service Provider (SSP) administration. The bulk of this post only applies to MOSS, as there is no SSP for WSS. <span id="more-331"></span>This means that WSS does not provide:</p>
<ul>
<li> My Sites</li>
<li>Audiences and all of the targeting functionality they unlock</li>
<li>Search across site collections (which has massive implications to how WSS can scale)</li>
<li>Any of the other features below, including the Business Data Catalog and Excel Services</li>
</ul>
<p>What WSS does provide that is analogous but less robust is:</p>
<ul>
<li>WSS Search: search within a Site Collection
<ul>
<li>However, custom scopes and People Search are also missing</li>
</ul>
</li>
<li>User Information List: The UIL is populated from Active Directory with current user information at the time of the user&#8217;s first login. The user information list can have additional column data, but it needs to be updated manually rather than by scheduled synchronisation</li>
</ul>
<p>Neither WSS Search nor the User Information List have configuration options.</p>
<p>The remainder of this post will focus on SSP administration in MOSS 2007.</p>
<h2>User Profiles and My Sites</h2>
<h3>User profiles and properties</h3>
<p>MOSS 2007 supports importing user profiles from Active Directory, other LDAP directories or custom profile stores. Additionally, SSP administrators can:</p>
<ul>
<li>Configure import schedules</li>
<li>Manually add or view user profiles</li>
<li>Manually run import jobs and review import logs</li>
<li>Manage profile properties</li>
</ul>
<p>User Profile planning is critical to populating profiles with accurate, relevant and current information. As User Profile data are the building blocks of audience compilation, the ramifications of poor planning are felt widely, as illustrated in more detail in the Audiences diagram above</p>
<h3>Profile services policies</h3>
<p>Profile services policies apply to user profiles and My Sites. Manage policy enforcement, attribute visibility and user override settings here</p>
<h3>My Site settings</h3>
<ul>
<li>Specify the Personal Site Provider application, path and naming format</li>
<li>Disallow/allow users to choose the language of their own My Site from the list of language packs deployed to the server</li>
<li>Update default membership of the My Site Reader group for newly created My Sites</li>
<li>Specify a preferred Search Centre for searches initiated from the My Site</li>
</ul>
<h4>My Site Global Deployments</h4>
<p>My Site global deployments are also configured within the My Site settings page and the trusted My Site locations are specified in the next screen below. This note from the SSP Administration site helps to explain My Site Global deployments:</p>
<blockquote><p>Multiple My Site deployments can exist in the same environment allowing for specific users to have their My Site hosted by a different Shared Service Provider, this is common with global deployments. When a user&#8217;s My Site is hosted by a Shared Service Provider other than this one, that user will be blocked from using My Site related personalization features provided by this Shared Service Provider. The loss of functionality includes the ability to add users to their Colleagues list, the use of My Links and viewing people search results grouped by social distance.</p>
<p>Enabling My Site to support global deployments, will allow a users who&#8217;s My Site is hosted by a different Shared Service Provider to perform actions such as adding colleagues and links to their default My Site and viewing people search results grouped by social distance. To associate specific users with different Shared Service Providers use the Trusted My Site hosts list.</p>
<p><strong>Note:</strong> It is recommended that you implement a profile replication solution before enabling My Site to support global deployments. Without a profile replication solution in place users that have their My Site hosted on a different Shared Service Provider will have a disconnected user experience.</p></blockquote>
<h3>Trusted My Site host locations</h3>
<p>If My Site Global Deployments are enabled, this setting specifies the trusted My Site locations defined in other Shared Service Providers. Users are partitioned to distinct My Sites by audience or distribution/security group membership</p>
<h3>Published links to Office client applications</h3>
<p>Manage and Create audience-targeted links to SharePoint sites, useable through the My SharePoints tab in Office 2007 Open/Save As dialogue boxes. Note: this assumes Client Integration Features are enabled for the web application(s) and a supported authentication method is in use</p>
<h3>Personalization site links</h3>
<p>Adds audience-targeted or global links in between the My Home and My Site links, as below:</p>
<p><img class="alignnone size-full wp-image-395" title="PersonalisationSiteLinks" src="http://tristanwatkins.com/wp-content/uploads/PersonalisationSiteLinks.jpg" alt="PersonalisationSiteLinks SharePoint 2007 administration part IV: SSP administration" width="382" height="76" /></p>
<h3>Personalization services permissions</h3>
<p>Assign rights to create personal sites and use personal features. Delegate My Site management of analytics, audiences, profiles and permissions</p>
<h2>Search</h2>
<h3>Search settings</h3>
<h4>General settings</h4>
<ul>
<li>Specify content sources and crawl schedules
<ul>
<li><span style="text-decoration: underline;">Crawl Settings</span></li>
<li>Specify the behaviour for crawling this type of content
<ul>
<li>Crawling everything under the hostname will also crawl all the SharePoint Sites in the server.
<ul>
<li>Crawl everything under the hostname of each start address if the links on the start address tend to point to relevant content</li>
</ul>
</li>
<li>Select crawling behaviour for all start addresses in this content source
<ul>
<li>Crawl only the SharePoint site at each start address if the content available on linked sites is not likely to be relevant, and the content on the site itself is relevant</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<ul>
<li>Specify rules, such as inclusion/exclusion and unique authentication for specific paths</li>
<li>Manage crawled file types</li>
<li>Specify the default content access account</li>
<li>Reset all crawled content</li>
<li>Manage, create and view search scopes</li>
</ul>
<h4>Metadata Property Mappings</h4>
<p>Map crawled properties to managed properties and determine inclusion of the managed property in search scopes</p>
<h4>Add Server Name Mappings</h4>
<p>Set up a translation from a crawled address to a search result’s rendering of that same location. This is a one-to-one replacement, as follows:</p>
<p><img class="alignnone size-full wp-image-401" title="AddServernNameMapping" src="http://tristanwatkins.com/wp-content/uploads/AddServernNameMapping.jpg" alt="AddServernNameMapping SharePoint 2007 administration part IV: SSP administration" width="495" height="249" /></p>
<h4>Configure Search-based Alerts</h4>
<p>Search-based Alerts configuration options are useful for temporarily globally disabling Search-based alerts when a catalogue is reset, as users may receive a deluge of notifications when the crawl recompiles the catalogue</p>
<h4>Specify Authoritative Pages</h4>
<ul>
<li>Create lists of the <em>most authoritative</em>, <em>second-level authoritative</em> and <em>third-level authoritative</em> pages</li>
<li>Demote <em>non-authoritative</em> sites</li>
<li>Force immediate ranking updates</li>
</ul>
<h3>Search usage reports</h3>
<p>View search usage statistics by month, year, originating-query-Site-Collections and Search Scope</p>
<h2>Office SharePoint Usage Reporting</h2>
<h3>Usage reporting</h3>
<p>Enable/disable advanced usage analysis processing for site and site collection administrators. Enable/disable search query logging for Search usage reports in the SSP administration site</p>
<h2>Audiences</h2>
<h3>Audiences</h3>
<ul>
<li>Create audiences by reporting chain or group membership, or based on user profile property rule satisfaction</li>
<li>View/Delete rules</li>
<li>Specify audience compilation schedules</li>
</ul>
<p>A lot of planning needs to be invested in audiences due to the potential complexity of their use for targeting content throughout the organisation. To illustrate, see the chart at the top of this post.</p>
<h2>Excel Services Settings</h2>
<h3>Edit Excel Services settings</h3>
<p>Configure Excel Calculation Services security, load balancing, session management, memory utilisation, caching and external data connections</p>
<h3>Trusted file locations</h3>
<ul>
<li>Define WSS, UNC or HTTP trusted locations of Excel workbooks</li>
<li>Define location-specific session management, workbook/chart size limits, calculation behaviour and external data connection rules</li>
<li>Allow/disallow user-defined functions</li>
</ul>
<h3>Trusted data connection libraries</h3>
<p>A list of trustworthy data connection library locations</p>
<h3>Trusted data providers</h3>
<p>Add/edit/delete trusted OLE DB, ODBC or ODBC DSN data provider types</p>
<h3>User-defined function assemblies</h3>
<p>Add/manage file or GAC paths to user-defined functions in .NET assemblies</p>
<h2>Business Data Catalog</h2>
<ul>
<li>Import application definitions</li>
<li>View applications and entities</li>
<li>Manage BDC permissions</li>
<li>Edit the profile page template</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-iv-ssp-administration/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>SharePoint 2007 administration part III: web application administration</title>
		<link>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-iii-web-application-administration/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sharepoint-2007-administration-part-iii-web-application-administration</link>
		<comments>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-iii-web-application-administration/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 06:00:03 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[web application]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=328</guid>
		<description><![CDATA[This is the third post in a six-part series on SharePoint 2007 administrative commands. The first part was an overview and the second covered Farm administration. This part covers web application administration, which is carried out in SharePoint Central Administration. These administrative functions are carried out by farm administrators, but scoped at the application level [...]]]></description>
			<content:encoded><![CDATA[<p>This is the third post in a six-part series on SharePoint 2007 administrative commands. The first part was an <a title="SharePoint 2007 adminsitration part I: Overview" href="../?p=312" target="_self">overview</a> and the second covered <a title="SharePoint 2007 adminsitration part II: Farm administration" href="http://tristanwatkins.com/?p=322" target="_self">Farm administration</a>. This part covers web application administration, which is carried out in SharePoint Central Administration. These administrative functions are carried out by farm administrators, but scoped at the application level rather than across the entire farm.<span id="more-328"></span></p>
<h2>Application Creation/Extension</h2>
<p>Set up a new site/application in IIS or configure a new zone for an existing application</p>
<h2>Remove SharePoint from IIS Web Site/Delete Web Application</h2>
<p>The opposite of above</p>
<h2>Define Managed Paths</h2>
<p>Add/Delete explicit paths. Define Wildcards.</p>
<p>New Site Collections can only be created at available unused explicitly defined paths, or beneath wildcards. If new Site Collection creation will require approval  by Central Administrators, explicit paths will need to be created for new Site Collections. If Site Collection creation is delegated, wildcards will need to be provided in order for Site Collection creators to have a location to create their new sites</p>
<h2>General Settings</h2>
<h3>Default Time Zone</h3>
<p>Select a default time zone</p>
<h3>Default Quota template</h3>
<p>Select a default storage quota template for new site collection creation. See <a title="SharePoint 2007 adminsitration part II: Farm administration" href="http://tristanwatkins.com/?p=322" target="_self">part II</a> of this series for more information on storage quota template creation. Note: storage templates can still be specified during Site Collection creation &#8211; this merely sets the default quota template</p>
<h3>Person Name Smart Tag and Presence Settings</h3>
<p>Enable: yes/no</p>
<h3>Maximum Upload Size</h3>
<p>Define the maximum upload size in megabytes, up to two gigabytes</p>
<h3>Alerts</h3>
<p>Enable/disable alerts for the web application. Specify a maximum number of alerts per/user, if desired</p>
<h3>RSS Settings</h3>
<p>Enabled/disable RSS feeds for the web application</p>
<h3>Blog API Settings</h3>
<p>Turns On/Off the API, which allows blog posts from client tools, like Word 2007. Also configure acceptance of user name and password from the API</p>
<h3>Web Page Security Validation</h3>
<p>Turns validation on/off and sets validation expiration in minutes, or to, “never”. Note: this is not the same as the SSP “Session State”, which is used in some MOSS applications, and is reviewed in more detail in <a title="SharePoint 2007 adminsitration part II: Farm administration" href="../?p=322" target="_self">part II</a> of this series</p>
<h3>Send User Name and Password in E-Mail</h3>
<p>Specifies whether to send users their user name and password by e-mail. This may be convenient, but may breach security policy</p>
<h3>Backward-Compatible Event Handlers</h3>
<p>Turns on/off backward-compatible event handlers, which will only be applicable to WSS 2/SPS 2003 event handlers in the transition period following an upgrade</p>
<h3>Change Log</h3>
<p>Specifies change log event retention in days</p>
<h3>Recycle Bin</h3>
<ul>
<li>Turns the recycle bin on/off for all sites within a web application</li>
<li>Specifies first-stage deleted item retention in days</li>
<li>Specifies the second stage recycle bin at 1-500% of storage quota</li>
</ul>
<p>Note: site collections are created with a storage quota template, which specifies maximum storage available, so site second stage recycle bin retention is controlled by a combination of the storage quota applied to the site collection and the percentage of live site storage allocated to the secondary recycle bin</p>
<h2>Manage Content Databases</h2>
<p>Add new content databases to an application. Take content databases on/off-line (which controls new site creation within the databases, rather than taking the database offline as one would do in SQL server). It is sometimes preferable to create new site collections in their own (or new) content databases. This on/off-line functionality can aid that process, although there are better ways to manage this from the command line</p>
<h2>Web Application Features</h2>
<p>Activate/Deactivate features scoped at the web application level. Features can also be scoped at the farm, site collection or site level</p>
<h2>Blocked File Types</h2>
<p>Manage blocked file extensions per application</p>
<h2>Information Management Policy Usage Reports</h2>
<p>Moss-only.</p>
<ul>
<li>Enable/Disable Information Management Policy Usage reporting for the web application</li>
<li>Schedule recurrence</li>
<li>Specify report location</li>
<li>Specify default or custom report template</li>
</ul>
<h2>Alternate Access Mappings</h2>
<p>Assign up to five distinct zones, each consisting of one or more “internal URLs” per-Load Balanced, or “Public URL”. The public URL is the address which links on pages and in address bars are rendered in. Note: there can also be multiple host-named site collections created within the default zone (with STSADM only) and the default zone must be the most secure, as users who cannot be associated with a zone are automatically authenticated with Default zone policies</p>
<h2>Application Security</h2>
<h3>Security for Web Part Pages</h3>
<p>Allow/prevent users to create connections between web parts. Allow/prevent users to access the online web part gallery</p>
<h3>Self-Service Site Management</h3>
<p>Enable/Disable self-service site creation at the top-level web site. Specify requirement for secondary contact</p>
<h3>User Permissions</h3>
<p>Specifies which list, site and personal permission settings are available for selection within a web application. This is not an assignment of permissions to users or group, but management of the availability of permission settings to the web application</p>
<h3>Web Application Policy</h3>
<p>Assign Full Control, Full Read, Deny Write or Deny All permissions, per zone, to users or groups. This can be particularly useful if exposing read-only content to an extranet site, for instance</p>
<h3>Authentication Providers</h3>
<ul>
<li>Specify Authentication providers
<ul>
<li>Basic Authentication</li>
<li>Integrated Windows Authentication (NTLM or Kerberos)</li>
<li>Forms Based Authentication (FBA)
<ul>
<li>LDAP</li>
<li>ADAM</li>
<li>SQL Membership Provider</li>
<li>Any other ASP.NET 2.0 Authentication Providers</li>
<li>Note: no FBA authentication providers are provided with WSS out of the box. These need to be sourced/written independently</li>
</ul>
</li>
</ul>
<ul>
<li>Web Single Sign-On (SSO)
<ul>
<li>MOSS-only</li>
</ul>
</li>
</ul>
</li>
<li>Enable/Disable anonymous access (this setting allows site administrators to allow anonymous access, it does not automatically enable it where authorisation has already been configured). Disabling anonymous access removes this option</li>
<li>Enable/Disable client integration features (FBA does not support client integration features until WSS v3/MOSS 2007 SP2, so this setting can be used to prevent unexpected behaviour in earlier versions)</li>
</ul>
<h2>Workflow Settings</h2>
<p>Enable/disable user-defined workflows. Manage Workflow task notifications for internal and external users</p>
<h2>Site Use Confirmation and Deletion</h2>
<p>Enable e-mail notifications to owners of disused site collections or set automatic deletion after a number of unanswered confirmations</p>
<h2>Document Conversions</h2>
<p>MOSS-only.</p>
<ul>
<li>Enable document conversions for a web application</li>
<li>Specify a document conversion load balancer</li>
<li>Schedule conversion timer jobs</li>
<li>Manage availability to document libraries, time-out, retry and file size settings for installed converters, including the following by default:
<ul>
<li>InfoPath to Web Page</li>
<li>Word to Web Page</li>
<li>Word with Macros to Web Page</li>
<li>XML to Web Page</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-iii-web-application-administration/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SharePoint 2007 administration part II: Farm administration</title>
		<link>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-ii-farm-administration/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sharepoint-2007-administration-part-ii-farm-administration</link>
		<comments>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-ii-farm-administration/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 23:45:40 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[farm]]></category>
		<category><![CDATA[SharePoint 2007]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=322</guid>
		<description><![CDATA[This post is part two of a six part series on SharePoint 2007 administrative commands. The first post is an overview of the effort. This section identifies what farm administrators can do at the farm level. Farm administrators also administer SharePoint web applications, but I will be covering that functionality in the next post. Note: [...]]]></description>
			<content:encoded><![CDATA[<p>This post is part two of a six part series on SharePoint 2007 administrative commands. <a title="SharePoint 2007 adminsitration part I: Overview" href="http://tristanwatkins.com/?p=312" target="_self">The first post</a> is an overview of the effort. This section identifies what farm administrators can do at the farm level. Farm administrators also administer SharePoint web applications, but I will be covering that functionality in the next post.</p>
<p>Note: farm administrators can take ownership of any site collections or deny access to entire web applications, so the people filling this role must be trusted. Auditing can identify and alert the Site Collection Owners to the act of taking ownership, but damage can be done in the intervening period.</p>
<p>As mentioned in the first post, this is a brief command reference organised by administrative scope.<span id="more-322"></span></p>
<h2>Assign/Remove Farm Administrators</h2>
<p>All farm administrators have the right to add/remove other farm administrators, so they must all be trusted equally</p>
<h2>Manage Servers, Services and Identities</h2>
<ul>
<li>Assign SharePoint Server Roles and Enable/Disable Services</li>
<li>Remove servers</li>
<li>Configure service accounts and application pool identities</li>
</ul>
<h2>Specify Default Database Server</h2>
<p>New content databases will be created on this server unless otherwise specified</p>
<h2>MOSS Shared Services</h2>
<p>Note: configuration of Shared Services is performed within the SSP Administration site (this will be covered in part IV). These Central Adminstration settings establish and control the relationships between Shared Services and applications within the farm</p>
<h3>Create and Configure Shared Services</h3>
<p>Create new SSPs, assign a default SSP, associate web applications with SSPs or rebuild an SSP from backup</p>
<h3>Manage Shared Services between Farms</h3>
<p>Manage provision or consumption of Shared Services from/to other farms</p>
<h3>Configure Session State</h3>
<ul>
<li>Check the state of Shared Services enabled in this farm</li>
<li>Enable/disable Session State and specify duration</li>
</ul>
<p>Session State is a store of specific user session information required by some MOSS applications, enabled by default when an SSP is created. It leverages the underlying ASP.NET Session State to minimise quantities of postback data and to maintain sessions across load balanced servers in a transparent manner to end users. Generally the only reason to disable this setting is for troubleshooting.</p>
<p>Note: this is not to be confused with a security validation timeout. Also note: there is a separate Form Session State within the InfoPath Forms Services Configuration</p>
<h2>Manage Timer Job Definitions and Statuses</h2>
<p>This is where SharePoint does what it’s told, or fails to do so. Farm administrators can disable these jobs if warranted and monitor their success/failure</p>
<h2>Solution Management</h2>
<p>View solution deployment statuses or deploy solutions to the farm, or to specific web applications</p>
<h2>Configure Single Sign-On (SSO)</h2>
<p>This feature is available in MOSS only. Manage server settings, encryption keys, enterprise application definitions (SSO settings for each application authenticated by the service) and database properties for the Microsoft Single Sign-on Service</p>
<h2>Backup/Restore</h2>
<p>Perform backups and restore from within Central Administration at the web application or database level</p>
<h2>Configure Antivirus</h2>
<p>Require scan on up/down-load. Allow/prevent users from downloading infected documents. Determine if antivirus will attempt to clean infected files</p>
<h2>Quota Templates</h2>
<p>Create/modify Storage Quota templates. These are later applied during site collection creation. Storage quotas are very important to managing how SharePoint scales within recommended content database growth limits. Failing to design and implement storage quotas effectively can result in underperformance. Note: storage quota templates also directly affect the second stage recycle bin retention space</p>
<h2>Data Retrieval Service</h2>
<p>Enable/Disable Data Retrieval Services, used for querying with WSS, OLEDB, SOAP Passthrough or XML-URL. These services are used for connecting Data View Web Parts to their data sources.</p>
<p>Note: Data View Web Parts were originally available in WSS 2/SPS 2003. Data View Web Parts are edited with SharePoint Designer, which is not always desirable. Accordingly it may be preferable to disable these services to prevent those connections. In WSS 3/MOSS 2007 there may be other ways to achieve similar results using Reporting Services or the Business Data Catalogue for instance</p>
<h2>Logging and Reporting</h2>
<p>Enable and configure error reports, customer experience improvement program participation, event logging, trace logging and usage analysis processing</p>
<h2>Farm Features</h2>
<p>Enable Enterprise Features. Activate/De-active farm-wide features. To quote MSDN, “Unlike other Feature types, a global Feature is activated by default in the farm. A farm Feature contains several elements that are critical for implementing applications and logic”. Examples are Excel Services features and Global Web Parts. Features can also be scoped at the application, site collection or site level</p>
<h2>Master Site Directory</h2>
<p>MOSS only. Specify a location for the Master Site Directory. Is Site Creation metadata mandatory or not? Which categories of metadata are required, if so?</p>
<h3>Site Directory Links Scan</h3>
<p>MOSS only. Enables automatic updates to the Master Site Directory based on specific scan locations. The Links Scan can also update Site Properties</p>
<h2>E-mail Settings</h2>
<p>Configure outgoing and incoming e-mail settings and create/approve/reject distribution groups</p>
<h2>Records Centre</h2>
<p>MOSS only. Once a site or site collection has been created with the Records Centre site template, this page can be used to configure the farm’s connection to that record centre, which targets the <em>Send To &gt; Records Centre</em> functionality at this location. A farm can only have one records centre configured in this way, although if there is a compelling reason to set up multiple Records Centres, there is nothing in SharePoint preventing new site or site collection creation with the Records Centre template</p>
<h2>Content Deployment Paths and Jobs</h2>
<p>MOSS only. Manage content deployment between site collections, within or between farms. Specify the paths, content to include and schedule</p>
<h2>InfoPath Forms Services</h2>
<p>MOSS and Forms Server 2007 only. Upload/manage form templates. Upload/manage data connection files. Enable the web service proxy and/or enable the web service proxy for user forms</p>
<h3>Configure InfoPath Forms Services</h3>
<p>Configure browser-enabled form template settings. Manage data connection timeouts, response sizes and encryption. Manage authentication settings. Configure session thresholds and session state (see the SSP Session State configuration section above for more information)</p>
<h2>Information Rights Management</h2>
<h3>Service Configuration</h3>
<p>Turn on IRM. Use the default server in Active Directory or specify a sever</p>
<h3>Policy Configuration</h3>
<p>MOSS only. Manage the availability of Information Rights Management Features to the farm. Default policies are defined as follows:</p>
<table border="0" cellspacing="0" cellpadding="0" width="97%">
<tbody>
<tr>
<td valign="top"><span style="text-decoration: underline;">Name</span></td>
<td width="90%" valign="top"><span style="text-decoration: underline;">Description</span></td>
</tr>
<tr>
<td valign="top"><strong>Labels </strong></td>
<td width="90%" valign="top">Generates labels that   can be inserted in Microsoft Office documents to ensure that document   properties or other important information are included when documents are   printed. Labels can also be used to search for documents.</td>
</tr>
<tr>
<td valign="top"><strong>Auditing </strong></td>
<td width="90%" valign="top">Audits user actions on   documents and list items to the Audit Log.</td>
</tr>
<tr>
<td valign="top"><strong>Expiration<a href="https://r1portalcentraladmin.r1spdev.virtual/_admin/featuresettings.aspx?id=Microsoft.Office.RecordsManagement.PolicyFeatures.Expiration"> </a></strong></td>
<td width="90%" valign="top">Automatic scheduling   of content for processing, and expiry of content that has reached its due   date.</td>
</tr>
<tr>
<td valign="top"><strong>Barcodes </strong></td>
<td width="90%" valign="top">Generates unique   identifiers that can be inserted in Microsoft Office documents. Barcodes can   also be used to search for documents.</td>
</tr>
</tbody>
</table>
<p>Additional policies can be created, edited or imported at the Site Collection level. Accordingly, it is critical to consider the implications of separating or grouping content at the Site Collection level with these requirements in mind, as well as concerns about ownership, authorisation, taxonomy and ccale</p>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/sharepoint-2007-administration-part-ii-farm-administration/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>SharePoint 2007 administration part I: Overview</title>
		<link>http://tristanwatkins.com/index.php/moss-2007-administration-part-i-overview/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=moss-2007-administration-part-i-overview</link>
		<comments>http://tristanwatkins.com/index.php/moss-2007-administration-part-i-overview/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 19:44:32 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[SharePoint 2007]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=312</guid>
		<description><![CDATA[Last night I remembered that after I read the SharePoint Administrator&#8217;s Companion I put together my own administrative guide. I needed something much shorter that would take the SharePoint administrative interfaces as a starting point. This was effectively a click-by-click administrative reference. In fact, I assembled it by going through each button click available. I [...]]]></description>
			<content:encoded><![CDATA[<p>Last night I remembered that after I read the <a title="SharePoint Administrator's Companion" href="http://www.microsoft.com/mspress/books/9537.aspx" target="_blank">SharePoint Administrator&#8217;s Companion</a> I put together my own administrative guide. I needed something much shorter that would take the SharePoint administrative interfaces as a starting point. This was effectively a click-by-click administrative reference. In fact, I assembled it by going through each button click available.<span id="more-312"></span></p>
<p>I didn&#8217;t have a blog at the time, but I&#8217;ll be publishing it over the next few days, starting with an overview below. It will be followed with:</p>
<ul>
<li> <a title="SharePoint 2007 adminsitration part II: Farm administration" href="http://tristanwatkins.com/?p=322" target="_self">Farm Administration</a></li>
<li><a title="SharePoint 2007 administration part III: web application administration" href="../?p=328">Web Application Administration</a></li>
<li><a title="SharePoint 2007 administration part IV: SSP administration" href="../?p=331">Shared Service Provider Administration</a></li>
<li><a title="SharePoint 2007 adminsitration part V: Site Collection Administration " href="http://tristanwatkins.com/?p=333" target="_self">Site Collection Administration</a></li>
<li><a title="SharePoint 2007 adminsitration part VI: Site Administration " href="http://tristanwatkins.com/?p=335" target="_self">Site Administration</a></li>
</ul>
<h2>Overview</h2>
<p>A typical MOSS 2007 farm will consist of at least four web applications:</p>
<ul>
<li>SharePoint Central Administration (always only one per-farm)</li>
<li>Shared Service Provider (SSP) Administration (there can be up to twenty SSPs per-farm, although performance guidelines recommend no more than three)</li>
<li>My Site (there can be many per-farm, but only one per-SSP)
<ul>
<li>My Sites can reside within the SSP Administration web application, but for administrative purposes, such as backup/restore, this is often impractical</li>
<li>Also note that each My Site is its own Site Collection, so there is excellent scalability</li>
</ul>
</li>
<li>SharePoint web applications (there can be many sites within many site collections within many web applications), to include some or all of the following:
<ul>
<li>Corporate web sites</li>
<li>Extranets</li>
<li>Intranets</li>
</ul>
</li>
</ul>
<p>End-users will generally only concern themselves with the intranet/extranet/internet sites and their My Site. Central Administration and Shared Service Provider Administration sites provide distinct administrative functionality and scope. The next post will cover farm administration functionality in the Central Administration web application.</p>
<p>This guide is focused on MOSS 2007, but will identify all MOSS-specific functionality.</p>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/moss-2007-administration-part-i-overview/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

