Skip Ribbon Commands
Skip to main content
Home
April 11
SharePoint 2010 Search Crawl common errors
by  Adnan AhmedNo presence information  on 11/04/2012 06:39
Category: Search; SharePoint 2010

SharePoint search crawl error: "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. ( Error from SharePoint site: HttpStatusCode Unauthorized The request failed with HTTP status 401: Unauthorized. )"

   

There are following three very common reason of why you get above error, when trying to crawl a SharePoint 2010 based web application:

  1. Make sure that SharePoint Default Content Account has "Full Read" permission on the web application.
    1. In order to check default content access account, browse to Central Admin site then browse to search administration page. You should find the default content access account in the middle of the page similar to the screen shot below:

    1. Now browse to Manage Web Application, then select web application and click User Policy Ribbon button. A pop up window will appear. Please check whether the default content access account exists or not. If not, then add it and assign FULL READ permission.
  2. Second most common reason is loop back adapter issue. Follow the instructions below to check, if you are facing loop back adapter issue:
    1. Remote into the server, where Search service is configured. Now browse to the web application by using the Search Content Access account. If you get HTTP 404 error then it means this is a loop back adapter issue. Follow one of my old posts to fix this issue.
  3.  Make sure that all CSS styles, page layout pages and Master pages in the Master Page Gallery (http://[Your Portal]/_catalogs/masterpage/Forms/AllItems.aspx) are PUBLISHED.

Please leave your comments, if above resolution works for you.

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
April 05
How to access Active Directory Users from a domain group in SharePoint
by  Adnan AhmedNo presence information  on 05/04/2012 02:45

Sometimes you need to apply permission based on users, SP groups and domain groups specified in a People or Group field in SharePoint. You can use SharePoint API to easily find out, list of users in any given SharePoint Group but if SP groups contains domain group then you need to get help from System.DirectoryServices.AccountManagement.dll.

Add a reference to System.DirectoryServices.AccountManagement.dll assembly in your project and execute the following piece of code to get a Hash table of users exist in any domain groups within an Active Directory.

public static Hashtable GetUsersFromActiveDirectoryDomainGroup(Hashtable uniqueUsers, string domainGroupName)

{

 

try

{

string domainName = "mydomain"; // specify AD Domain name here

 

// Code below should also work as a normal AD user but sometime, I noticed that permission of a normal user is not enough to iterate through each user so it is safe to execute the code below by using elevated privileges i.e. app pool account of the web application

SPSecurity.RunWithElevatedPrivileges(delegate()

{

using (PrincipalContext principalContext = new PrincipalContext(ContextType.Domain, domainName))

{

using (GroupPrincipal groupContext = GroupPrincipal.FindByIdentity(principalContext, IdentityType.SamAccountName, domainGroupName))

{

if (groupContext!= null)

{

foreach (Principal principal in groupContext.GetMembers(true))

{

if (!uniqueUsers.ContainsKey(string.Format(@"{0}\{1}", domainName, principal.SamAccountName.ToLower())))

uniqueUsers.Add(string.Format(@"{0}\{1}", domainName, principal.SamAccountName.ToLower()), string.Format(@"{0}\{1}", domainName, principal.SamAccountName.ToLower()));

 

}

 

}

}

}

 

});

}

catch (Exception ex)

{ }

return uniqueUsers;

 

}

 

Reference: http://blogs.technet.com/b/brad_rutkowski/archive/2008/04/15/c-getting-members-of-a-group-the-easy-way-with-net-3-5-discussion-groups-nested-recursive-security-groups-etc.aspx

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
August 10
How to install and configure Remote Blob Storage for SharePoint Server 2010
by  Adnan AhmedNo presence information  on 10/08/2011 12:36
This article describes how to install and configure Remote Blob Storage (RBS) for SharePoint Server 2010 based on the Microsoft TechNet article. I have configured RBS for SharePoint Server 2010 on my VMware with the following configuration:

 

  • Windows Server 2008 R2 Standard Edition
  • SQL Server 2008 R2 Standard Edition
  • SharePoint Server 2010 Standard

The steps in this article to configure RBS are still valid for an environment, which contains more than WFEs or SQL Server. Any additional required for multiple WFEs are also explained.

Steps required to configure RBS for SharePoint Server 2010

Pre-requisite:

The user account to configure RBS must be local admin on all SP 2010 WFEs and dbcreator and securityadmin SQL Server roles on the database server.

  1. Enable FILESTREAM on the database server

FILESTREAM is installed by default as part of the SQL Server installation but it is not normally enabled, although FILESTREAM can be enabled during the SQL Server installation. Follows steps below to enable FILESTREAM for SQL Server.

Note: Steps below are provided in the Microsoft TechNet, but I have included screen shots wherever an explanation is deemed necessary.

  1. Log into the database server with an account with dbcreator and securityadmin permission on the database server.
  2. On the Start menu, point to All Programs, point to Microsoft SQL Server 2008 R2, point to Configuration Tools, and then click SQL Server Configuration Manager.
  3. In the list of services, right-click SQL Server Services, and then click Open.
  4. In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
  5. Right-click the database server instance and then click Properties.
  6. In the SQL Server Properties dialog box, click the FILESTREAM tab.
  7. Select the Enable FILESTREAM for Transact-SQL access check box.
  8. If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
  9. If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.

  1. Click Apply to apply changes.
  2. Now open the SQL Server Management Studio, click New Query to display the Query Editor.
  3. In Query Editor, enter the following Transact-SQL code:

EXEC sp_configure filestream_access_level, 2

RECONFIGURE

  1. Click Execute. See screen shot below.

  1. Provision a BLOB store for each content database

BLOB storage needs to be configured on each content database, which will use RBS functionality.

Notes:

  • It is recommended to choose disk volume for BLOB store that does not contain the operating system, paging files, database data, log files, or the tempdb file.
  • Only local physical volume can be used in case of SQL Server Standard Edition. You will be required to install Enterprise edition, if you want to use Network path for BLOB storage.

Follow steps below to provision BLOB storage.

  1. Log into the database server.
  2. Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.
  3. Connect to the instance of SQL Server that hosts the content database.
  4. Expand Databases.
  5. Click the content database for which you want to create a BLOB store, and then click New Query.
  6. Create a BLOB storage folder for each content database e.g. E:\SQLServerBlobStorage\. Please don't create the folder, where BLOB files will be created as this will be created by the SQL query.
  7. Now execute the following query:

use [WSS_Content]

if not exists

(select * from sys.symmetric_keys

where name = N'##MS_DatabaseMasterKey##')

create master key encryption by password = N'Admin Key Password !2#4'

Note: Replace the following before executing the above query:

  • Replace [WSS_Content] with the content database name
  • Replace [N'Admin Key Password !2#4'] with your defined master encryption key
  1. Once the above query is executed, you should the following message.

  2. Now execute the following query.

use [WSS_Content]

if not exists

(select groupname from sysfilegroups

where groupname=N'RBSFilestreamProvider')

alter database [WSS_Content]

add filegroup RBSFilestreamProvider contains filestream

 

Note: Replace[WSS_Content] with the content database name

  1. Once the above query is executed, you should the following message.

  1. Now execute the following query.

use [WSS_Content]

alter database [WSS_Content]

add file (name = RBSFilestreamFile, filename =

'c:\Blobstore')

to filegroup RBSFilestreamProvider

 

Notes:

  • Replace [WSS_Content] with the content database name
  • Replace c:\Blobstore with the local path of BLOB store e.g. E:\SQLServerBlobStore\
  1. Once the above query is executed, you should the following message.

Trouble Shooting

Following errors may occur during the execution of the above queries. This section provides errors generated and how to fix them.

Error #1: If Windows Firewall on the database server is blocking remote debugging. Then you may get the following error.

Resolution: Choose Unblock remote debugging from any computer or disable firewall on the database server. See screen shot below.

Error #2: Following error will occur during the last query, if you specify create the folder specified in the SQL query.

Resolution: You should not create the BLOB folder specified in the query. SQL query will create the BLOB folder for you.

  1. Install the RBS client library on each Web server

Download the RBS client library RBS_x64.exe file from http://go.microsoft.com/fwlink/?LinkID=165839&clcid=0x409.

Note: Do not try to install RBS_x64.exe directly as the installation wizard sets certain default values that are not recommended for SharePoint Server 2010. The RBS client library must be installed on each WFE and App servers in the SharePoint Server 2010 farm.

Follow steps below to install RBS client utility:

  1. Log into the web server and open command prompt (Run as Administrator).
  2. Browse to the folder, where you have copied the RBS_x64.exe file and execute the following command:

msiexec /qn /lvx* rbs_install_log.txt /i RBS-x64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content" DBINSTANCE="DBInstanceName" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1

Note: Replace the following depending upon your scenario:

  • Replace rbs_install_log.txt with the name of the log file, if this file already exists or for any other reason.
  • Replace RBS_x64.exe to the RBS client utility name that you have downloaded, if different.
  • Replace WSS_Conntent with the content database name.
  • Replace DBInstanceName with the SQL Server instance name.

 

Note: Don't include RBS client utility name at the start of the above command.

  1. To install the RBS client library on all additional Web and application servers

Note: NO need to follow this step, if SP 2010 is configured on only ONE server.

Download the RBS client library RBS_x64.exe file from http://go.microsoft.com/fwlink/?LinkID=165839&clcid=0x409.

Follow steps below to install RBS client utility:

  1. Log into the web server and open command prompt (Run as Administrator).
  2. Browse to the folder, where you have copied the RBS_x64.exe file and execute the following command:

msiexec /qn /lvx* rbs_install_log.txt /i RBS_x64.msi DBNAME="WSS_Content" DBINSTANCE="DBInstanceName" ADDLOCAL=Client,Docs,Maintainer,ServerScript,FilestreamClient,FilestreamServer

Note: Replace the following depending upon your scenario:

  • Replace rbs_install_log.txt with the name of the log file, if this file already exists or for any other reason.
  • Replace RBS_x64.exe to the RBS client utility name that you have downloaded, if different.
  • Replace WSS_Conntent with the content database name.
  • Replace DBInstanceName with the SQL Server instance name.
  1. Repeat this procedure for all remaining Web servers and application servers in the SharePoint farm.

    1. To confirm the RBS client library installation

  2. The rbs_install_log.txt log file is created in the same location as the RBS_x64.msi file. Open the rbs_install_log.txt log file by using a text editor and scroll toward the bottom of the file. Within the last 20 lines of the end of the file, an entry should read as follows: Product: SQL Remote Blob Storage – Installation completed successfully.

Note: This log file can be over 1.3MB size and over 15699 lines.

  1. On the computer that is running SQL Server 2008, verify that the RBS tables were created in the content database. Several tables should be listed under the content database that has names that are preceded by the letters "mssqlrbs". Execute the following SQL command.

use WKRPWEB_Content

select * from dbo.sysobjects

where name like 'rbs%'

 

Result should be similar to the following:

  1. Enable RBS for each content database

 

Now enable the RBS on the web server by executing the following power shell command.

Note: You must perform this procedure once for each content database.

To enable RBS by using Windows PowerShell

  • On the Start menu, click All Programs.
  • Click Microsoft SharePoint 2010 Products.
  • Click SharePoint 2010 Management Shell.
  • At the Windows PowerShell command prompt, type the following command:

$cdb = Get-SPContentDatabase <ContentDatabaseName>

$rbss = $cdb.RemoteBlobStorageSettings

$rbss.Installed()

$rbss.Enable()

$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])

