# Friday, January 30, 2009

We have launched Turkey's first Sharepoint user group named Sharepoint Turkiye throught ISPA.

posted on Friday, January 30, 2009 9:26:23 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Me and Oktay Sert create a public Sharepoint User Group site named "Sharepoint Turkiye".

We plan that, SharepointTurkiye.Org is a local user group covers alla Sharepoint developers, administrators and information workers on local side on Turkey.

SharepointTurkiye.Org is a local adoption of Microsoft SharePoint Products and Technologies. The Association provides support and guidance to the community by establishing connections between SharePoint professionals, resources, education and information.

Site is now under construction, please wait for launch...

posted on Friday, January 30, 2009 9:15:44 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Thursday, January 29, 2009

Windows SharePoint Services is a versatile technology included in Microsoft Windows Server 2003 that enables organizations and businesses of all sizes to increase the efficiency of their processes and improve team productivity.

With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to the documents and information they need.This quick reference guide provides helpful tips and tricks for using Windows SharePoint Services while highlighting new features in Version 3.0.

You can download this document via this link : http://www.microsoft.com/downloads/details.aspx?familyid=80FD0D64-4BD0-476B-BFD9-39DA34C22EFB&displaylang=en

posted on Thursday, January 29, 2009 8:56:57 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Wednesday, January 28, 2009

Scott Guthrie writes excellent post about ASP.Net MVC 1.0 RC is now available! It is great news for many customers who has been asking for this. You can read this very very long post via this link, and you can read release notes about this RC via this link. If you want to download ASP.Net MVC 1.0 RC use this link.

Congratulations to the Microsoft ASP.NET team for their hard work on the MVC out-of-band releases...

posted on Wednesday, January 28, 2009 9:28:14 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Jan Tielens's SmartTools project new version has released. You can find it on project home site at CodePlex

 http://www.codeplex.com/smarttools

posted on Wednesday, January 28, 2009 9:27:39 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Windows SharePoint Services is a versatile technology included in Microsoft Windows Server 2003 that enables organizations and businesses of all sizes to increase the efficiency of their processes and improve team productivity.

With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to the documents and information they need.This quick reference guide provides helpful tips and tricks for using Windows SharePoint Services while highlighting new features in Version 3.0.

You can download this document via this link : http://www.microsoft.com/downloads/details.aspx?familyid=80FD0D64-4BD0-476B-BFD9-39DA34C22EFB&displaylang=en

posted on Wednesday, January 28, 2009 8:55:50 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

The workbooks that you want to access must be placed in a trusted location. If not, the calls to open the workbook will fail. You can add a URL to the trusted location list by using the SharePoint 3.0 Central Administration page. Alternatively, you can use script to create a batch file.

-----------------------------------------------
@ECHO off
REM
REM Script to add a URL or site to the trusted location list
REM Last Updated: 11/2/05
if "%1" == "/?" GOTO Help
if "%1" == "" GOTO Help
SET LocationType=SharePoint
for /f "usebackq skip=3" %%i in (`%windir%\system32\cscript /nologo %windir%\system32\iisvdir.vbs /query "Office Web Services"`) do set variable=%%i
set sspname=%variable:~1%
:Arguments
if "%2" == "Unc" SET LocationType=Unc
if "%2" == "UNC" SET LocationType=Unc
if "%2" == "unc" SET LocationType=Unc
if EXIST "%commonprogramfiles%\Microsoft Shared Debug\web server extensions\12\BIN\stsadm.exe" (
SET STSADM="%commonprogramfiles%\Microsoft Shared Debug\web server extensions\12\BIN\stsadm.exe")
if EXIST "%commonprogramfiles%\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" (
SET STSADM="%commonprogramfiles%\Microsoft Shared\web server extensions\12\BIN\stsadm.exe")
if NOT EXIST %STSADM% (
ECHO Error: STSADM.EXE cannot be found in your system.
GOTO Error
)
ECHO.ECHO Adding %1 to the Trusted Locations list ...
ECHO Type = %LocationType%
ECHO SSP Name = %sspname%
%STSADM% -o add-ecsfiletrustedlocation -ssp %sspname% -location %1 -includechildren true -locationtype
%LocationType% -allowexternaldata dclandembedded
-warnondatarefresh true -abortonrefreshonopenfail false
if NOT %ERRORLEVEL% == 0 (
ECHO Error: Error running stsAdm
GOTO Error
)
ECHO.
ECHO ********************************
ECHO %1 has been added
ECHO ********************************
ECHO.
PAUSE
GOTO End
:Error
ECHO.
ECHO ********************************
ECHO Failed!
ECHO ********************************
ECHO.
PAUSE
GOTO End
:Help
ECHO.
ECHO The command line syntax:
ECHO AddToTrusted
http:///customsite>
ECHO AddToTrusted
\\\foldername> unc
ECHO.
ECHO Examples:
ECHO C:\AddToTrusted
http:///customsite>
ECHO C:\AddToTrusted
\\\foldername> unc
PAUSE
GOTO End:
End

