Different type of SharePoint Server 2007 server farm topologies.

Introduction
This article discuss about understanding the different type of SharePoint server farm topologies.
Overview
The SharePoint Server 2007 server farm design vary based on the customer requirements, security perspective and size requirement. The topology designs can be created based on the size of the server farm namely small, medium, and large which can focus on either a single or multiple farm models.
Different type SharePoint Server Roles
Web Front End Server : A front-end server that provides the web services used to render applications (Presentation layer).
Application Server : A front-end server that provides applications services such as search and index (Services layer)
SQL Database Server : A dedicated server running either Microsoft SQL Server 2005. In large farms, this is typically a SQL Server clustered configuration with two or more servers.
Domain controller : Provide authorization and authentication service to Office SharePoint users.
Small server farm :
Small server farm which consist of two-server, one of the servers hosts the Web front end and the application services, while the second server hosts the SQL Server database. This provides a way to manage the database separately but adds complexity without adding scalability or availability.
This type of smallest deployment that is recommended for demonstration, training environment or very small organization or user group.
If you notice that architecture diagram has domain controller, either demonstration environment or very small group, I am sure that there will be existing domain controller server, you may consider re-use.

Small Farm System Architecture
Medium server farm :
Part of this article is to help you determine the minimum requirements which allow you design and achieve your customer goal.
To design high-availability solution, you must deploy a server farm. To decide you may need to discuss following items with your customer and analysis the outcome.

Question	Yes	No
Is your overall availability requirement below 99%?
Is the availability of your data critical?

Question 1 Is your availability requirement 99% or greater? If your customer response to “YES”, which means organization looking for high availability on Office SharePoint Server 2007.
I order to meet above requirement you need to design your Web Front End Server to the two-server deployment, which will gain scalability and availability by load-balancing requests so that if one server goes down, the system up and running.
Question 2 Is the availability of your data critical?, If your customer response to “YES”, which means organization is looking for high availability and gain scalability to safe from data loss, so your design need to be clustered or mirrored database server .

Medium Farm System Architecture
Large server farm :
Part of this article is to help you determine the Large server farm configuration which is suitable for an enterprise-level SharePoint environment:
To design enterprise-level SharePoint environment, you may need to discuss following point with your customer and analysis the outcome (This question are in-addition to medium farm server questions).

Application server role	Service
Query
Excel Calculation Services
Index & Search (External System i.e. ERP, CRM, File share and Lotus Notes)
Windows SharePoint Services 3.0 search

Enterprise-level SharePoint environment :
_ Two or more load-balanced front-end web servers running Office SharePoint Server 2007
_ Two or more application servers running Office SharePoint Server 2007
_ One Index & Search servers running Office SharePoint Server 2007
_ Two or more clustered database servers running SQL Server 2000 or 2005
_ SAN Storage

The above architecture diagram shows Web Tier, Application Tier and DB Tier which design to serve different purposes, each of the servers provides specific SharePoint Server 2007 services such as Index Services or Excel Calculation Services, and the front-end servers provide web content services.
The servers in server farm (WFE server, Application server, Index server) must run with Office SharePoint Server 2007.
Database server which configure clustered or mirrored environment with SAN storages.
Conclusion
There is nothing special or difficult on above architect design, basically understanding the customer requirements (i.e. future user growth rate, storage capacity, system availability, security, and system performance requirements) put this pieces of information together and analysis and provide possible solutions architecture that meet your customer goal.
Other SharePoint related article :
1. Microsoft Office Servers Overview with Logical Architecture
2. Office SharePoint Server 2007 Features
3. Setup and Install SharePoint 2007 Server (MOSS) on Virtual PC

SharePoint Hit Counter

to add Hit counter on SharePoint site homepage.
Let's go through how to insert "Hit Counter"
1. SharePoint Designer Open Site and Page that you need insert "Hit Counter"
2. Open Page in Edit Mode and place the cursor where you want to insert the hit counter.
3. Go to Insert - Web Component

4. Select Hit counter and System display different types styles that readily available.

5. Click on Finish, system will open the below Hit Counter Properties window
6. To start the counter on given number Select Reset counter to option and give number to star.

7. Once you click OK, The counter will be inserted to your page.

8. Preview on Web browser and start refresh your page the counter will increase count.

Cannot start service SPUserCodeV4 on computer