$rbss

Where:

  • <ContentDatabaseName> is the name of the content database.

 

  1. Test the configuration of RBS on the SharePoint 2010 farm:

    1. Browse to the RBS data store directory on the database server and determine the current size of the folder.
    2. Now browse to the SharePoint web site, which is configured to use RBS.
    3. Navigate to any document library and upload files over 100KB.
    4. Now check the BLOB store folder size to see, if new files are copied.

  2. How to change the default file size for RBS storage

 

Execute the following Power Shell command on the Web/App server to change the minimum Blob Storage file size. Recommended value is 1MB or greater.

$db = Get-SPContentDatabase [ContentDBName]
$db.RemoteBlobStorageSettings.MinimumBlobStorageSize=[FileSizeInBytes]
$db.Update()

Note: Replace the following in the above Power Shell command:

  • Replace [ContentDBName] with the content database name
  • Replace [FileSizeInBytes] with the file size in bytes

 

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
July 05
How to install and configure SharePoint Server 2010 SP1 on the existing SP 2010 Farm
by  Adnan AhmedNo presence information  on 05/07/2011 12:39

This article assumes that SharePoint Server 2010 is already installed and configured. You can download the SharePoint Foundation 2010 and SharePoint Server 2010 SP1 from the following locations:

Upgrading the existing SharePoint Server 2010 farm to SharePoint Server 2010 SP1 consist of the following three steps:

 

