Nicholas Bisciotti's Blog

Error: "Unable to display this Web Part"

2011-10-27T15:06:00.004-04:00

Description

A Data View Web Part (DVWP) is configured to display data from a Microsoft SQL Server datasource. However, instead of data from the datasource, the Data View Web Part displays the following error message:

"Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Micrsofot SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator."

Solution *

1. Using SharePoint Designer, test the datasource for the DVWP. One possible cause for this error is that the credentials for the datasource are expired, as indicated in the SharePoint Designer dialog box.

2. Open SQL Server Management Studio, expand Security, expand Logins, right-click on the Login and click Properties. Uncheck the "Enforce Password Expiration" checkbox and click OK.

3. Test the Data View Web Part, datasource again in SharePoint Designer. If the issue is resolved, test the DVWP also in the Web browser.

* Disclaimer: This solution represents only one of many possible solutions and may or may not be applicable in your environment.

Lessons from an ERP Project Failure and Vendor Law Suit

2011-10-20T10:56:00.007-04:00

A customer/vendor conflict:

In a recent Computerworld article, Chris Kanaracus explains how Epicor Sued Over Alleged ERP Project Failure. In the article, the customer attributes the project failure due to shortcomings in Epicor software. Customer states, "The project did not go well due to a variety of shortcomings in Epicor's software."

Here is my analysis:

In my experience doing these sorts of procurements, when specific business requirements are defined well and included in the RFP, SOW, and contractual documents, then many project risks (both cost and schedule types) are shifted to the vendor. If the vendor agrees to meet a specific requirement and both customer and vendor sign the contract, then vendor is on the hook. However, if the requirement is not documented in the initial contract, then the vendor may later push back by describing the requirement as "out of scope" and will only do the work if they can bill the hours. Scope creep is not only common in ERP projects, it is actually a well-accepted fact.

As a casual reader of the article, I must state up front that I don't have all the facts in this story. I only know what I read in the article. So, based on the article and past experiences I can go out on a limb and suggest two things that might have happened:

The customer failed to specify the steps of a key process and include those details in their contract with Epicor. Therefore, the process became ambigious and unclear.
Epicor team attempted to remedy a technical shortcoming through additional pro services (billable time), and they failed to reach customer satisfaction before the bill got to be a million bucks.

Lessons to be learned:

This article reminds us of some key lessons that we can use when working with vendors.

Invest as much time as necessary into defining processes well.
Identify specifics even if they are obvious or assumed.
Include specific business requirements, solution requirements, use cases, story board, and other illustrations in the vendor contractual document.
Group related requirements into "categories" and seek fixed pricing estimate for each category (this forces vendor to do more careful estimates and makes the project easier to manage).
Create a project completion checklist up front (should map closely to the categories) and include that the contracts.
Realize even if you defined requirements really well, you still might miss important ones. Therefore, remember to buffer the project budget to cover requirements that may have been missed.

A fixed bid estimate may cost up to 25%-40% more than a standard estimate, but that is a significant discount over the 500%-1000% overrun that is not only possible, but likely if the requirements are not clearly spelled out and the work begins.

References

Kanaracus, C. (August, 2011). Epicor sued over alleged ERP project failure. Retrieved October 20, 2011 from http://www.computerworld.com/s/article/9219127/Epicor_sued_over_alleged_ERP_project_failure?taxonomyId=144&pageNumber=1.

SharePoint 4.0: How to Set the "Enable Client Integration" Setting on a Web Application

2011-09-25T15:57:00.000-04:00

Description

How to set the "Enable Client Integration" setting for a Web Application in SharePoint Server 2010.

Solution

1. Navigate to Central Administration, Application Management, Web Applications, Manage Web Applications.

2. Click to highlight the Web application for which you would like to disable client integration.

3. Click "Authentication Providers"

4. Click on the Zone name.

5. In the "Edit Authentication" dialog, "Client Integration" section, configure the "Enable Client Integration?" setting. Click Save.

SharePoint 4.0: Content Type Column Does Not Display in Datasheet View

2011-08-29T18:58:00.003-04:00

Thanks to Glyn Clough for suggesting the correct answer to this over Twitter!

Description

When creating a Datasheet View in SharePoint Server 2010 and choosing to display the Content Type column in the view, the Content Type does not appear in the view.

In this Datasheet View Definition, the Content Type column is in position #4.

The Content Type column does not display in the Datasheet View.

This is especially frustrating when working with documents in bulk because you would want the ability to modify the Content Type of multiple documents at one time. When the Content Type column doesn't display in Datasheet View, it is not possible to modify the Content Type of multiple documents at once.

Solution

The solution is to modify the Datasheet View and set the Content Type column to position #1.

1. Navigate to the SharePoint site where the Document Library is located.
2. Site Actions > View All Site Content.
3. Click on the Document Library to open the default view.
4. On the Ribbon, click on the Library tab.
5. On the Ribbon, click on Library Settings.
6. Beneath the Views heading, click on the Datasheet View, or the Standard View you would like to open in Datasheet mode.
7. Set the Content Type column to display in position #1.
8. Click OK to save the changes.

In this Datasheet View definition, the Content Type column is in position #1.

The Content Type column does, indeed, display in the Datasheet View.

References

Clough (2011). Glyn Clough's Blog - All About Microsoft SharePoint. Retrieved August 29, 2011 from http://www.glynblogs.com.

SharePoint 4.0: Unable to Open PDF Files in Edit Mode from Document Library

2011-08-29T18:14:00.005-04:00

Description

SharePoint users having Adobe Acrobat Professional expect to be able to open PDF files in Edit Mode, directly from a SharePoint document library. These users are not able to open PDF files in Edit Mode. When attempting to edit a PDF document directly from a SharePoint Document Library, they receive the error message, "The document could not be opened for editing."

Solution

The issue may be corrected by modifying the Require Check Out setting of the Document Library.

1. Navigate to the SharePoint site where the Document Library is located.
2. Site Actions > View All Site Content.
3. Click on the Document Library to open the default view.
4. On the Ribbon, click on the Library tab.
5. On the Ribbon, click on Library Settings.
6. Beneath the General Settings heading, click on Versioning Settings.
7. Note the current setting for Require Check Out. If Require documents to be checked out before they can be edited? is set to No, change this to Yes.
8. Click OK to save the configuration change.
9. From the Document Library, invoke the Document Context Menu by hovering the mouse over the title of the PDF document. Check out a PDF document.
10. Open the Document Context Menu again, and select to Edit Document (assumes that Adobe Acrobat Professional is installed on client computer).

Refer to Check out and edit a file for more information on the "Use my local drafts folder" prompt.

Reference

Adobe (2011). Which Acrobat X Software is right for you? Retrieved August 29, 2011 from http://www.adobe.com/products/acrobat.html.

Microsoft Office (2011). Check out and edit a file. Retrieved August 29, 2011 from http://office.microsoft.com/en-us/windows-sharepoint-services-help/check-out-and-edit-a-file-HA010153570.aspx

Error: Microsoft SQL Server: Cannot connect to (local)

2011-08-29T17:45:00.000-04:00

Description

Error when attempting to log into SQL Server Management Studio: "Cannot connect to (local)."

Solution

As the error message indicates, the SQL Server is not accessible. The issue may be caused by one of the following:

1) Issue with Server Connection Configuration

Start > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager

Verify the correct protocols are configured (this will vary based on type of environment). Refer to Microsoft TechNet article, Choosing a Network Protocol, for further assistance with this topic.

2) Issue with Service Account Authentication
Start > Administrative Tools > Services
Verify that the SQL Server (MSSQLServer) Service is running. If it is not running, try to start it. Make sure the Service Account credentials are properly configured and that the account is not locked out.

References

Microsoft TechNet (August, 2011). Choosing a Network Protocol. Retrieved August 29, 2011 from http://technet.microsoft.com/en-us/library/ms187892.aspx.

Error: Content Type Still in Use

2011-07-05T19:08:00.001-04:00

Description

When attempting to delete a content type from the site collection, Content Type Gallery, an error is returned:

Error
The content type is in use.
Troubleshoot with Microsoft SharePoint Foundation.
Correlation ID: 50b2222f-ee94-406eb7bb-d12a0be59dcd

Solution

There must be a document library, some place within the site collection using the Content Type that you are trying to delete. For this reason it is not possible to delete the Content Type. To fix this issue, identify the document library that is currently using the Content Type. Change the Content Type of any documents in the library currently set to the Content Type. Delete or remove the Content Type from the document library.

Once you've done this, it will be possible to delete the Content Type from the gallery.

Links: SharePoint 4.0 Service Pack 1

2011-07-05T15:28:00.001-04:00

SharePoint Foundation 2010

KB 2460058: Description of SharePoint Foundation 2010 SP1
http://support.microsoft.com/kb/2460058

White paper: Service Pack 1 for SharePoint Foundation 2010
http://technet.microsoft.com/library/hh301732(office.14).aspx

SharePoint Server 2010

KB 2460045: Description of SharePoint Server 2010 SP1
http://support.microsoft.com/kb/2460045

White paper: Service Pack 1 for SharePoint Server 2010
http://technet.microsoft.com/library/hh285676(office.14).aspx

Related Links

Known issues when you install Office 2010 SP1 and SharePoint 2010 SP1
http://support.microsoft.com/kb/2532126

List of all SharePoint 2010 and Office Server 2010 SP1 packages
http://support.microsoft.com/kb/2510766

Microsoft SharePoint Server 2010 June 2011 Cumulative Update
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2536599

Update Center for Microsoft Office, Office Servers, and Related Products
http://technet.microsoft.com/en-us/office/ee748587.aspx

Updates for SharePoint 2010 Products
http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

Registration Open! SharePoint Saturday New York City 2011

2011-06-15T09:08:00.004-04:00

Registration Open!

SharePoint Saturday New York City 2011

Saturday, July 30, 2011 from 7:30 AM - 6:00 PM (ET)

New York, NY

A CRM Vendor Pricing Whitepaper and Its Proper Place in the Overall CRM Procurement Process

2011-06-08T13:03:00.005-04:00

SugarCRM recently published a whitepaper titled, "CRM Vendor Pricing: A Comparative Analysis." The whitepaper explains pricing models for the CRM industry as a whole, and then provides detailed pricing information for a short list of CRM vendors. The whitepaper also provides a Total Cost of Ownership (TCO) analysis of the vendors (SugarCRM, 2011).

The reason I am posting is because this whitepaper reminded me of a common pitfull organizations fall into with CRM projects and I thought I would write about it. The pitfall I am referring to is beginning or leading a CRM project discovery with vendors and products, instead of through a more analytical process focused around business requirements. While the information in the whitepaper is certainly useful, I believe it is most relevant to project teams who have already gotten to the point where they are evaluating a short list of CRM vendors to compare capabilities, pricing, and other aspects of the overall investment and just need some help collecting and understanding pricing models and numbers.

Based on my observations in the field, I believe that too many organizations initiate a CRM project based on superficial vendor or product information, such as advertisements or pricing. I think this is a huge mistake and very common. Instead of a reactive approach, I believe that the best possible CRM vendor/product selection decision is one that spawns from due process. The project management processes that I've found to be very supportive, leading up to a CRM vendor/product selection, include the following:

1. Project Charter - Purpose, business case, initial scope statement, team, affected organizations, order of magnitude
2. Requirements Analysis - Surveys, interviews, general business requirements, technical requirements, solution requirements
3. Scope Management Plan - Project scope baseline, requirements traceability matrix, boundaries, constraints, etc.
4. Request for Proposal (RFP) - Template with detailed questions to be issued to vendors
5. Vendor Evaluation Round 1 - Identify all possible candidates
6. Vendor Evaluation Round 2 - Use requirements to eliminate and reduce list to a "short list", try to narrow down to less than 5
7. Vendor Evaluation Round 3 - Issue RFP to short list, conduct demonstrations, narrow down to 3
8. Final Comparison - Present full comparison of final 3 vendors with advantages/disadvantages, cost comparisons, etc.
9. Vendor/Software selection

Based on the steps listed above, the whitepaper and the type of information it contains, really comes into play around step 6.

Reference

Blytheco (2011). Blytheco Sets its Own Competitive Prices for Sage CRM. Retrieved June 8, 2011 from http://www.blytheco.com/sagecrm/price.asp

Blytheco (2011). Sage SalesLogix Price List. Retrieved June 8, 2011 from http://www.blytheco.com/saleslogix/price.asp

Sage (2011). Sage ACT! Pro 2011. Retrieved June 8, 2011 from http://www.act.com/products/2010/act/

Salesforce.com (2011). Sales Cloud. Retrieved June 8, 2011 from http://www.salesforce.com/crm/editions-pricing.jsp

SugarCRM (2011). CRM Vendor Pricing: A Comparative Analysis. Retrieved June 8, 2011 from http://media.sugarcrm.com/white_papers/CRM_Total_Cost_of_Ownership_Analysis.pdf

Sonoma Partners (2011). Microsoft Dynamics CRM Online (SaaS / Hosted). Retrieved June 8, 2011 from http://www.sonomapartners.com/microsoft-crm-pricing.aspx

SugarCRM (2011). Sugar Subscriptions & Pricing. Retrieved June 8, 2011 from http://www.sugarcrm.com/crm/products/editions.html

SPS New York: SharePoint 2010 Search Driven Design Patterns: Better Portal Designs with Fewer Compromises

2011-06-07T09:06:00.008-04:00

Event:
SharePoint Saturday New York
Saturday, July 30th, 2011

Session Title:
SharePoint 2010 Search Driven Design Patterns: Better Portal Designs with Fewer Compromises

Abstract:
When designing a SharePoint 2010 Intranet, collaboration portal, or business process solution we are faced with many decisions and challenges. While our objectives for user experience, information architecture, security model, and administrative model are driven primarily by business requirements, technology limitations tend to force certain decisions on us. This session explores search driven portal design patterns and explains how we can leverage the SharePoint Server 2010 Search feature area in creative ways, leading to better portal designs with fewer compromises.

Slides:

20110730 0100PM SharePoint Saturday Search Driven Design Patterns - Bisciotti.pdf

SharePoint Designer 2010: How to Show Toolbox

2011-06-06T15:55:00.003-04:00

Description

In SharePoint Designer 2010, the Toolbox provides a way to work with SharePoint Controls, Data View Controls, Server Controls, and Page Fields. However, in order to use the Toolbox, you must first make it visible.

Solution

Follow these steps to make the SharePoint Designer 2010 toolbox visible:

1. Click "Insert"
2. Click "SharePoint to expand the "Add SharePoint Controls" menu
3. Click "Show Toolbox"

SharePoint 4.0: Content Type Hub Synchronization Steps (Publish/Subscribe)

2011-05-26T12:32:00.017-04:00

Description

In a SharePoint Server 2010 environment, custom content types have been created on a Content Type Syndication Hub site collection (Content Type Publisher). However, the Content Type Subscriber site collection does not contain published content types in its Site Content Types Gallery.

Assumptions

The following configurations have already been verified:

1) The service account permissions are correct
2) The Managed Metadata Service Application is configured properly
3) The Managed Metadata Service Connection is configured properly and the setting for "This service application is the default storage location for Keywords" is checked off.
4) The Subscriber site collection has the following Site Collection Features enabled:

SharePoint Server Publishing Infrastructure5) The Publisher site collection has the following Site Collection Features enabled:

SharePoint Server Publishing Infrastructure, Content Type Syndication Hub

Solution

The following steps may be required to synchronize the content types between the publisher and the subscriber.

