myspace views counter
Skip to main content

Adnan Ahmed (SharePoint Architect)

Go Search
Adnan Ahmed
Project Server Gurus
Mohammed MOSS2007
Pathik's SharePoint Blog
Sanjay's SharePoint World
Sankar Adapa
Sharepoint With Amit
Need a blog here!

Microsoft Office SharePoint Server 2007 Gurus > Adnan Ahmed (SharePoint Architect)
Adnan Ahmed is a Senior MS Solutions Consultant in Version 1, the IT Consulting Company in Ireland and has involved with many large enterprises to help them realise real benefits of SharePoint 2010. MCPD SharePoint 2010 Developer| MCITP SharePoint Administrator 2010 | MCTS SharePoint 2003/2007 | MCTS Project Server 2007| MCSD.NET
Deployment Roadmap for WSS 3.0 and MOSS 2007 Updates

How to determine which version of  WSS 3.0 / Microsoft Office SharePoint Server 2007 you are using


Microsoft has also added a new section on the Microsoft TechNet web site to help with identifying current required SharePoint patch levels. The latest SharePoint 2007 path level is released on 27th April, 2010. The latest SharePoint 2007 patch level is called April 2010 cumulative update (CU).


WSS 3.0/MOSS 2007 Patch Level

Microsoft KB Number

Version Number

Release Date

MOSS 2007 or WSS 3.0 April 2010 Cumulative Update

981042 / 981043


27th April, 2010

MOSS 2007 or WSS 3.0 April 2010 Cumulative Update

978395 / 978396


23rd February, 2010

MOSS 2007 or WSS 3.0 December 2009 Cumulative Update

977026 / 977027


15th December, 2009

MOSS 2007 or WSS 3.0 October 2009 Cumulative Update

974988 / 974989


27th October, 2009

MOSS 2007 or WSS 3.0 August 2009 Cumulative Update

973399 / 973400


25 August 2009

MOSS 2007 or WSS 3.0 June 2009 Cumulative Update

971537 / KB 971538


15th July, 2009

MOSS 2007 or WSS 3.0 April 2009 Cumulative Update

968851 / 968850


30th April, 2009

MOSS 2007 or WSS 3.0 SP2

953334 / 953338

28th April, 2009

MOSS 2007 or WSS 3.0 Infrastructure Update

951695 / 951297

15th July, 2009

MOSS 2007 or WSS 3.0 SP1

936984 / 936988

8th December 2007





How to configure PDF iFilter for SharePoint Server 2010 or Search Server 2010

I have recently installed and configured Search Server 2010 Express on my VMware machine for evaluation purposes. Once I configured basic steps to configure Search Centre site and necessary settings, I decided to install PDF iFilter (x64). Last year, I posted similar article on how to install and configure PDF iFilter for SharePoint 2007 (64bit), which can be found at: I didn't find any single decent article on Google, which clearly explain the process of installing and configuring PDF iFilter for SharePoint Server 2010 or Search Server 2010 Express edition. So I decided to follow my own article and I was hoping that it should be straight forward to install and configure PDF iFilter for SharePoint 2010. Apart from updating the registry settings required to update GUID for .pdf, remaining steps are similar.

Follow steps below to install and configure PDF iFilter on SharePoint Server 2010 or Search Server Express 2010.

  1. Install PDF iFilter 9.0 (64 bit) from
  2. Download PDF icon file from pdf16.gif and copy at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\
  3. Add the following entry in docIcon.xml file, which can be found at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML

    <Mapping Key="pdf" Value="pdf16.gif" />

  4. Add pdf file type on the Manage File Type page under Search Service Application.
  5. Open registry by executing regedit on the Start --> Run.
  6. Navigate to the following location:

    \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension

  7. Right-click Extension, a menu will appear.
  8. Click New--> Key to create a new key for .pdf. See screen shot below.

  9. Enter .pdf and save key.


  10. Now add the following GUID in the default value as shown in the figure below.



  11. If you are configuring SharePoint Server 2010 then restart Search service by executing the following command on the command line:

    NET STOP OSearch14

    NET START OSearch14

  12. If you are configuring PDF iFilter on Search Server 2010 then restart the SharePoint Server Search 14 service as shown in the figure below.

  13. Perform incremental to include PDF files.
  14. PDF iFilter is successfully configured. Now you can search for the content of PDF file. See screen shot below.


    Note: SharePoint Server 2010 or Search Server 2010 Express provide out of the box search support for .ZIP files, so you download have to install Microsoft Filter pack as you used to do with MOSS 2007.


    I do hope that you will find this article useful. Please leave your comments.


How to configure SSL certificate for the central administration web site of SharePoint Server 2010

In this article, I will explain how to install and configure self-signed SSL certificate for the central administration web site in SharePoint Server 2010. This procedure is also applicable for any other web applications for both SharePoint 2007 and SharePoint 2010.

Follow steps below to configure SSL certificate for central administration web site:

Create Self-Signed SSL Certificate:

  1. Log into the web server by using the SharePoint Set up account.
  2. Open IIS Manager. Click on the IIS Server and then double click Server Certificates.
  3. Click Create Self-Signed Certificate link as shown in the figure below.



        4. Enter the name of the SSL certificate that you want to associate with the central administration web site.



        5. SSL certificate is created.