Install SharePoint Foundation 2010 SP1

 

Follow the steps below to install SharePoint Foundation 2010 SP1:

  1. Log into the SharePoint application server by using the SharePoint Setup account and execute the sharepointfoundation2010sp1-kb2460058-x64-fullfile-en-us.exe file.
  2. SharePoint Foundation 2010 SP1 installation wizard will start.
  3. Tick Click here to accept the Microsoft Software License Terms and Click Continue.

     

  4. SharePoint Foundation 2010 SP1 installation is in progress…

     

     

  5. Once the installation of SharePoint Foundation 2010 SP1 is installed. The installer will request you to reboot the server. You should ignore this message and click NO.

     

     

  6. Now log into the remaining SharePoint Web/App servers in the farm and follow the above steps.

     

     

Follow the steps below to install SharePoint Server 2010 SP1:

 

  1. Log into the SharePoint application server by using the SharePoint Setup account and execute the officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe file.
  2. SharePoint Server 2010 SP1 installation wizard will start.

     

     

  3. Tick Click here to accept the Microsoft Software License Terms and Click Continue.
  4. SharePoint Server 2010 SP1 installation is in progress…

     

     

  5. If SharePoint Server 2010 SP1 installation is failed for any reason as shown in the figure below then you need to re-execute the officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe file.

     

     

  6. SharePoint Server 2010 SP1 installation is in progress…

     

  7. SharePoint Server 2010 SP1 installation is in progress…

     

     

  8. Now log into the remaining SharePoint Web/App servers in the farm and follow the above steps.

     

     