-----------------------------------------------

Save the file as AddToTrusted.bat and run it (Start>Run>cmd)

posted on Wednesday, January 28, 2009 8:54:55 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

The Business Data Catalog is a Microsoft Office SharePoint Server 2007 feature that exposes and incorporates Line-of-Business (LOB) data into other baseline portal functionality, such as lists and enterprise search. To incorporate this data into your portal, you must build an XML file that identifies where the data is stored (either Microsoft SQL Server or a Web service) and what the data looks like (for example, what the data types and primary keys are).

You found nice article in MSDN to learn how to create an application definition file.

Article is here : http://msdn2.microsoft.com/en-us/library/bb410048.aspx

posted on Wednesday, January 28, 2009 8:54:00 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Tuesday, January 27, 2009

If you want to add new content types to Microsoft Office Sharepoint Server 2007 you read Bob Mixon's nice article. He explains how to create new content types and manage them.

http://msd2d.com/Content/Tip_viewitem_03NoAuth.aspx?id=d5fd9392-25e3-4771-b563-b25fceb55c52&section=Sharepoint

posted on Tuesday, January 27, 2009 8:53:02 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Monday, January 26, 2009

Microsoft Sharepoint MVP Pierre Vivier writes custom webpart for Sharepoint that manages Events on Lists and Documents Libraries.

You can view, add and delete events, and even find automatically interesting classes and events from an assembly name. You can download it here and you can read more here

Thanks Pierre

posted on Monday, January 26, 2009 8:52:16 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Sunday, January 25, 2009

1. On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
2. On the Operations page, in Topology and Services, click Servers in farm.
3. On the Servers in Farm page, click the server on which you want to configure the search service.
4. Click Start next to Office SharePoint Server Search.
5. On the Office SharePoint Server Search Settings page, in the Query and Indexing section, make sure that the Use this server for indexing content and Use this server for serving search queries check boxes are selected.
6. In the Default Catalog Location section, type a path to a physical folder to store the index files, or use the default location that is specified.
7. In the Contact E-Mail Address section, specify a valid e-mail address.
8. In the Service Account section, click Configurable, and in User name and Password, type the user name and password for the user account under which you want the Search service to run. The user account must be a member of the Administrators group on the computer that is running the Search service. If you want to use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers, see the Known Issues/Readme for Office SharePoint Server 2007 Beta 2. The user name must be in the format DOMAIN\username.
9. In the Web Front End And Crawling section, do one of the following:
If you are configuring the search service on a server that provides Web services and renders Web content, click No dedicated Web front-end computer for crawling

If you are configuring the search service on a server that is a standalone search server that does not provide Web services and render Web content, click Use a dedicated web front end computer for crawling, and then, in Select a web front end computer, click the computer you want to use for crawling.

posted on Sunday, January 25, 2009 12:34:47 PM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