Bind Self-Signed SSL Certificate with the central administration web site:

        6. Right-click Central Administration web site. On the context menu, click Edit Bindings.

       7. A windows dialogue box will appear.



          8. Click Add to create a new binding for central administration web site.

          9. On the Add Site Binding window, select https from the Type dropdown and select SSL certificate from SSL certificate dropdown. Click OK to save changes.

           10. Click Remove button to remove default http binding as shown in the figure below.



        11. Now we have only https binding left for the central administration web site.



Update SSL Settings for the central administration web site

         12. Select SharePoint Central Administration v4. Double-click SSL Settings to open SSL Settings page.

13. Configure the following options and click Apply to save settings.

         - Require SSL (checked)

         - Require 128-bit SSL (checked)

         - client certificate: Ignore (selected)




Execute STSADM command to update registry settings on the SharePoint Farm

 14. Open command prompt and execute the following statement.


STSADM -o setadminport -port 443 -ssl



          15. Now open SharePoint Central Administration Website.



          16. As you see in the screen shot above, Internet Explorer is showing SSL certificate error. Now to browse to alternate access mapping page and specify fully qualified domain name for the central administration web site. i.e. ServerName.DomainName. Once the alternate access mapping settings are updated, close your browser and open the central administration web site again.



I do hope that you will find this article useful, when SSL certificate for the SharePoint web applications. Please leave your valuable comments.




Free SharePoint Server 2010 Exam Preparation by Microsoft E-Learning

Microsoft E-Learning is offering free SharePoint 2010 certification preparation by Microsoft Certified Trainers. You can register for these certification preparation sessions by clicking the links provided below.

  • Certification Preparation session: SharePoint Server 2010 TS and Pro Exams: 70-667 and 70-668 by Telmo Sampaio Microsoft Certified Trainer (MCT)

Start Date: Thursday, May 13, 2010 12:00 PM Pacific Time (US & Canada)

  • Certification Preparation session: SharePoint Server 2010 Developer: Exam 70-573 by Christopher Harrison, Microsoft Certified Trainer (MCT)

Start Date: Thursday, May 20, 2010 8:00 AM Pacific Time (US & Canada)

  • Career Specialization for Network Administrators: Skills necessary to become a SharePoint Administrator by Russ Kaufmann

            Start Date: Wednesday, May 26, 2010 12:00 PM Pacific Time (US & Canada)

How to install and Configure SharePoint Server 2010 RTM

SharePoint Server 2010 RTM is available to download for MSDN/TechNet subscribers. This article describes steps required to install and configure SharePoint Server 2010 RTM Edition on a one box VMware 64 bit edition.


  • Windows Server 2008 with SP2 or Windows Server 2008 R2
  • Cumulative update package 7 for SQL Server 2008 Service Pack 1 (10.0.2766.0) or later
  • SharePoint 2010 Installer will automatically install the remaining software prerequisites

Steps to follow:

  1. Download SharePoint Server 2010 ISO image for MSDN web site
  2. Run setup.exe to start the installation process. Software prerequisites will be installed.


       3.Restart your computer to complete the software prerequisites installation.

       4. SharePoint 2010 setup will start. On the screen below enter product key and click Continue to proceed.


         5. Click I accept the terms of this agreement and click Continue to proceed.

         6. Choose File location and click Install Now.

         7. SharePoint 2010 installation is completed. Click Close to Run the SharePoint Products Configuration Wizard.

         8. SharePoint configuration wizard is started. Click Next to continue.



         9.The wizard will inform you that the number of services will be restarted or reset during the installation. Click Yes to continue.


         10. Choose Create a new server farm option. Click Next to proceed.



         11.  On the Specify Configuration Database Settings screen, enter the following:

          - Database Server: enter database server name  

          - Database Name: Enter SharePoint Configuration Database Name

         - Database Access Account:

           User Name: Enter SharePoint Server Farm access account

            Password: Enter password

          12. Enter farm security settings.


          13. On the SharePoint Central Administration Web Application screen, configure the following:

       - Specify port number (Checked)

          Enter a port number between 1 and 65535.

         - Authentication Provider: Choose NTLM

         14. On the next screen, click Next to proceed.

          15. SharePoint configuration start provisioning SharePoint 2010 Farm.


         16. Once SharePoint farm configuration is completed, a summary screen will appear to provide the information regarding the farm.



I do hope that you will find this article useful in installing SharePoint 2010 in your environment.

SharePoint 2010 is available to download for MSDN/TechNet Subscribers

Great news! SharePoint 2010 can be downloaded for MSDN/TechNet Subscribers.

You may be interested in to download some other relevant downloads available for MSDN/TechNet subscribers.

Project Professional 2010

Office 2010

Enjoy and please leave your comments about your experience in installing SharePoint Server 2010.

SharePoint 2010: External Content Type Connectivity Error “The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.”

After watching a training video of Andrew Connell on Channel 9, I decided to create my first external content type to connect to my sample Adventure Works database. As expected after creating necessary Meta data and BCS service applications, when I tried to connect to External content type from MS SharePoint Designer, I got the following error message. 

Then I tried to browse Meta data service application and got the following weird error message.