Follow the steps below to run the SharePoint configuration wizard:

 

  1. Log into the SharePoint application server by using the SharePoint Setup account and run the SharePoint configuration wizard.
  2. Click Next to proceed…

     

     

  3. You will be informed that IIS, SharePoint Timer and Administration services will reset during the configuration wizard. Click Yes and then Click Next to proceed…

     

     

  4. On the next screen, click Next to proceed…

     

     

  5. SharePoint configuration wizard will start upgrading the farm. Please be patient as it may take 15-20 minutes depending upon the connected content databases on the farm.

     

     

  6. Unfortunately the configuration wizard was failed in my case as shown in the figure below.

     

     

  7. Click Finish to complete the wizard and analyse the log file.
  8. In my case, configuration wizard was failed due to the following errors.

     

     

  9. Re-run the SharePoint configuration wizard. SharePoint configuration wizard is successful.

     

     

  10. Now verify that SharePoint 2010 farm is upgraded to SP1 level by checking the version number of Microsoft.Office.Server.dll, Microsoft.SharePoint.dll files and on the central administration web site. See screen shot below for details:

     

     

     

     

    I do hope that this article will help you to upgrade your existing SharePoint Server 2010 farm. Please share your experience in upgrading SharePoint Server 2010 farm to SP1 level.

     

 

 