1. On the SharePoint Central Administration home page, click the Application Management tab on the navigation bar.
2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
3. On the Manage this Farm's Shared Services page, click SharedServices1.
4. On the Shared Services Administration page, in Search, click Search Settings.
5. On the Configure Search Settings page, in the Crawl Settings section, click Default content access account.
6. In the Default content access account section, in Account, Password, and Confirm Password, type the user name and password for the user account that you want to use to crawl content on your sites. This account must be a domain user account. It is recommended that you use the principle of least privilege and select a unique user account that cannot modify content and does not have administrative rights on your front-end servers or on your back-end database servers.
7. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user account that you specify will be added to the Web application Full Read policy for your farm. The user name must be in the format DOMAIN\username.
8. Click OK.
9. In the Crawl Settings section, click Content sources.
10. On the Manage Content Sources page, click Local Office SharePoint Server sites.
11. On the Edit Content Source page, in the Crawl Schedules section, under Full Crawl, click Create schedule.
12. In the Manage Schedules dialog box, configure schedule settings for full crawls of your content, and then click OK.
13. In the Crawl Schedules section, under Incremental Crawl, click Create schedule.
14. In the Manage Schedules dialog box, configure schedule settings for incremental crawls of your content, and then click OK.
15. In the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.

posted on Sunday, January 25, 2009 12:30:40 PM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Configure surface area settings in SQL Server 2005 
      - Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
      - In the SQL Server Surface Area Configuration dialog box, click Surface Area Configuration for Services and Connections.
      - In the tree, open your instance of SQL Server, open Database Engine, and then click Remote Connections.
      - Click Local and Remote Connections, click Using both TCP/IP and named pipes, and then click OK.

Security account requirements
To install Office SharePoint Server 2007 in a server farm environment, at-least 2 accounts are required:

      - A user account that you can use to install Office SharePoint Server 2007 and run the SharePoint Products and Technologies Configuration Wizard. This account must be:
            - A domain user account.
            - A member of the Administrators group on each of your front-end servers.
            - A member of the SQL Server Logins, which grants login access to your SQL Server instance.
            - A member of the SQL Server Database Creator server role, which grants permission to create and alter databases.
            - A member of the SQL Server Security Administrators server role, which grants permission to manage server logins.
      - A unique domain user account that you can specify as the Office SharePoint Server 2007 service account. This user account is used to access your SharePoint configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator server role, and the SQL Server Security Administrators server role. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.

posted on Sunday, January 25, 2009 12:24:23 PM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Before you install and configure Office SharePoint Server 2007, make sure your servers have the recommended hardware and software. To deploy a server farm, you need at least one server computer acting as a Web server and an application server, and one server computer acting as a database server. The server computers must meet the following requirements:

Hardware requirements

    Front-end Web server and application server computers: a dual-processor computer with processor clock speeds of 2.5-gigahertz (GHz) or higher and a minimum of 2 gigabytes (GB) of RAM. Back-end database server: a dual-processor computer with processor clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.

Software requirements Web and Application Server

    Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1) Microsoft .Net Framework 2.0 Microsoft .Net Framework 3.0 The Web server and application server computers must be configured as Web servers running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode. Each of the computers must be using the NTFS file system. Windows Server 2003 includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.

Back-End Database Server
The back-end database server computer must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. It is assumed that you have installed and configured the database program on the back-end server computer. You do not need to set up or create specific databases for Office SharePoint Server 2007. The Office SharePoint Server 2007 Setup program will create the necessary databases when you install and configure Office SharePoint Server 2007.

posted on Sunday, January 25, 2009 12:11:57 PM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

It's easy!!!
You can execute STSADM Utility with following parameters :

stsadm.exe -o backup -directory C:\BackupFolder -backupmethod full -url http://SiteURL -filename backup.dat -overwrite

posted on Sunday, January 25, 2009 8:51:34 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

The SharePoint team provided us with this blog post describing a feature to install in your SharePoint environment that allows you to attach the debugger to the SharePoint process with a click of a button. It becomes available in the site settings menu.

Read Details : http://blogs.msdn.com/sharepoint/archive/2007/04/10/debugger-feature-for-sharepoint.aspx

posted on Sunday, January 25, 2009 8:50:55 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

When you implement a Sharepoint Site project your page title includes "Home" string. But we can't find any way to remove "Home" string.
The first step to changing it is to understand where this string is stored. Easiest way to do that is to open the default.aspx page with Sharepoint Designer. We can see it contains a content block that replaces the master page's Title content placeholder.