The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.


After reviewing the installing steps of SharePoint 2010, I have found out that I needed to install a hot fix for Windows Server 2008 (Windows6.0-KB976394-x64),

which can be found at

Install this hot fix and restart the server to fix this issue.


You also need to follow the following article to fix the SSL Cert issue.

Reassigning the correct SSL certificate to SharePoint 2010 Web Services IIS Site


I do hope this article will help you to fix this problem.




SharePoint 2007 couldn’t send any email, when using Exchange 2007

MS Exchange 2007 is by default more secure than MS Exchange 2003 and it does not allow anonymous client machines to send emails by using MS Exchange 2007 SMTP server. I have recently installed MS Exchange Server 2007 for my SharePoint 2007 integration environment. I could easily associate mailboxes to domain user accounts and check emails by using MS Outlook web access (OWA). I have configured the SMTP server name of my exchange server in the Outgoing e-mail settings in the SharePoint central Administration. When I try to add users in my SharePoint and allow SharePoint to send e-mail to news users, SharePoint throws the following exception.

"The user or users have been added successfully, but there was an error in sending the e-mail message. The server may not be set up correctly to send e-mail. To verify that e-mail is configured correctly, contact your server administrator. "

Then I looked at further into the SharePoint logs to find out the actual cause of this error. SharePoint logs have provided me the following exception.

#160005: Bad response from SMTP host'': 530 5.7.1 Client was not authenticated .


Actually MS Exchange Server 2007 does not allow anonymous client machines to send emails. To fix this problem, I have followed the interesting msdn blog article and it worked perfectly fine.

In this article, I will provide you screen shots of steps required to create a Receiver Connector in Exchange 2007 to receive e-mail from Internet (or client machines).

Steps to follow:

  • Open MS Exchange 2007 Management Console
  • Click Server Configuration on the left side of the Exchange Management Console and then Click Manage Hub Service, as shown in the screen shot below.

  • Right Click Hub Transport and Click New Receiver Connector... as shown in the figure below.

  • In the New SMTP Receiver Connector window, enter receiver name and select Internet as the intended use for this receiver connector. Click Next to proceed.

  • In the next screen, specify FDQN name of MS Exchange server 2007 and Click Next to proceed.

  • In the next screen, the wizard will provide you details of the new SMTP receiver connector, Click New to create a new receiver connector.

  • Now New SMTP Receiver Connector is successfully created. SharePoint 2007 will still throw the exception, when try to send an email.
  • Now double click the newly created SMTP Receiver Connector and specify the Remote Servers with the specified IP ranges to send emails. You can specify only SharePoint server IP addresses in the Receive mail from remote servers that have these IP addresses section as shown in the figure below.

I do hope that you will find this article useful for your troubleshooting.

Please follow my blog article, if you would like to know the steps required to install MS Exchange Server 2007.

Download: Free MS Office 2010 e-book
Microsoft press has released first e-book for MS Office 2010. Full detail can be found at:
How to install MS Exchange Server 2007 on a MS Windows Server 2008 VMware/VPC

Last week, I was involved in building the Integration environment for SharePoint 2007 for public facing web site. As you all know that POP3 Service is removed from MS Windows Server 2008. The POP3 service was very useful e-mail service on a development virtual PC to configure SharePoint alerts. I wanted to test SharePoint alerts on our integration environment, so I decided to install Exchange Server 2007 on a Windows Server 2008 VMware for my SharePoint integration. I have never installed and configured Exchange Server 2007 on a test/dev/production environment, so I was bit nervous and excited to install and configure on my SharePoint environment.

I am really excited to say that it was really painless process for me to install Exchange Server 2007 on a VMware running Windows Server 2008. During the installation and configured, I have taken screen shots of steps required to install and configure MS Exchange to help SharePoint professionals, who have no previous background of administering MS Exchange Server like me.

Steps required to install MS Exchange Server 2007 on a MS Windows Server 2008

  1. Run MS Exchange Server 2007 ISO Image


  2. The Exchange installer wizard will install. Step 1 and Step 2 of the installation wizard will already be installed on MS Windows Server 2008. Click "Step 3: Install Microsoft Windows PowerShell". A pop up command window will appear as shown above to provide you information on how to install Windows PowerShell.
  3. I have followed the command prompt approach to install Windows PowerShell. Open command window and run the following command:

    ServerManagerCmd –i PowerShell


  4. It takes 2-3 minutes to install Windows PowerShell.

  5. Once Windows PowerShell is installed on your server, run the MS Exchange installer again.

  6. This time, Click "Step 4: Install Microsoft Exchange Server 2007 SP1". On the Introduction screen, Click Next to proceed.

  7. On the Next screen, Choose "I accept the terms in the license agreement" and Click "Next" to proceed.

  8. On the next screen, choose "NO", if you don't want to send Error reports.

  9. Choose Typical Exchange Server Installation in the step below and Click Next to proceed.

  10. Enter Exchange Organisation name and Click Next to proceed.

  11. Click NO, if you don't have client machines running MS Outlook 2003 or earlier versions. Click Next to proceed.

  12. On the next screen below, Exchange setup will check that all pre-requisite components of the server are installed.

  13. Readiness Check step has identified number of missing windows components on my server.

  • Install Ldifde.exe. Run ServerManagerCmd –i RSAT on the command prompt to install this feature.

  • Ldifde.exe is successfully installed. Now installed all remaining components of IIS 7. Open Server Manager and Select Roles and Click Add Role Service to select all required IIS 7.0 services for MS Exchange Server.

  1. Once you have installed the missing components for MS Exchange, Click Install in the MS Exchange wizard to start the MS Exchange installation.

  2. MS Exchange Server 2007 will install total 6 items as shown in the figure below.

  3. MS Exchange 2007 Server is installed successfully.