Permanent Link to Post | Email Post Link | Number of Comments 2 Comment(s)
May 29
Steps required to Install and Configure MS Dynamics CRM 2011 -- Part 1
by  Adnan AhmedNo presence information  on 29/05/2011 05:09

I have been looking for working on MS Dynamics CRM quite some time apart from SharePoint and Project Server as my main specialties for last 7-8 years. MS Dynamics CRM 2011 is now becoming an integral part of the MS SharePoint and its associated servers like MS Project Server. Couple of weeks back, I was involved on a project that integrate MS SharePoint Server 2010 with MS CRM 2011 i.e. MS SharePoint Server 2010 was involved in the overall architecture to provide MS CRM search. My role in the project as a SharePoint Consultant to install and configure SharePoint Server 2010 and its associated services such as Business Data Connectivity Services to connect to CRM database to provide enterprise capability for MS CRM.

After the successful deployment of MS SharePoint 2010, I have decided to evaluate the MS CRM 2011 myself to see, how can combine both technologies to get the best of both. This article is a part of series of articles that I will write in the coming weeks to explore the steps required to install and configure MS CRM 2011.

I would urge you to study the Microsoft Dynamics CRM Implementation Guide as this document form the basis of my MS CRM installation on my VMware environment. The purpose of this article and series of other article that I will write in the coming weeks to provide you step by step guide with screen shots of every steps, which I used to install and configure MS CRM 2011. I do hope that this will help you in deploying MS CRM 2011 in a single machine or on the farm environment.

Pre-requisites:

  • SQL Server 2008/ SQL Server 2008 R2 with SSRS are already installed and configured on the database server running Windows Server 2008/Windows Server 2008 R2 x64 bit machine.
  • Create an Organizational unit in the active directory for MS Dynamics CRM groups.

  • Create the following four service and one installer domain account in the Active Directory before installing the MS CRM 2011 on a multi-server farm environment. For non-production or single server environment, you can simply choose to use the same service account for all four CRM services.

You can find more information on TechNet web site.

  1. Log into the MS CRM 2011 server by using the CRM installer account and execute the SetupServer.exe which can be found inside the server\amd64 folder.
  2. Choose "Install Microsoft Dynamics CRM Server" option.

  3. Choose "Get updates for Microsoft Dynamics CRMS (recommended). Click Next.

  4. Installer will check for update. Click Next.

  5. Now MS Dynamics CRM setup program copy files to the temporary folder.

  6. Now enter product key.

  7. Accept the service agreement and click "I Accept" button to proceed to next step.

  8. The installer will detect the necessary components that needs to be installed before installing the MS Dynamics CRM 2011. Click Install.

  9. Now MS Dynamics CRM installer each pre-requisite component listed in the figure below.

  10. Now all the pre-requisite components are installed. Click Next to proceed.

  11. Specify the location, where you want to install MS Dynamics CRM.

  12. In my scenario, I was deploying MS Dynamics CRM 2011 on a single VMware machine but for the server farm environment, you can install Front End and Back End Server components on two separate machines.

  13. Choose "Create new deployment" and specify the database server name. If this server is becoming a part of the existing CRM farm, then you should select "Connect to, and if necessary, upgrade an existing deployment".

  14. Click Browse button to locate the OU that you have created before.  

  15. Click Next to proceed to next step.

  16.  Now specify the service accounts for each MS CRM services. The detail of each account are provided in the pre-requisites section above.  

  17.  Now either select the pre-created web site in IIS or allow the installer to create a new MS CRM web site for you. Specify the PORT number. Default value is 5555.

     

  18. On the Specify E-mail Router Settings page, enter the name of the computer where the E-mail Router will be installed. This computer routes Dynamics CRM e-mail messages. You can leave this box blank. However, if you install the E-mail Router later you must add the computer where the E-mail Router is installed. Click Next to proceed.  

         

  19. On the Specify the Organization Settings page, Click Browse button to select ISO currency code. I have selected Ireland as I am based in Dublin, Ireland.

    a)    In the Display Name box, type the organisation name e.g. LItwareinc_CRM

    b)    In the Unique Database Name box, you can keep the name that is automatically generated or you can type a unique name that must be limited to 30 characters. Spaces and extended characters are not allowed.

    c)    For this installation the organisation name is litwareinc

    d)    In the SQL collation list, keep the default selection or select a different database collation that the organisation database will use to sort and compare data characters. The default SQL collation changes based on the base language selection.

  20. On the "Specify Reporting Services Server", specify the Report Server URL. Click Next to proceed.

  21. On the "Help Us Improve the Customer Experience" page, click Next to proceed.

  22. On the "Select Microsoft Update Preference" page, click Next.

  23. On the "System Checks" page, Click Next to proceed.

  24. On the next screen, The setup will inform you that some of the IIS related services will be restarted during the install. Click Next to proceed.

  25. On the "Ready to Install Microsoft Dynamics CRM" screen, click Install.

  26. Setup will start installing the MS Dynamics CRM Server. This will take 10-15 minutes.

  27. Microsoft Dynamics CRM Server setup is completed. Untick Launch Reporting Extensions for SSRS Setup option and click Finish to close the setup screen.

    In the Part --2 of this series, I will provide detail on how to install Reporting Extensions for SSRS Setup. Please leave your comments.

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
October 06
How to prevent users from modifying web part zone
by  Adnan AhmedNo presence information  on 06/10/2010 12:44

