Sharepoint 2010 : Lookup Column

The lookup column in Sharepoint 2010 packs a very nice & practical feature.
Now while populating a lookup value, corresponding column values of the looked up item can also be populated (from the source list).
In Moss 2007, that would have required an event handler. That's simple, the way things should be.

Sharepoint 2010 Beta is here......

Get your 64bit OS/PC ready!!!
The wait is over, SharePoint 2010 beta is here, follow the direct download link.


Why developers like SharePoint 2010?

Article by Paul Krill

Integration with Visual Studio is one change that makes SharePoint much easier to develop collaboration apps, developers say

Short Overview of SharePoint Features in Visual Studio 2010

Original article by Peter Jausovec
"As you probably know, Visual Studio 2010 was announced earlier this week and it contains a lot of cool features and project templates for SharePoint developers. Below is a short overview for some of the SharePoint development related features and project templates.

Configurable deployment

With all new SharePoint project templates you can leverage new configurable deployment feature which lets you configure the way you want to deploy or retract your project. Besides using provided, out of the box deployment steps (Run Pre-Deployment Command, Run Post-Deployment Command, Recycle IIS Application Pool, Retract Solution, Add Solution, and Activate Features) you can use SharePoint extensibility to create your own, custom deployment steps and deployment configurations.

Sandboxed and farm solutions

Some SharePoint projects can be deployed either as sandboxed or farm solutions. Sandboxed solutions run in a secure and monitored process that has limited resource access and with farm solutions user must have SharePoint administrator privileges to run or deploy the solution. You can read more about SharePoint sandboxed solution here.

Extending SharePoint Tools

Even though Visual Studio 2010 contains a set of project templates you can also extend them. You can create extensions for projects, project items, define your own project item types and create deployment extensions. You can read more about extending SharePoint tools on MSDN.

Feature and Package Designer

Feature and package designers give you the ability to customize features in your solution and with packaging designer you can customize which features are getting deployed and how. More about feature and package designer is here.

SharePoint Explorer

SharePoint Explorer is a new tool window that gives you a view into your SharePoint server. You can get a hierarchical view of lists, sites and workflows on your SharePoint server.

SharePoint Project and Project Item Templates

The following SharePoint specific project templates and project item templates are available in Visual Studio 2010:
Project Templates
  • Empty SharePoint project
  • Visual Web Part project
  • Sequential and State Machine Workflow
  • Business Data Connectivity Model
  • Event Receiver
  • List Definition
  • Content Type
  • Module Project
  • Site Definition
Project Item Templates
  • Empty Element
  • Web Part
  • User Control
  • Application Page
  • Association Form
  • Initiation Form
  • Business Data Connectivity Resource Item
  • List Instance
  • List Definition From Content Type
  • Global Resources File
Besides above mentioned project templates, there are two import project templates for importing .WSP file contents and importing reusable workflows:
  • Import Reusable Workflow
  • Import SharePoint Solution Package

How to download, install and get started

If you are a MSDN subscriber, you can download Visual Studio 2010 from here. Download will be available to everyone on October 21st.
If you want to know how to download and install Visual Studio 2010 watchChannel9 video.
To get you started, head over to MSDN and read some of the walkthroughs on SharePoint Development in Visual Studio 2010."

SharePoint 2010 Snack! a must for Developers

5 Videos of SharePoint 2010 for developers. It will all seem very easy for those who are familiar with MOSS 2007

SharePoint 2010: Professional Developer Evaluation Guide and Walkthroughs

The SharePoint 2010 developer evaluation guide describes the SharePoint 2010 developer platform, including walkthroughs of some of the new capabilities for developers.

SharePoint 2010 : Jeff Teper, Microsoft

A very interesting post by Jeff Teper – Corporate Vice President, SharePoint Server, Microsoft on SharePoint 2010, read more...

c# : Read XML from URL

There are multiple methods to capture XML from a URL, but this particular example is helpful when you are dealing with special characters of foreign languages. The loaded XML will display them in correct format for the charset specified.

//Include the following packages
using System.Net;
using System.IO;

//request the particular web page
HttpWebRequest request = (HttpWebRequest)WebRequest.Create("");

//define the login credentials of the requested file/page
request.Credentials = new NetworkCredential(”UserName”, “Password”);

//get the response from the request
HttpWebResponse response = (HttpWebResponse)request.GetResponse();

//create a stream to hold the contents of the response
Stream receiveStream = response.GetResponseStream();