Steps required to activate MS Exchange Server 2007 Product Key

  1. Restart the server. Once the server is rebooted, Open MS Exchange Server 2007 Console.

  2. Click Enter Product Key link to open Product Key window. Enter MS Exchange key and click Enter to activate your product.

  3. MS Exchange Server 2007 is successfully activated.


Steps required to create Mailboxes for Domain User Accounts in MS Exchange Server 2007

  1. Run MS Exchange Server 2007 Console. Right Click Mailbox under Recipient Configuration menu and then Click New Mailbox to create or associate domain user's mail boxes.

  2. Choose User Mailbox and Click Next to proceed.

  3. In my scenario, I wanted to associate mailboxes for existing users that I had already created on my domain controller for my Integration environment. Click Existing Users option button and Click Add to select users from the domain controller.

  4. On the screen below, specify Mailbox database. Click Next to create mailboxes for the selected existing domain user accounts.

    Now you have successfully created mailboxes for existing domain user accounts. Next step is to open the MS Outlook web access to test an email account. Click Client Access menu in the Server Configuration. On the right side of the screen, you will see OWA folder. Double Click OWA folder to locate the MS Outlook OWA URL as shown in the figure below.

    Open the MS Outlook Web Access URL and after entering user credentials you will see, user's mailbox.

    Now you are ready to use MS Exchange Server 2007. I do hope that you have found this article useful. Please leave your comments and follow my blog for more articles.



SharePoint 2007 configuration wizard failed (Cannot connect to database server or database server does not exist)

Last week, I was building a SharePoint Integration environment on 64-bit VMware machines, which are hosted on VMware ESXi Server. All VMware machines in my environment are built on Windows Server 2008 operating system. The database server virtual machine is using SQL Server 2008 Sp1 (64 bit). After installing the SharePoint 2007 on one of my virtual machine, I have started the SharePoint Configuration Wizard. On Step 2 of configuration wizard, I have got an unusual error message that SharePoint cannot connect to my database server or database server name does not exist. I have seen similar type of messages during configuration wizard in the past and most of the time; the issue was to do with network connectivity.

My first thought was to ping the DB server from my SharePoint WFE virtual machine. Surprisingly, I was able to ping my DB Server by either DB Server Name or IP address. I have defined SQL Server aliases for my SQL Server, so I thought may be SharePoint does not like SQL Server alias name on windows 2008 server platform. I decided to connect SQL Server 2008 machine by creating an ODBC connection from SharePoint box. Surprisingly, I have found out that I could not be able to successfully connect SQL Server 2008 machine from SharePoint box by using ODBC connection. This means that SharePoint was not causing any issue in connecting the database server. After spending quite a bit of time on internet, trying to figure out this issue, I have found out that in windows 2008 server, windows firewall is enabled by default and it disabled all ports except Port 80. I tried to disable Windows 2008 firewall on SQL Server 2008 box and hurrah, I was able to create an ODBC connection successfully from the SharePoint server. I knew that Network Administrators don't like to disable Windows firewall completely. After further investigation, I have found out that you need to add SQL Server default port i.e. 1433 or whatever port number that you are using to communicate with SQL Server must be added in the exception list in the Windows firewall. Once you exclude SQL Server Port e.g. 1433 in the windows firewall, you can successfully pass the step 2 of SharePoint configuration wizard. Screen shot below describes how to exclude SQL Server Port in the windows firewall.


How to configure SSL certificate for SharePoint web application on IIS7/Window Server 2008

The configuration of SSL certificate on IIS 7 (Windows Server 2008) is bit different than in IIS 6. In this article, I will demonstrate on how to configure SSL certificate on SharePoint Central Administration Site, which is deployed on Windows 2008 Server.

  • Log on to SharePoint Web Front End Server
  • On command prompt, type inetmgr to open IIS Manager.
  • Click on the IIS Server (Machine Name) and then Double Click Server Certificates



  • Click Create Self-Signed Certificate link on the right side of the pane.

  • Enter the name of SSL Certificate. You can create separate SSL certificate for each web application in your SharePoint farm.

  • Click OK to create the certificate.
  • Now, extend the SharePoint Central Administration web site.
  • Open Internet Explorer and browse Central Administration web site
  • Click Application Management and then click Create or extend Web application

  • Click Extend an existing Web application link.

  • Enter the following information in the next screen below:
    • IIS Web Site (Port): Enter 443
    • Host header: Enter host header name of your central administration web site
    • Security Configuration (Use Secure Socket Layer (SSL)): Select Yes
    • Zone: Choose the zone for the central administration web site which is free


  • Now open IIS Manager and Right click on the extended Central Administration Web Site and Click Edit Bindings.

  • Click Edit button, this action will open another window. Select SSL certificate that you have previously created and click OK to associate the SSL certificate.

  • Open Internet Explorer and browse SharePoint central administration site on https protocol e.g. https://centraladminssl/

    Note: The error on the above page shows that your certificate is not trusted. ON production environment, you must trusted 3rd party certificate e.g. VeriSign etc.