Issue: How to prevent users (especially contributors) in modifying web parts in a web part zone

Resolution:

I faced a problem, when specifying a Data Form View Web Part in the Page Layout Page by using the SharePoint Designer 2007 that user especially contributors can modify web part properties and even close/delete web part from the page. I wanted to allow users (contributors) to update updateable field of the page in Edit Mode, but can only view my web part. Technically, there is no way you can prevent users by modifying/removing web part properties from the browser. I found a very simple way to fix this issue by modifying the properties of the web part zone from the SharePoint Designer 2007.

Follow the steps below to modifying web part zone properties.

  • Open Page Layout Page or web part in the SharePoint Designer 2007
  • Select Web Part Zone and right click à Web Part Zone Properties.
  • A screen below will pop up.

 

  • The default browser settings of the web part zone are as follows:
    • Allow users to add, remove, resize, and move Web Parts (Checked)
    • Allow users to change personal Web Part settings (Not Checked)
    • Allow users to change Web Part settings for all users (Checked)
  • Un-checked all Browser settings for Web Parts contained in the zone as shown in the figure below.

Web Part Zone Modified Permissions

  • Now Save and publish page layout page. Modify web part zone option will not be available for all users and web parts within the modified zone will only be modified from the SharePoint Designer 2007.
Share
Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
September 19
How to install and Configure SharePoint Server 2010 RTM
by  Adnan AhmedNo presence information  on 19/09/2010 08:25

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.

Notes:

  • 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.

Share
Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
September 19
Free SharePoint Server 2010 Exam Preparation by Microsoft E-Learning
by  Adnan AhmedNo presence information  on 19/09/2010 08:15

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)
​

 

Share
Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
September 19
How to configure SSL certificate for the central administration web site of SharePoint Server 2010
by  Adnan AhmedNo presence information  on 19/09/2010 07:42

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.

    6.  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.    

        

  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.    

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

     

    12.    

    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.    

  15. Now open SharePoint Central Administration Website.

    16.    

     

  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.

    Share
    Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
    September 18
    How to configure PDF iFilter for SharePoint Server 2010 or Search Server 2010
    by  Adnan AhmedNo presence information  on 18/09/2010 16:22
    Category: SharePoint 2010; Search

    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: http://www.mossgurus.com/adnan/Lists/Posts/Post.aspx?ID=9. 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 http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
    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.   

      {E8978DA6-047F-4E3D-9C78-CDBE46041603}

         

    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.

    Share
    Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
    Alert Me Alert Me
     

     About this blog

    		 
    About this blog

    The posts on this blog 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.