//create your XML document
XmlDocument mySourceDoc = new XmlDocument();

//load the file from the stream

//close the stream

Today's Sharepoint Tip : _spBodyOnLoadFunctionNames

In most cases SharePoint pages are based on a master page that contains the "body" element. These content pages can’t directly add a function to the body’s onload event. In order to work around this limitation, SharePoint provides the "_spBodyOnLoadFunctionNames" array. When the body is loaded, the onload event handler executes each function whose name is contained in this array.

'<'script language="javascript"'>'
function FunctionName()
// Code

SharePoint & it's Competitors

Shawn from CMS watch has a very interesting point in the latest trend for competing with (by alternate CMS systems) SharePoint head on. Though at these times, the best bet for them is to move along.

"As any product gains in popularity, especially if it's seen as dominant, you tend to see more and more news about alternatives that inevitably get dubbed "killers." The news media and the product's competitors are continually trying to best the dominant solution and predict a product's demise. We can see this clearly with the iPhone and, as Seth Gottlieb pointed out, "who isn't working on a SharePoint killer?" But in many cases, these "killers" are only hopefuls with virtually no evidence they could harm a fly."

Read more here

How to get Raw HTML from a Page : System.Net.WebResponse

Retrieving a page's HTML can sometimes be necessary in applications. You could be filling columns for actual meta data of sites or may retrieving remote web sites for specific content. It's require very simple code to do all the stuff

// pass the site URL
string strHTML = Strip(Request(strWebURL + "/" + file.Url, "GET"));