Now your SharePoint central administration is running on SSL certificate.


How to Sysprep Windows 2008 Servers

The way we use to Sysprep windows machine are changed in Windows Server 2008. I should admit that it's lot simpler and less painful to Sysprep Windows Server 2008 than any of the previous versions of Windows.

You can find complete detail about Sysprep on Sysprep for Windows Microsoft web site. In a nutshell, it allows us to re-use one of your virtual machine with new name i.e. to make cloned images on VPC or VMware etc. The Sysprep removes system specific information such as SID, reset Administrator password and reset the windows product activation.

Steps required to Sysprep Windows 2008 Servers:

  1. Run Sysprep.exe tool at the windows command prompt.

    You can find Sysprer.exe at c:\Windows\System32\sysprep\sysprep.exe

  2. A System Preparation Tool 3.14 will be presented. Specify the following settings before clicking the OK button.

    1. Choose "Enter System Out-of-Box Experience (OOBE)" in the System Cleanup Action Setting.
    2. Check the "Generalize" check box to regenerates the computer security identifier (SID).
    3. Select "Shutdown" option for Shutdown configuration.
  3. Click "OK" to start Sysprep work.
  4. The Windows Server 2008 will be shutdown itself.

Note: If you have already copied VHD file (VPC) or VMDK file (VM Ware) for new virtual machine, then you can choose to select "Reboot" option in the Shutdown Options Settings in the Sysprep tool. Once you restart the Windows Server 2008 machine, you will see the following screen shot. After couple of minutes, you will be asked to specify Time Zone, Language and reset the admin password.

SharePoint Foundation 2010 Beta (x64) and SharePoint Designer 2010 Beta (x86 & x64)

I was downloading some other Microsoft components from MSDN subscription web site and found out that SharePoint Foundation 2010 Beta (x64) and SharePoint Designer 2010 Beta (x86 & x64) are also available to download for MSDN subscribers. It's really good news for SharePoint gurus so hurry up and download the SharePoint 2010 to start play with this new product from Microsoft.

In the next couple of weeks, I will be blogging some new features of SharePoint 2010 with screen shots to provide a comprehensive view of features that SharePoint professionals should start looking at. So please do come again and visit my site for exploring new features of SharePoint 2010.


SharePoint 2010 Book
During the SharePoint Conference attendees got a SharePoint 2010 book. You can download this book from Eric Harlan's web site 
SharePoint 2007 or Windows SharePoint Services 3.0 with SP2 slipstream version

You must install SharePoint 2007/WSS 3.0 with SP1 or later version on Windows Server 2008 operating system. Otherwise your installation will fail.

Note for Windows Server 2008 Release 2: You must install WSS 3.0 or MOSS 2007 with SP2 slipstream version. WSS 3 or MOSS 2007 without SP2 slipstreamed would be blocked by windows. Complete detail can be found at Install MOSS 2007 & WSS 3.0 on Windows Server 2008 R2 – you will need SP2 slipstream

To install MOSS 2007/WSS 3.0 with SP2, you can download the slipstream builds from Microsoft web site:

Windows SharePoint Services 3.0 with SP2 (x86)

Windows SharePoint Services 3.0 with SP2 (x64)

You can build slipstream version of MOSS 2007 with SP2 by following these articles:



Comprehensive list of development tools for SharePoint Server 2007

I have tried to summarise the list of development tools that you require on your day to day development. Please post your comment, if I miss anything here.