Error occurred in deployment step 'Retract Solution': Cannot start service SPUserCodeV4 on computer 'SHAREPOINT'.

You can do the following steps to resolve it.
1. Go to Central Administration
2. Open "System Settings"
3. Open "Manage services on server"
4. Locate the service “Microsoft SharePoint Foundation User Code Service”
5. Start the service  “Microsoft SharePoint Foundation User Code Service”
http://social.msdn.microsoft.com/Forums/is/sharepoint2010general/thread/2af4352a-7379-44c8-99e3-0a33ed1a1db1

Classic mode authentication to Claim based authentication

Recently i presented SharePoint 2010 permission and visited MSDN Forum people asking about how to convert web application that created with classic mode authentication to claim based authentication.
Yes, you can convert only via PowerShell Script.

$ConvertApp = get-spwebapplication “http://<web application name>”
$ConvertApp.useclaimsauthentication = “True”
$ConvertApp.Update()

Please Note : Once you convert the web application to use claim based authentication, you cannot return to classic mode authentication

SharePoint 2010 Uploading multiple files Failed

Uploading multiple files via SharePoint Multiple files uploads…failed mainly for file extension such .CS and .JAVA these files not in SharePoint 2010 File Block List under central admin.
By the way when you upload single file including .CS/.JAVA ext. no issue.
Notice that the issue happen following actions
1. Upload Multiples files (i.e .CS / .Java) Failed.
2. Windows Explore also fail to upload.

So how to overcome this issue. By removing file extension from IIS request filter allow to upload .CS and .JAVA files.
To help others :
1. Go to IIS
2. Select your website and Find Request Filtering

3. File Name Extensions tab and Select your extension for the list
4. Right click the and Remove.


5. Upload your files via SharePoint 2010.

Silverlight base STSADM commands

Silverlight base STSADM commands technical reference available at TechNet Web site.
Beside a view that shows all the commands you can choose a view.

For details view go to
http://technet.microsoft.com/en-us/office/sharepointserver/cc948709.aspx
http://technet.microsoft.com/en-us/windowsserver/sharepoint/dd418924.aspx

Modify this view page cannot be displayed Error Code : 500 Internal Server (ISA)

When user go and Click SharePoint - View - Modify this view action menu (OR) Modify Column link the browser display following message “The Page cannot be displayed” Error Code : 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217)


When I search online, Microsoft support provided me following work around for the issue, configure the Web publishing rule so that it does not block high-bit characters.
1. Start the ISA Server or Microsoft Forefront Threat Management Gateway, Medium Business Edition Management tool.
2. Expand ServerName, where ServerName is the name of your ISA Server or Microsoft Forefront Threat Management Gateway, Medium Business Edition computer.
3. Click Firewall Policy, click the Web publishing rule that you created to publish the Exchange Server computer for access by OWA users, and then click Edit Selected Rule.
4. Click the Traffic tab, click Filtering, and then click Configure HTTP.
5. Click to clear the Block high-bit characters check box, and then click OK two times.
6. Click Apply to update the firewall policy, and then click OK.
But doesn’t solve my problem. Later I found that the issue coming from ISA HTTP Filter policy…. to resolve follow the below steps.
General Tab
The figure shows the default settings on the General tab of the HTTP policy properties
1. Start the ISA Server
2. General tab of the HTTP policy properties
3. Un Check Verify normalization, (Select if you want to block requests with URLs containing escaped characters after normalization.)

According to Tech Net
Web servers receive requests that are URL encoded. This means that certain characters may be replaced with a percent sign (%) followed by a particular number. For example, %20 corresponds to a space, so a request for http://myserver/My%20Dir/My%20File.htm is the same as a request for http://myserver/My Dir/My File.htm. Normalization is the process of decoding URL-encoded requests.
Because the % can be URL encoded, an attacker can submit a carefully crafted request to a server that is basically double-encoded. If this occurs, Internet Information Services (IIS) may accept a request that it would otherwise reject as not valid. When you select Verify Normalization, the HTTP filter normalizes the URL two times. If the URL after the first normalization is different from the URL after the second normalization, the filter rejects the request. This prevents attacks that rely on double-encoded requests.
Note that while we recommend that you use the Verify Normalization function, it may also block legitimate requests that contain a %.
Now we do not have an error.... Hope this information may helps someone…. If yes provide me comments and feedback
codeproject