Full article is here : http://weblogs.asp.net/avnerk/archive/2007/04/11/customizing-moss-page-title.aspx

posted on Sunday, January 25, 2009 8:50:09 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

If you get "Enable ASP.NET extensions" message while installing MOSS 2007, run the following command:

aspnet_regiis -iru

You will find this utility in the following folders:

C:\Windows\Microsoft.NET\Framework\v1.1.4322
C:\Windows\Microsoft.NET\Framework\v2.0.50727

posted on Sunday, January 25, 2009 8:36:04 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

When you publish a Microsoft Office InfoPath 2007 template to a computer that is running Microsoft Office Form Server 2007 and Active Directory Federation Services (AD FS), you receive the following error message:


"The following URL is not valid: http://servername"

To fix this problem :

Method 1

Use the Central Administration page in Microsoft Windows SharePoint Services to upload and to start the InfoPath Form Template (.xsn) file. To do this, follow these steps: 

1. Locate the Central Administration page in Windows SharePoint Services.
2. Click the Application Management tab. 3. In the InfoPath Form Services section, click Manage form templates. 4. Click Upload form template. 5. Click Browse, select the form template to be uploaded, and then click Open. 6. Click Upload, and then click OK. 7. On the Manage Form Templates page, select the form that was uploaded, and then click Activate to a Site Collection. 8. Make sure that Activation Location is set to the correct site, and then click OK. 9. Add the activated form to a document library where multiple content types has been enabled.

Method 2

Use the Central Administration page to turn off AD FS. To do this, follow these steps: 

1. Locate the Windows SharePoint Services site where you want to publish the form.
2. Click Site Actions, and then click Site Settings. 3. In the Site Collection Administration column, click Site collection features, and then click Deactivate to turn off AD FS.
posted on Sunday, January 25, 2009 8:35:16 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

1.  5046: Inside Look at Building and Developing Solutions with Microsoft® Office SharePoint® Server 2007

Summary: This is the eLearning version of the product.
Audience: developers
Delivery Method: Self-paced e-Learning (online)

2. 
5060: Implementing Microsoft® Windows® SharePoint® Services 3.0
Summary: This learning product will teach IT Professionals how to implement Windows SharePoint Services 3.0 in their organizations. It will provide them with the knowledge and skills necessary to ensure a successful implementation.
Audience: IT professionals
Delivery Method: Instructor-led (classroom)

3. 
5061: Implementing Microsoft® Office SharePoint® Server 2007
Summary: This learning product will teach IT Professionals how to implement Microsoft Office SharePoint Server 2007 in their organizations. It will provide them with the knowledge and skills necessary to ensure a successful implementation.
Audience: IT professionals
Delivery Method: Instructor-led (classroom)

4. 
3199: First Look: Getting Started with the 2007 Microsoft® Office System
Summary: At the end of this half-day clinic, students will understand how the 2007 Microsoft Office System provides many benefits to an organization including enhanced collaboration, personal productivity and an effective enterprise content management solution.
Audience: IT professionals
Delivery Method: Instructor-led (classroom)

5. 
3369: First Look: Getting Started with Windows® SharePoint® Services 3.0
Summary: At the end of this half-day clinic, the students will have a basic understanding of the features and technologies new to Microsoft Windows SharePoint Services 3.0.
Audience: IT professionals
Delivery Method: Instructor-led (classroom)

6. 
3372: HOL: Getting Started with the 2007 Microsoft® Office System
Summary: At the end of this half-day hands-on lab, students will understand the benefits of the 2007 Microsoft Office system and be able to describe the new features related to the client and server components of the 2007 Microsoft Office system.
Audience: IT professionals
Delivery Method: Instructor-led (classroom)

7. 
3373: HOL: Getting Started with Windows® SharePoint® Services 3.0
Summary: At the end of this half-day hands-on lab, the students will have a high-level understanding of the features and technologies new to Microsoft Windows SharePoint Services 3.0.
Audience: IT professionals
Delivery Method: Instructor-led (classroom)