//The Request Function
String Request(String uri, String verb)       {

            WebRequest request = WebRequest.Create(uri);
            request.ContentType = "application/x-www-form-urlencoded";
            request.Method = verb;
            request.ContentLength = 0;
            WebResponse response = request.GetResponse();
            if (response == null) return null;
            StreamReader reader = new StreamReader(response.GetResponseStream());
            return reader.ReadToEnd().Trim();

// The Strip function, to remove style, scripts & Html tags from the text

 public string Strip(string text)
            text = Regex.Replace(text, "", "", RegexOptions.Singleline | RegexOptions.IgnoreCase);
            text = Regex.Replace(text, "", "", RegexOptions.Singleline | RegexOptions.IgnoreCase);
            text = Regex.Replace(text, @"<(.|\n)*?>", string.Empty);
            text = text.Replace("\r\n\t", " ").Replace("\n", " ").Replace("\r", " ").Replace("\t", " ");
            return text;

// That's All

Making Sense of the SharePoint 2010 Pie

With so many blogs now on SharePoint, it has become more like a box of choclates, You never know what you're gonna get.

Mark bower in his article has explained the Sharepoint 2010 pie, here is a repost

"A new version of SharePoint gives us an updated SharePoint Pie. Like the SharePoint 2007 pie, SharePoint 2010 has six slices, most subtly renamed."

Collaboration becomes Communites
  • Renamed, perhaps to emphasize the intent to make SharePoint 2010 a more social experience.
  • Aim to empower people to work together in new ways through ad-hoc collaboration in communities of interest or in work-group communities
Content Management becomes simply Content
  • Does this imply a de-emphasis of SharePoint as a serious content management platform? I think not. I suspect this is a desire to move people away from traditional equation of content management to web content management, towards a broader view of content management…covering document management, records management as well as web content management.
Search stays as Search
  • What’s publicly known right now is inclusion of FAST technologies and improvements to people and line of business application search. At the top end of the market Microsoft is loosing out to the likes of Autonomy, and they’ll want to put the brakes on that.
Business Intelligence becomes Insights
  • The new name emphasises the business impact, rather than the technology function, which is powerful. Perhaps again, Microsoft is taking a broader view of this capability, thinking about getting insights in a more human way, through crowdsourcing or collaborative approaches, as well as simply through data crunching. Just speculating.
Business Process and Forms becomes Composities
  • Composite Applications being a more corporate-friendly word than mashups.
  • The idea once again I think is to broaden the category to include other user and developer tasks of creating custom business solutions through mashing together web parts, forms and processes.
Portal becomes Sites
  • This moves away from positioning SharePoint as an Intranet Portal product to being a product capable of serving as a intranet, extranet or Internet site

SharePoint Object Hierarchy: How it all fits together

A very useful article by Martin Kearn about How objects in SharePoint relate to each other? It gives you a bird eye view of the country called SharePoint.

From the article:
"I often get asked to clarify how all of the objects in SharePoint relate to each. For example, people do not always understanding the differnence between a site collection and a site or how a web application and content database relate to each other.

To help out, I have produced this diagram which I think explains all of the main SharePoint objects and how they relate to each other. I did consider writing some kind of description to go with this, however I think it is better that I just do my best to answer any questions via the comments. If there are any re-occuring themes, I'll add to this article and try to explain them."

10 Things SharePoint Can Do for Your Firm

By Mark Gerow
Special to
July 28, 2009

"I often find myself staring at Microsoft SharePoint and wondering how I can do more with it to enable a 21st century law firm; one in which attorneys, clients and staff can easily share ideas, expertise and information across time and distance. How can it be used to reduce costs while expanding the ways in which we collaborate?
In this article I'll suggest 10 ways you can use SharePoint today in your firm to improve attorney effectiveness, deliver better client service and reduce costs. This is not a "how to" but a "what now" article, written to answer that perennial question: "now what?" "











How to programmatically determine customized pages in a site

What happens when the need is to determine programmatically that a given page has been customized/ghosted or not?

We can use the "vti_hasdefaultcontent" property of the "SPFile" class to determine whether a file is customized or native.

SPFile file = SPContext.Current.Web.RootFolder.Files["default.aspx"];

bool IsCustomized = (bool)file.Properties["vti_hasdefaultcontent"];

SharePoint 2010 Technical Preview

From SharePoint's team blog:
"Today, we’re announcing that SharePoint 2010 has reached the technical preview engineering milestone. The SharePoint team is running a limited, invitation only Technical Preview program. While we’re not sharing SharePoint 2010 details at this point, we did want to give our customers & partners a sneak peek at SharePoint 2010! We’re very excited about SharePoint 2010 and looking forward to the SharePoint Conference this October where we’ll talk about all the investment areas across workloads and the platform. What we’re sharing today is just a fraction of what will be in SharePoint 2010!"
More here...

UPN (User Principal Name) for Authentication

It's common for end users to complaint about the domain prefix that they have to use at the login for a SharePoint site (windows authentication). And it frustates users when they can't login with their usernames and have to be reminded time and again about the domain prefix.

One alternative is to use UPN or User Principal Name to be used as login. UPN is nothing but a suffix that is added after a username which can be used in place of "Samaccount" name to authenticate a user. So lets say if your company is called Microsoft, then instead of Microsoft\Username you can use at the authetication popup.

Adding an UPN to active directory is straight and simple (only requirement is the access to global catalog server).

10 Themes for SharePoint : Packaged and Delivered

Microsoft' released a set of 10 themes for SharePoint and we just packaged them into a solution file with installer. Simply download & install.

Download :

Theme Preview

SharePoint Best Practices : Architecture, Planning, Installation, Development Environment,Backup and Recovery, Virtualization

Every now and them we hear stories where things went wrong because no body planned a thing. The new companies implementing such technology have very less know how in terms of details and best practices, and that's where opportunist or say amateurish developers try to score easy brownies. For them it's a easy and fast way to lay hands on SharePoint development and learn as they go but that comes as a cost to the company which in turn puts the blame on the technology.

Michael Nemtsev on has come up with a 6 series best practises guide on how to extract the best out of SharePoint. Here are the snippets and link to posts

Part 1 - Architecture and Logical Planning
"Many factors may affect farm design, performance, scalability and redundancy - from hardware devices in organization network, to network topology. As a result, leveraging and finding compromises among those factors helps to build consistent, reliable and flexible environment."
Organizations adopting SharePoint face a variety of tasks - from planning, strategy, infrastructure and architecture design, UI Design, migration, and to development. All these tasks imply flexible infrastructural baseline before actual work starts. However, in reality we face the outdated environment and misconfigured farms that are not ready to implement new requirements. In such cases, baseline architecture becomes foundation stone of all SharePoint projects.
Why would we care about infrastructure and not about something else, for example development? Fixing infrastructure errors is very expensive task and leads into significant changes across SharePoint farm.Development errors are not so expensive and can be fixed relatively quickly

Architectural Planning
Plan your farm and network communications before starting actual installation. The first thing to start is designing SharePoint architecture across corporate network. This includes understanding network structure, examining network devices and choosing the right SharePoint topology to fit the existing infrastructure and new requirements.

Network response time is one of the important factors that can affect SharePoint farm design. Ideally, you need to measure the latency between SharePoint servers and users in order to reorganize servers according the smallest response time.

Network latency is the key point to determine which of the proposed scenarios to implement in the current SharePoint deployment. (Latency is the time required for a packet to travel from one point on a network to another).

Analyse the existing infrastructure and plan a SharePoint topology for redundancy.There are several different topologies - from three to six servers in farm, which can be used as a baseline. Which one to choose depends on the level of redundancy and available hardware. Not all clients can afford topology with six or ten servers in farm due to budget limitation or data centre capabilities. Finding the compromise between numbers of servers, type of hosting and servers’ roles become critical task, because this choice will affect performance and extensibility of the SharePoint farm for several years ahead.

Logical Planning

Plan number of site collections and sub sites in advance - content, location, security. Start with the single site collections and several sub sites rather then creating several site collections, and try to avoid new site collection if there are no requirements for this. The reason of such structure is that each new site collection works as a new application, with isolated scope to features, templates and search. Maintaining such structure is much easier than several site collections.

Do not end up with one big content database, because data optimisation will cause troubles in this case. For the small and development environments, single content database might be a preferable choice. However, for the large farms create several content databases and organize site collections among them. Having several content databases with sites helps to address the following:

  • Keep content database size <100>
  • Data usage optimization.
  • Simplify farm backup and restoration.
  • Flexibility for Disaster Recovery (DR) strategies.

Part 2 - Installation & Configuration
The recommended Windows environment that offers the best performance for SharePoint is to have 64-bit servers. Such an environment provides significantly larger address space than 32-bit one; more room for SharePoint assemblies, CLR/Native APIs, Network Stack, IIS/ASP.NET and other components hosted in their respective tiers.

Stsadm Technical Reference for SharePoint Server 2007 & Windows SharePoint Services 3.0

Now that's cool, an simple and sweet application in silverlight for all your STSADM commands! No more seraching the black screen for the correct command. 

For MOSS 2007

For WSS 3.0

Web Package .fwp

A Web package is a bundled collection of files that you export or import for use in a Web site. A Web package uses an .fwp file name extension. You may want to create a Web package if you want to share or reuse Web pages, a Web site, a list, or a library structure. When you create a Web package, you can include the whole Web site in the package. Or, you can include only the specific Web pages that you want. After you create a Web package, you can import and deploy the .fwp file to as many Web sites as you want.

A Web package may include the following items:
Any documents in lists and in libraries
Web pages
Web Part pages
Custom link bars

However, a Web package cannot contain list data, subsites, or security and permissions settings. When a Web site is moved as empty content, list data that is part of the original Web site does not move with the Web pages in the package. For example, a document library may contain a column that you created to track the status of documents. When you package the library, the package includes the documents, the custom column, and the settings for that column. The package does not include the data that indicates the status of the documents.

Bug in SharePoint Service Pack 2 Changes a Production License to Trial

From cmswire :

During the installation of Server Pack 2 for SharePoint 2007, a product expiry date is accidentally triggered, effectively rendering production licenses into trial licenses. Hmmm, not good.

Microsoft was quick to respond with an apology and somewhat comforting news that this bug will not affect how SharePoint functions until the expiry date has passed (180 days from the service pack install). They also said it will have no impact on customer data, configuration or application code.

While a hotfix is in the works, you can now get a manual workaround to resolve the problem. Note this was the most popular link in the blog announcing the bug. The fix requires SharePoint Admins to re-enter their product licenses numbers in the Convert License Type page in Central Administration.

The bug affects Office SharePoint Server 2007, Project Server 2007, Form Server 2007, Search Server 2008 and Search Server 2008 Express, but not Windows SharePoint Services 3.0.

Microsoft is still encouraging organizations to install the service pack. You just also have to apply the manual fix to the expiration date at the same time and you'll be on your way.

SharePoint 2010 Features

Edit : Official Update is out, catch it here....

SharePoint Server 2010 Preliminary System Requirements

64 Bit! Yes, that's what next decade is all about. In a good sense, it opens the way for large RAM on servers. Though enterprise MOSS 2007 are already 64 bit, SharePoint 2010 will empower developers with the new hardware and OS.
The other thing is cross browser support, which will satisfy many a clients.

Microsoft has released prelimenary system requirements:

  1. SharePoint Server 2010 will be 64-bit only.
  2. SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
  3. SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
In addition to the requirements listed above we also wanted to share with you some preliminary detail about SharePoint Server 2010 browser compatibility. 

To ensure the best possible experience across multiple browsers we’re focusing our SharePoint 2010 engineering efforts on targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems.  In addition we’re planning on an increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems.  Due to this focus Internet Explorer 6 will not be a supported browser for SharePoint Server 2010.

So, what can you do today to get into the best shape for SharePoint Server 2010?

  1. Start by ensuring new hardware is 64-bit.  Deploying 64-bit is our current best practice recommendation for SharePoint 2007.
  2. Deploy Service Pack 2 and take a good look at the SharePoint 2010 Upgrade Checker that’s shipped as part of the update.  The Upgrade Checker will scan your SharePoint Server 2007 deployment for many issues that could affect a future upgrade to SharePoint 2010.
  3. Get to know Windows Server 2008 with SharePoint 2007, this post is a great starting point.
  4. Consider your desktop browser strategy if you have large population of Internet Explorer 6 users.
  5. Continue to follow the Best Practices guidance for SharePoint Server 2007.
  6. Keep an eye on this blog for updates and more details in the coming months.

Microsoft Office 2010 Beta is here! Sharepoint 2010 in 2 months!

Office 2010 beta is here for all to test ! and along comes the new SharePoint designer(won't work with MOSS 2007 sites)

And Microsoft will launch an invitation-only SharePoint Server 2010 beta test in July with a select group of customers and then follow the program up with a public testing phase ahead of the Office 2010 release in the first half of next year.

The SharePoint 2010 beta/technology preview will be invitation-only and will focus on a number of its enterprise customers and target specific enterprise deployment scenarios.

Case Study: Pfizer & Content Managment

After having started my carrer in Sharepoint from Pfizer's projects, it's nice to know how the company has come a long and successfull way in content management.

They took the risk of being early starters and with super Microsoft's support, the result has been more than just great.

 A case study from Gartner on Pfizer Shows Why & How:

Like many large global companies, Pfizer had multiple content management systems in place and a range of user needs. It ultimately standardized on two global solutions: one to address collaborative content and one a system of record for regulated documents.


This Case Study details how Pfizer standardized on a basic content services (BCS) offering for work in progress along with a robust enterprise content management (ECM) platform that addresses Food and Drug Administration (FDA)-mandated content applications. CIOs, business and IT leaders, and application managers executives should read this study to see how Pfizer dealt with governance issues, migration from legacy systems and the costs of maintaining two solutions.

Key Findings
  • Pfizer had multiple content management systems (CMS) in place resulting in costly maintenance fees, strains on support and development resources, and siloed content. By standardizing on two platforms for clearly delineated tasks, it can eliminate servers and support for the legacy systems.
  • Success factors included having a solid business case, implementing a strong governance policy, leveraging third-party solutions where necessary and establishing a methodology for recouping costs.
  • Pfizer adopted a self-service model for new site provisioning that is enabled through a custom-created Site Wizard.
  • Consider the coexistence of a collaborative document management platform and a more process-centric system to balance user needs and different content applications. Identify deployment scenarios and establish clear usage guidelines, so users understand when to use which tool.
  • Build a solid business case for your SharePoint investments and for retiring legacy systems by focusing on opportunities for hard dollar savings, such as eliminating servers, not renewing maintenance fees and reducing the number of support resources applied to legacy applications.
  • As you begin to standardize on a shortlist of vendors in ECM and embark on a strategy to retire legacy systems, adopt a holistic approach to moving content into the newer systems. Along with migrating metadata and content objects, this approach should consider human issues such as going through a content valuation exercise to prune content volume.
About Pfizer
Pfizer, a global pharmaceutical company, adopted a two-prong strategy to solve its content management requirements. Pfizer's two-pronged approach is a prime example of how many Gartner clients are addressing the varying content types they must manage and providing users with appropriate tools for the tasks. It highlights the importance of good governance, building a solid business case and rationale, and leveraging third-party solutions to extend its Microsoft SharePoint implementation.


Like many large global companies, Pfizer had multiple content management systems deployed, resulting in costly maintenance fees, strains on support and development resources, and siloed content. Yet, Pfizer recognized it had a range of user needs and that one solution would not meet all. It ultimately standardized on two: Microsoft Office SharePoint Server 2007 (MOSS), a basic content services offering for collaborative content and EMC Documentum, a process-centric solution for its regulated documents. Documentum also serves as the official repository for all corporate records.

The Challenge

Being a pharmaceutical company, Pfizer had to accommodate highly regulated documents and records, but it also needed a way to support the more ad hoc and collaborative processes. For managing and storing its controlled documents and those associated with new drug submissions to the FDA, Pfizer had implemented EMC Documentum. Over the years, it has invested heavily in Documentum, resulting in a large collection of software and servers with associated customizations and IT resources. For its more casual document and content management needs, however, Pfizer had a variety of legacy systems including EMC eRoom, Open Text Livelink, Vignette's Web content management system, Plumtree and ColdFusion sites, Lotus Notes databases, Microsoft Exchange Public Folders and traditional file shares. Having this plethora of content repositories and applications resulted in costly maintenance fees, strains on support and development resources, and siloed content. Pfizer is not unusual in this regard. In a 2008 Gartner survey of nearly 400 respondents (see Note 1), 69% of enterprises indicated they had more than six repositories.


Pfizer set about to consolidate its legacy content management systems. Since the firm had already made a lasting investment in EMC Documentum, the Worldwide Technology team chose to keep it as the enterprise standard for regulated documents and corporate records. EMC's Centera is used as the long-term archive for inactive documents and records. For collaborative and work in progress content, Pfizer chose to build an enterprise collaboration platform on MOSS. This is in keeping with Gartner's advice to IT leaders, architects and planners that they consider SharePoint as a tactical basic content service providing a place to store, find and deliver documents and other content associated with project-related activities or work-in-progress content. When content is deemed final and needs to be kept long-term, it should be moved into an ECM system

Known formally within Pfizer as Enterprise Collaboration Framework (ECF), the SharePoint implementation is a collaborative, non-validated environment that handles business operational content as well as work in process documents. It is the global standard replacing the multitude of legacy systems for non-regulated content, especially eRoom and Livelink. Pfizer already migrated its static Web pages off of Plumtree into MOSS and has begun migrating other content. It anticipates moving fully to MOSS and Documentum by 2010. It will eventually be used to support the Web content capabilities now delivered via Documentum. ECF went live in September 2007, after a six-month early adopter phase. Part of the success of its coexistence strategy was due to communication and setting expectations. The Pfizer Technology Engineering team communicated to the users that Documentum focuses on facilitating the life cycle of a document, while SharePoint's focus is on facilitating the life cycle of a team.

Pfizer's ECF (MOSS) is used for a variety of collaborative and ad hoc content management activities. These include managing weekly meetings, building a knowledge base with wikis, maintaining custom contact information about team members, publishing information via a blog, task routing, creating slide show presentations and soliciting feedback with discussion boards. Pfizer implemented a library of prebuilt site templates to enable faster site creation. ECF is becoming as pervasive as e-mail within Pfizer.

EMC Documentum and ECF coexist at Pfizer and are well integrated. Pfizer worked with EMC to develop the integration between Documentum and SharePoint. Content can be easily promoted from SharePoint into Documentum. Schema Logic is used to provision shared taxonomies so that the same metadata can be enforced in both systems. Pfizer originally selected Fast (now owned by Microsoft) as the search engine to support federated searches against both systems. According to Program Manager, David Biersach, Pfizer's goal is to leverage the best of both tools and provide a smooth interoperability experience for end users.


Pfizer now has more than 41,000 active SharePoint users with 1,000 top-level, cross business unit sites and 7,000 total active team sites. It also supports secure external collaboration sites accessible to authorized non-Pfizer employees. SharePoint is installed in four data centers and supports 11 Pfizer divisions and 122 departments. By design, approximately 42% of team sites are open to all Pfizer employees, rather than just a select group and over 25% of the current team sites have members that span departments and geographic locations. This has fostered information sharing and collaboration within Pfizer.

Though it required a number of third-party add-ons and partner solutions, Pfizer found SharePoint to be agile and easy to use. Training was handled through a combination of Web-based training and classroom-based training. As implemented, ECF did not require Office 2007. Approximately 60% of Pfizer's collaborative workflow needs were met out of the box with SharePoint; another 30% are addressed via SharePoint Designer and the remaining 10% were addressed without the need for custom code using K2's blackpearl product. Pfizer leverages Cisco for load balancing, AvePoint for fine-grained backup and restore, and Vital Path for content and metadata migration. So far, Pfizer has migrated 1.3 million documents from at least eight legacy systems into ECF.

To recoup costs of the SharePoint infrastructure (licenses, FTEs, third-party add-ons and so on) and the costs of legacy system migration, Pfizer initially implemented a chargeback approach. The business departments are charged a flat fee for each SharePoint site they created. Costs were assigned to the primary owner of the department of the site and a detailed use report was provided to each department head listing every site that was assigned to them. This approach has worked well as the businesses wanted greater transparency in service costs than they had received in previous content management solutions. However, the IT department found that they have had to grant a lot of exceptions in the per site fee and it is no longer practical. In 2009, they are considering moving to a model based on storage volume (x$ per gigabyte of storage per year) rather than the per-site fee.

Critical Success Factors

Governance and usage guidelines. Pfizer put in place a strong governance policy and guidelines for usage of ECF and Documentum. Everyone at Pfizer has their own MySite and the IT leadership encourages business colleagues to create and delete sites often as projects continually come and go. Communication was key; Pfizer created a document platform comparison matrix to help explain the standard tools. It also enabled self-provisioning through an online site request wizard. This requires users to identify document types and proposed use cases for the site to ensure compliance with their governance directives.

Shared services approach. By implementing SharePoint as a shared services approach and charging back the business, the IT department's cost model had a positive chilling effect on stopping the rampant proliferation of sites for spurious reasons. This approach gave the business transparency into costs and resulted in them taking an active role in self-policing SharePoint sites.

Content valuation exercise. Content migration efforts required the business to pare down content volumes. Though the human effort required was not trivial, the benefits were worth the effort. As part of this assessment, they found that some documents in the organization had not been touched in five years. They were able to reduce 13 terabytes of document storage down to six or seven terabytes prior to migration.

Business case and executive sponsorship. The CFO and CIO required hard dollar savings. Pfizer built a business case on hard dollar savings and cost avoidance: taking servers out of the data center, not renewing software licenses and maintenance, and by reducing costs for support resources associated with legacy systems. Success will be measured by how quickly they can decommission legacy systems, with the anticipation that that will occur by 2010.

Lessons Learned

Migration. Pfizer's IT team had looked at many third-party tools and tried a few; yet found the current generation of tools and the content migration market to be in its infancy. There is urgent demand for improvement of the tools and for deeper expertise among the consulting services providers. They ended up having to write some of their own scripts to analyze documents and information in legacy systems to prune unwanted data. When doing migrations, it can be the little things, such as file naming conventions and document links, that trip you up. With SharePoint it is easy to break links to documents if a team site needs to move to a completely new or renamed path hierarchy.

Managing the businesses expectations. This was where they went wrong, according to Pfizer. They had a formal timeline for doing inventory, metadata mapping and migration, and records management, but it was too aggressive and was driven by artificial funding timelines and not realistic estimates of how long these tasks would truly take to completely accomplish. Business often did not know whether documents were needed for legal or records management purposes. An ongoing challenge is the need to ensure that SharePoint is not used as a dumping ground, but as an active content collaboration tool.

Microsoft SharePoint 14 == Microsoft SharePoint 2010

From the official SharePoint blog:

"You have probably seen the news announcement today where we announced the public beta for the new Microsoft Exchange Server 2010. As part of that announcement, we also talked about some of the names for the “14” wave of products including Microsoft Office 2010 and Microsoft SharePoint Server 2010. I wanted to answer some questions that I think will inevitably pop to the top of your mind:
What happened to the Office piece of the name? We love MOSS. . . .
The first thing you’ll notice is that the MOSS acronym goes away with the new name since Office is no longer in the SharePoint official name. No one should worry that SharePoint doesn’t work great with Office 2010 since we removed Office from the name, just like people didn’t worry whether SharePoint was a great portal product when we removed Portal from the 2007 name.
The primary reason why we took Office out of the name - lots of folks associate the name Office with the Office client. We wanted to take the opportunity to reestablish the Office name and brand to be synonymous with the client suite. I say “Give the people what they Want” so everyone should immediately think of Microsoft Office = Office apps.
Don’t try to acronym Microsoft SharePoint Server to MSS since MSS is already taken by Microsoft Search Server. Just remember, SharePoint is SharePoint is SharePoint.
What about Windows SharePoint Services?
When you read through the announcement, you may be wondering what happened to Windows SharePoint Services. While we didn’t announcement anything new for WSS, and I want to assure you that we’re definitely working on a new v4 version of the product. It’s too early to drill into any of the details but WSS is getting a lot of new features and will be a great release. We’ll talk more about WSS at a later date.
So, what was announced?
Here are my key takeaways from the interview with Chris Capossela:
• Exchange 2010 will lead the way for the 2010 (previously referred by its codename “14”) wave of technologies and it will be available in the second half of 2009. You can download a beta today.
• Using Office Web applications, customers will be able to create, edit and collaborate on Office documents through a browser.
• IT professionals will be able to choose to either deploy and manage on-premises or hosted as a service.
• For developers, we are working on Open APIs, deep support for industry standards and developer tool support with Visual Studio 2010."
Actually MOSS sounded better, but anyways we will learn to say "SharePoint Twenty Ten" very soon! 
* Just registered, no wonder good ones were already taken!

SharePoint: How to display blog feed using XML Web Part?

There is no RSS Viewer web part in Windows SharePoint Services 3.0 and my client wanted to show list feed on our intranet homepage. The constraint was, not to use some third-party Web Parts. Searching around the net, I found out that the XML Web Part is practically the same thing. After all, what’s an RSS feed other than an XML file? Getting a little creative, I thought of other ways to simply retrieve the content from other lists.

My solution? XML Web Part

Here's my list feed example as easy step-by-step guide.

1).Move to SharePoint page you want to add your list feed.

2).Open this page in edit view and add new Web Part called XML Web Part.