The list is growing and now I have 66 development tools for SharePoint listed in this post.

  1. App Pool Manager (
  2. U2U CAML Query Builder (
  3. .NET Reflector (
  4. SharePoint Explorer for WSS 3.0 ( )
  5. SharePoint Log Reader (
  6. BDC Meta Man Tool (
  7. SharePoint Inspector (
  8. SharePoint Explorer for WSS 3.0 (
  9. SharePoint Dispose Checker Tool (
  10. Windows SharePoint Services 3.0 SDK (
  11. Microsoft Office SharePoint Server 2007 SDK (
  12. Microsoft InfoPath 2007
  13. Microsoft SharePoint Designer 2007
  14. Microsoft Office 2007
  15. WSP Builder for SharePoint (
  16. Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions (
  17. Windows SharePoint Services 3.0 Tools: Visual Studio 2008 Extensions (
  18. SharePoint Administration Toolkit v2.0
  19. SmartPart (
  20. SharePoint Installer (
  21. SOAP calls to the SharePoint web services (
  22. Microsoft Network Monitor 3.2 ( ) Thanks to Patel for providing me this link.
  23. SharePoint Work Acceleration Toolkit 2007 aka (SWAT) (
  24. MetaVis Architect for SharePoint (
  25. SharePoint 2007 Test Data Population Tool ( Capacity planning and performance testing tool that populates data for testing SharePoint deployments
  26. Imtech Test Content Generator v1.3.0.0
    Creating a given number of publishing pages with the desired page layout and content
  27. SharePoint Tips Utility Pack
    Collection of tools including recursively delete sites, create and modify lists in multiple sites at once, and push a web part to multiple sites at once.
  28. SharePoint Cross-site Configurator
    Automates the process of deploying MOSS site settings in all or selected sites in a server farm. Includes applying master pages, web titles, audit controls and expiration policies.
  29. SharePoint Content Deployment Wizard
    Allow a granular selection of content to be exported from site collections, webs, lists, folders, and list items to a .cmp file (Content Migration Package) which can be copied to other servers for import.
  30. Sushi Tool for SharePoint
    Performs common administrative tasks. Can backup sites, copy views between sites, bulk create sites, apply themes just to name a few functions
  31. SharePoint Developer Bookmarklets
    Great set of bookmarks to make navigating a SharePoint Web Site easier.
  32. LINQ to SharePoint
    Provides a custom query provider for LINQ that allows the querying of SharePoint lists using LINQ syntax
  33. SharePoint config store
    Provides the framework for using a SharePoint list for application configuration values
  34. SharePoint Dispose Checker Tool
    Helps to check that unmanaged SharePoint objects are correctly disposed of in code
  35. PowerShell Extensions for SharePoint
    Provides functionality for working with the SPWeb object.
  36. SharePoint Automation
    Extensions that assist in the use of working with the SharePoint object model from PowerShell.
  37. The SharePoint PowerShell Module (SPoshMod)
    Framework for SharePoint PowerShell scripts.
  38. AC's WCM Custom Commands for STSADM.EXE
    STSADM extensions for publishing sites and generating content type and column features.
  39. Imtech OCD Export
    Simplifies the process of provisioning Publishing Pages by extracting existing pages to XML. The files generated allow you to wrap your Publishing Pages in a Feature.
  40. SharePoint Automation
    List of almost 100 STSADM extensions that cover a variety of development and administrative tasks.
  41. stsadmWin 2007
    Provides a Windows UI version of the STSADM tool
  42. SharePoint 2007 Features
    Large collection of SharePoint features designed for developers and administrators. Provides assistance for debugging, logs, field and content type development, publishing sites, event receivers, and many more.
  43. SmartTools for SharePoint
    Collection of SharePoint features such as What's New, Auto complete Text Field, Enhanced Site Actions, and more
  44. Yet Another CAML Query Tool
    Converts SQL-like queries into CAML.
  45. Imtech ListInstance Generator
    Generates the ListInstance based on the List Template from a particular Feature
  46. CAML.NET
    Set of .NET language-based tools for creating dynamic, reusable CAML query components. Build CAML queries dynamically in code while preserving the syntactic structure of the native CAML language.
  47. SharePoint Manager
    SharePoint object model explorer for inspecting your SharePoint environment. Can browse every site on the local farm and view every web, list, event receiver, etc... Enables the changing of properties
  48. RedGate Reflector
    Allows exploration of any .NET assembly, including those provided by SharePoint. Shows where and how methods and objects are used. Find feature for fields, properties, and methods.
  49. Search Community Toolkit
    A number of tools and code samples that have been contributed to enhance the Microsoft search experience (Microsoft Office SharePoint Server 2007 (MOSS) Search, Search Server 2008 and Search Server 2008 Express).
  50. SharePoint Search Service Tool
    Web service client that can explore the scopes and managed properties of a given SharePoint Search SSP, build queries in either Keyword or SQL Syntax, submit queries, and examine the raw web service results.
  51. zevenseas SharePoint Search Coder
    Allows graphical building of queries and examination and testing of the SQL generated by the object model.
  52. SharePoint Query Web Service Test Tool
    Test tool for WSS V3's Query web service. Allows you to generate the request XML and send it to the web service.
  53. STORM
    Tests any web service (including SharePoint)
  54. Fiddler
    Examines the network traffic of pages as they load. Check the size of pages. Recommended for deploying public facing websites.
  55. Firebug for Firefox
    Net console provides network statistics.
  56. YSlow for Firebug for Firefox
    Analyses page performance and provides network statistics
  57. SharePoint Development Environment Modifications (SPDevMod)
    Collection of STSADM extensions and plugins for Visual Studio
  58. Code Rush/Refractor Tools for SharePoint Developers
    Extensions to Code Rush/Refractor to assist SharePoint development.
  59. Imtech Fields Explorer Visual Studio 2008 plug-in
    Quickly find the field names needed for CAML queries and controls
  60. Microsoft - BDC Definition Editor
  61. ARF is a FREE development framework for SharePoint
  62. CSS Friendly Adapters
  63. Mobile Entrée(TM) is the first ever SharePoint mobile application framework (
  64. The SharePoint branding tool for easy configuration of themes, logos, etc. (
  65. SharePoint Deployment tool / Capacity planning tool ( with instructions on how to use it (
  66. SharePoint Site Manager 2007 (
  67. Debug View for windows (An excellent tool for tracing/debugging)

 Download DebugView (286 KB)

Thanks to Matthew Marino, Jeremy Thake , Yaroslav Pentsarskyy and Jason Hall for providing me some of the above URLs.


Thanks to Dan Jordan for suggesting me SOAP calls to SharePoint Web Service link.


How to setup Windows Server 2008 Domain Controller on a VPC (Server)

This article will explain how to setup Windows Server 2008 Domain Controller on a VPC. Steps remain the same for physical machine. Follow the steps below to setup domain controller:

1.    Logged into machine as local administrator


2.    Run dcpromo command on windows command prompt. System will start checking whether the binaries are already installed already. It may possible, if you have run dcpromo command previously.


3.    The Active Directory Domain Services Installation Wizard will start as shown in the figure below. You can either enable advanced mode installation checked or leave it unchecked. In my case, I have enabled advanced mode installation. Click Next to proceed.



4.    Operating system compatibility announcement will be display. Please read the message and Click Next to proceed.




5.    Next screen will allow you to choose Deployment Configuration i.e. Create a new domain or Add this machine to existing domain controllers. In my case, I have chosen "Create a new domain in a new forest". Click Next to proceed.



6.    Enter Fully Qualified Domain Name (FQDN) of your forest. In my case, I have entered for my VPC. Click Next to proceed



7.    As I have selected advanced mode installation in step 2 above, so Domain NetBIOS Name screen will appear Otherwise installation will skip this screen. Enter NetBIOS name of the domain in the next and Click Next to proceed.



8.    Next screen will allow you to select Forest functional level; I have chosen Windows Server 2003, which will allow me to add WIN2003 or later version of domain controller to my domain. Click Next to proceed.



9. In the previous step, as I have selected Windows Server 2003 as my forest functional level, so that domain functional level screen appears at this stage. I have again selected Windows Server 2003 as my domain functional level and click Next to proceed.



Note: I have chosen Windows Server 2008 in the previous step then installer will automatically skip this step.


10. In the Additional Domain Controller Options screen, you will be asked to select Domain Name Service (DNS) to install as part of your domain controller installation. If you want to make this Domain Controller to server as DNS server as well, then check DNS Server checkbox. In my case, I have checked DNS Server checkbox and clicked Next to proceed.

11.  Please make sure that you have assigned static IP to your domain controller otherwise you see screen shot below. Assign static IP and click NO to proceed

12. If the wizard cannot create a delegation for the DNS server, it displays a message to indicate that you can create the delegation manually. Click YES to proceed

13. Now you will have the location where the domain controller database, log files and SYSVOL are stored on the server.

14. This screen will allow you to specify windows paths to store database information, log files and SYSVOL. SYSVOL stores Group Policy objects and scripts. Leave the default path settings and click Next to proceed.

15. In the Directory Services Restore Mode Administrator Password (DSRM) screen, enter the Directory Services Restore Mode Administrator Password.

Note: The Directory Services Restore Mode Administrator password is different from the Domain Administrator Password. Assign a password for the Administrator account that will be used, when this domain controller is started in Directory Services Restore Mode. Always use strong password for Directory Service Restore Mode Administrator account.

16. Next screen will display settings that you have selected during installation wizard. These settings can exported to an answer file for use with use with other unattended operations. Click Next to proceed.

17. Now DNS installation will start. See screen shot below.

18. Now Group Policy Management Console will start. Wait for Group Policy Management Console operation to finish.

19. Configuring DNS Server configuration console will start, once Group Policy Management Console will complete. See screen shot below.

20. Setting up this server or VPC to host Domain Controller is completed. Click Finish.

21. Click on Restart Now to restart your server or VPC for the changes to take effect.

22. Once server will reboot, this server will become a domain controller.

Please provide your comments about this article.


Summary of sessions of European Best Practices SharePoint Conference 2009

Last month, I have attended European SharePoint Conference held in London. Overall the conference was a success and everybody learnt a lot from SharePoint MVPs, who are best in delivering of what they know.  I have written down my notes during the conference and decided to share best practices discussed in the sessions that I had attended. Once I will receive DVD of all sessions, I will update my blog to provide more information on best practices discussed in other sessions.

Session: Best Practices for developing a SharePoint Web Part (Presented by Todd Bleeker)

§  Naming Convention for choosing library name

o    CompanyProject.Contents.Purpose

e.g. PMCentrix.WebParts.Navigation

o    Naming Convetion for Choosing Web Part class name


e.g. MyTasksPart.cs

§  Path of User Controls

Create a folder under ..[12 hive]\template\controltemplates\UserControl\

Create a User Control folder for a place to deploy all of your user controls.

§  Inherit Web Part class by using ASP.NET Web Part Library to develop a web part

o    i.e.  System.Web.UI.WebControls.WebParts

§  Always use CreateChildControls() as an event to write your code

o    Never use Render()event of a web part

o    Never use RenderControl()event of a web part

o    Rarely use RenderContents() event of a web part

o    Avoid using OnInit() event

o    Always call the Base Class method before even your try... catch statement

§  Must sign and give strong name to your web part assembly

§  Consider to deploy your web part assembly in the web application BIN directory instead of GAC i.e. Prefer to use Code Access Security (CAS) instead of Global Assembly Cache (GAC) for deploying web part assembly

o    Benefits of deploy Web Part assembly into BIN folder:

§  Fastest iterative approach i.e. code, compile and refresh

§  No need to recycle application pool of web application

§  Use Static Version for versioning of your web part assembly

§  WSPBuilder is an industry tested tool for creating a deployment package for your web part, so why not use it.

§  Use Web Part properties and avoid and hardcoded text

§  Call EnsureChildControls() procedure before writing your web part code in the CreateChildControls() event

Session: SharePoint, SQL Server Storage Best Practices (Presented by Mike Watson)

§  SQL Health is equal to SharePoint Health, so never only consider the sizing matrix of SharePoint

§  How to scale SQL Server: You have two options; Scale Up i.e. by adding more memory or add more SQL Servers in the cluster or Scale Out i.e. Add another SQL Server after every 1TB of content space

§  Scale Out is more flexible for replication operation but Scale Up is more cost effective

§  Best Practice: Allocate 10% of overall SharePoint Content or 300GB disk space for Tempdb database

§  Allocate separate and dedicate disk space for logs

§  Best practices for choosing RAID level:

o    Use RAID 10; why??

§  Better redundancy

§  Faster and less impacting rebuilds

§   2 * write performance

§  Optimised for IO operation

§  Disadvantages:

·         Expensive

·         Lower your overall disk capacity


§  Use RAID 5 when:

o    Storing content

o    Content is replicated

o    SQL failure is automatic between content

o    Issues with RAID 5:

§  Recovery takes longer

§  Slow for write operations

o    Risky

§  Best practices for network bandwidth (Gigabit or better network)

§  Extra attention should be given to MySite. MySite takes more time to render than team site

§  Never program SharePoint database to use autogrow

§  64-bit hardware for SQL Server is recommended

§  Use multiple data files for SharePoint database i.e. no. of data files = no. of CPU core

§  Defragment your databases regularly

§  Use differential backups

§  Don’t virtualise SQL Server

§  Ideally don’t exceed 5 web server per SQL instance

§  Scale SQL Server Out as you add more SharePoint servers

§  Prioritise your SQL Server Hardware in the following order:

o    SQL Server à Index à Excel à Search à WFEs

§  Best practices for virtualisation

o    Hardware guidance does not change in virtualisation

§  i.e. 4 processors physical = 4 processors virtual

§  16GB RAM physical = 16GB RAM virtual

o    Use Pass through or fixed VHD

o    Don’t use dynamic disk in a production farm

o    Network is tricky. Use multiple NICs and NIC teaming on the hosts

§  Isolate Shared Services Provider (SSP) under the following circumstances:

a)    10 million items indexed

b)    Multiple farms consuming shared services

c)    100K user profiles + people search + my sites + significant use of audience

o    Any combination of two or more from above are true

§  Index Server does not index all versions because you get search result of only latest content

Session: Best Practices for developing Custom Field Types (Presented by Todd Bleeker)

§  Custom Field Types do not work with datasheet view and MS Office application i.e. in Information panel

§  You must sign custom field type assembly and deploy to GAC

§  Naming Convention for custom field types:

o    Field: [Purpose]Field.cs

o    Control Class: [Purpose]FieldControl.cs

o    Value Class: [Purpose]FieldValue.cs

o    Field types_[Purpose].xml

§  Always use HTML Encode, when you render to prevent Script/SQL injection hacks

Notes from other sessions

§  Important tools to setup Kerberos Authentication

o    Kebtray.exe

o    Klist.exe

o    Network Monitor 3.2

o    ADSIEdit.msi

o    Filldler Tool

§  Use Ken Schaefer’s Blog for information regarding IIS and Kerberos

SharePoint Search crawl error on Windows Server 2008 Operating System
You get following error message, when you try to create a web application using host header name e.g. or http://portal/
See screen shot here
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
Resolution: Follow the KB article KB896861 to disbale loop back
Here are the steps to follow:
  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key:
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and then restart your computer.
1 - 20 Next
The posts on this weblog are provided "AS IS" with no warranties, and confer no rights.
The opinions expressed herein are personal and do not represent those of my employer.
View Syed Adnan Ahmed's profile on LinkedIn

 Mark Harrison's RSS Feed

Cannot retrieve the URL specified in the XML Link property. For more assistance, contact your site administrator.

 Joel's RSS Feed

Cannot retrieve the URL specified in the XML Link property. For more assistance, contact your site administrator.

 SharePoint Popular Blogs

Adnan's blog on Project Server
Bob Fox's Blog
Spencer Harber (MVP)
Andrew Connell (MVP)
Heather Solomon (MVP)
Dustin Miller
Scot Hiller (MVP)
Ishai Sagi (MVP)
Joel Oleson
Arphan Shah
Mike Watson
Natalya Voskresenskaya
Asif Rehmani
Adnan blog on

 My Articles

  Extending SharePoint Server 2007 by using Features
  Wrapper API for using Microsoft Active Directory Services
  How to configure SharePoint Portal Server 2003 to search contents of list attachments
  Useful SQL Queries to Analyze and Monitor SharePoint Portal Solutions Usage
  Dynamic HTML Page creation & Search through Free Text and Meta Tags of HTML by Using Index Server
  Encrypt Password Field in SQL Server, Registry Information & Query String

 ‭(Hidden)‬ Admin Links