8. 
3374: HOL: Getting Started with Microsoft® Office SharePoint® Server 2007
Summary: At the end of this one-day hands-on lab, the students will have a high-level understanding of the features and technologies new to Microsoft Office SharePoint Server 2007..
Audience: IT professionals
Delivery Method: Instructor-led (classroom)
posted on Sunday, January 25, 2009 8:34:38 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Clinic 3369: Getting Started with Microsoft® Windows® SharePoint® Services 3.0 (Beta) 

Summary: In this clinic, you explore the features and technologies new to Microsoft® Windows® SharePoint® Services (WSS) 3.0.
You are also provided with information about deployment, configuration and migration to WSS 3.0.
Audience: IT Pro
Available Offline: Yes
Price: Free, 90-day subscription

Clinic 3370: Getting Started with Microsoft® Office SharePoint® Server 2007 (Beta) 
Summary: In this clinic, you explore the 2007 Microsoft® Office System to understand how it provides many benefits to an organization including enhanced collaboration, personal productivity and an effective enterprise content management solution.
You are also provided with an overview of the server and client components that make up the 2007 Office System.
Audience: IT Pro
Available Offline: Yes
Price: Free, 90-day subscription

Clinic 5045: Inside Look at Developing with Microsoft® Windows® SharePoint® Services 3.0 
Summary: In this 2-hour premium clinic you will learn about the rich capabilities that Windows SharePoint Services 3.0 offers to developers. The clinic will focus on Architecture and List Management, Building and Extending Windows SharePoint Sites, and Packaging and Deploying Windows SharePoint services solutions.
Audience: Developer
Available Offline: Yes
Price: Free, 1-year subscription

Clinic 5046: Inside Look at Building and Developing Solutions with Microsoft® Office SharePoint® Server 2007 
Summary: In this 2-hour premium clinic you will learn about the rich capabilities that Office SharePoint Server 2007 offers to developers. The clinic will focus on Fundamentals of Building Solutions with Office SharePoint Server 2007, Building Business Solutions with Office SharePoint Server 2007 and how to Incorporate Office SharePoint Services into Business solutions.
Audience: Developer
Available Offline: Yes
Price: Free, 1-year subscription
posted on Sunday, January 25, 2009 8:33:40 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.

1. In the SharePoint Web Application Management section, click Create or extend Web application. 

2. On the Create or Extend Web Application page, click Create a new Web Application.

3. On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site, and change the port setting to port 80. This will allow you to access your site by typing http://ServerName. If you use a nonstandard port number you will have to include the port number in the URL to access your site (for example, http://servername:port/).

4. In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify any other settings in this section.

Note: By default, the authentication provider is set to NTLM.

6. In the Load Balanced URL section, do not modify the default settings.

7. In the Application Pool section, select Create new application pool, and use the default settings for the application pool name.

8. Click Configurable, and in User name and Password, type the user name and password for the user account under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.

9. In the Database Name and Authentication section, verify the database information and ensure Windows Authentication (recommended)is selected.

10. In the Search Server section, do not modify the default settings.

11. Click OK.

12. On the Application Created page, which appears after successful creation of the Web application, click Create a new Windows SharePoint Services site collection. 

Create the site collection for your Web application 
1. On the Create Site Collection page, in the Title and Description section, in Title, enter a title for the new site.

2. In Description, enter a description of the site collection.

3. In the Web Site Address section, click Create site at this URL, and in URL path click (root).
It is most common to create a site collection at the root; however, you can create a site collection at a specific URL path.

4. In the Primary Site Collection Administrator section, in User name, type the user name of the site collection administrator. This can be the same user account that you specified as the Office SharePoint Server 2007 service account, but you should follow the principle of least privilege and use a user account that does not have administrative privileges or rights on your front-end or back-end servers.

5. In the Quota Template section, select a predefined quota template to limit resources used for this site collection.

Note: You can also select No Quota, thereby allowing this site collection to use any available resources.

6. In the Template Selection section, click the Publishing tab, and then click Corporate Intranet Site.

7. Click OK to create the site collection with the attributes you specified. Upon successful completion, a Top-Level Site Successfully Created page appears.

8. Click OK to return to the SharePoint Central Administration home page, or click the http://ComputerName link to go to your new SharePoint site home page.
posted on Sunday, January 25, 2009 8:23:07 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