1) Publish the Content Types

Content Type Hub Publisher site collection > Site Actions > Site Settings > Galleries > Site Content Types
Click on Content Type
Click on "Manage publishing for this content type"
Click OK

Repeat this step for all content types that requiring publishing

2) Run the Timer Jobs

Central Administration > Monitoring > Timer Jobs > Review Timer Job Definitions

2a) Run the Content Type Hub Timer Job

Set the View to "All"

Click on the Timer Job, "Content Type Hub" Timer Job
Click "Run Now"

2b) Run the Content Type Subscriber Timer Job

Set the View to "Web Application"
Select the Web Application that contains the subscriber site collection
Click on the Timer Job, "Content Type Subscriber"
Click "Run Now"

3) Verify

Content Type Hub Subscriber site collection > Site Actions > Site Settings > Galleries > Site Content Types
Verify that the subscriber has received the published content type from the Content Type Hub

Reference

Microsoft TechNet (May, 2010). Content type and workflow planning (SharePoint Server 2010). Retrieved May 26, 2011 from http://technet.microsoft.com/en-us/library/cc262735.aspx.

Share-n-dipity (October, 2009). Publish and Subscribe to Content Types in SharePoint 2010. Retrieved May 26, 2011 from http://blogs.technet.com/b/speschka/archive/2009/10/30/publish-and-subscribe-to-content-types-in-sharepoint-2010.aspx

Links: SharePoint 4.0: March 2011 Cumulative Hotfix

2011-05-17T15:48:00.002-04:00

Descriptions

SharePoint Foundation 2010
KB2475880: Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): March 3, 2011
http://support.microsoft.com/kb/2475880

SharePoint Server 2010
KB2475878:
Description of the SharePoint Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package): March 3, 2011
http://support.microsoft.com/kb/2475878

Downloads

SharePoint Foundation 2010
Download for Microsoft SharePoint Foundation 2010
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475880

SharePoint Server 2010
Download for Microsoft SharePoint Server 2010
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475878

Error: Microsoft SQL Server Shared Feature Directory (INSTALLSHAREDDIR, INSTALLSHAREDWOWDIR)

2011-05-17T15:32:00.006-04:00

Description

During an installation of Microsoft SQL Server 2008 R2 x64 Standard Edition on a Windows Server 2008 R2 Service Pack 1 x64 Standard Edition operating system, I encountered issues on the Feature Selection screen.

Issue #1 - While the installation is 64bit, the Shared Feature Directory is hard coded as x86 - this is wrong.

Issue #2 - Error: "The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure the specified path is valid and different than the INSTALLSHAREDDIR path."

Solution

Aside from the regular disclaimer about don't modify the registry unless you have backups and know what you are doing, I want to also mention that the solution that worked for me does not apply to all situations. For example, if I experienced this issue while installing on an Itanium processor, then the solution would be different (Microsoft Support, 2011).

So, having said that, the solution for this particular situation was the following:

1. Open the Registry Editor

2. Export the following key (as a backup)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-518\Components\0D1F366D0FE0E404F8C15EE4F1C15094]

3. Delete the key.

4. Close the Registry Editor.

5. Open the Command Prompt (Start > Run > CMD)

6. Type the following command:

[Path to Setup.exe]\setup.exe /action=install /INSTALLSHAREDDIR=”C:\Program Files\Microsoft SQL Server\" /INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server\" (MSDN, 2011)

7. Press Enter. The SQL Server Setup launches from the beginning.

Notes

"INSTALLSHAREDDIR" is the 64-bit shared component files directory with a path of "Program Files\Microsoft SQL Server" (Microsoft Support, 2011)

"INSTALLSHAREDWOWDIR" is the 32-bit shared component files with a path of "Program Files(x86)\Microsoft SQL Server" (Microsoft Support, 2011)

When specifying the the directories, there are known issues with putting a "\" at the end of the path. For this reason, omit the symbol.

Examples:
Good - Program Files\Microsoft SQL Server
Bad - Program Files\Microsoft SQL Server\

Reference

Microsoft Support (2011). You receive an error message if you change the "Shared component directory" path on the Feature Selection screen when you install SQL Server 2008 on a computer that is running an Itanium-based version of Windows. Retrieved May 17, 2011 from http://support.microsoft.com/kb/955458.

MSDN (2011). How to: Install SQL Server 2008 from the Command Prompt. Retrieved May 17, 2011 from http://msdn.microsoft.com/en-us/library/ms144259(SQL.100).aspx.

MSDN (2011). Feature Selection. Retrieved May 17, 2011 from http://msdn.microsoft.com/en-us/library/ms143786.aspx.

MSDN (2011). File Locations for Default and Named Instances of SQL Server. Retrieved May 17, 2011 from http://msdn.microsoft.com/en-us/library/ms143547(v=SQL.105).aspx.

SPS Boston: SharePoint 2010 Search Driven Design Patterns: Better Portal Designs with Fewer Compromises

2011-03-21T11:21:00.006-04:00

Event:
SharePoint Saturday Boston
Saturday, April 9th, 2011

Session Title:
SharePoint 2010 Search Driven Design Patterns: Better Portal Designs with Fewer Compromises

Abstract:
When designing a SharePoint 2010 Intranet, collaboration portal, or business process solution we are faced with many decisions and challenges. While our objectives for user experience, information architecture, security model, and administrative model are driven primarily by business requirements, technology limitations tend to force certain decisions on us. This session explores search driven portal design patterns and explains how we can leverage the SharePoint Server 2010 Search feature area in creative ways, leading to better portal designs with fewer compromises.

Slides:

20110730 0100PM SharePoint Saturday Search Driven Design Patterns - Bisciotti.pdf

Naming Convention for SharePoint Databases

2011-03-01T17:02:00.001-05:00

Naming conventions are obviously important to SharePoint farms. Having a naming convention drastically improves efficiency related to configuration tasks, troubleshooting, documentation, and knowledge transfer. While I use naming conventions for various aspects of a SharePoint farm, this post explains a naming convention I use for SharePoint databases.

Here it is:
FarmAbbreviation_DatabaseCategory_Component_InstanceNumber_DatabaseType_InstanceNumber

Farm Abbreviation: A consistent abbreviation used to prefix all objects in a farm including IIS Application Pool, IIS Web Site, IIS Web Site directory, and databases.
Database Category: WebApp for Web Application and SvcApp for Service Application.
Component: Name of the Web Application or name of the Service Application.
Instance Number: Two digit, incremental number of component instance.
Database Type: For Web Applications, this is ContentDB. Some service applications use multiple databases so Database Type describes which one it is.
Instance Number: Two digit, incremental number of Database Type.

Examples:

The first content database for a Web Application named "Intranet", in a Farm abbreviated as "SPF01" would read as follows:
SPF01_WebApp_Intranet_01_ContentDB_01

An additional content database added to the "Intranet" Web Application would be incremented by 1, as follows:
SPF01_WebApp_Intranet_01_ContentDB_02

The Reporting database of a Web Analytics Service Application would read like this:
SPF01_SvcApp_WebAnalytics_01_ReportingDB_01

SharePoint 4.0: PowerShell Get-SPDatabase | Select Name

2011-03-01T16:49:00.002-05:00

This is just a quick tip about using PowerShell to retrieve a list of SharePoint databases. When you run Get-SPDatabase, you are provided the Name, Id, and Type of SharePoint databases. However, by default, the entire name might not be legible.

While there are extensive ways to do formatting in PowerShell, some times you just need a quick command to read the database names in entirety. So, if you run Get-SPDatabase | Select Name, only the database name is brought in entirety.

Links: Windows Server Catalog

2011-02-03T17:45:00.000-05:00

The Windows Server Catalog (http://www.windowsservercatalog.com) Web site is a useful reference. It includes software and hardware testing status, third party compatibility and certification, and server virtualization validation program information.

SharePoint Saturday Hartford Speaker Social on Friday January 28

2011-02-01T16:38:00.001-05:00

Despite being the last one to arrive at the SharePoint Saturday Hartford Speaker Social on Friday January 28, 2011, there was still enough time to goof around for a while before we had to sit down for dinner. Here, I managed to remain upright for a photo with Talbott Crowell, Geoff Varosky, and Fernando Leitzelar.

SPS Hartford: SharePoint 2010 Search Driven Design Patterns: Better Portal Designs with Fewer Compromises

2011-01-23T11:08:00.011-05:00

Event:
SharePoint Saturday Hartford
Saturday, January 29, 2011

Session Title:
SharePoint 2010 Search Driven Design Patterns: Better Portal Designs with Fewer Compromises

Abstract:
When designing a SharePoint 2010 portal for collaboration or business process facilitation we are faced with many challenges. While our intentions for user experience, Information Architecture, and security model are driven primarily by business requirements, technology limitations tend to force us into certain decisions. This session explains how search driven design patterns can result in better portal designs with fewer compromises.

Slides:

20110730 0100PM SharePoint Saturday Search Driven Design Patterns - Bisciotti

Error: SharePoint Server 2010 Installation, SharePoint Configuration Failed

2011-01-20T18:15:00.001-05:00

Description:

After configuring the operating systems and SQL Server instance in a multi-tiered server farm, I installed the SharePoint Server 2010 prerequisites and server binaries on the first Web front end. Next, I opened PowerShell and began creating a new farm from the command line. After only the first step, I received the error shown below.

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> New-SPConfigurationDatabase -DatabaseName "FarmName_Configuration_Database_01" -DatabaseServer "FarmDBSQLAlias" -A
dministrationContentDatabaseName "FarmName_Content_Database_01" -Passphrase (ConvertTo-SecureString "FarmPassPhrase" -AsPlaintext -Force) -FarmCredentials (Get-Credential)
...
New-SPConfigurationDatabase : CREATE FILE encountered operating system error 3(The system cannot find the path specifie
d.) while attempting to open or create the physical file 'I:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\
MSSQL\Data\FarmName_Configuration_Database_01_log.LDF'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
At line:1 char:28
...

So, I navigated to the log directory: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS and opened up the current PSCDiagnostics log file.

CTRL + F "error" brought me to this error:

...
01/20/2011 17:46:26 10 ERR Exception: System.Data.SqlClient.SqlException: CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'I:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\FarmName_Configuration_Database_01_log.LDF'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
...

Solution:

After viewing the log file message, I immediately knew what the cause of the error was. The SQL Server default path for LDF was not accessible because it hadn't been created yet. During the SQL Server 2008 R2 installation, I specified a particular default drive letter for MDF and LDF. After the installation, I changed the default path location for LDF's to a different drive letter, however, the new folder path (I:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data) didn't exist yet!

The fix was simply to go to the I: drive letter and create the necessary folder paths that I had set as the default LDF location for the SQL instance.

Note: When you install SQL Server 2008 R2 and you encounter the screen that asks for the default locations, be sure to set the MDF first and then the LDF second. The reason is that if you do the MDF path second, the installation wizard will reset your LDF location back to the MDF setting. It's just one of those things!

Links: Microsoft SQL Server 2008 R2 Feature Pack

2011-01-20T15:24:00.001-05:00

Microsoft SQL Server 2008 R2 Feature Pack
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=CEB4346F-657F-4D28-83F5-AAE0C5C83D52

Microsoft® SQL Server Report Builder 3.0 for Microsoft® SQL Server 2008 R2
Microsoft® SQL Server® PowerPivot for Microsoft® Excel
Microsoft® SQL Server® 2008 R2 Reporting Services Add-in for Microsoft® SharePoint® Technologies 2010
Microsoft® SQL Server® 2008 Reporting Services Add-in for Microsoft® SharePoint® Technologies 2007
Microsoft® SQL Server® 2008 R2 Policies
Microsoft® Sync Framework 2.0 Software Development Kit (SDK)
Microsoft® SQL Server® Compact 3.5 SP2 For Windows Mobile
Microsoft® SQL Server ®Compact 3.5 SP2 Server Tools
Microsoft® SQL Server® Compact 3.5 SP2 Books On-line
Microsoft® SQL Server® JDBC Driver 3.0
Microsoft® Connector 1.1 for SAP BW for SQL Server® 2008 R2
Microsoft® System CLR Types for SQL Server® 2008 R2
Microsoft® SQL Server® 2008 R2 Remote Blob Store
Microsoft® SQL Server® 2008 R2 Books On-line
Microsoft® SQL Server® 2008 R2 Upgrade Advisor
Microsoft® SQL Server® 2008 R2 Native Client
Microsoft® Core XML Services (MSXML) 6.0 SP 1
Microsoft® OLEDB Provider for DB2
Microsoft® SQL Server® 2008 R2 Command Line Utilities
Microsoft® SQL Server® Service Broker External Activator for SQL Server® 2008 R2
Microsoft® Windows PowerShell Extensions for SQL Server® 2008 R2
Microsoft® SQL Server® 2008 R2 Shared Management Objects
Microsoft® SQL Server® 2008 R2 ADOMD.NET
Microsoft® Analysis Services OLE DB Provider for Microsoft® SQL Server® 2008 R2
Microsoft® SQL Server® 2008 R2 Analysis Management Objects
Microsoft® SQL Server® 2008 Data Mining Add-ins for Microsoft® Office 2007
Microsoft® Datamining Viewer Controls For Microsoft® SQL Server® 2008
Microsoft® SQL Server® Migration Assistant
Microsoft® SQL Server® 2008 R2 Best Practices Analyzer

(Microsoft, 2011)

Reference

Microsoft (2011). Microsoft SQL Server 2008 R2 Feature Pack. Retrieved January 20, 2011 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=CEB4346F-657F-4D28-83F5-AAE0C5C83D52.

Error: SharePoint Server 2010 Setup Errors, Prerequisites Needed

2011-01-19T16:25:00.005-05:00

Description:

After running SharePoint Server 2010 setup.exe, Setup Errors occur.

Setup is unable to proceed due to the following error(s):

This product requires the Windows Identity Foundation.
This product requires Microsoft Sync Framework Runtime v1.0 (x64).
This product requires Microsoft SQL Server 2008 Native Client. Install SQL Server 2008 Native Client and re-run setup.
Windows Server Features or Role Services required by this product are not enabled. For a complete list, refer to the link below.
This product requires Microsoft Filter Pack 2.0.
This product requires Internet Information Services (IIS) 7.0 or higher, with ASP.NET v2.0 set to 'Allow' in the list of IIS Web Server Extensions.
This product requires the IIS 6 Management Compatibility component to install.
This product requires Hotfix for Microsoft Windows (KB976462) or above.

For the list of pre-requisites needed to install the product please refer to:
http://go.microsoft.com/fwlink/?LinkId=106209

Solution:

1. Windows Identity Foundation
http://www.microsoft.com/downloads/details.aspx?FamilyID=eb9c345f-e830-40b8-a5fe-ae7a864c4d76&displaylang=en

2. Microsoft Sync Framework Runtime v1.0 (x64)
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=C88BA2D1-CEF3-4149-B301-9B056E7FB1E6&displaylang=en

3. Microsoft SQL Server 2008 Native Client
Installing SQL Server Native Client
http://msdn.microsoft.com/en-us/library/ms131321.aspx

4. Windows Server Features or Role Services
Start > All Programs > Administrative Tools > Server Manager
Add Roles and Features:
i. Application Server
ii. File Services
iii. Web Server (IIS)

5. Microsoft Office 2010 Filter Packs
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5CD4DCD7-D3E6-4970-875E-ABA93459FBEE&displaylang=en

6. Internet Information Services (IIS) 7.0 or higher, with ASP.NET v2.0 set to 'Allow' in the list of IIS Web Server Extensions.
i. Start > All Programs > Administrative Tools > IIS Manager
ii. ISAPI and CGI Restrictions
iii. Confirm that ASP.NET V2.0 is set to "Allow"

7. Hotfix for Microsoft Windows (KB976462) or above.
A hotfix for the.NET Framework 3.5 Service Pack 1 is available for Windows 7 and for Windows Server 2008 R2 as a prerequisite for Microsoft Office SharePoint Server 2010
http://support.microsoft.com/kb/976462

Reference

Microsoft TechNet (July, 2010). Hardware and software requirements (SharePoint Server 2010). Retrieved January 20, 2011 from http://technet.microsoft.com/en-us/library/cc262485.aspx.

Windows Server: How to Configure SQL Server Client Alias Using CLICONFG

2011-01-19T15:52:00.005-05:00

In certain multi-tiered SharePoint Server farms, it does make sense to implement SQL Server Client Aliases on Web and App Servers to abstract the connection SharePoint Server uses to connect to its database server. Using SQL Server Client Aliases makes it easy to point SharePoint to a different database server, if a need arises, because it can be done through modification of the alias configuration (e.g. redirect to a standby database server, online and ready to go, standby server having a different server name than the original, production database server).

Considerations for SQL Server Client Alias configurations should be made prior to installing SharePoint Server. When deciding whether or not to implement SQL Server Client Aliases, you might think about these items:

Just because you can doesn’t mean you should - what need is driving this configuration?
Apply the “so what” test - what are the risks of doing versus not doing?
Thirdly, it probably makes sense to have server naming conventions in place before you go and abstract things by adding one more layer of names - will aliases confuse anybody?

1. Start > Run > Type “cliconfg” > Enter. This brings up the SQL Server Client Network Utility.

2. On the General tab, enable “TCP/IP” protocol.

3. On the Alias tab, add the server alias configuration.

4. Keep the defaults on the DB-Library Options tab.

5. Review the Network Library information on the Network Libraries tab. Click Apply and OK.

6. At this point the Alias has been created and the SharePoint installation may proceed.

SharePoint 4.0: Search Core Results Web Part Internal Error

2011-01-09T16:06:00.006-05:00

Description:

Search results page error caused by Core Results Web Part after modifying the Fetched Properties.

Error:
"Internal server error exception:
Troubleshoot issues with Microsoft SharePoint Foundation
Correlation ID: aba98106-d203-48bf-bdc9-bf2f8dd15bcd"

Solution:

In addition to the Column Name tags, the Fetched Properties must be properly opened and closed with Columns and /Columns tags, respectively. One possible cause for this error is that thet Fetched Properties XML is missing the opening and closing tags.

Windows Server: ADO.NET Data Services Update for .NET Framework 3.5 SP1

2011-01-03T13:14:00.006-05:00

This update is required in order to install SharePoint Server 2010 on Windows Server 2008 R2.

"The ADO.NET Data Services framework consists of patterns and libraries that enable the creation and consumption of REST-based data services for the web. This update to the Microsoft .NET Framework 3.5 SP1 provides additional features which extend the functionality provided in version 1.0 of the ADO.NET Data Services framework."
(Microsoft, 2010)

Reference

Microsoft (2010). ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2. Retrieved January 3, 2011 from http://www.microsoft.com/downloads/details.aspx?FamilyID=79D7F6F8-D6E9-4B8C-8640-17F89452148E&displaylang=fi&displaylang=en.

Microsoft (2010). A hotfix for the.NET Framework 3.5 Service Pack 1 is available for Windows 7 and for Windows Server 2008 R2 as a prerequisite for Microsoft Office SharePoint Server 2010. Retrieved January 3, 2011 from http://support.microsoft.com/kb/976462.

Windows Server: Enable Execution of PowerShell Scripts

2010-12-28T08:49:00.004-05:00

This post describes the steps to enable execution of PowerShell scripts on the Windows Server operating system.

1. Click Start, All Programs, and click "Administrative Tools"

2. Right-Click Windows Powershell Modules, Select "Run as Administrator"

3. At the command prompt (PS C:\Windows\system32>), type the following:
Set-ExecutionPolicy RemoteSigned

4. The Execution Policy Change prompt will display. Respond with "Y":

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might exposeyou to the security risks described in the about_Execution_Policies help topic.
Do you want to change the executionpolicy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y

Windows Server 2008: MSInfo32 and Winver

2010-12-27T13:52:00.008-05:00

System Information - To locate OS version, edition, and many details about hardware and software components.

Start > Run > Type "MSInfo32" and press Enter

About Windows - To locate OS version, edition, service pack level, and memory.

Start > Run > Type "Winver" and press Enter

Microsoft Word 2010: Hanging Indent

2010-12-13T20:31:00.006-05:00

This post explains the steps to format a list with a hanging indent, using Microsoft Word 2010. In this example, I am starting out with a list of references which are indented to the left.

1. Highlight the text to be formatted.
2. On the Ribbon, next to the word "Paragraph" click the chevron to open the paragraph formatting window.
3. Beneath the Indentation heading, set the "Special" field to "Hanging" and set the "By" field to "0.5."
4. Click OK

5. At that point, the list should be reformatted with a hanging indent.

SharePoint 4.0: Locating or Verifying Farm Version Number

2010-12-13T17:16:00.007-05:00

This post explains how to tell the version of a SharePoint 2010 server farm. In order to verify the complete farm, it is necessary to verify the version of DLLs as well as the Configuration Database.

A. Verify the version of DLLs.
Steps:
On each server where SharePoint 2010 is installed:
1. Open Windows Explorer.
2. Navigate to \Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI
3. For each of the following DLLs, locate the file. Right-click the file > Properties > Details.
4. Note the version

OWSSVR.DLL (SharePoint Foundation)

Microsoft.SharePoint.dll (SharePoint Foundation)

Microsoft.SharePoint.Portal.dll (SharePoint Server)

B. Verify the version of the Configuration Database

Steps:

From SharePoint 2010 Central Administration:

1. Navigate to SharePoint 2010 Central Administration > System Settings > Manage servers in this farm.

2. Note the "Configuration database version."

SharePoint 4.0: Records Center Behaviors? or Bugs!

2010-12-13T16:18:00.009-05:00

I have been busy developing a proof-of-concept (POC) environment based on some design patterns involving SharePoint 2010 Records Center and Search. In this POC, Records Center is acting as a top level site collection and is storing quite a bit of content. There are numerous content types and site columns, carefully planned and configured on the site collection, to support tagging Records Center documents with lots of metadata.

In this POC environment, I have dedicated a Web application to Records Center and for discussion purposes, the URL of the site collection can be http://recordscenter.domain.com. As I write this blog post, it is December 13, 2010. My SharePoint 2010 environment is running at version 14.0.5128.5000, which reflects RTM with the October 2010 Cumulative Updates. The SharePoint Foundation and SharePoint Server DLLs, and SharePoint Database are all current with the same version. I have tested with Site Collection Publishing and Site Publishing features enabled and disabled.

During the testing process, I have discovered some unexpected behaviors related to Records Center. Microsoft Support may stamp these with the trusty "By Design" label, but since I am currently in the process of pushing these issues through the Microsoft Support channels, I cannot speak to their response at this time. I do know that these behaviors are inconvenient and troublesome. Below is a list.

A. Cannot template a sub-site beneath a Records Center site collection.
To recreate the issue, follow these steps:
1. Start from a Records Center site collection.
2. Create a sub-site using the blank site template.
3. Attempt to save the site as a template.

Problem: Error: An unexpected error has occurred.

B. Cannot export a document library and then import it as a different name, in a Records Center site collection.
To recreate the issue, follow these steps:
1. Start from a Records Center site collection.
2. Create a sub-site using the blank site template.
3. Create a document library in the blank sub-site.
4. Using STSADM, export the document library to a .cmp file.
E.g.
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
stsadm.exe -o export -url http://webapplication/subsite/library -filename \\server\fileshare\templatelibrary.cmp -includeusersecurity -nologfile

5. Using STSADM, import the document library .cmp file, as a different name.
E.g.
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
stsadm.exe -o export -url http://webapplication/subsite/library -filename file://server/fileshare/templatelibrary.cmp -includeusersecurity -nologfile...
Finished with 15 errors.A list, survey, discussion board, or document library with the specified title already exists in this Web site. Please choose another title.

Problem: Error: The .cmp file cannot be imported because an existing document library having the same title (different than name, which affects the document library URL) already exists.
This behavior might make sense in a Records Center given the Content Organizer and its functionality which routes documents, based on content type, to appropriate document libraries using the Title of the document library. Still, templating document libraries in a Records Center is especially important, since Records Center typically have well defined site columns. It is only natural that we will want to template document libraries efficiently in a Records Center.

References
Microsoft SharePoint Team Blog (2010, December). October 2010 Cumulative Updates for SharePoint & Project Server 2010 Republished. Retrieved December 13, 2010 from http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=957.

Microsoft Support (2010, October). Description of the SharePoint Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package): October 26, 2010. Retrieved December 13, 2010 from http://support.microsoft.com/default.aspx?scid=kb;EN-US;2394320.

Microsoft Support (2010, December). Hotfix Request. Retrieved December 13, 2010 from http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2394320.

SharePoint 4.0: Where to Locate Details for Errors with Correlation ID

2010-12-07T10:05:00.004-05:00

The Correlation ID error seemed to be especially common in Beta versions of SharePoint Server 2010. However, I have managed to surface this one a few times in RTM. The screen print below illustrates what the error looks like on the Web page.

The error doesn't provide much information about the root cause. So, to uncover the details, it makes sense to investigate further by examining the log files. Here is how to do that:

1. Note the date and time of the error message.
2. Open a local console or RDP session to a SharePoint server in the farm.
3. From Windows Explorer, navigate to Program Files > Common Files > Microsoft Shared > Web Server Extensions > 14 > Logs.
4. Sort the log files by Date Modified, Descending. Then, open the file containing the event using a text editor, such as Notepad.
5. CTRL +F to locate instances of the word "Error." Then match the date/time stamp.

It isn't likely that this information will provide a direct answer, but at least you have more words to work with while researching.

SQL Server 2008: Edit Top 200 Rows

2010-12-02T10:53:00.004-05:00

SQL Server 2005 and earlier versions had an Open Table command available when you right-click a table. This allows you to open the table and make edits to fields. In SQL Server 2008, the Open Table command is replaced with the Edit Top Rows command. The default for this is 200, which of course, is obnoxious.

To change this setting, follow these steps from SQL Server Management Studio (SSMS):

Tools > Options (This opens the General Scripting Options Dialog Box)
SQL Server Object Explorer > Commands
Table and View Options: Value for Edit Top Rows command (Change this value)

After modifying the setting, you will see that the menu is updated accordingly.

Reference

Microsoft (2010). Options (SQL Server Object Explorer/Commands). Retrieved December 2, 2010 from http://msdn.microsoft.com/en-us/library/cc280381.aspx.

Focus More on Birdhouse Less on Hammer

2010-10-25T18:50:00.009-04:00

Mauro Cardarelli recently plugged something I said, "focus more on the birdhouse and less on the hammer." If Mauro hadn't used that analogy with me a few times before, I probably would have used a different one like, "focus more on the crazy noodles and less on the fork."

The birdhouse analogy refers to the focus of conversations and presentations at SharePoint related conference sessions, meetings, and discussions. My underlying criticism is that it seems that the community has become more focused on what the SharePoint platform can do and not focused enough on the business solutions that we are building with the platform. I think the community stands to gain a lot if more emphasis was placed on what we are building with the platform, why, and how we measure value to the businesses receiving these solutions.

I understand that we do need to know the SharePoint product well in order to develop useful business solutions with it. However, I think it is easy for us become consumed by the SharePoint platform; and its capabilities and limitations and lose sight of the fact that SharePoint is merely a vehicle that helps us get to a destination. The business solutions are the true end game, not the platform and tools we use to build the solutions. Some of the design patterns and methodologies we find to be effective may even be transferrable to other technologies.

As workers, we in the SharePoint community are responsible for ensuring that the solutions we develop will provide the outcomes that the sponsors and stakeholders expect. I think that if we spend too much time trying to figure out the best ways to get "there," and too little time on establishing complete and clear visions of where "there" is, then we are missing the target. As a community, I think we may miss valuable opportunities to share lessons learned and best practices for solving common business problems using the SharePoint platform.

When we only focus only on the hammer, we miss the point. Let's have more conversations and presentations about the birdhouse, how we designed it, why we designed it a certain way, and what we learned from the whole experience.

Use SharePoint Worfklow Like Robots on a Conveyor Belt

2010-10-25T18:33:00.005-04:00

The idea of automating a business process with SharePoint workflow to make things more efficient and consistent sounds like a novel concept and a way leverage a technology investment. However, if you examine any major business process from the top down, what you will find is that it is made up of several tasks (some linear, some not) as well as decisions which are based on a constantly changing environment and context. These decisions are not only in support of executing the process, but often times the process itself is being evaluated real time.

Take for instance, the beginning portion of a new hire process that a company might have. This might involve a series of human interactions between candidate and recruiter. An application is submitted and the recruiter would evaluate the application, comparing it to an open requisition. The recruiter would interpret the information on the application and ask for clarification. If a match is made, then an interview might occur, and so on.

When the people involved are attempting to execute a process such as this, it is only natural that the changing conditions of the work environment will prompt questions about what tasks need to be completed, who should complete the tasks, what information should be gathered, how should that information be evaluated, what laws exist, etc.

Although, it is possible to automate certain tasks in this process, SharePoint workflow is not designed for automating the entire business process. Where SharePoint workflow really comes in is making discrete tasks more efficient. For example, the workflow technology may be used to transfer an applicant's information into a database where it can be easily compared with open requisition criteria.

The technology is not going to do a human's work, though, and it is not practical to even try to make it. No, instead, a more appropriate approach to leveraging SharePoint workflow is for efficiency gains which target small steps or tasks; ones that are completely black and white, like modifying and loading records into a custom list or database, moving documents, or sending out an e-mail when a specific event occurs.

Portal site designs which help guide the human through a series of steps is essential to a workflow solution. The portal provides the framework to guide the user, while the workflow elements provide automation for specific tasks that occur during the process.

Whatever the application, the goal is usually to provide tools that allow the human to logically string each step together, flowing as if the site is a virtual conveyor belt and the workflow elements (conditions/actions) are specific robots that do stuff at each stage. The overall solution should help guide and progress the overall process in a consistent direction so that humans can participate, contribute, and derive the needed results.

Still, in an ever changing environment, it is only natural that the conveyor belt will need to be stopped and participants will ask each other whether the process is effective and efficient enough, and what might need to happen differently. The simple fact is, every business process is a work in progress.

NESQL 2010 October 14 Virtualizing SQL Server

2010-10-15T17:59:00.009-04:00

I attended a New England SQL Server User Group meeting last night. Brent Ozar did a presentation on Virtualizing SQL Server.

During the last few years, I have become a fan of virtualization for SharePoint environments, including the SQL Server database server role. I know many in the SharePoint community are skeptical about this, so, it was interesting to observe the opinions and responses from the local SQL Server community. I think the majority of the room was still skeptical (as expected) about virtualizing SQL Server. However, Brent did a good job of providing guidance on how to get the best performance out of a SQL environment when it is virtualized.

Beyond enlightening me about some of the finer details of how virtualization impacts I/O, Brent's presentation provided greater validation for my opinion of virtualizing SQL Server. At this point, I believe the technology is definitely mature enough to handle all roles (including database role) of most production SharePoint environments. That is; if adequate hardware is allocated and if virtualization is implemented well.

Some of the take-aways I scribbled down include the following (no warranties with these notes because I can barely read what I wrote):

CPU
- CPU-Z is a great, free utility for monitoring true CPU performance on guest systems
- In a virtual environment, more cores assigned to a SQL Server VM may actually leads to worse performance due to overhead related to instruction assignment behavior in shared environments relative to processor caching.

RAM
- In VMWare, set memory reservations, don't over commit RAM, use large pages (Microsoft, 2010).
- In SQL Server, remember to set min/max memory appropriately.

Storage
- Group DBs logically based on purpose, maintenance schedule, security, etc.
- Still separate Temp DB in virtual environments.

I believe Brent will be presenting the complete version of his presentation at the PASS Summit in November. Either way, if you are reading up on this topic, then check out his blog post on Virtualization Best Practices.

Reference

CPUID (2010). CPU-Z supports the new Intel Sandy Bridge processors. Retrieved October 15, 2010 from
http://www.cpuid.com/news/26-cpu_z_supports_the_new_intel_sandy_bridge_processors.html

Microsoft (2010). SQL Server and Large Pages Explained. Retrieved October 15, 2010 from http://blogs.msdn.com/b/psssql/archive/2009/06/05/sql-server-and-large-pages-explained.aspx.

Ozar (2010). Virtualization Best Practices. Retrieved October 15, 2010 from http://www.brentozar.com/sql/virtualization-best-practices/.

Reference: Tab Navigation

2010-10-15T17:36:00.001-04:00

I'm always looking for ways to improve navigation. Tab navigation can be useful sometimes, depending on the situation. The resources below are helpful when exploring tab navigation options with SharePoint 3.0 and SharePoint 4.0.

Easy Tabs 5

Tab Navigation using CSS only

Reference

Humbert, C. (August, 2010). Easy Tabs Version 5.0. Retrieved October 15, 2010 from http://www.pathtosharepoint.com/sharepoint-user-toolkit/Pages/Easy-Tabs-v5.aspx.

Solomon, H. (August, 2005). Tab Navigation using CSS only - Great for SharePoint. Retrieved October 15, 2010 from http://heathersolomon.com/blog/archive/2005/08/10/1434.aspx.

SharePoint Saturday Boston #3 Webinar Series

2010-10-15T08:46:00.003-04:00

The SharePoint Saturday Boston #3 Webinar Series schedule was recently announced. As part of this series, I will be presenting "Implementing SharePoint for Enterprise Search: Methodology and Mechanics" on Friday, December 10, 2010 at 11:45 AM.

Click Here to Register

Agenda
11:45 AM EST – 11:55 AM EST Welcome and Sign-In
11:55 AM EST – 12:00 PM EST Speaker Introduction
12:00 PM EST – 1:00 PM EST Presentation

For more information or to register for other Webinars, visit the SharePoint Saturday Web site, SharePoint Saturday Boston #3 Webinar Series: http://www.sharepointsaturday.org/boston/Pages/SPSBos3WebinarSeries.aspx

Reference: Location Codes

2010-10-14T15:52:00.003-04:00

I was doing some ETL work today and needed to translate location codes from one system to another. These resources were helpful in creating a reference table.

Official USPS Abbreviations

List of U.S. States by Time Zone

Reference

United States Postal Service (2010). Official USPS Abbreviations. Retrieved October 14, 2010 from http://www.usps.com/ncsc/lookups/usps_abbreviations.html.

Wikipedia (2010). List of U.S. States by Time Zone. Retrieved October 14, 2010 from http://en.wikipedia.org/wiki/List_of_U.S._states_by_time_zone.

SharePoint 4.0: How Search Indexing Works

2010-10-05T18:37:00.010-04:00

The crawl process is essential to the Indexing side of SharePoint 2010 Search. Exploring the Search Service Application screens provides some insight to the configurable components that make up Search in SharePoint 2010, but you may actually have to dive deep into the system documentation and other resources to gain an understanding for the steps that occur within the subsystems, when SharePoint is instructed to crawl content.

The crawl process goes something like this:
1. Full crawl started
2. Start address moved to queue
3. Protocol determined
4.Connector selected
5. iFilter opens files
6. Content index created on crawl server
7. Index moved in batches to query server
8. Data written to Crawl and Property databases
(Microsoft, 2010)

One myth about SharePoint 2010 crawl process is that when content is crawled it never touches the file system of the Crawl Server and goes directly to Query Server...this isn't true. The way it works in environments that have crawler and query roles on separate servers is; a content index is built on the crawl server initially, but is moved in batches to the query server(s). The point when all batches have propogated to the query server, then it may appear as if there is no foot print on the Crawl server's file system...this is because all the batches have been moved up.

From a server topology perspective, Search requires three different server roles. These include Crawl Server, Query Server, and Database Server. Each of these roles plays a role in the crawl process. For scalability and availability, the architecture supports configurations that include one or many of each of the server roles. Determining the best topology is a balancing act of capacity requirements with available resources.

Reference

Microsoft (2010). Microsoft SharePoint 2010 Product Information Capabilities Search. Retrieved September 22, 2010 from
http://sharepoint.microsoft.com/en-us/product/capabilities/search/Pages/default.aspx.

Enterprise Search Summit Fall 2010

2010-10-01T08:02:00.002-04:00

There will be an Enterprise Search Summit in Washington D.C. November 16-18, 2010. The event is taking place at the Renaissance Washington, DC Hotel.

For more information, click here.

SPS Boston: Implementing SharePoint for Enterprise Search: Methodology and Mechanics

2010-09-30T22:28:00.011-04:00

On Saturday, September 25, 2010 I presented a session at SharePoint Saturday Boston.

Title:
Implementing SharePoint for Enterprise Search: Methodology and Mechanics

Abstract:This session explains how following a proven approach and using certain configuration techniques can ensure the success of a SharePoint Search implementation. The prevalence of search technologies available on the World Wide Web has caused stakeholder expectations to remain high. Yet, an Enterprise Search solution is an excellent opportunity to introduce exciting capabilities and productivity gains for a business. Included in the presentation is a walk-through of project phases, a review of key design considerations, and examples of recommended configurations.

Click HERE to access slides.

In the near future, I do intend to create individual blog posts from some of the presentation slides so that I can expand on some of the topics in greater detail. If you would like to request that I write a blog post explaining a particular Search topic, please submit a request using the comments feature of this post.

Microsoft Project 2010: Outline Number and Fill Down

2010-09-08T19:36:00.006-04:00

I was recently updating a Microsoft Project file and encountered a couple items worth mentioning.

First, by inserting a column called "Outline Number," Project automatically populates the Work Breakdown Structure (WBS) task ID (WBS column does the same thing). This is much better than doing it manually.

Secondly, Microsoft Project doesn't let you paste a value into a range of cells like Excel. So, instead of manually typing in durations or pasting one at a time, there is a "Fill Down" menu option. Select the cell that contains the value you want, select the range, right-click, and select "Fill Down."

This will fill in the range with the source value.

Why Move to SharePoint 2010?

2010-08-05T08:33:00.003-04:00

From a technology road map perspective, I think it makes sense to migrate to the SharePoint 2010 platform to be current with technology. Doing so extends the lifespan of platform support and work efforts by three years (typical product cycle). The 2010 platform provides a more stable and scalable architecture too. Furthermore, innovation in the community occurs with the most current version, so to participate in the knowledge sharing on the Web, at events, and conferences, it requires remaining current.

Beyond these reasons, business needs continue to evolve and mature. The product features of the latest version enable the delivery of better solutions, with less effort, with less customization. Aggregating information from different systems is easier now (Search, BCS). It is easier to provide end user conveniences, such as Outlook calendar integration or multi-select actions in document libraries. Branding is easier with the themes engine. There are more Search tools (e.g. navigators) available, allowing search experiences to be more like what people expect from using Web. In fact, the 2010 Search technology is rich enough to use as a development tool. Taxonomy and Folksonomy features help make organizing and navigating through content easier, while Managed Metadata Services help ensure consistency.

Different scenarios require different thought processes and approaches to 2010. For example, existing SharePoint Web sites which are flat and primarily exist to push Web content to many consumers, may benefit from a straight software upgrade. On the other hand, redesign opportunities exist for other types of SharePoint applications which are more interactive; which support business processes or facilitate workflows.

At this point, it makes sense to design and develop anything new directly in 2010, to take advantage of the technology and community benefits. Doing so also reduces duplication in efforts since there will not be a future need to upgrade the new solutions to 2010; they will already be there. That, by itself, is a legitimate reason to go 2010.

Reference

Microsoft (2010). SharePoint 2010 Product Information Overview. Retrieved August 5, 2010 from http://sharepoint.microsoft.com/en-us/product/capabilities/Pages/default.aspx.

Missing the Point on Spirit of Governance

2010-08-04T18:28:00.007-04:00

Over a short period of time in the SharePoint community, the term "governance" has evolved to describe a class of software products or features. Yet, IT governance has nothing to do with what tools a SharePoint administrator has. Instead, IT governance has everything to do with the people and processes side of things; and the decision making framework that, when in play, can be used to determine that a portal should exist, who should manage it, who it should serve, how decisions will be made affecting it. Governance is really about policies, processes, roles, responsibilities, and priorities (Ross, 2004).

The scope of an effective Information Management Governance Model spans beyond a specific solution, such as SharePoint Intranet or collaboration portal, and encompasses the Information Management practices occurring throughout the organization. A SharePoint governance model should be a subset to that. Putting this in the context of documentation, an overarching Information Management Statement of Governance document should exist and define the framework at the global level, while specific statement of governance documents should be maintained for each Information Management system within the organization; SharePoint being one of those.

The IT project management framework is another significant and relevant topic to governance. The project management framework established the processes followed to initiate, plan, and execute IT projects. These processes should include such activities as the evaluation of new SharePoint projects in the context of the organization's overall information architecture. Aligning the project management decision making with Information Management, business, and IT decision making results in solutions that have backing, are sustainable, and actually provide business value.

The spirit of governance is really about defining what the processes should be, and if generous enough, explaining why to some extent. In the end, governance models maintain decision making integrity amongst people...that is not something a portal administrator can do by running a report or recovering a deleted site.

Reference

Ross, J., Weill, P. (2004). Recipe for Good Governance. Retrieved August 4, 2010 from http://www.cio.com/article/29162/Recipe_for_Good_Governance.

Event: SharePoint Saturday Boston 2010

2010-07-30T20:49:00.005-04:00

SharePoint Saturday Boston, 2010 (#3)

When:
Saturday, September 25th, 2010

Where:
Microsoft Corporation

201 Jones Road

6th Floor

Waltham, MA 02451

Call for Speakers:

http://www.sharepointsaturday.org/boston/Pages/speakers.aspx/

Three SQL Server Settings for SharePoint Environments: Autogrowth Option, Auto Shrink Option, Shrink Database Task

2010-07-30T18:21:00.013-04:00

As I was tuning a SharePoint environment today, I thought it would be a good opportunity to post a brief message about three SQL Server settings: Autogrowth, Auto Shrink, and the Shrink Database Task.

1. Autogrowth - Fixed Amount:

This setting applies to data files (.mdf) and transaction log files (.ldf). Autogrowth allows or prevents SQL Server from automatically increasing the size of the files when the need arises. In SharePoint environments, it is best to do capacity planning in advance and set the intial database sizes appropriately. Then, set the Autogrowth value for both the data files and the log files to a fixed amount. This ensures that the files grow in consistent increments. The fixed amount should be somewhat substantial, relative to the size of the database. This ensures that the growth does not occur too frequently.

2. Auto Shrink - Turn it Off:

Auto Shrink is an option that allows or prevents SQL Server from automatically reducing the size of database files. By default, the SQL Server Model database has the Auto Shrink option off. As Paul Randal points out, enabling Auto Shrink can lead to Auto-Grow, Auto-Shrink loops as well as database fragmentation, and other performance issues (Randal, 2007). As a general rule of thumb for most SharePoint environments, this option should remain off for system and content databases.

3. Shrink Database Task - Don't Schedule It:

The Shrink Database Task is an available Maintenance Plan Task. If set, this operation will reduce the size of a database according to a schedule, leaving a specified amount of free space. As with the Auto Shrink option, the Shrink Database Task leads to performance issues and is not recommend in SharePoint environments.

So, if an existing SharePoint environment does have a scheduled Shrink Database Task, then a suggested action would be to remove the Shrink Database Task and then plan to monitor and manage database size using a manual approach. When determining a plan for managing database size, it is important to keep Database Recovery Models in mind.

Reference

Randal, P. (August, 2008). Top Tips for Effective Database Maintenance. Retrieved July 30, 2010 from http://technet.microsoft.com/en-us/magazine/2008.08.database.aspx?pr=blog.

Randal, P. (March, 2007). Turn AUTO_SHRINK off!! Retrieved July 30, 2010 from http://blogs.msdn.com/b/sqlserverstorageengine/archive/2007/03/28/turn-auto-shrink-off.aspx.

Why Information Silos Are So Persistent

2010-07-27T16:45:00.005-04:00

Information silos are disparate entities that exist as rogue systems, utilities, spreadsheets and Access databases. Actually, an information silo might be anything that is not centrally managed or does not conform to existing design patterns. Silos may or may not be considered an official part of the enterprise...awareness about the silo doesn't change its definition.

Most of the time, these tools were developed to fill a gap. A gap between what the enterprise offers and what certain areas of the business actually need to function. They serve a purpose; and in many cases they are significant to the processes that they support.

Considering where technology is today, why are are information silos so persistent, more prevalent than ever? Why can't IT just build something into the enterprise architecture?

One reason (or cause) is because of the technology, which has become easier to work with and more accessible to people inside and outside of IT Departments. A person of any role can go on the Internet and figure out how to set up an Access database. In many cases, this is much easier than approaching a centralized IT department with their requirements. The Internet isn't going to say "no." By circumventing IT, nobody asks for funding, tries to minimize or question the need, or compromise the intention in any way. But, if the request did go to the IT department might, there might be resistance.

Secondly, a rogue solution is much less risky for a business person in terms of exposure and process transparency. By setting up a tool of their own, a business person may struggle a bit with configuration, but at no point is their process going to be visible to other people for criticism. If the person was to bring their requirements to the table and ask for help, then a lot of questions might be asked, putting guarded knowledge at risk. Unfortunately, for protective types, this means that the process would, in fact, become more transparent. The original process owner would become a "stakeholder" with influence rather than an "owner" with full control.

Beyond that, information silos also exist when an organization's methodologies and practices for providing holistic solutions are not mature enough to truly help. For example, IT organizations which are disorganized and reactive, might not be capable of helping the business person with their needs. There's no process, no authority, no plan to handle this sort of thing.

All of these situations challenge a centralized Information Management strategy.

General Business Requirements vs. Solution Requirements

2010-07-24T14:14:00.002-04:00

What came first, the solution or the need? Let's hope the need, but we all know that is not always (often not) the case. With the great technologies available to us today, rapid application development enables us to solve problems. But, does the ease of development actually create a new set of problems? Yes, it does.

When the software development process is lengthy and drawn out, it forces many planning activities such as requirements analysis, design specifications, and planning. Not doing these things leads to costly adjustments later. The lengthy process also forces organizations to really think about what solutions they are developing and how these solutions fit into the big picture. We've got it pretty easy today. With portals, collaboration, search, BI, content management, and workflow platforms today, some times doing it "wrong", undoing it, and doing it again is actually less expensive than the cost of planning and documenting.

Yes, I am familiar with the twelve principles of the Agile Manifesto (Agile Alliance, 2001). I like agile development when it follows some organized processes and produces artifacts that can be used for reference later. You still need documentation for future development, disaster recovery, and repair.

However, what I don't like is "rapid solutioning" or the practice of directly jumping from a problem to a solution design without any sort of further questioning, analysis, thought, or sanity checks. When you encounter a problem, and immediately form a solution and begin developing it, a lot is lost. You are not considering what other stakeholder needs are, what other colleagues are already working on, and how this "fly by the seat of your pants" solution actually fits in (or doesn't) into your overall information architecture.

Working with my colleagues, we recently began formalizing our thoughts around the solutioning process. One of the first roadblocks we encountered had to do with semantics. We began observing that our push for "requirements" was being misunderstood. When a problem-solution situation arose, we would explain that we needed to analyze requirements. The response to this typically included design specifications. We would then stop and say, no, we don't want detailed design specifications, what we want is to understand the problem better and understand how it impacts other people, so we can create a solution that will fit into our information architecture in a way that adds value and doesn't undermine anything else we are doing.

After a few more of these scenarios we decided that we had to make others aware of our solutioning process and how we think, so that everybody would be able to communicate with each other better. The first thing we did was make a distinction between the types of requirements that we would discuss in the course of solutioning.

We decided on the following:

General Business Requirements - Facts and opinions that help understand the problem better. These are not design specifications and do not explain a solution. Instead, this information explains what the business needs are.

Solution Requirements - Facts and opinions that define how a solution is supposed to look, feel, or act. This information directly dictates the design specifications.

So, now when a new request arises, we start by gathering "general business requirements." We then consult with stakeholders, policies, procedures, standards, goals, etc. and analyze the information. Once we have all the facts, we begin to design a solution. At that time, we ask stakeholders to help us define the "solution requirements." The result of the latter activity is a design specifications document. Next, we schedule and plan the development activities and proceed from there.

Reference

Agile Alliance (2001). Principles Behind the Agile Manifesto. Retrieved July 24, 2010 from http://agilemanifesto.org/principles.html.

SharePoint 4.0: Summary Links Data Column Type

2010-07-22T09:15:00.009-04:00

In SharePoint, there is a column type called, "Summary Links Data." Microsoft desribes this column type as "Columns that represent summary links for a page. Summary Links include a title, description, image, and URL and are used on publishing pages to present grouped links by using a set of shared styles" (Microsoft, 2010).

This column type is brilliant in theory, but unfortunately they don't appear to work as expected. Here is my assessment of the Summary Links Data column type.

In SharePoint 2010, if I add a Summary Links Data column to document library, then add a new document, the new or edit document properties page looks correct. The Summary Links Data column is represented by an editable summary links control.

However, after the links have been added and the document uploaded, you return to the document properties using the "View Properties" page. The result of this is that the links are not visible. Huh?

OK, so let's try a custom list. Added the column to a custom list. Adding or editing an item results in a non-editable field. So, the Summary Data List story just got even worse in custom lists...

Reference

Microsoft (2010). Create a site column. Retrieved July 22, 2010 from http://office.microsoft.com/en-us/sharepoint-server-help/create-a-site-column-HA010177759.aspx.

Site Columns: SharePoint 2010 vs. SharePoint 2007

2010-07-22T08:26:00.005-04:00

When comparing the "create site column" screen of SharePoint 2010 versus the one in SharePoint 2007, the features are mostly similar except for three enhancements in 2010. These include:

1. Column types for Rich Media and Managed Metadata.
2. "Enforce unique values."
3. Column validation.

(Microsoft, 2010)

During the past few years, I do remember occasions when I was "wishing" for the ability to apply unique permissions at the site column or content type level, but these abilities are not something available in SharePoint 2010.

I imagine field level or content type security would require a more dynamic design at the list and library level, since the list and libraries still work off the static template model, storing their own column definitions in XML as they were defined at the time of list or library creation, and maintaining their own security settings. This is evident when you delete a site column that is being used in a list or library. The site column is removed from the site column gallery, but a local instance of it still remains on the list or library.

In order for field level or content type security to be possible in SharePoint, each site column and local column definition would need to be expanded to include a security definition. List and library views would also need to become more security aware, rendering different columns based on varying security contexts. So, pushing down unique site column or content type security is more than the platform can handle at this time.

Microsoft SharePoint Server 2010

Microsoft Office SharePoint Server 2007

Reference

Microsoft (2010). Create a site column. Retrieved July 22, 2010 from http://office.microsoft.com/en-us/sharepoint-server-help/create-a-site-column-HA010177759.aspx.

Microsoft (2010). Introduction to Columns. Retrieved July 22, 2010 from http://msdn.microsoft.com/en-us/library/ms450825.aspx.

Fiddler

2010-07-21T08:54:00.011-04:00

A gentleman named Eric Lawrence has developed a very useful Web debugging tool named, Fiddler. The Fiddler Web site is http://www.fiddler2.com/fiddler2/version.asp. I've used this tool recently to pinpoint performance issues, security issues, and authentication issues.

"Fiddler is an HTTP debugging proxy written by Eric Lawrence of Microsoft.[1] It seamlessly captures HTTP traffic and logs it for the user to review.[4] It can also be used to "fiddle" with HTTP traffic as it is being sent.[3] By default, traffic from Microsoft's WinINET HTTP(S) stack is automatically directed through Fiddler at runtime, but any browser or application can be configured to route traffic through Fiddler.

The new version, known as Fiddler2, offers support for interception and tampering with HTTPS traffic." (Wikipedia, 2010)

To install Fiddler, follow these steps:

1. Download Fiddler.
2. Run the setup.exe.

To run a trace, follow these steps:

1. Open Fiddler (Start > All Programs > Fiddler2).
2. Begin a trace (File > Capture Traffic).
3. Launch Internet Explorer and produce the activity you would like to trace.
4. Stop the trace (File > uncheck Capture Traffic).
5. Save the trace file (File > Save > All Sessions).
6. Now, you are able to analyze the activity and pinpoint issues. You may also consider comparing the Fiddler trace to the Application Event log from the client and server machines.

Reference

Lawrence, E. (2010). Fiddler2 - Installation Information. Retrieved July 20, 2010 from http://www.fiddler2.com/fiddler2/version.asp.

Wikipedia (2010). Fiddler (software). Retrieved July 20, 2010 from http://en.wikipedia.org/wiki/Fiddler_(software).

Microsoft Certifications for SharePoint 2010

2010-07-21T08:16:00.002-04:00

For the 2010 generation, the Microsoft SharePoint certifications tracks have been enhanced. Below is a breakout of the certifications available.

Microsoft Certified IT Professional (MCITP): SharePoint Administrator 2010

70-668 PRO: SharePoint Server 2010, Administrator
http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-668

70-667 TS: Microsoft SharePoint 2010, Configuring
http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-667

Microsoft Certified Professional Developer (MCPD): SharePoint Developer 2010

70-576 PRO: Designing and Developing Microsoft SharePoint 2010 Applications
http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-576

70-573 TS: Microsoft SharePoint 2010, Application Development
http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-573

Microsoft Certified Master program (MCM)
http://www.microsoft.com/learning/en/us/certification/architect.aspx

Microsoft Certified Architect certification (MCA)
http://www.microsoft.com/learning/en/us/certification/master.aspx#tab2

Reference

Microsoft (2010). Microsoft SharePoint – Training Portal. Retrieved July 21, 2010 from http://www.microsoft.com/learning/en/us/training/sharepoint.aspx.

Prometric (2010). Microsoft Certifications. Retrieved July 21, 2010 from http://www.prometric.com/Microsoft/default.htm.

Connected Lookup on Codeplex

2010-07-12T18:38:00.004-04:00

It is called many names; Connected Lookup, Cascading Dropdowns, Dependencies, etc. Whatever the nomenclature, the requirement to have one choice column drive the choices in a another choice drop down is an extremely common requirement in SharePoint applications.

There is a Codeplex project that I discovered today, for WSS 3.0 and MOSS 2007. I've pretty much halted future development on MOSS 2007 at this point but I thought I'd post the link regardless.

Reference

Codeplex (2010). SharePoint Connected Lookup. Retrieved July 12, 2010 from http://cl.codeplex.com/.

Link: Process Monitor

2010-07-06T15:44:00.007-04:00

Microsoft offers Process Monitor as a free download. In short, this tool helps capture detailed events and isolate issues. I recently used Process Monitor when I encountered a performance issue with one of my portals; the default.aspx page was taking a long time to save. Process Monitor helped me isolate the issue and determine that the cause was a buffer overflow.

Reference

Microsoft (2010). Windows Sysinternals, Process Monitor v2.91. Retrieved July 6, 2010 from http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

SharePoint Datasheet View, Office 2010 Compatibility

2010-06-25T20:10:00.011-04:00

When considering when to upgrade to Microsoft Office 2010 on your client machine(s), there are many considerations, one of those being the level of compatibility of between the Office Suite and SharePoint Server 2010 and/or SharePoint Server 2007.

As it stands, Microsoft Office 2010 Standard Edition lacks many key compatibility features with SharePoint Server, while the Editions such as Office Professional and Office Professional Plus offer much more (Microsoft, 2010). One of the most important usability features of compatibility is the ability to manage information inside SharePoint lists and libraries is datasheet view. I know that once this feature is adopted by a user base, it is not something that can be taken away because people rely on on datasheet to manipulate data fast and easy.

Regardless of whether Office 2010 is 64-bit 0r 32-bit, the edition of office must be ABOVE STANDARD. This means that if you have Office 2010 Standard, you DO NOT have datasheet view. I cannot imagine having a SharePoint environment in which I do not have access to datasheet view, and so I would base my decision on which Office Suite to use solely on datasheet view...in other words, Office 2010 Standard is dead to me and I only care about Professional and higher from this point forward.

In the process of upgrading my primary client system to Office 2010 Professional Plus, I also had to decide between 64-bit and 32-bit. 32-bit is still recommended for maximum compatibility with add-ins and third party products, while 64-bit is intended for individuals who are working with large amounts of data (Microsoft, 2010). 32-bit is also more convenient to run. Datasheet view is automatically available to use if you have Microsoft Office 2010 (above Standard Edition) 32-bit. Datasheet view isn't automatic for 64-bit though, as evident by this error message:

Error: "The list cannot be displayed in Datasheet view for one or more of the following reasons:..."

To make my life as complicated as possible, I decided to go with 64-bit. So, how is does 64-bit Office 2010 complicate the datsheet view capability? Well, I quickly learned that as of the 64-bit flavor of Office 2010 has additional requirements in order for datasheet view to be available. After installing the 64-bit Office suite (remember, must be Standard Edition or higher), you must do one of the following, in order to avoid the obnoxious pop-up error above:

A. Download and install the 2007 Office System Driver for Data Connectivity Components.

B. Install the 2007 SharePoint Services Support, which is available on the Microsoft Office 2007 installation media.

Reference

Microsoft (2010). 2007 Office System Driver: Data Connectivity Components. Retrieved June 28, 2010 from http://www.microsoft.com/downloads/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en.

Microsoft (2010). 64-bit editions of Office 2010. Retrieved June 28, 2010 from http://technet.microsoft.com/en-us/library/ee681792.aspx.

Microsoft (2010). Compare server integration features between Office suites available through volume licensing. Retrieved June 28, 2010 from http://office.microsoft.com/en-us/buy/compare-server-integration-features-between-office-suites-available-through-volume-licensing-FX101850719.aspx.

Microsoft (2010). Compatibility Between the 32-bit and 64-bit Versions of Office 2010. Retrieved June 28, 2010 from http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx.

Microsoft Office 2010: About 64-bit

2010-06-25T20:04:00.004-04:00

As the computer industry as a whole is evolving 64-bit to the de facto standard, even for client systems, we seem to be at a cross roads with this next wave of Microsoft Office products where we still need to choose between 64-bit or 32-bit.

One important thing to be aware of is that running 64-bit AND 32-bit versions of Microsoft Office on the same operating system is not supported. Here are some links that provide information about the 64-bit version of Office 2010 as well as information about compatibility in general.

Microsoft TechNet: 64-bit editions of Office 2010

Microsoft TechNet: Application compatibility assessment and remediation for Office 2010

Reference

Microsoft (2010). 64-bit editions of Office 2010. Retrieved June 25, 2010 from http://technet.microsoft.com/en-us/library/ee681792.aspx.

Microsoft (2010). Application compatibility assessment and remediation for Office 2010. Retrieved June 25, 2010 from http://technet.microsoft.com/en-us/library/ff394407.aspx.

SharePoint 3.0: Command for Forcing Hotfix Installation

2010-06-17T14:41:00.003-04:00

From "%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin", run this command:

psconfig.exe –cmd upgrade –inplace b2b –force

Reference

Microsoft (2010). Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Office SharePoint Server). Retrieved June 17, 2010 from http://technet.microsoft.com/en-us/library/cc263093(office.12).aspx.

Links: Microsoft Licensing Information for SharePoint 2010

2010-06-14T09:45:00.003-04:00

Microsoft SharePoint 2010 Licensing
http://sharepoint.microsoft.com/en-us/buy/Pages/Licensing-Details.aspx

Microsoft SQL Server 2008 Licensing
http://www.microsoft.com/sqlserver/2008/en/us/licensing.aspx

Microsoft Windows Server 2008 Licensing
http://www.microsoft.com/windowsserver2008/en/us/licensing-R2.aspx

SharePoint 4.0: Attach Content Database to Web Application

2010-06-02T10:12:00.004-04:00

An especially important administrative capability for disaster recovery, upgrading from SharePoint 3.0, and general administration of Web applications is the ability to attach a content database to a Web application.

Here are the steps:

1. Attach the content datbase to the SQL Server instance. If moving a content database in from a different farm, then this may require doing a SQL Server database restore. Be sure that the MDF and LDF files are created in a location which is consistent with your other content datbases.

2. Open PowerShell. With the security context of an administrator account having shell access, open PowerShell on a SharePoint 2010 server.
Start > Administrative Tools > SharePoint 2010 Management Shell

3. Test the content database.
Type the following command:
Test-SPContentDatabase -Name %ContentDbName% -WebApplication %WebApplicationName%

4. Attach the content database to SharePoint Web Application.
Type the following command:
Mount-SPContentDatabase -Name %ContentDbName% -WebApplication %WebApplicationName%

5. Verify the attached content database. Navigate to SharePoint Central Administration > Application Management > Manage Content Databases. Verify the database name, database status, and current number of site collections. If necessary, adjust the Site Collection Level Warning and Maximum Number of Site Collections settings appropriately.

Reference

Microsoft Technet (2010). Add a content database (SharePoint Server 2010). Retrieved June 2, 2010, from http://technet.microsoft.com/en-us/library/cc825314.aspx.

Three Nice Enhancements to the Send To Functionality of SharePoint in 2010

2010-06-01T18:21:00.002-04:00

1. Multiple connections. In 2007, you could only configure one Sent To (presumably a Records Center) location per farm. In 2010, you can configure multiple Send To Connections.

2. Turn on or off manual submission from the Send To menu. For each configured Send To connection, you can check a box to either enable or disable this location from appearing in the context menu of a document.

3. Sent To action. Last but not least, for each configured connection, you can configure the Send To action to be copy, move, or move and replace with link. If you can remember in 2007, this was a mighty gap that required some workflow trickery to make it practical. Now we have some out of box comfort.

Thoughtful Quote

2010-05-24T19:17:00.003-04:00

"To make knowledge work productive will be the great management task of this century, just as to make manual work productive was the great management task of the last century."

- Peter Drucker, 1978

How Communication Gaps Can be Viewed as Opportunity for Business Analyst Function

2010-05-21T19:45:00.011-04:00

I find myself analyzing things quite a bit throughout the day. Some people accuse me of thinking too much. I don't know, it is just a natural thing I do, I guess. I ponder a lot.

One thing I ponder about from time to time is the impact that words have on work, people, and communications in general. Words are very significant in my profession. Words appear everywhere. In Web portals, they are used to instruct people how to use the Web site or how to perform a function. In presentations, words are used to concisely deliver a big message, one little message at a time. A funny thing about words is how they conjure up different emotions and different meanings to different people.

So, how does all of this relate back to the theme of this blog? Well, UX topics aside, there are some interesting behavioral patterns that I recently noticed, because I had been fixated on words. Recently, I happened to be observing a debate between colleagues, regarding the best way to configure a feature of a new Learning Management System (LMS). For background, this LMS Web application is intended to deliver courses and track professional development information for employees. It happens to be a third party product.

During the course of debates I realized that there is a distinct difference between the way that the software developer interpreted the name of a software feature versus the way that a business stakeholder interpreted it, in the context of them working together on the system implementation. Both individuals were working together, exploring how the third party application works, and trying to figure out the best way to leverage the product in order to meet the business requirements.

During this adventure, the two individuals came across a product feature called "curriculum." Here is the behavior that I noticed:

The software developer evaluated and experimented with the "curriculum" feature and tried to figure out different ways to use the feature in order to meet the business requirements.

The business stakeholder, performing the same experiment, forcefully attempted to make the software behave as they understand the word "curriculum" to mean in normal business context.

The two individuals then reached a disagreement when the software developer offered various options for how the feature could be used, while the business stakeholder argued that "no, a curriculum means this and so it must only be used like this." Not only did the two disagree on what the word means in general business context, but both also disagreed on the appropriate way to approach the software configuration task.

Do you see the distinction?

The software developer views the "curriculum" not for what the label means, but for what the actual program capability is and how it interacts with other related capabilities in the system. On the other hand, the business stakeholder had a fixed idea because of the label.

What is the point of all of this? Business analysis. A business analyst function is extremely important on a Web application project. Whether this function is performed by a dedicated expert, absorbed and performed by the project manager (or other resource), there needs to be a person who can understand the business requirements while also understanding the developers' way of thinking so that these two perspectives can be united and a common goal can be met.

SharePoint 4.0: Formula for Estimating Content Database Size

2010-05-13T16:32:00.002-04:00

Formula

((D × V) × S) + (10 KB × (L + (V × D))) = C

C = Database Size in KB
D = # Documents * 3
L = # List Items
S = Average size of documents in KB
V = Average # Versions in a Document Library (Greater than 0)

Reference

Microsoft (2010). Storage and SQL Server capacity planning and configuration. Retrieved May 13, 2010 from http://technet.microsoft.com/en-us/library/cc298801(office.14).aspx.

Links: MSDN Ramp Up Track, SharePoint for Developers

2010-05-12T16:18:00.002-04:00

Microsoft has a Ramp Up program on MSDN, to help facilitate learning and professional development, http://msdn.microsoft.com/en-us/rampup/default.aspx. There are some interesting tracks, including the following ones related to SharePoint:

MSDN Ramp Up Track, SharePoint for Developers Part 1
http://msdn.microsoft.com/en-us/rampup/dd221355.aspx

Introduction to Web Parts
Data Lists for Developers
Programming Event Handlers
Workflow in SharePoint
Silverlight and SharePoint

MSDN Ramp Up Track, SharePoint for Developers Part 2
http://msdn.microsoft.com/en-us/rampup/dd320759.aspx

Page Navigation – Integrate navigation into your SharePoint application
Page Branding – Brand a SharePoint site to look like your existing web application
Web Services – Access list data using built-in web services
Custom Content Types – Implement behaviors from different document types
User Management – Manage web site users without code

Links: Microsoft SharePoint 2010 Launch Event

2010-05-12T09:48:00.003-04:00

Microsoft SharePoint 2010 Launch Event
http://sharepoint.microsoft.com/2010launch/en-us/Pages/home.aspx

Webcast
May 12, 2010
11:00 AM EDT
Keynote to be delivered by Stephen Elop.

Links: SQL Server Reporting Services (SSRS) SDK for PHP

2010-05-11T16:28:00.006-04:00

Here are some references for information on interoperability between SQL Server Reporting Services and PHP:

Interoperability Bridges and Labs Center
http://www.interoperabilitybridges.com

SQL Server Reporting Services (SSRS) SDK for PHP
http://www.interoperabilitybridges.com/projects/sql-server-reporting-services-sdk-for-php

SQL Server Reporting Services (SSRS) SDK for PHP on Codeplex
http://ssrsphp.codeplex.com/

(Microsoft, 2010)

Reference

Microsoft (2010). SQL Server Reporting Services SDK for PHP. Retrieved May 11, 2010 from http://www.interoperabilitybridges.com/projects/sql-server-reporting-services-sdk-for-php.

SharePoint 3.0: Setting Default Expires Date on Announcements

2010-05-11T14:23:00.005-04:00

Description:

When using the out of box Annoucements web part in SharePoint 3.0, items do not have a default value. For practical purposes, when using the web part in sites, it usually makes sense to limit the number of announcements that display in the view that is positioned on the Web page.

So, in order to limit the items in a view, it makes sense to use sorting on a field such as Expires in conjunction with an item limit on the view. And, if you are going to sort (on Expires), you need to make sure that all items have a value to be sorted on. Otherwise, those items lacking the Expires won't appear.

Solution:

An easy way to ensure that all items have an Expires date is to set the default value of the column. To do this, navigate to the Announcements list, to Settings, List Settings. In the "Additional Column Settings" area, set the "Default Value" to a "Calculated Value" of =[TODAY]+60. This will default the Expires date to be sixty days from when the announcement item is cerated.

User Experience (UX) in Web Portals

2010-04-29T19:58:00.005-04:00

Planning and executing information management projects accounts for a major portion of the overall effort. However, there is still quite a bit of time that is required to be spent on refining and communicating concepts to colleagues and to the business. Perceptions about why you are developing a portal or system and what it will look like have a tremendous amount of impact to the success of a project.

User Experience tends to be one of the facets of information system design that draws quite a bit of controversy because it is very subjective. Combining information architecture concepts, system capabilities, features, security models, business requirements, functional requirements, standards, and policies to develop a design will get you most of the way there. However, there are still some very volatile aspects to the design process; these include emotion and perception.

The measure of user experience of a system is highly subjective. People's attitudes, situations, level of knowledge, and other factors produce an emotional response every time the person uses the system. Although I have lots of past experiences, projects, and communications to draw from for guidance on how best address matters related to UX debates; I've decided that I really need to collect some factual information to keep in the toolbox. I think that behavior studies, polls, statistics, and other sources of research are required to build a solid fact base to support decision making. It is simply not good enough to speculate how people think and how people will respond to a particular system design.

I plan to invest some time in this topic and then reflect on my findings in subsequent posts.

Sample Sizing Estimate for SharePoint Server 2010 Search Environment

2010-04-27T15:26:00.006-04:00

Below is a sample search storage estimate for environment with 500GB content databases. This was calculated by adding up the sum of MDF files. There are so many considerations for storage, and this is just a rough sketch of the storage aspects related to the Search Service Application. This does not consider base installation overhead nor does it factor in other SharePoint Service Applications (SSA), Office integrations, User Profiles, Usage Database, PowerPivot, etc..

1.
ContentDBSum = Measure the size on disk of MDF files. For this example, 500 GB.

2.
IndexTotalIndexSize = ContentDBSum * .035 or 17.5 GB
QueryComponentIndexSize = TotalIndexSize / Number of Index Partitions
StorageQueryComponentIndexSize * 3 single query component with space for index merging
QueryComponentIndexSize * 4 single query component with space for index repartioning or 70 GB

3.
TotalPropertyDBSize = ContentDBSum *.015 or 8 GB
TotalPropertyDBLogSize = ContentDBSum *.0031 or 2 GB

4.
TempDBSize = TempDBSizeContentDBSum * .00034 or 1 GB

5.
TotalCrawlDBSize = ContentDBSum *.046 or 23 GB
TotalCrawlDBLogSize = ContentDBSum *.011 or 6 GB
ContentDBSum *.011 = TempDBSize = 6 GB

6.
SearchAdminDBSize = # items in index * .3 or override as 5 GB
In this case, I don't know how many items there will be in the index so I am going to allocate 5GB.

7.
Backup Size = basically, add all of the database sizes together.

Reference

Microsoft Technet (2010). Performance and capacity test results and recommendations. Retrieved April 27, 2010 from http://technet.microsoft.com/en-us/library/ff608068(office.14).aspx.

Links: Planning SharePoint Server 2010 Search

2010-04-26T09:00:00.005-04:00

(1 of 4) Microsoft: Search Technologies for SharePoint 2010 Products
http://www.microsoft.com/downloads/details.aspx?familyid=D7C0091E-5766-496D-A5FE-94BEA52C4B15&displaylang=en

(2 of 4) Microsoft: Search Environment Planning for Microsoft SharePoint Server 2010
http://www.microsoft.com/downloads/details.aspx?familyid=5655EACA-22DF-4089-BCD3-38A1F5318140&displaylang=en

(3 of 4) Microsoft: Search Architectures for Microsoft SharePoint Server 2010
http://www.microsoft.com/downloads/details.aspx?familyid=22FFC029-2C08-457D-8311-CA457C6D160E&displaylang=en

(4 of 4) Microsoft: Design Search Architectures for Microsoft SharePoint Server 2010
http://www.microsoft.com/downloads/details.aspx?familyid=5A3CA177-FB9A-4901-9797-0C384277DB7C&displaylang=en

Windows Server 2008 R2 Data Center VS Enterprise

2010-04-23T19:29:00.007-04:00

Here is a quick overview when comparing Windows Server 2008 R2 Datacenter vs. Enterprise. Based on the licensing model for Windows Server 2008 R2, it may be more cost effective for many virtual infrastructure environments to license Datacenter Edition rather than Enterprise Edition. Furthermore, the hot pluggable hardware features of Datacenter Edition may be a key discriminator.

Role: No difference

Core Installation Features: No difference

Features: No difference

Technical Specifications: See Below

Datacenter
· hot add processors
· hot replace memory
· hot replace processors
· Virtual image use rights = Unlimted
· X64 sockets = 64

Enterprise
· No - hot add processors
· No - hot replace memory
· No - hot replace processors
· Virtual image use rights = Host plus 4VM
· X64 sockets = 8

Reference

Windows Server 2008 R2: Overview of Editions
http://www.microsoft.com/windowsserver2008/en/us/r2-editions-overview.aspx

Inconsistency in Information Management System Governance, Projects is Kryponite

2010-04-09T18:20:00.007-04:00

I continue to revisit the thought that a SharePoint governance model (policies, procedures, standards, resources, etc.) can be undermined if an organization does not employ proper and consistent governance for all of its information management activities and systems.

Consistency is important because it level sets the way that people approach information management projects, including SharePoint projects. If some projects were to take a fly by the seat of your pants approach, disregarding governance concepts, it is bad because the resulting deliverables will be inconsistent from what the guiding principles that the governance model is supporting. What is worse is the sloppy result is the one that is achieved first, since it takes less time to do things when you circumvent processes.

Meanwhile, you might have some projects following the rules and progressing a bit slowly while the wild wild west ones are moving fast and crossing the finish line earlier. By the time the "good" project finishes, the wild wild west has already become the de facto standard. A precedent is set and now all of those "unnecessary" rules are perceived as pockets of resistance and momentum builds in avoiding the rules rather than following them. This is a vicious cycle and requires quite a lot of effort to reverse the damage. It is much easier if the executive sponsors can support the governance concepts, then promote and mandate accordingly.

The benefits of the formal approach to projects and adherence to information management governance is obvious to anybody who has experienced a complete project life cycle and then stuck around long enough to observe the after effects. This topic is very much philosophical; do you want to manage projects short-sighted to get the project completed or do you want to manage projects for the greater good, long term to support the guiding principles of the governance model?

I will draw an analogy. You live in the mountains and have a wood stove. You can spend cheap money buying an axe, then hurry to chop wood with it to meet an immediate need of filling the stove once. Or, you can invest more money on a chainsaw and then be able to provide wood for the stove, more efficiently, every time you need it moving forward. It is called return on investment. Sustainable efficiency and the ability to produce higher quality deliverables (which are easier to maintain) is the result of following a slow and steady approach to information management projects; taking the time to remain aligned with the principles of the governance plan.

Documenting Your SharePoint Server Search Design Specifications

2010-03-22T11:08:00.006-04:00

During a SharePoint Server Search implementation, it is especially important to document the technical design specifications of Search, prior to configuring. By creating a Search Design Specifications document and continiously managing changes in it, the document acts as a good reference for future projects, knowledge transfer, upgrades, migrations, and disaster recovery scenarios.

When I document search specifications, I do it in a Word document and capture detailed information in a similar format to how the actual configuration screens appear. Here are some samples:

Content Sources

Crawl Rules

Crawl Schedules

Metadata Property Mappings

Scopes

SharePoint 3.0: How to Create an Anonymous Discussion Area in an Existing Web Application

2010-03-22T09:13:00.006-04:00

Description:

You want to create a discussion board area that is anonymous, so that people can post messages without requiring to authentication and without tracking their identities in discussion posts.

Solution:

Here are steps to create an anonymous, stand alone dicussion area:

Step 1. Enable Anonymous Access on Existing Web Application

Central Administration > Application Management > Application Security > Authentication Providers
Click "Default"Anonymous Access > Check "Enable anonymous access" > Click "OK"

Note the description of the setting you are enabling: "You can enable anonymous access for sites on this server or disallow anonymous access for all sites. Enabling anonymous access allows site administrators to turn anonymous access on. Disabling anonymous access blocks anonymous users in the web.config file for this zone."

Tom Daddario adds "Make sure your intended Web Application is selected before modifying any configuration settings."

Step 2. Create a site collection

Central Administration > Application Management > Create Site CollectionProvide Title, URL, Template, and Site Collection Adminstrators, click "OK"

Step 3. Enable Anonymous Access on Site Collection

Site Actions > Site Settings > Advanced PermissionsPermissions for Site > Settings > Anonymous AccessAnonymous Access > Select "Entire Web site" > Click "OK"

Step 4. Create Discussion Board

Click "View All Site Content"Click "Create"Communications > Click "Discussion Board"Provide Name > click "OK

Step 5. Modify Anonymous Permissions on Discussion Boards

Discussion Board > Setting > Click "Discussion Board Settings"Click "Permissions for this Discussion Board"Actions > Click "Edit Permissions" (click "OK" to message)Settings > Click "Anonymous Access"Anonymous Access > Anonymous users can: > Select "Add Items, Edit Items, and View Items" > Click "OK"

Links: PowerPivot videos on Microsoft Technet...

2010-02-26T14:24:00.004-05:00

PowerPivot videos on Microsoft Technet...

PowerPivot Part 1 - Loading Data
http://edge.technet.com/Media/PowerPivot-part-1-Loading-Data/

PowerPivot Part 2 - Preparing data
http://edge.technet.com/Media/PowerPivot-part-2-Preparing-data/

PowerPivot Part 3 - Analysis
http://edge.technet.com/Media/PowerPivot-part-3-Analysis/

PowerPivot Part 4 - Sharing in SharePoint 2010
http://edge.technet.com/Media/PowerPivot-part-4-Sharing-in-SharePoint-2010/

PowerPivot Part 5 - Management
http://edge.technet.com/Media/PowerPivot-part-5-Management/

Use Case Points for Project Estimating

2010-02-24T19:41:00.002-05:00

Use Case Points is a project estimating technique that helps you to determine complexity level of use cases, human participants, non-functional requirements, and software environments (Cohn, 2005).

Due to the rapid development nature of SharePoint, I think Use Case Points may be an efficient estimating tool for large SharePoint projects which are being formally managed. Such projects typically have an upfront investment in business analysis and likely have documented outputs including use cases. Use cases can be written like a sequential script of steps and exceptions to explain various ways that the system will be used. I think use cases themselves provide a great deal of value on a portal or search project because they provide greater visibility and detail about the requirements of the solution.

So, taking an artifact (use cases) that might already exist for a SharePoint project, you can simply use this information and apply the Use Case Points technique to gain other insights about time and cost estimates for the project.

Reference

Clemmons, R. (2006). Project Estimation With Use Case Points. Retrieved February 24, 2010 from http://www.stsc.hill.af.mil/crosstalk/2006/02/0602Clemmons.pdf

Cohn, M. (2005). Estimating With Use Case Points. Retrieved February 24, 2010 from http://www.methodsandtools.com/archive/archive.php?id=25.

Koirala, S. (2004). How to Prepare Quotation Using Use Case Points. Retrieved February 24, 2010 from http://www.codeproject.com/KB/architecture/usecasepoints.aspx.

Ten Reasons Why I Love VMWare for SQL Server

2010-02-18T17:41:00.007-05:00

Sometimes it seems as if there is a "do not virtualize SQL Server" echo in the SharePoint community, at conferences, and events. For many practical reasons, I reject this sentiment and believe that SQL should be one of the first roles to virtualize.

Here's ten quick reasons:

1. Storage - SAN storage, local drives or ISCSI drives. Storage can grow as requirements change.

2. Performance - Yes, SQL Server requires a lot of resources, but if you use resource governor in SQL Server 2008 and later you can control a lot of the spikes. In a virtualized environment, the pool of shared resources provides good spillover coverage for member servers.

3. HA - VMotion. Enough said. Sure, you can still leverage SQL native HA features such as clustering, replication, log shipping...but hardware failures occurring at a local site can be covered seamlessly with VMotion and require far less configuration at the DBMS level.

4. VMWare Snapshots - Right-click and snapshot before making configuration changes. Big sigh of relief for QA processes.

5. VMware Templates - Build an operating system, template it, re-use it over and over again.

6. SAN Snapshots - Many of the current storage arrays, such as Dell EquaLogic, ship with snapshot capabilities.

7. Centralized Management - Yeah, I like being able to access the whole farm from one console and monitor what is going on, quickly remote into systems.

8. Disaster Recovery - Advanced features to help facilitate remote site recovery. Several more layers of data and configuration protection than physical environments.

9. Physical to Virtual - Drivers aren't an issue, capture and protect important systems that happen to be running on legacy hardware.

10. Little Conveniences - How about an ISO drive where you can store and back up all of your ISO images for operating systems, software applications, etc.

Program Evaluation and Review Technique (PERT)

2010-02-17T19:31:00.004-05:00

Having worked in many different types and sizes of companies, I have always found there to be a great variance in how long it takes to accomplish certain tasks. For example, one organization might have lots of hardware at it's disposal, while another might need to order hardware. Or, another good one is the task of setting up DNS records. I've been in places where I can simply log into Active Directory myself and create what I need without hesitation, while other places can take upwards to a week to get a DNS record pointing to an IP address.

Whatever the case, the majority of the time it is the company's processes and resources that define how long something takes.

This week, I've been using the Program Evaluation and Review Technique (PERT) to estimate the duration of an extranet portal project. Fortunately, I have a very good sense for the company's processes so I can factor these things in fairly accurately. Still, I really like to include PERT calcualtions in my project plan because it allows me to factor in optimism and pessimism and come up with an accurate duration.

With PERT you calculate a weighted average by doing this:
Optimistic Time + 4 * Most Likely Time + Pessimistic Time / 6 (Schwalbe, 2009)

So, if I wanted to estimate the time it takes to spin up some virtual machines and configure a SharePoint 2010 Farm completely from scratch, I might do something like this:

3 workdays + 4 * 5 workdays + 10 wordays / 6
Result = 7.5 workdays

Reference

Schwalbe, K. (2009). Information Technology Project Management (6th Edition). Boston: Course Technology.

Issue: Windows Server 2008, JavaScript Blocked on Internet Explorer

2010-02-17T17:45:00.010-05:00

Description:

On a Windows Server 2008 system, JavaScript is being blocked in Internet Explorer.

Solution:

1. Open Server Manager

Start > Control Panel
Programs > Turn Windows features on or off
Server Manager
Put the cursor on the root node called, "Server Manager"

2. Turn Off the Internet Explorer Enhanced Security Configuration for Administrators and Users.

FAST and Windows: A Blessing for Innovation

2010-02-10T19:58:00.009-05:00

In a recent post on the Microsoft Enterprise Search Blog, Bjørn Olstad (CTO of FAST) published a post titled, Innovation on Linux and UNIX, which explains the longer term technology strategy for FAST with respect to supported operating systems. The post describes an increased focus of innovation for the product, for Windows operating system installations, while gradually deprecating support for Linux and Unix installations.

I can sort of understand the negative reactions to this announcement and the notion that customers may turn to other search platforms to maintain their Linux/Unix operating standards. However, I believe that this is a truly good decision by Microsoft, which will result in a higher quality product.

The reality is; in order to push innovation of the search platform forward beyond its current boundaries of functionality and performance, it is an inherihent requirement that the low level levels of the architecture be tightly bonded with the operating system. By not making this long term decision, a forced common denomintor is then imposed on the platform at higher levels of the architecture, ultimately inhibiting the product. Multiple OS support for installations actually sets the platform back. We've seen this as recent as 5.3 when we are required to install FAST ESP as a 32 bit application along with Java runtime 32 bit. This is a 64 bit world now, get with the program.

My sense is that the product roadmap will offer great improvements in the document processor and query processor pipelines, linguistics, user experience, etc. These improvements are required to allow search to become the leading functional component for indexing, transforming, and presenting not only content but navigation, functional components, and structures on Web sites. The relationship that search platforms will have with tomorrow's Web applciations, is comparable to the relationship that relational databases have with yesterday's Web sites. This innovation simply cannot afford to be spread thin.

Links: Windows PowerShell compiled Help for SharePoint Server 2010

2010-02-09T08:37:00.005-05:00

I am relieved that Microsoft has published PowerShell help files for SharePoint. The help files will certainly come in handy. These are available for download:

Windows PowerShell compiled Help for SharePoint Server 2010
http://www.microsoft.com/downloads/details.aspx?FamilyID=045f7af5-b226-4a05-8ace-4e17cfdef856&displaylang=en

This site contains separate help file (.chm) downloads for:
· Access Services
· ECM
· Excel Services
· InfoPath
· PerformancePoint
· Search
· Secure Store
· SharePoint Foundation Search
· SharePoint Products
· State Service
· User Profile
· Visio Services
· Web Analytics
· Word Services

Strange Computer Virus

2010-02-01T09:04:00.008-05:00

This might be the first time I am posting a computer cleanup instruction on this blog, but I feel compelled since several people around me have been complaining about a common set of symptoms hitting their computers recently. I thought I could share some steps that a colleague took to successfully clean an infected system.

DISCLAIMER:

The purpose of this post is for informational purposes only and to share some steps performed on an infected system to fix a computer virus, related to symptoms described in the Problem section of this post. I don't know the name of the virus at this time. And, please don't go and modify the registry unless you know what you are doing.

Description:

System virus, automatically redirects internet explorer to a site that requests purchase of an anti-virus product. Task manager becomes blocked and inaccessible.

Solution:

Part I

* Boot the infected system and at the BIOS Press [F8] (Prior to Windows Displaying)
* Select “Safe Mode”
* Log in with the local administrator account
* Start, Run, Type MSCONFIG, and click OK
* Open Windows Explorer, and invoke the file property view and select “show hide files..”
* Look for a strange file type without much detail pointing directly to a user profile, sub to the application directory. Eg. “Document and Settings” > “User Profile”…..”
* Deselect the file and write the file name down. This will prevent it from launching during start up.
* Reboot into Safe Mode again.
* Log in as the local Administrator account.
* Browse to: “Document and Settings” > “User Profile”….. abs search for file name written down in the previous step.

Part II

* On a separate computer, download ATF-Cleaner
http://www.atribune.org/index.php?option=com_content&task=view&id=25&Itemid=25
* Copy ATF-Cleaner.exe to a USB drive so that you can move it onto the infected system
* Copy ATF-Cleaner.exe to the desktop of the infected system
* Double-click and run ATF-Cleaner.exe
* Click “Select and Delete All”
* Now review search results and delete directory where file is contained.
* Open Regedit – and Export a copy of the registry
* Select Edit > Find and Search for file.
* Delete file reference key
* Reboot
* Login in Windows in normal mode and test

Governance Concepts, Strategy, and Authority

2010-01-07T22:41:00.005-05:00

One of the initial challenges with establishing governance model is organizing the concepts appropriately. In order for governance to be effective, the concepts need to be grouped according to the appropriate scope, authority, and audience.

Information Management is a concept that may apply across an entire enterprise; same with corporate polices and procedures. However, the SharePoint platform may only be responsible for organizing a sub-set of an organization's information and therefore the scope of this is smaller. Additionally, SharePoint is technical in nature and so the emphasis on Information Technology audience is greater. For these reasons, it makes little sense to try to encapsulate all of the governance topics for an organization's information management needs, within a SharePoint governance plan. Instead, topics should be divided and organized appropriately.

For example, if you were on a whiteboard brainstorming and creating idea clouds for the purpose of outlining your governance topics, you might start to group topics like this:

Information Management Statement of Governance

Overview
Roles and responsibilties
Decision making processes
Explanation of information architecture
How taxonomies are developed and integrated
References to file naming conventions
References to policies and procedures

SharePoint Governance

Overview
Roles and responsibilities
Operating processes
Explanation of the applied use of SharePoint with respect to Information Management
References to SLA
References to policies and procedures

Policies and Procedures

Information Security policies
System Use policies
Support policies
Request processes
Project processes

Thinking about these concepts right is a prerequisite to creating governance documents and perhaps even beginning to model any new, collaborative solutions. Authority needs to be defined and delegated up front. Without a central managing body having necessary authority, the decision making process will be a constant road block.

Consider this classic scenario; a hypothetical Information Technology department owns and manages technology systems for an organization. They don't happen to possess authority to own or commence initiatives around analysis, design, and integration of information architecture policies and processes. This department decides to deploy SharePoint as a technology offering. A likely, potential result of this is that the deployment becomes a commodity service. The odds that this platform will do much to improve information management practices throughout the organization, are thin. The initiative was not started by the body which governs information architecture practices for the company.

Now consider a variation. Consider that this hypothetical business unit now has the authority to work with other business units collectively, and facilitate a company wide initiative to analyze, interpret, and parse the information management requirements of the company, the teams, and the individuals. They also have authority to facilitate the creation and management of information management policies and procedures. Finally, they retain the authority to own and manage technology systems. This scenario has a much greater potential to produce a full bodied SharePoint deployment, adding lots of value throughout the business by integrating information management capabilities. In this scenario, the technology can actually be used to mandate how documents are organized, where they are stored, and how they are tagged.

Having said this, a commodity service may be the right next step for an organization, who is to say. But evolution of processes tell us that one day, silos of information will want to be joined. Progression is a natural thing and it should be embraced. SharePoint as a commodity service is not the end game, it is a starting point. Strategy is recognizing progression paths and figuring out how to make it happen. There will be people fighting the progression and arguing the direction is wrong, that they have different ideas. There will be resistance. Strategy demands authority. Governance provides it. The right combination of these pieces can act as one hell of a steam roller.

Outline for Disaster Recovery Plan Document

2010-01-07T10:08:00.002-05:00

The purpose of this post is to share a disaster recovery plan outline. This is an outline that I have been evolving for several years. And, although this outline was intended for SharePoint environments, it can be used for any system or application.

The reason I like this outline is because I know it works. Unlike many other plans on the Web, I think this outline provides more complete coverage of the business and technical aspects of disaster recovery. Many of the plans I have seen are merely explanations of the SharePoint product features and limitations, or advertisements for third party products. Detailing what SharePoint's strengths and weaknesses are with regards to backup and restore will not do you an ounce of good in the event you need to perform a recovery of some sort. Additionally, no matter what tools you have for backing up and restoring, you still need a good plan to address the process. Different tools only change the content of the backup and recovery procedure section of the plan, they don't change the structure of the document or eliminate the need for any of the sections of the document.

The audience for this document can include the tactical team members who execute the plan, but also the business stakeholders, sponsors, and business process owners who are affected by the availability and recovery policies and procedures. Everybody should be involved with contributing to and reviewing the plan. This review process is very healthy because it resets expectations and keeps everybody on the same page.

SharePoint Disaster Recovery Plan Outline

I. Overview
a. Explanation of the document
b. Explanation of when to use the plan

II. Business Profile
a. Application or system owners, points of contact
b. Application or system summary
c. Related business processes
d. Usage information
e. Availability requirements (link to SLA)
f. Recovery requirements (link to SLA)

III. Technical Profile
a. Hardware inventory
b. Software inventory
c. Related systems
d. Vendor contact information (contact, support agreement information, etc.)

IV. Failure Scenarios
Matrix listing all failure scenarios with description of each scenario

V. Backup Procedures
Instructions for each method of back up used to support every possible recovery scenario

VI. Recovery Procedures
Instructions for recovering from each failure scenario

VII. Verification Procedures
a. Functional testing
b. Security testing
c. Performance testing
d. Checklists

VII. Appendix
a. Glossary
b. Links to policies, procedures

VIII. References

Interesting Change Affecting Microsoft Office 2003 and 2007

2010-01-07T10:03:00.004-05:00

According to KB978951, versions of Microsoft Office 2003 and 2007 sold after January 2010 will no longer include some of the custom XML tagging capabilities. Full details are available in the article, "Description of the January 2010 update for Office Word."

Governance: Capability Driven, Not Platform Driven

2009-12-28T14:58:00.014-05:00

Although I have no survey or poll results to support this; I believe that the SharePoint community as a whole is putting more weight on the topic of governance as time moves forward. I am basing this on the number of blog posts, conference presentations, third party products, and research available on the Web. Microsoft even has made a SharePoint governance plan template (SharePoint Products and Technologies Governance Plan) available for download.

I have mixed emotions about some of the messaging in the community. I think the topic of governance has become so SharePoint-centered that the original intent of governance becomes lost. Taking a few steps back, I thought I might weigh-in on the subject.

