SharePoint 2010 Document ID Feature

One of the many new features which Microsoft has introduced with SharePoint 2010 is Document ID. As most of you might be aware that in a traditional ECM [Enterprise Content Management] application each content object has its own unique ID, which is used by that object throughout its lifetime in the ECM system, no matter where the file was placed in the system. I would say this was one of the major drawback of SharePoint 2007 for eg. If you had published a document link in a SharePoint blog which was located in a XYZ document library, and later for some reason the document was moved to ABC document library within the Site Collection. You would end up with broken link.

But not anymore with Document ID. Once enabled all your documents within a Site Collection will have a unique ID and can be located using the ID no matter where the file is located in your Site Collection.

To enable the Document ID Feature

1. Go to Site Settings > Site Collection Features and Activate the Document ID Service.

2. Or you can use the following SharePoint 2010 Management Shell cmdlet to Activate the Document ID Service.

Enable-SPFeature -id docid -url <site collection url>

3. To customize the Document ID and apply Document ID to all existing Documents in the Site Collection. Go to Site Settings > Document ID Settings

And provide the String with which the Document ID will begin. I have provided Apollo for this example. Click Ok.

4. Now if you go to your document properties you should see, it has a new property called Document ID followed by a Unique ID for that document

5. The above document now has a unique ID and we can use the following link to locate the document no matter where the document is in the Site Collection

http://SP2010Servername/_layouts/DocIdRedir.aspx?ID=APOLLO-10-2

6. Note the Document ID’s might not show up instantaneously after activating the Document ID Service, the reason behind this is it creates a Timer Job for the same and once the job is executed by SharePoint you should start seeing the Document ID Field with those Unique ID’s, But if you can’t wait you can manually Run the Document ID assignment job under Central Administration > Monitoring > Review Job Definitions, or if you want to go the old school style you can run the following SharePoint 2010 Management Shell cmdlet to trigger the same.

Start-SPTimerJob -Identity DocIdAssignment

As we can see with Document ID locating and linking your document in SharePoint 2010 is easier than ever.

Steps to Upgrade SharePoint 2007 to SharePoint 2010

Steps to Upgrade SharePoint 2007 to SharePoint 2010

Recently I have a requirement is to migrate a SharePoint website created in wss3.0 to wss4.0. For moving the website to SharePoint 2010, you have to upgrade the WSS 3.0 to WSS 4.0. Follow these steps

1. Take the backup of current live website (wss3.0) using stsadm utility. 
2. Create a new machine having Windows 2008 64-bit R2 and SQL Server 2008 R2 Express 64-bit.
3. Install WSS 3.0 64-Bit and created a Site Collection using the same URL of the original server. Then patched it until it matched the 32-bit WSS 3.0 exactly.
4. Restore backup (created in step 1) on to newly created machine.
5. Once we had a working site on newly machine then simply install SharePoint Foundation 2010 and it upgraded the server to WSS 3.0 to WSS 4.0.
6. Upgrade all SharePoint custom web parts (previously build in 32 bit with VS 2008) as per 64 bit configuration.