If you installed and configured Office SharePoint Server 2007 on a single front-end server, and a user browses to your server, the server will render the content that is in your Web application. However, if you added subsequent front-end servers to your server farm, the newly-added servers will not have alternate access mappings configured to your Web application. To map newly-added front-end servers to your existing Web application, you need to configure alternate access mappings.

Before you configure alternate access mappings, install and configure Office SharePoint Server 2007 on all of the front-end servers that you want to add to your server farm, and make sure that the servers are joined to your server farm. See "Run Windows SharePoint Services Setup" and "Run the SharePoint Products and Technologies Configuration Wizard" for information about installing and configuring Office SharePoint Server 2007.
To configure alternate access mappings 


1. On the SharePoint Central Administration home page, click the Operations tab.

2. On the Operations page, in the Global Configuration section, click Alternate access mappings.

3. In Alternate Access Mapping Collection, click Change Alternate Access Mapping Collection.

4. In the Select an Alternate Access Mapping Collection dialog box, click the Web application that you want to modify. If you have created only one Web application, and you specified port 80 for the Web application, the Web application should be listed as SharePoint (80).

5. Click Edit Outbound URLs, and verify that your Web application is listed in the Default zone for outbound URLs. The outbound URL is the URL that you want users to use to access your Web application.

Note: If you have a load-balanced configuration with a host name, add the host name to the Outbound URL for the Default zone.

6. Click Save.

7. Click Add Incoming URLs.

8. On the Add Incoming URLs page, in New default zone URL protocol, host and port type the URL for the server that you want to map to your Web application. Typically, this is http://servername:portnumber/.

Note: If you have a load-balanced configuration, you should add the server name of each of your front-end Web servers to the list of internal URLs. This will allow each of your Web servers to reach the content in your common Web application. Also, make sure the zone you selected for the incoming URL matches the zone of the outbound URL for the load balancer. You can have multiple incoming URLs associated with a single outbound URL.

9. In Zone, make sure that Default is selected.
10. Click Save.
posted on Sunday, January 25, 2009 8:21:49 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

1. On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.
2. On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
3. On the Manage this Farm's Shared Services page, click New SSP.

Important: If you have not created a Web application for the SSP administration site, you need to create one before you create the SSP. If you have already created a Web application for the SSP administration site, skip to step 14.

4. On the New Shared Services Provider page, click Create a new Web application.
5. On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site, and do not modify the default settings in this section.
6. In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify the default settings in the remainder of this section.
7. In the Load Balanced URL section, do not modify the default settings.
8. In the Application Pool section, click Create new application pool.
9. In Application pool name, enter the name of your application pool or use the default name.
10. Click Configurable, and in User name and Password, type the user name and password for the user account under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.

11. In the Database Name and Authentication section, verify the database information and make sure that Windows Authentication (recommended)is selected.
12. In the Search Server section, do not modify the default settings.
13. Click OK. Upon successful creation of the Web application, the New Shared Services Provider page appears.
14. In the SSP Name section, in Web Application, select the Web application that you created for the SSP, and do not modify any of the default settings in this section.
15. In the My Site Location section, do not modify any of the default settings.
16. In the SSP Service Credentials section, in User name and Password, type the user name and password for the user account under which you want the SSP to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
17. In the SSP Database section, you can either accept the default settings (recommended), or specify your own settings for the database server, the database name, or the SQL authentication credentials.
18. In the Search Database section, you can either accept the default settings (recommended), or specify your own settings for the search database server, the database name, or the SQL Server authentication credentials.
19. In the Index Server section, in Index Server, click the server on which you configured the Search service.

Note: If there is no index server listed in the Index Server section, then no server in your farm has been assigned the index server role. To assign the index server role to a server in your farm, follow the instructions in the "Configure the Search service" section earlier in this topic.

20. In the SSL for Web Services section, click No.
21. Click OK. Upon successful creation of the SSP, the Success page appears.
22. On the Success page, click OK to return to the Manage this Farm's Core Services page

posted on Sunday, January 25, 2009 8:21:00 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback