Showing posts with label Best Practices. Show all posts
Showing posts with label Best Practices. Show all posts

22 December, 2013

Precautions while installing sharepoint language packs?

Language packs enable you to create site collections and sites in multiple languages without requiring separate installations of SharePoint in each language.

SharePoint language pack is one of the vital functionality from ends user perspectives. This is just like another SP functionality that needs to be use on daily basis but yes its one time activity!

Hello All,
By means of this article, I would to consolidate audience’s views / comments so that it will be useful for all the SharePoint communities.

Thank you.

22 February, 2013

Upgrade Best Practices SharePoint Server 2010

I was in a process of giving the details about migration to a organisation from 2007 to 2010 and found this useful article on Technet .

To ensure a smooth upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, follow these best practices

  • Update your servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later.
Your environment must be updated to Service Pack 2 of Office SharePoint Server 2007 to run the upgrade process, either for an in-place or database attach upgrade. We recommend that you install the October 2009 Cumulative Update because it includes improvements to the pre-upgrade checker tool. Ensure that the environment is fully functioning before you perform an upgrade.

  •  An upgrade does not solve any problems that might already exist in your environment. Therefore, ensure that the environment is fully functioning before you perform an upgrade. For example, if you have Web applications that are no longer being used, unextend them before you upgrade. If you want to delete a Web application in Internet Information Services (IIS), unextend the Web application before you delete it; otherwise, SharePoint Server 2010 will try to upgrade the Web application even though it does not exist, and the upgrade will fail. If you find and solve problems beforehand, you are more likely to meet the upgrade schedule that you have estimated.

  • Before you try an in-place upgrade, migrate to 64-bit servers. Upgrade your operating system to a 64-bit version of Windows Server 2008 R2 or Windows Server 2008 with Service Pack 2 (SP2). If you are using SQL Server, upgrade or migrate to a 64-bit version of Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3.

  • Do not try to combine these operations with your upgrade process. You cannot perform an in-place upgrade unless your system already runs on a supported operating system and platform.

  • Run the pre-upgrade checker to look for potential issues.

The pre-upgrade checker reports missing customizations and issues with orphaned sites, and more, so that you can address these issues before you perform your upgrade.

 For more information, see Run the pre-upgrade checker (SharePoint Server 2010).
  • Perform a trial upgrade on a test farm first.

Back up the live farm, restore to test servers, and then perform the upgrade. Examine the results to set expectations for what the live upgraded sites will look like, to determine how much post-upgrade customization will have to be done, and to estimate how long the upgrade will take. Try a full search indexing crawl. For more information, see Use a trial upgrade to find potential issues (SharePoint Server 2010).
  • Plan for capacity.
Ensure that you have disk, processor, and memory capacity sufficient to handle upgrade requirements. For more information about system requirements, see Review system requirements for upgrade (SharePoint Server 2010). For more information about how to plan the disk space that is required for upgrade, see Estimate how long the upgrade process will take and the space that you need (SharePoint Server 2010). For more information about how to plan for capacity, see Performance and capacity management (SharePoint Server 2010).
  • Back up your environment.
Perform a full backup of your environment before upgrading. That way, you can recover your environment if you must roll back from an upgrade. For more information, see Back up environment before an in-place upgrade (SharePoint Server 2010).
  • Optimize your environment before upgrade.
A few key limits have changed in SharePoint Server 2010, such as query throttling on large lists and lower limits on the number of site collections allowed per content database (from 5,000 warning and 15,000 limit to 2,000 warning and 5,000 limit). Be sure to optimize your Office SharePoint Server 2007 environment to meet these limits or restrictions before upgrade to mitigate errors during the upgrade process or broken lists or sites after upgrade. For more information about the site collection limit, see SharePoint Server 2010 capacity management: Software boundaries and limits. For more information about large lists and addressing the lower limit on site collections, see Clean up an environment before upgrade (SharePoint Server 2010).
  • (Optional) If you are using the database attach upgrade method, set the original databases to read-only.
If you expect a long outage window while you perform a database attach upgrade, you can set the databases in the original environment to be read-only so that users can continue to access their data without changing it. For more information, see Attach databases and upgrade to SharePoint Server 2010.
  • Do not add any servers to your server farm after you begin the upgrade process.
Running the SharePoint Products Configuration Wizard upgrades the configuration database. The configuration database contains the list of servers in the farm. Servers added to the farm after the configuration wizard has been run are not included in the database. Therefore, servers added after the wizard runs do not appear in the upgraded version topology. If you need to add servers to your farm, do so either before you start the upgrade or after you have completed the upgrade process.
  • After upgrade, review the Upgrade Status page and upgrade logs to determine whether there are issues that must be addressed. Then review the upgraded sites.
The Upgrade Status page reports on the upgrade progress, and the upgrade logs list any errors or warnings that occurred during the upgrade process. You should verify all of the sites and test them before you consider the upgrade complete. For more information, see Verify upgrade and review upgraded sites (SharePoint Server 2010).

26 December, 2012

IMP Considerations while Uploading large files or many files to a library

Microsoft Recommendations
If you are uploading large files--or many files that add up to a large total size--to a library, you may get errors due to the file size limit in SharePoint or timeout errors in your version of Internet Explorer.
Steps you can take to get around these errors include:
  • Upload 100 or fewer files. Uploading more than 100 files at a time is not supported.
  • Avoid uploading files larger than 250 MB, which is the maximum file size by default.
  • If your organization maintains an on-premises deployment of SharePoint, ask the server administrator to verify or increase the maximum file size limit to accommodate the size of the files you are uploading. The default size limit is 250 MB, but it can be increased.
  • For file sizes exceeding 2 GB, if you see a "Working on it" message that never goes away, follow the instructions in Microsoft Support: Internet Explorer error "connection timed out" when server does not respond.

19 March, 2011

File Name, Length, Size and Invalid Character Restrictions and Recommendations

New Blocked File Types

If you were familiar with the WSS 2.0 list, there are some new Blocked File Types: .asmx, .rem, .resx, .soap, or .ashx.  If they existed before upgrade they are no longer visible or cannot be opened after upgrade.  These file extensions have been added to the list of blocked file extensions.

You now have the ability to make differences between farm wide blocked file types and web application blocked file types.  If you want to un block it, it needs to be removed at both farm and application levels, but you can add specific blocked files for a single web application.  The farm level block list for example will override anything removed at the web application level.

My most commonly removed blocked files are .chm (help files), .lnk (url link), .url (url link) 

My most commonly added blocked files are .mp3 (audio), .pst (mail), .vhd (virtual hard drive)

Site Names

-In WSS Site Names may not contain the following characters: \ / : * ? " < > | # { } % & " ~ +
-You cannot start a site name, sub site name, or a site group name with an underscore (_) character or with the period character (I recommend avoiding the (_) underscore in site names)
-You cannot use the period character consecutively in the middle of a site name
-You cannot use the period character at the end of a site name

File Names

-Invalid characters: " # % & * : < > ? \ / { | } ~ 
-Cannot be longer than 128 characters
-You cannot use the period character consecutively in the middle of a file name
-You cannot use the period character at the end of a file name
-You cannot start a file name with the period character

Folder Names

-You cannot use the following characters anywhere in a folder name or a server name:  ~ # % & * { } \ : < > ? / | "
-Cannot be longer than 128 characters
-You cannot use the period character consecutively in the middle of a folder name
-You cannot use the period character at the end of a folder name
-You cannot start a folder name with the period character

Max File Upload/Download Sizes

The default max single file upload size is 50 MB by default for a web application.  

Microsoft IT limits their environment at 100 MB, and the maximum that the product itself can handle or support is 2GB which is essentially a SQL limit.  By setting the limit to blank will essentially support what SQL will support.

Increase the maximum upload size

1.  Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
2.  Under Virtual Server Configuration, click Configure virtual server settings.
3.  On the Virtual Server List page, click the virtual server you want to change.
4.  On the Virtual Server Settings page, under Virtual Server Management, click Virtual server general settings.
5.  Under Maximum upload size, type the maximum file size (in MB) that you want to allow to be uploaded.
6.  Click OK.

1. Get into the SharePoint Central Administration Site
2. Select "Application Management"
3. Under the "SharePoint Web Application Management" section select "Web Application General Settings"
4. Change the "Maximum Upload Size"

If IIS is timing out when you upload large files, you can configure the Connection timeout setting in IIS to allow more than the default 120 seconds (2 minutes).

Tune the IIS connection timeout

1.    Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2.    Right-click the virtual server you want to configure, and then click Properties.
3.    Click the Web Site tab.
4.    In the Connections section, in the Connection timeout box, type the number of seconds you want IIS to wait before timing out.
5.    Click OK.