3).If Web Part is added to page then open it's settings window.

4).On the field XML Link insert your list feed URL. Check out if link is correct and content is receivable by clicking the link titled as Test Link.

5).Push button titled as [XSL Editor].

6).XSL editing window is opened and now insert XSL code given below. When inserted click [OK].

7).If everything is okay then you should see your list's titles as bulleted list and then save edited page.

XSL you need is here. Take it using copy and paste.

'<'?xml version="1.0" encoding="UTF-8"?'>'

'<'xsl:stylesheet version="1.0" xmlns:xsl="" exclude-result-prefixes="xsl"'>'

'<'xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/'>'

' <'xsl:template match="/"'>'

' <'div'>'

'<'xsl:apply-templates select="rss/channel"/'>'



'<'xsl:template match="rss/channel"'>'

'<'xsl:variable name="link" select="link"/'>'

'<'xsl:variable name="description" select="description"/'>'


'<'xsl:apply-templates select="item"/'>'



'<'xsl:template match="item"'>'

'<'xsl:variable name="item_link" select="link"/'>'

'<'xsl:variable name="item_title" select="description"/'>'


'<'a href="{$item_link}" title="{$item_title}" '>'

'<'xsl:value-of select="title"/'>'





Note : There is a security issue in the above post. Please set the “Anonymous Access” for the site to "entire site".

  • NOTE : "There is a security issue",We need to enable the Anonymous Access for the site collection,only then we are able to see the result.

    Server Hardware Sizer for MOSS

    The HP ProLiant Sizer for Microsoft Office SharePoint Server 2007 is an automated tool that provides a quick and consistent methodology to determine a "best-fit" server for your individual needs and enables you to both quickly compare different solution configuration (what-if scenario) and also to obtain a highly detailed, customizable server and storage solution complete with bill of materials and pricing.

    Kodak Scanners adds Sharepoint Button

    March 17, 2009: Kodak has added direct scanning to Microsoft Sharepoint Server tor the KODAK i1200 and i1300 Series Scanners.

    “Business use of MICROSOFT SHAREPOINT Server to share and store documents has exploded during the past year. Kodak recognizes the importance of this and rises to the challenge, providing customers easy scanner uploads to SHAREPOINT Servers with a just a press of the scanner’s button,” said Tony Barbeau, Vice President, Marketing, Document Imaging, Business Solutions and Services, Eastman Kodak Company.

    “Entering paper content to MICROSOFT SHAREPOINT repositories has never been so easy.”

    The MICROSFT SHAREPOINT Server connection is totally automated, requiring no additional server components and featuring a new status utility program allows users to scan and upload images simultaneously. Smart Touch enhancements also include bitmap image output, single page PDF output and customized shortcuts.

    Other new features include:

    * improved identification and deletion of blank pages;

    * merging front and rear images;`and

    * capability for third party applications to initiate scans via the Smart Touch feature, passing the image back to an application.

    For power users, KODAK Capture Pro Software, available separately, offers an even richer button function that also supports batch separation, complex file indexing and many other production quality features.

    via idm