Application Templates for Windows SharePoint Services 3.0

In November 2006 I posted on the availability of Application Templates for Windows SharePoint Services 3.0; currently all 40 of the “Fastastic 40” Application Templates are available for Windows SharePoint Services 3.0 in English including 20 English Site Admin templates and 20 Server Admin templates which are also available in multiple languages to include French, Italian, German, Spanish, Portuguese (BR), Japanese, Korean, Hebrew, Chinese (simplified), and Chinese (traditional).


Application Template Resource Center



Template Descriptions



Upgrade Toolkit for SharePoint Sites and Templates



Role-Based Templates for SharePoint My Site



Windows SharePoint Services Application Templates Grouped by Business Area



For more information visit:  http://www.microsoft.com/technet/windowsserver/sharepoint/wssapps/templates/default.mspx or see my November 2006 post at http://blogs.technet.com/wbaer/archive/2006/11/21/discover-application-templates-for-windows-sharepoint-services-3-0.aspx.

Configuring SharePoint Products and Technologies for Cross-Forest Deployments

 



People Picker works both cross-domain and cross-forest in one and two way trust environments.

People Picker will issue queries to all two-way trusted domains and two-way trusted forests to search People & Groups out-of-the-box. *People Picker uses the Windows SharePoint Services Web Application logon identity to access the target domain/forest.  If the Web Application pool does not have access to the target domain/forest, People Picker will need to be configured to use an account with access to the target domain/forest using the following STSADM operations:

STSADM –o setapppassword –password <password>
which establishes the Credential Key used to encrypt/decrypt the service logon identity in the configuration database. This must be configured identically on all servers that have the Windows SharePoint Services Web Application service configured.

NOTE This operation not required in scenarios where the target domain/forest is trusted. Each server farm should use a unique credential key.

STSADM.exe –o setproperty –pn peoplepicker-searchadforests –pv <domain(s)/forests(s)> -url http://<webapp&gt;

The format of

<domain(s)/forests(s)>
is a list of
forest:DnsName,LoginName,Password
or
domain:DnsName,LoginName,Password
separated by a semicolon where necessary in scenarios where the target forest/domain is trusted, People Picker can be configured using
forest:DnsName
or
domain:DnsName

Co-hosting Collaboration and Personal Site Collections within an Individual Web Application

One of the most common questions I receive is how to co-host traditional “team” and personal Site Collections (My Sites) within an individual Web Application in Microsoft Office SharePoint Server 2007. While possible, there are several important steps that you should be aware of.

The public profile page is a document specific to the SPSMSITEHOST site template (My Site Host); unless a My Site Host is defined in the server farm, public profile pages will not be available to users. A Web Application can have only one (1) root Site Collection, and as a result can host only one (1) site template. In a portal specific scenario, an Enterprise site template is generally applied to the root Site Collection, typically the Publishing or Collaboration portal. To ensure the public profile page is made available to the root Site Collection, it becomes necessary to establish a web under the root Site Collection that will host the My Site Host site template. In order to achieve this you will need to create a new web at http://<server>/<web&gt; that will host the My Site Host site template containing person.aspx. Person.aspx is hosted in the %commonprogramfiles%Microsoft SharedWeb Server Extensions12TEMPLATESiteTemplatesSPSMSITEHOST directory.

There are several considerations that apply to this scenario:

· The SPSMSITEHOST template must be applied to the web hosting the public profile page.

· The web hosting the My Site Host site template cannot use an existing managed path, e.g. /personal or /sites.

· The Shared Services Provider (SSP) should be configured to use the root Site Collection + My Site Host web as the My Site Host. This can be configured under Shared Services Administration | User Profiles and My Sites | My Site settings | Personal Site Services.

· The root web application should have the managed path /personal defined in Central Administration to maintain URL differentiation between traditional “team” and personal Site Collections.

This process will permit continuation of the typical SharePoint Portal Server 2003 configuration and Site Collection hosting model with one key difference:

· Personal Site Collections will be available to users through http://<server>/<user&gt;.

· Public profile pages will be rendered to users through http://<server>/<public&gt;?person.aspx?guid=<guid>.

The example scenario below illustrates a database migration approach upgrade where a root web application is selected as both the traditional “team” and personal Site Collection host:

Step 1 Upgrade the _SITE database using the database migration approach. See command line reference below:


STSADM -o -addcontentdb -url http://<rootwebapplication&gt; -databaserver <SQLServer> -databasename <portal>_SITE


Step 2 Upgrade the database hosting the personal site collections using the database migration approach. See command line reference below:


STSADM -o -addcontentdb -url http://<rootwebapplication>/personal databaserver <server> -databasename <personalsitesdb>


Step 3 Create a new web under the root Web Application (http://<rootwebapplication&gt;) using the My Site Host template. See command line reference below:


STSADM -o createweb -url http://<rootwebapplication>/public -template SPSMSITEHOST -title “Home” -description “Some Description”


Step 4 Introduce the managed path /personal to the root Web Application if it does not already exist.

Step 5 Upgrade the _PROF database using the database migration method. See command line reference below:


STSADM -o restoressp -title <ssptitle> -url http://<sspwebapplication&gt; -ssplogin <domainusername> -mysiteurl http://<rootwebapplication>/public -indexserver <indexserver> -indexlocation “D:Program FilesMicrosoft Office Servers12.0DataOffice ServerApplications” -keepindex -sspdatabaseserver <databaseserver> -sspdatabasename <sspdatabasename> -ssppassword <password>


This process is beneficial to the database migration upgrade approach in scenarios where you are upgrading the SharePoint Portal Server 2003 _SITE, profile and content databases or optionally select to establish a new SSP in your server farm. If selecting to establish a new SSP; the root web application can be created prior to creating the SSP allowing for the establishment of the new root Site Collection as the My Site Host during the SSP creation.

Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System Available!

The Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System is now available from the Microsoft Download Center!


The Microsoft Best Practices Analyzer programmatically collects settings and values from data repositories including Microsoft SQL Server, Registry, and Performance Monitor.  The data when collected is processed and a set of comprehensive best practice rules are applied to the topology.  Server farm administrators benefit from a detailed report listing of recommendations that can be applied to the environment resulting in performance and scalability improvements in additon to optimizing uptime.


Download [http://www.microsoft.com/downloads/details.aspx?familyid=cb944b27-9d6b-4a1f-b3e1-778efda07df8&displaylang=en] the Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and 2007 Microsoft Office System today.


Sample Microsoft Best Practices Analyzer Output

Using the Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System



  1. Download BestPracticeAnalyzer.exe  from http://www.microsoft.com/downloads/details.aspx?familyid=cb944b27-9d6b-4a1f-b3e1-778efda07df8&displaylang=en.

  2. Save the file to a location on your server.

  3. Double-click BestPractiveAnalyzer.exe to extract the contents of the package.

  4. Open a Command Prompt and change the directory to the location of where you extracted BestPracticeAnalyzer.exe

  5. Run sharepointbpa.exe -cmd analyze -substitutions SERVER_NAME <ServerHostingCentralAdminWebApp>.

  6. NOTE Replace <ServerHostingCentralAdminWebApp> with the server name of the machine hosting the Central Administration Web Application; any server in the server farm hosting the Central Administration Web Application can be used; this is required to obtain the server farm configuration data.

  7. The report will be generated as sharepointbpa.report.htm in your selected installation directory from Step 3 above.

The Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System can be run as often as required and should be run periodically to monitor and remediate issues that may have arised since the last run in the server farm.  See below for output after remediation (Incoming Mail Settings and DCLs were optionally not configured/remediated in this example):


Configuring Trusted File Locations for Excel Services

The following information is a reference guide to configuring Trusted File Locations for Excel Calculation Services in Microsoft Office SharePoint Server 2007.  Your configuration may vary due to performance and hardware considerations; you should test configuration parameters for performance and scale before application to a production environment.


 


Open your Shared Services Administration site and select Trusted file locations under Excel Services Settings.

Click Add Trusted File Location to add a new Excel workbook file location considered trustworthy. Trusted file locations can include Windows SharePoint Services Web Applications, network file shares, and web folder addresses. Excel Services will deny requests to open files that are not stored in any trusted location.

Step 1 Location

Location settings specify the address of the trusted location, type and scope of trust.

1. Address field, specify the address of the trusted location. In this example we will use the sample Web Application – http://fabrikam.

2. Location Type field, select the storage type of the trusted location, this example uses the sample Web Application – http://fabrikam and will be configured as a Windows SharePoint Services storage type.

3. Children trusted under Trusted Children to trust child libraries or directories, in this example using the http://fabrikam Web Application all documents from Document Libraries on this server will be rendered as a result of selecting Children trusted.

4. Provide a Description of the purpose of this trusted location. This is not a requirement to configure Excel Services; however, is beneficial for the management and identification of configured trusted locations hosted by the Shared Services Provider.

Step 2 Session Management

Session Management settings determine the behavior of Excel Calculation Services sessions using workbooks from the specified trusted location. Configurable settings include session timeouts and request durations.

1. Session Timeout field specify the maximum time in seconds that an Excel Calculation Services session can remain open ad inactive. This value will be dependent on the performance of your environment and server hosting Excel Calculation Services. The default session timeout is 300 seconds. The session timeout is measured from the end of reach request and the session subsequently shut down at the timeout specified. For example an inactive session of 290 seconds will be reset once activity has been resumed or shutdown if it remains inactive after 300 seconds.

2. Short Session Timeout field specify the maximum time in seconds that an Excel Web Access session can remain open and inactive. This setting is similar to the Session Timeout setting, though applies exclusively to Web Access sessions and the duration is measured from the end of the initial Open request. The default session timeout is 75 seconds.

3. Maximum Request Duration field specify the maximum duration in seconds of a single request in a session. The default request duration is 300 seconds.

Step 3 Workbook Properties

Workbook property settings specify the behavior of workbooks from the specified trusted location in Excel Calculation Services sessions. Configurable settings include the maximum size of a workbook that can be opened and the maximum chart size in that can be opened by Excel Calculation Services.

1. Maximum Workbook Size field specify the maximum size of a workbook that can be opened by Excel Calculation Services. The default maximum size value is 10MB.  In our corporate deployments in MSIT we have configured this setting to 100MB on application servers running Windows Server 2003 x64 Edition with 8GB RAM (4 proc).

2. Maximum Chart Size field specify the maximum chart size that can be opened by Excel Calculation Services. Any positive integer can be specified as a value in this field; the default maximum size value is 1MB.  In our corporate deployments in MSIT we have configured this setting to 10MB on application servers running Windows Server 2003 x64 Edition with 8GB RAM (4 proc).


Step 4 Calculation Behavior

Calculation behavior settings specify the calculation modes in Excel Calculation Services for workbooks in the trusted location. For most medium-large farms; the default settings are appropriate.

1. Volatile Function Cache Lifetime field specify the value for the maximum time in seconds that a computed value for a volatile function is cached for automatic recalculations. The default maximum volatile function cache lifetime is 300 seconds.

2. Workbook Calculation Mode field specify the calculation mode of workbooks in Excel Calculation Services. Manual, Automatic and Automatic except data tables settings override the workbook settings. The default calculation mode value is File which retains the workbook settings. The default workbook calculation mode is File.

Step 5 External Data

External data settings specify how Excel Calculation Services should handle external data connections in workbooks from the trusted location.

1. Allow External Data field specify external data processing setting. To disable external data connections select the radio button labeled None; otherwise, select the radio button(s) labeled Trusted data connection libraries only or Trusted data connections libraries and embedded to allow connections embedded in workbooks from the trusted location. The default external data connection value is None.

2. Refresh warning enabled to display a warning before refreshing external data in workbooks from the trusted location. The default warn on refresh value is enabled.

3. Stopping open enabled to stop the open operation on a file from the trusted location when the file contains Refresh on Open data connections and cannot be refreshed when opened or the user does not have an Open right to the file. This setting can be used in conjunction with Warn on Refresh. The default stop when refresh on-open fails value is enabled.

4. Automatic refresh (periodic / on-open) field specify the value for the automatic refresh duration in seconds. This setting specifies the time in seconds the system can use external query results. A value should be specified here if external data connections are allowed. The automatic refresh value is 300.

5. Manual Refresh field specify the value for the manual refresh duration in seconds. This setting specifies the time in seconds the system can use external query results. A value should be specified here if external data connections are allowed. The manual refresh value is 300.

6. Maximum Concurrent Queries Per Session field specify the value for the number of external data queries that can execute concurrently in a single session. This value can be any positive integer and has a default value of 5 concurrent queries per session.

Step 6 User-Defined Functions

1. User-defined functions allowed to permit user-defined functions to be called from workbooks from this trusted location. The default user-defined functions value is disallowed.


Click OK to commit the configuration when complete.