When push comes to shove, SharePoint is simply a platform, a means to an end. It is a tool to facilitate a capability. If that capability happens to be information management, then SharePoint is providing the technical functionality required to make managing information better.

My take on governance planning is that an organization should first address the capability (e.g. information management) as a whole, and then develop a plan for it. Once that overarching effort is in motion, it should branch off into defining the policies, processes, and measures specifically addressing SharePoint.

The flaw I see in creating a governance plan starting with SharePoint platform is that too many questions and risks about the overall initiative of providing that information management capability exist. This flaw may be a symptom or an indicator of larger ailments in the organization such as a lack of clarity or a lack of sponsorship (or a lack of clarity within its sponsorship). The way I see it, if an executive management team is willing to embrace the idea of using the SharePoint platform, then it ought to be willing to accept and embrace the larger initiatives at hand; which is where governance should originate.

In conclusion, I think that in order to maintain long term credibility with the subject of governance planning, we in the SharePoint community should share more ideas about how to integrate SharePoint governance into existing corporate governance as well as how to properly originate governance where it does not already exist. And, in order to do this I think it requires stepping out of the world of SharePoint and taking a wholistic view of the organization and understanding the fundamental policies and processes at play, as well as understanding what is the underlying intent and purpose for which SharePoint is being deployed.

My Favorite Windows 7 Feature

2009-12-18T10:58:00.004-05:00

For me, the most valuable enhancements to usability affect the basic things that I do the most often. This includes browsing folders and opening files. And, although, I do like to keep twelve or more windows open at one time, I do not like clutter.

For this reason, my favorite Windows 7 feature is the ability to right click on an open application and then click a shortcut to open another instance of that application.

2009 SQL Server Magazine Best SharePoint Product

2009-12-18T09:39:00.003-05:00

I thought it might be interesting to note the SQL Server Magazine, 2009 Best SharePoint Product awards. Here they are:

2009 SQL Server Magazine Best SharePoint Product

Editor's Best

Gold: ControlPoint for SharePoint, Axceler, www.axceler.com
Silver: Professional Archive Manager, Metalogix, www.metalogix.net
Bronze: NearPoint for SharePoint, Mimosa Systems, www.mimosasystems.com

Community Choice

Gold: Site Administrator for SharePoint, Quest Software, http://www.quest.com/
Silver: Colligo Contributor Pro, Colligo Networks, http://www.colligo.com/
Bronze: CorasWorks Workplace Sutie 10, CorasWorks, http://www.corasworks.com/

References:

2009 SQL Server Magazine (2008, December). 2009 SQL Server Magazine Editor's Best and Community Choice Awards. SQL Server Magazine, pp. 12-19.

Error: SQL Server Maintenance Plan, Database Backup Job

2009-12-17T21:17:00.004-05:00

Description:

When executing a SQL Server maintenance plan, having a database backup job, an error occurs. The issue is that the SQL Server Agent service account does not have access to the backup folder. This happens more frequently on backup folders which exist on a separate server, such as a backup server.

1. First, navigate to SQL Server Management Studio > Maintenance Plans > Right click on maintenance plan > View History.

You might see something like this in the history:

"Action: Execute maintenance plan (full backup of all SQL databases). ErrorMessage: Execution failed: See the maintenance plan and SQL Server Agent job history for details. Additional Information: Job 'Backup SQL' failed. (SqlManagerUI)"

2. Next, navigate to the history log for the SQL Server Agent job:

SQL Server Management Studio > SQL Server Agent > Jobs > Right click on job > View History > Highlight the error > Click Export > Export a log file > Open the log file in a text editor

...and you might see entries like this:

"Reason for failure: " failed with the following error: "Cannot open backup device 'backup device name'. "
"Error information: Operating system error 5(Access is denied.)."

Solution:

The solution to this is to configure the appropriate access for the SQL Server Agent service account on the folder security access control list and the folder sharing access control list.

However, the catch here is that you may need to add the service account directly to the access control list, as opposed to an AD group in which the user account belongs. In fact, I tested this by doing the steps below.

1. Deleted the maintenance plan and created it again.

2. Added the backup folder location, and clicked Next.

This brought up an error:

"Maintenance Plan Wizard: The Database Engine service could not resolve the specified folder location. Either the location does not exist, or the current login account does not have access to it. Verify that the folder exists, and that the login account has permissions on it."

3. Added the SQL Server Agent service account directly to the backup folder's access control lists for folder security and folder sharing. After doing this, the creation of the maintenance plan was successful.

I Respectfully Disagree

2009-12-05T21:14:00.012-05:00

As I was searching for some references for a risk management white paper that I am writing, I stumbled upon an old PowerPoint on the Web titled, "Risk Management and ROI: The IT Leadership Financial Conversation." It was created by Peter G. W. Keen of Delft University in Sepetember 2004. This PowerPoint was used to educate an IT Leadership community attending a CIO summit.

As I looked through the PowerPoint for some insight to use in my paper, I started finding statements such as:

"ROI from IT: There is none. There never will be." (Keen, 2004)
"ROMI not ROI: Return on Minimized Investment" (Keen, 2004)
"80% of IT costs are hidden below the surface - and a navigation threat" (Keen, 2004)

The more slides I viewed, the more I realized that I completely disagree with the intent of the message; essentially to encourage CIOs to view IT as a business liability which needs to be tightly controlled and driven primarily by its cost drivers.

I disagree because I think a better approach for CIOs to take is to understand the purpose of the technologies their teams are evaluating, understand the costs and benefits, and choose projects which support the objectives of the organization. Managing cost should be part of the decision making process, but it should not be the primary driver. When cost is measured, all aspects of cost should be included. And, the financial benefits of the project should also be measured and included.

The objective of Information Technology is to facilitate two very important capabilities for today's businesses:

1. Revenue generation
2. Business productivity (process efficiency)

Most leaders in the IT space generally understand the financial benefits of the IT projects they choose to pursue, but perhaps the IT industry as a whole generally does not place enough emphasis on methodologies and practices for measuring and translating these back to the financial statement. This would require more focus, analysis, calculation, and validation.

To be clear, I am not saying that all IT projects are sensible and they should be done blindly. However, what I am saying is that it is incorrect to characterize IT as a business function that shows no return on investment.

If you deploy a technology that allows people to attend meetings over the Web instead of traveling to another location, then your costs are those which are required to implement and maintain the technology while your savings are those which you do not spend to travel? Both sides of equation need to be considered, not just cost.

I also disagree with the claim that 80% of IT costs are hidden. I believe that if budgeting is done properly, most IT costs are completely visible and manageable. There are always some unforeseen costs with IT, but by learning from past experiences, it becomes possible to anticipate these variations.

In summary, I disagree with the PowerPoint. Information Technology can have a positive ROI, and costs can be manageable and predictable. I think the real problem is some organizations just don't know how to measure these things effectively.

References:
Keen, P. (2004). The IT Leadership Financial Conversation. Retrieved December 5, 2009 from www.peterkeen.com/presentations/IT%20Risk%20Management.ppt.

Windows Server 2008: Active Directory Protection From Accidental Deletion

2009-11-20T15:12:00.005-05:00

Description:

When you create an Organizational Unit (OU) or security group in Active Directory, there is checkbox titled, "Protect container from accidental deletion." If you create the object with this check box marked, then you have to follow special steps if you would like to delete that OU in the future.

If you attempt to delete the object while it is protected, then you will receive the error, "Active Directory Domain Services. You do not have sufficient privileges to delete object, or this object is protected from accidental deletion."

Solution:

1. Open Active Directory Users and Computers.
2. Select the root domain, "company.domain.com."
3. From the menu bar, select "View" and "Advanced Features."
4. Navigate to the OU you would like to delete.
5. Right-click, properties.
6. Select the "Object" tab.
7. Uncheck the option, "Protect object from accidental deletion."
8. Now the object is no longer protected. You can proceed with deleting the object.

SharePoint 3.0: Allowing SharePoint RSS Viewer Web Part to Read SharePoint RSS Feeds

2009-11-19T10:25:00.008-05:00

Description:

SharePoint RSS Viewer Web Part does not display RSS feed from SharePoint list or library.

After configuring a SharePoint RSS Viewer Web Part to display an RSS feed from a SharePoint RSS list, you receive the error, "The RSS webpart does not support authenticated feeds."

Solution:

Configure anonymous access on the list which is serving the RSS feed.

1.
Enable anonymous access for the Web Application containing the list which is serving the RSS feed.
- Central Administration > Application Management > Application Security > Authentication Providers > Edit Authentication
- Edit Authentication > Anonymous Access: Check "Enable anonymous access"
- Edit Authentication > Click "Save"

2.
Enable anonymous access for the site collection containing the list which is serving the RSS feed.
- Site Collection > Site Actions > Site Settings Site Collection Settings > Advanced Permissions
- Advanced Permissions > Settings > Anonymous Access
- Change Anonymous Access Settings > Anonymous Access: Select "Lists and Libraries"

3.
Enable anonymous access for the list which is serving the RSS feed.
- List > Settings > Permissions for this List > Settings > Anonymous Access
- Assign the "Read" or "View Only" permission level to the Anonymous User

References:

Holmes, T. (2008). Enabling Anonymous Access in SharePoint 2007. Retrieved November 19, 2009 from http://blog.tylerholmes.com/2008/01/enabling-anonymous-access-in-sharepoint.html.

Back from SharePoint Conference 2009

2009-10-26T10:32:00.016-04:00

I have returned home from ten days in Las Vegas NV where I attended the Microsoft SharePoint Conference 2009 at Mandalay Bay. I cannot say that I am happy to be home, especially since I have to clean up after myself again. I love throwing wet towels on the floor and then going out for the day so that I can return to the hotel room at the end of the day and the towels are magically clean and put away.

There were many highlights of the conference. The cocktail reception, the keynote, the sessions, the Huey Lewis & the News concert, catching up with old friends and meeting new ones.

The bottom line is SharePoint 2010 delivers!! It is going to be an awesome, next three years working with this generation of products and technologies. Things are moving full steam ahead.

I especially enjoyed the governance planning session by my friends, Susan Hanley and Scott Jamison.

Friday's full day workshop on SharePoint Server 2010 Installation and Upgrade Training by Shane Young and Todd Klindt from SharePoint911 was fantastic and informative. It was more fun than hanging out at House of Blues Foundation Room until 3:00am...almost.

Most of all I love the fact that I won all of my gambling money back at the craps table after I checked out on Saturday morning, as I was killing some time before the cab ride to the airport. I hit three point numbers and several hard ways. Folks were happy to be winning and I received an applause for the good shooting.

Links: CommonCraft: SharePoint in Plain English

2009-09-17T19:20:00.005-04:00

I've seen this video posted on various blogs. I like it a lot. Its titled, "SharePoint in Plain English." It is by CommonCraft, http://www.commoncraft.com/. Brilliant!

View Here:
http://www.commoncraft.com/custom-video-sharepoint-plain-english

Download Here:
http://download.microsoft.com/download/A/5/6/A56BB856-74F5-4A6B-887B-876BAE88116F/SharePoint%20in%20Plain%20English.zip

Migrating Internet Explorer Favorites and RSS Feeds

2009-08-30T18:07:00.004-04:00

With Windows 7 releasing soon, it will be time to think about migrating user profile settings to a new operating system build.

Aside from file folders, and desktop files, you may have a bit of time invested in the Internet Explorer favorites and feeds. Even if it only saves a couple minutes of searching in the end, I thought it would be worthwhile to post locations of these items on a source Vista build.

Favorites:
C: (Operating System) \Documents and Settings\UserProfileName\Favorites

RSS Feeds:
C: (Operating System) \Documents and Settings\UserProfileName\AppData\Local\Microsoft\Feeds

SharePoint 3.0: Clarifying Check Out Status on Multiple Document Upload

2009-08-21T13:09:00.010-04:00

I found a post on TechArchive.net, "Re: disabling check out on document library upload," in which the author was observing that multiple document uploads were resulting in status of "checked out" after uploading. The author cited a post of mine, "SharePoint V3: Achieving Checked-In Status When Uploading Mulitple Documents," and explained that the post didn't solve the issue.

So, I am posting the two possible reasons why, after uploading multiple documents to a document library, the uploaded documents have the status of "checked out."

1. Require check out is configured on the library

I did a test, configuring six document libraries, and then performed a multiple document upload. Here are the results:

a.
Document library configurations resulting in "checked out" status when multiple documents are uploaded:
Require Check out + No Versioning
Require Check out + Major Versioning
Require Check out + Major and Minor Versioning

b.
Document library configurations resulting in "checked in" status when multiple documents are uploaded:
No Require Checkout + No Versioning
No Require Check out + Major Versioning
No Require Check out + Major and Minor Versioning

2. The document library is configured with a required field. When the document upload completes, the field is not populated and the status for each of the uploaded documents is set to "checked out."

SharePoint 3.0: Custom Permission Levels

2009-08-17T08:52:00.007-04:00

When planning site collection security models for SharePoint deployments, there is certainly a case for simplicity and sticking to the out of box permission levels. Doing this requires the least amount of thought, administrative effort, documentation, and training.

As an added benefit of sticking with the out of box, you can leverage many of the Web based training tutorials and end user, computer based training modules, that are available on the Web with since most of these instructional resources are based on out of box configurations.

Having said that, circumstances and business requirements can require something different than the out of box permission levels. For example, you might want to lock out SharePoint Designer from some users by configuring a permission level that excludes the "Use Remote Interfaces" permission. Or, you might want to prevent content contributors from being able to delete by excluding the "Delete Items" permission. In most cases, having thirty three distinct permissions allows enough flexibility to accommodate.

When I need to utilize custom permission levels, I put a good amount of effort into planning for these and ensure to be consistent with their names, descriptions, and definitions. Below is a sample matrix that I used for planning four custom permission levels, instead of using those which are out of box.

Publishing SharePoint Web Applications in ISA Server

2009-08-14T18:11:00.003-04:00

Background:

This article assumes SharePoint Web applications are configured with NTLM Authentication, that multiple Web applications are being published outside a company's firewall, and ISA Server is being used as a firewall. The scenario described also assumes that a one set of Windows credentials has access to multiple SharePoint Web applications.

Description:

It is common for a SharePoint environment to include multiple Web Applications. Since each Web Application requires its own IIS Web site and may have its own IP address and host header, having mutliple Web applications does create some complexity and therefore requires some consideration.

It gets a bit more complicated when multiple Web applications need to be made accessible outside of a company's local network, such as an extranet or public internet scenario. In this case, firewall rules and NAT must be configured for each Web application to protect the organization and the application being published.

Then comes the user experience. Inside the network, client computers often times belong to the same domain as the SharePoint servers, or at least a trusted domain. Furthermore, the domain URLs are considered either "Local Intranet" or "Trusted" by the users' internet browser. In this environment, a user can navigate from Web application to Web application without receiving an authentication prompt. Life is good on the local network.

This all changes when Web applications are published outside the company's firewall. First, client computers accessing the sites no longer belong to the same domain as the SharePoint servers. Second, the users' browsers aren't configured to automatically log users into the Web applications. The challenge this creates for the user is if a contiguous user experience requires accessing multiple Web applications, the user is going to receive an authentication prompt for each application.

Solution:

ISA Server allows Rules to share Listeners. What this means is that you can create one Listener and add multiple Web applications to that Listener. Then, you can create a Rule for each unique Web application, associating these Rules with the Listener.

The result of this is that users can access multiple, externally facing SharePoint Web applications, without requiring to authenticate to each one.