To begin with, the Support for Large Files was one of the enhancements made in Windows SharePoint Services SP 1. By default, the maximum size for uploading files is set to 50 MB. The maximum file size that it can go up to is 2,047 megabytes.

Now it is obvious that any cap on the maximum file size will stop the users from trying to upload larger files (including me!). Though SharePoint is meant to handle files that are up to 2 gigs in size, it is not practically feasible and not recommended as well.

However, there are circumstances where files of much smaller size fail to upload which makes one wonder as to what could be the reason. Hence I decided to write this post for all those who have come across this issue and are looking for some options to work around it.

On a SharePoint server (WSS 3.0, MOSS 2007, SharePoint Server 2010 or SharePoint Server 2013) when we upload any document larger that 50 megs on any document library, we can encounter the following error messages

• "An unexpected error has occurred"
• "The page cannot be displayed”
• "An unknown error occurred"
• "HTTP 404 – Page Not Found”
• “Request timed Out’

If you are using explorer view, the error message would be similar to

Could not find this item --> This is no longer located \\Servername\DavWWWRoot\team. Verify the item's location and try again".

Before we begin, I would like to mention that SharePoint is not really designed to handle huge files > 300 Mb). It stores all files in the content databases and that's where these large files are going. So I strongly recommend using file shares instead.

Going ahead, this can occur due to various reasons and I have listed a few of the possible causes and the workarounds for them

WORKAROUND(s)

Method 1  Increase the maximum upload size for the web application

Note : The default max single file upload size is 50 megs by default for a web application (in IIS 6.0) and 28 megs for IIS 7.0.

1. Go to 'Start > All Programs > Administrative Tools > SharePoint Central Administration > Application Management'.
2. Under SharePoint Web Application Management, click 'Web application general settings’.
3. On the Web Application General Settings page, choose the appropriate web application.
4. Under Maximum upload size, type the file size which you want to upload and click on OK. You can specify a maximum
   file size up to 2,047 megabytes.

Note:

Any upload size which is below 50 megs is enforced directly through web app settings. Above 50 megs, you need to make a some small change to the web.config file to allow larger uploads. Repeat the steps listed below for all zones for your web app all the servers which host the web application role.

• Open the web.config from 'C:\Inetpub\wwwroot\wss\VirtualDirectories\<Virtual Directory>' folder and modify it as follows
  

<httpRuntime maxRequestLength="51200" /> with <httpRuntime executionTimeout="999999" maxRequestLength="51200" />

• Perform an IISReset and you should be good to go.

See <httpRuntime> element in web.config for more information.   

Method 2  Increase the connection time-out setting in IIS

While uploading large files, there are chances that the request will timeout. By default, the IIS connection time-out setting is 120 seconds. Follow these steps to increase the connection time-out setting,

• Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
• Right-click the virtual server that you want to configure, and then click Properties.
• Click the Web Site tab. Under Connections, type the number of seconds that you want in the Connection time-out box,
  and then click OK.

Method 3 Increase the maximum upload size in the web.config file of web application

By default, the web.config file is located in the 'C:\Inetpub\Wwwroot\Wss\Virtual Directories\<Virtual Directory>' folder. Add the following configuration to the web.config, just before the <configuration> section closes out.

Here’s a screenshot of the web.config file after the change:

This sets the value of the maxAllowedContentLength property to 52428800 (in bytes) for the web application only.

See KB944981 - You cannot upload files that are larger than 28 MB on a Windows Server 2008-based computer that is running Windows SharePoint Services 3.0.

Note:

The following information is applicable to IIS 7.0 and suggests making a change to the ‘applicationhost.config’ file which is a core configuration file for IIS. For more information, see

Error message when you visit a Web site that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE".

The maxAllowedContentLength property specifies the maximum length of content in a request in bytes and it needs to be set on a Windows Server 2008 computer that has IIS 7.0-only installations. To change the value of the property, do the following

• Open command prompt and go to 'C:\windows\system32\inetsrv' directory
• Run the below command

appcmd set config /section:requestfiltering /requestlimits.maxallowedcontentlength:unit

where the variable "requestlimits.maxallowedcontentlength" unit specifies the maximum length of content.

For example, to specify 2000000000 as the maximum length of content, type the following at the command prompt, and then press ENTER:

appcmd set config /section:requestfiltering /requestlimits.maxallowedcontentlength:2000000000

• Perform an IISreset /noforce.

• More info is available at

• Configure Request Filters in IIS 7
• What is RequestFiltering? 

Method 4 Increase the default chunk size for large files

The large-file-chunk-size property sets the amount of data that can be read from server running SQL Server at one time.

• If you have a file that is greater than your chunk size (such as 70 MB when the chunk size is set to 5 MB), the file would be read in 14 chunks (70 / 5).
• The chunk size is not related to the maximum upload file size.
• The chunk size simply specifies the amount of data that can be read from a file at one time. By default, the large-file-chunk-size property is set to 5 MB.
• Check if the 'large-file-chunk-size' property is set or not

    Stsadm -o getproperty -propertyname large-file-chunk-size

• In order to set the large–file–chunk–size property, we need to use the command line. This property is configured for a server or server farm, and cannot be configured for an individual web app server. To set this property, use the following syntax:

   Stsadm.exe –o setproperty –pn large–file–chunk–size –pv <size in bytes>

More on this command is available at Large-file-chunk-size: Stsadm property (Office SharePoint Server) 

• After making a change to this property, perform an IISreset /noforce.

See What is the maximum value one can set for the Large-file-chunk-size ?

Method 5  Add the executionTimeout value

Increase the execution timeout for the upload page (upload.aspx) to prevent timeouts on the page. The default timeout for ASP.NET 2.0 is 110 seconds, so any uploads that are taking longer than that will result in a request failure. Add the executionTimeout value to web.config in the 'C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS' folder and the  ‘C:\Inetpub\wwwroot\wss\VirtualDirectories\<Virtual Directory>' folder.

• Navigate to 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS' folder on the SharePoint server.
• Open the 'web.config' file in notepad or any other text editor and add the executionTimeout parameter. For example, replace the value as follows

Existing code

<location path="upload.aspx">

    <system.web>

      <httpRuntime maxRequestLength="2097151" />

    </system.web>

</location>

Replacement code

<location path="upload.aspx">

    <system.web>

      <httpRuntime executionTimeout="999999" maxRequestLength="2097151" />

    </system.web>

</location>

• Open the 'web.config' file from the 'C:\Inetpub\wwwroot\wss\Virtual Directories\<Virtual Directory>'folder and modify it as follows
  

  Existing line :              <httpRuntime maxRequestLength="51200" />
  Replacement line :      <httpRuntime executionTimeout="999999" maxRequestLength="51200" />

Modify the web.config located in "12\CONFIG" folder

• Navigate to 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\CONFIG' folder on the SharePoint server and modify the 'maxRequestLength' property which by default is set to the following

  <httpRuntime
  maxRequestLength="51200"
  />
  

• Open the 'web.config' file in notepad or any other text editor and modify the value to match the other web.config files
• Save the file and perform an 'IISreset /noforce'.

Antivirus Exclusions

Make sure you have added Antivirus exclusions as per http://support.microsoft.com/kb/952167

ASP.Net Session State

• Open IIS manager, expand the 'Sites' node and select the SharePoint site
• Click on 'Session State' under 'Application Development' and verify that the 'Timeout' value is set to '120' minutes

You can also verify this from the web.config file

What is ASP.Net Session

ASP.NET session state enables you to store and retrieve values for a user as the user navigates the different ASP.NET pages that make up a Web application. HTTP is a stateless protocol, meaning that your Web server treats each HTTP request for a page as an independent request; by default, the server retains no knowledge of variable values used during previous requests. ASP.NET session state identifies requests received from the same browser during a limited period of time as a session, and provides the ability to persist variable values for the duration of that session.

See ASP.NET Session State for more information

Explorer view or Web client issues

While trying to use the explorer view, you may see the following error despite making the aforementioned changes

“Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved” message

If this is the case then the issue is most likely caused by a local restriction set on Web Client service. By default, Web Client file size limit is set to around 47 Mb. To increase this limit:

• Click Start, click Run, type regedit, and then click OK.
• In Registry Editor, locate the following registry key
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClientParameters
• Right click on the FileSizeLimitInBytes and then click Modify.
• In the Value data box, click on Decimal, and type 4294967295 and then click OK.
• Quit Registry Editor
• Restart Web Client service from Services.msc

Large file Support Limitations

The following features do not support files larger than 50 MB

• Virus checking
• Streaming files
• Client-side restoration of smigrate backup files (limited to 2 GB). The manifest files for an smigrate backup cannot be larger than 2 GB (SPS)
• Site templates (limit of 10 MB per site template, including content).

NOTE:

• As mentioned earlier, I would like to mention that SharePoint is not really designed to handle huge files > 300 Mb). It stores all files in the content databases and that's where these large files are going. So I strongly recommend using file shares instead.
• Also be aware that increasing you upload file size to 2 GB has performance ramifications so it a user uploads a file and there is no memory available no new requests can be handled until the memory is available again.
  
  

Additional Info

• Error message when you try to upload a large file to a document library on a Windows SharePoint Services 3.0 site: "Request timed out"
• Error message when you visit a Web site that is hosted on a server that is running IIS 7.0: "HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE"

Consider a scenario where you receive the following error when you browse to a SharePoint web app

The website declined to show this webpage
HTTP 403 
Most likely causes:
This website requires you to log in.

This issue is intermittent. Strangely, if we create a copy of the web.config file, rename the web.config file, refresh the home page, we receive an "HTTP 404 - Page Not Found" error. Rename the web.config file back and refresh the page. The site is browse able for a while before failing after some time

We see the following error in Failed Request Tracing

A procmon trace captured while accessing the web app from the server showed the following:

w3wp.exe 4180 CreateFile C:\inetpub\wwwroot\wss\VirtualDirectories\Web80.Contoso.com80\bin ACCESS DENIED Desired Access: Read Data/List Directory, Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: NT AUTHORITY\IUSR

This issue usually occurs when a request from an authenticated user without local admin rights results in a failed read of the /BIN directory by the impersonating w3wp.exe (IIS worker process for ASP.NET) process. This behavior is typically associated with lack of permissions to the temporary folder /BIN where ASP.Net assemblies are Just In Time (JIT) compiled.

Resolution

The solution is to ensure that the Authenticated Users or <SERVER NAME>\Users group (which usually contains DOMAIN\Users group) has Read & Execute, List Folder Contents and Read permissions on the /BIN folder below C:\inetpub\wwwroot\wss\VirtualDirectories\{Sitename80}. Follow the steps listed below to grant the required permissions:

• Open Windows Explorer and navigate to the /bin directory of your web application
• Right-click on the folder and click on Properties
• Go to Security tab and click on Edit
• Click on Add and add the local server group Authenticated Users or <SERVER NAME>\Users (this usually contains DOMAIN\Users group).
• Select the Read & Execute, List Folder Contents and Read permissions (if you are planning to add Everyone to the /bin folder, grant Read permissions only)
• Click OK to apply the new settings

Refresh the page and we should be able to browse to the site.

There are instances where this permission needs to be re-applied as part of every deployment and we may often find that the permissions have reset after touching the Authentication Providers settings in Central Admin.

More Information

If an administrator accesses the site/feature that caused the error, the subsequent requests from non-administrators would succeed. This behavior is typically associated with lack of permissions to the temporary folder where ASP.Net assemblies are Just In Time compiled.

The freb trace shows a 403.0 for ManagedPipelineHandler

It seems to go through quite a few ASPNet events - but happens during the ASPNetPageRender - it goes to the ASPNetPageRender Enter, then ASPNetHTTPHandler Leave.Only then does it get a 403.0 which is not an official RFC error. The first sub-status for 403 is 403.0.

Application pool in Classic or Integrated mode

1. Application Pool in Classic Mode – In this case, we can configure a Wildcard mapping for ASPNET_ISAPI.dll at the website level. That would propagate to child virtual directories. That should not need any further modifications at the virtual directory level.
2. Application Pool in Integrated Mode – In this case, all relevant virtual directories would need individual modifications. They need to be set for specific handler. E.g. ‘book’ virtual directory needs mapping for BookAPI and ‘movie’ directory would need mapping for MovieAPI.

When installing SharePoint 2013 prerequisites on Windows Server 2008 R2, the prerequisite installer fails with the following error

Appfabric installation failed because installer MSI returned with error code:1603

This is a generic MSI error message and does not give any indication about how to get the issue fixed. Uninstall or reinstalling only makes it worse.

The issue can be caused due to the following:

1. The path to the PowerShell executable that is needed for the AppFabric installation is incorrect.
2. In some scenarios, repeated uninstallation and re-installation does not fix the issue. This is because the installer does not remove the PSModulePath entry in Environment Variables during un-installation and the installation fails because the entry already exists.
3. If you are trying to install all the prerequisites manually as the server does not have a connection to internet.
   
   Note: Appfabric installation and configuration has to be done by the prerequisite installer ONLY and not in a stand-alone manner.

You can implement any one of the two solutions listed below

1. Solution 1
   
   Append the following path to PSModulePath entry in the environment variables - %SYSTEMROOT%\System32\WindowsPowerShell\v1.0
   
   
   • Go to My Computer, right-click Properties
   • On the System' page, click Advanced System Settings on the left-side pane.
   • If you receive a UAC prompt, click on Yes to launch the System Properties dialog box
   • From the Advanced tab, click Environment Variables
   • Within the System Variables section in the lower half, select PSModulePath and click on Edit (or double-click PSModulePath')
   • Append the following path to PSModulePath entry in the environment variables

   %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

   • Ensure that the PSModulePath entry looks like this:
     
     C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules
     
     
     
2. Solution 2
   
   
• There are chances that other applications might be referencing the same variable and may fail if it is deleted. This is what we can do if solution 1 does not help.
• Remove the PSModulePath entry from the 'Environment Variables' and re-run the installer. Once it completes successfully, ensure that the PSModulePath entry looks the same as mentioned in solution 1.
  
3. Solution 3

You can download the list of prerequisites from Links to applicable software

Links to the individual prerequisites:

• Microsoft .NET Framework version 4.5
• Windows Management Framework 3.0
• Application Server Role, Web Server (IIS) Role - Enable the Web Server (IIS) role and the Application Server role in Server Manager
• Microsoft SQL Server 2008 R2 SP1 Native Client
• Windows Identity Foundation (KB974405)
• Microsoft Sync Framework Runtime v1.0 SP1 (x64)
• Microsoft AppFabric 1.1 for Windows Server
• Windows Identity Extensions
• Microsoft Information Protection and Control Client (MSIPC) 
  
  MSIPC.dll - Microsoft Active Directory Rights Management Services Client. See AD RMS Client 2.0 Deployment Notes -  http://technet.microsoft.com/en-us/library/jj159267(v=ws.10).aspx for more information
  
• Microsoft WCF Data Services 5.0 for OData V3
  
  WCF Data Services 5.0 enables creation and consumption of data services for the Web according to version 3 of the Open Data Protocol (OData), which facilitates data access and change via standard HTTP verbs.
  
• Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)

The steps listed below are for AppFabric for Windows Server only

Follow these steps for installing AppFabric for Windows Server correctly

• Uninstall the Appfabric for Windows Server from Control Panel -> Programs and Features page
• Download the individual requirements to a network location or a local folder
• Install prerequisites for SharePoint 2013 manually
• From the Start menu, open the Command Prompt window using the Run as administrator option.
  
  - Navigate to the root of the SharePoint 2013 installation media or folder location
  - Type the prerequisite program switch and corresponding argument for the program that you want to install, and then press ENTER.
  For example:
  
  If we have to install AppFabric for Windows Server from a local source, we can run the following command:

  PrerequisiteInstaller.exe /AppFabric:<location Of the Appfabric installation file>

  This will kick off the prerequisite installer wizard which will then use the installation file stored locally on the machine as specified in the command-line to install Windows Server AppFabric. We can also install more than one prerequisite by using different switches with the PrerequisiteInstaller.exe command to install multiple components and specifying the installation path in the command line window. For example:

  PrerequisiteInstaller.exe /AppFabric:<location Of the Appfabric installation file> /IDFX11:<Install Windows Identity Foundation v1.1 from file>

  This command will install Appfabric and Windows Identity Foundation
  
  For a complete list of prerequisite installer operations and command-line options, see Prerequisite installer operations and command-line options
  

• The SharePoint 2013 prerequisite installer (prerequisiteinstaller.exe) installs the following software, if it has not already been installed on the server, in this order (provided you have downloaded the prerequisites locally):
  
  PrerequisiteInstaller.exe
  
  /SQLNCli:file - Install Microsoft SQL Server 2008 R2 SP1 Native Client from file
  /PowerShell:file - Install Windows Management Framework 3.0 from file
  /NETFX:file - Install Microsoft .NET Framework 4.5 from file
  /IDFX:file - Install Windows Identity Foundation (KB974405) from file
  /Sync:file - Install Microsoft Sync Framework Runtime v1.0 SP1 (x64) from file
  /AppFabric:<location Of the Appfabric installation file>
  /IDFX11:"<path>\Microsoft Identity Extensions.msi"
  /MSIPCClient:"<path>\msipc.msi"
  /WCFDataServices:"<path>\WcfDataServices.exe"
  /KB2671763:"<path>\AppFabric1.1-RTM-KB2671763-x64-ENU.exe

where "<file>" signifies the file location from where you want to install. If you do not specify the <file> option, the installer downloads the file from the Internet and installs it.

The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.<date>.<time>.log. You can check these log files for specific details about all changes the installer makes to the server.

See Install prerequisites for SharePoint 2013 from a network share for information about how to install the SharePoint 2013 prerequisites at the command prompt from a network share or local system. This approach is typically used when the server does not have a connection to internet.

• Download AppFabric 1.1 from Official Microsoft Download Center
• For more information about AppFabric for Windows Server, see AppFabric for Windows Server
  

What are Application templates

Application templates are out-of-the-box custom scenarios which are developed to address the needs and requirements of specific business processes or sets of tasks as in they can be used to create a dedicated site or workspace for a particular business process or task.

Application templates in WSS and MOSS are separated into two group of templates; Server Admin Templates and Site Admin Templates.

Server Admin Application Templates

1. Absence Request and Vacation Schedule Management
   A site for teams to share information on when team members will be away from the office and who to contact for issues.
2. Help Desk
   A site for teams to submit and manage customer support issues.  It provides lists to track service request history and includes a knowledge base.
3. Budgeting and Tracking Multiple Projects
   A site for teams to track multiple projects.  It provides lists to track general project information, project tasks, and project issues.
4. Inventory Tracking
   A site to track inventory items, levels, sales, and orders.
5. Bug Database
   A site for teams to track bugs in their shared software projects.
6. IT Team Workspace
   A site for an IT team site to manage incoming issues, projects, and bugs.
7. Call Center
   A site for teams to track customer support calls.  It provides lists to track customers, service request history and includes a knowledge base.
8. Job Requisition and Interview Management
   A site for teams to manage their job requisitions, candidates, and interviews.
9. Change Request Management
   A site for teams to track change requests in multiple projects.  It provides lists to track change requests, general project information, project tasks, project issues, and project risks.
10. Knowledge Base
    A site to manage and create knowledge assets within an organization.
11. Compliance Process Support Site
    A site for teams to help plan compliance processes.
12. Lending Library
    A site to track the assets of a team lending library.
13. Contacts Management
    A site for teams to track their shared contacts.
14. Physical Asset Tracking and Management
    A site for teams to track their existing physical assets and manage the process of proposing new assets.
15. Document Library and Review
    A site for teams to store documents and provide feedback on a per-version basis.
16. Project Tracking Workspace
    A site that supports team collaboration on projects.  This site includes Project Documents, Project Issues, Project Risks, and Project Deliverables lists which may be linked to tasks in Microsoft Office Project Server 2007.
17. Event Planning
    A site for teams to plan and manage events like conferences.
18. Room and Equipment Reservations
    A site for teams to manage the use of shared rooms and equipment.
19. Expense Reimbursement and Approval Site
    A site for teams to submit and manage expense reports.
20. Sales Lead Pipeline
    A site for sales teams to track contacts, accounts, leads, and opportunities.

Note: To install or remove a server admin template, you must have Administrator rights to both the Windows SharePoint 

          Services site and to the root of the server on which it is to be installed or removed.

  Installation and removal are done via the 'Stsadm.exe' command-line utility located at

  '%PROGRAMFILES%\Common files\Microsoft Shared\Web Server Extensions\12\Bin'
 

Site Admin Templates

These are custom templates which can be installed by individual site administrators in a template gallery without requiring farm administration access. Below is a list of these 20 templates
   

1.      Board of Directors

The Board of Directors application template provides a single location for an external group of members to store and locate common documents such as quarterly reviews, shareholder meeting notes and annual strategy documents. The template also tracks tasks, issues and calendar items so board members have a single location to view information relevant to them

2.      Business Performance Rating
The Business Performance Reporting application template helps organization managers track the satisfaction of customers through a combination of surveys and discussions. Surveys can be sent via Office InfoPath 2007 which are then consolidated by the template to give an overall response to a series of questions.

3.      Case Management for Government Agencies

The Case Management for Government Agencies application template helps case managers track the status and tasks required to complete their work. When a case is created, standard tasks and documents are created which are modified based on the work each case manager has completed.

4.      Classroom Management
The Classroom Management application template helps instructors and students organize and store information related to a particular class. The site includes document libraries to store assignments and lecture notes as well as calendars and announcement capability to enable communication from instructor to students.

5.      Clinical Trial Initiation and Management
The Clinical Trial Initiation and Management application template helps teams manage the process of tracking clinical trial protocols, objective setting, subject selection and budget activities. The site provides useful Office Word 2007 templates as well as the capability to create, track and assign tasks and issues related to a particular clinical trial.

6.      Competitive Analysis Site
The Competitive Analysis Site application template helps teams organize information about competitors and their products. The site provides useful Microsoft Office 2007 documents to perform SWOT and other useful competitive analysis techniques. Links to industry, company and product news can also be included to provide a single location for all competitive information.

7.      Discussion Database
The Discussion Database application template provides a location where team members can create and reply to discussion topics. Discussions are organized by categories, which are created by a site manager, and can be linked to Office Outlook 2007 via an RSS feed.

8.      Disputed Invoice Management
The Disputed Invoice Management application template helps accounts payable departments track open invoices including the potential savings associated with paying the invoice early. The site includes useful templates for analyzing the reasons invoices are being disputed as well as tracking who to contact for more information.

9.      Employee Activities Site
The Employee Activities Site application template helps manage the creation and attendance of events for employees. Activity owners use the site to review proposals for new activities and create event calendar items. Employees use the site to sign up as well as track which activities they’ve attended in the past.

10.  Employee Self-Service Benefits
The Employee Self-Service Benefits application template provides tools for an organization to inform employees about available benefits as well as enabling them to enroll for each benefit.

11.  Employee Training Scheduling and Materials
The Employee Training Scheduling and Materials application template helps instructors and employees manage courses and related materials. Instructors can use the site to add new courses and organize course materials. Employees use the site to schedule attendance at a course, track courses they've attended and to provide feedback.

12.  Equity Research

The Equity Research application template helps teams collaborate on researching stocks and other equities. It provides a central location for teams to store documents, post links, track news, and hold discussions related to the equities tracked by the site.

13.  Integrated Marketing Campaign Tracking

The Integrated Marketing Campaign Tracking application template helps marketing managers track the implementation and success of outbound marketing activities. The template allows a manager to create marketing activities and track the results of those activities, such as responses generated and sales completed. The template contains multiple methods of analyzing the success of the campaigns including automated calculations and Office Excel 2007 templates for more detailed analyses.

14.  Manufacturing Process Management

The Manufacturing Process Management application template helps teams to model and track manufacturing processes as well as tasks and issues that arise in the upkeep of these processes.

15.  New Store Opening
The New Store Opening application template helps a team manage the opening of new store locations or re-modeling of existing store location. The site provides a single location to manage tasks, issues, and documents for all store opening processes, enabling end users to view relevant information and providing project managers insight across the entire project.

16.  Product and Marketing Requirements Planning

The Product and Marketing Requirements Planning application template enables teams to manage the process of collecting and documenting requirements for new products. The site provides several Microsoft Office 2007 templates providing useful techniques for Marketing, Product and Steering committee actions as well as a template for meeting notes and financial information

17.  Request for Proposal
The Request for Proposal application template helps manage the process of creating and releasing an initial RFP, collecting submissions of proposals and formally accepting the selected proposal from amongst those submitted. The site also helps simplify the process of notifying individuals about the status of the RFP and submitted proposals.

18.  Sports League
The Sports League Site application template helps an intra-company league administrator manage a baseball league. The site tracks team information, players, captains and scheduled team activities such as games, practices and social events. Team members can enter in game results and perform analysis at a team, game or individual player level. The site also enables discussions between league members through a League Discussion board.

19.  Team Work Site
The Team Work Site application template provides a place where project teams can upload background documents, track scheduled calendar events and submit action items that result from team meetings. The site also tracks the creation and purpose of "sub-teams" as well as enables discussion of topics created by members of the team.

20. Timecard Management
The Timecard Management application template helps teams track hours spent working on various projects. The site enables team members to "punch in" on a particular project and "punch out" when they cease work. The system automatically generates the time worked by project, and can show managers who is working on a particular project, total hours versus budgeted time and the details of who worked on a each project entered into the site.

Downloads

• All 20 Site Admin templates                                                     (Available in English only)

• All 20 Server Admin Templates                                                (Available in Multiple languages)

• All 40 Application Templates as a single package download  (Available in English only)

Download the files and extract them to a folder on your local system say 'C:\Fab40' directory.

Listed below are the steps to install and deploy the WSPs and STPs to your SharePoint farm. Additionally, you can use the  commands to create a batch file that will help you expedite the installation and deployment of Server Admin and Site Admin Templates.

I have created a text file with the required set of commands for automating the installation and deployment of the templates. Change the file extension from ‘.txt’ to ‘.bat’ and then run the executable to complete the installation.

Install the Application Template Core Solution

1.      Before installing a server admin template, you must first download and install the Application Template Core solution called ApplicationTemplateCore.wsp.

2.      After downloading the solution, double click on the 'exe' to extract the files to a location on the server; e.g. 'C:\Fab40'

3.      Via command line, run "Stsadm -o addsolution -filename "C:\Fab40\ApplicationTemplateCore.wsp".

4.      Next, run "Stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment -immediate".

Note:

Additional attributes may be required based on your Windows SharePoint Services configuration like
Single Server:  [-local | -time <time to deploy at>]
Farm              :  [-immediate | -time <time to deploy at>]

To see the list of attributes, run Stsadm -help deploysolution or visit http://technet.microsoft.com/en-us/library/cc288449(office.12).aspx

5.      Run ‘Stsadm -o copyappbincontent‘

6.      To check the deployment status, browse to Central Administration > Operations tab > Solution management under Global Configuration. The solution(s) will be marked as Globally Deployed.

Install a template

1.      Download the template you want to install to the server.

2.      Double-click the .exe file to extract the files to a location on the server; e.g. 'C:\Fab40' .

3.      Via command line, run "Stsadm -o addsolution -filename "C:\Fab40\\<template_name>.wsp", where <template_name>.wsp is the .wsp file for your template.

4.      Next, run "Stsadm -o deploysolution -name <template_name>.wsp -allowgacdeployment"

Note:

Additional attributes may be required based on your Windows SharePoint Services configuration like
Single Server :  [-local | -time <time to deploy at>]
Farm              :  [-immediate | -time <time to deploy at>]

To see the list of attributes, run ‘Stsadm -help deploysolution’ or visit http://technet.microsoft.com/en-us/library/cc288449(office.12).aspx

5.      To check the deployment status, browse to Central Administration > Operations tab > Solution management under Global Configuration. The solution(s) will be marked as Globally Deployed.

6.      Run IISreset from the command line.

Using the new templates to create a new site

To create a new site, follow these steps

• From the Site Actions drop-down menu in the top right, select Site Settings.

• Under the Site Administration section, select 'Create Site' to create a new site using a site template.

• Complete the new SharePoint site information.
• In the Template Selection section, we will now have the new templates available under the “Application Templates” and “Custom” tabs.
• All deployed templates will be listed in this tab.
• Select the template to use for this site and click Create.

• A site will now be created using the chosen template.

Removing a template

This process will not remove any sites that were already created using the template. It will only prevent users from creating new sites based on the template. The Application Template Core solution must remain installed and deployed for other server admin templates to be installed.

1.      Removing a solution is done via the ‘Stsadm’ command line utility.

2.      To retract a solution from being available to SharePoint sites, run ‘Stsadm -o retractsolution -name <template_name>.wsp’ where <template_name>.wsp is the .wsp file for your template.

To see a list of optional attributes available with this command, run ‘Stsadm -help retractsolution’ or visit http://technet.microsoft.com/en-us/library/cc287669(office.12).aspx

3.      To remove a solution from the server, run ‘Stsadm -o deletesolution -name <template_name>.wsp’

To see a list of optional attributes available with this command, run ‘Stsadm -help deletesolution’ or visit http://technet.microsoft.com/en-us/library/cc288697(office.12).aspx

4.      The application template is now unavailable to SharePoint sites and the solution has been removed from the solution store.

Note:

You must be a Farm administrator to complete the installation and once you do these templates will be universally available. You will now have two new tabs called ‘Application Templates’ and ‘Custom’ under the ‘Template Selection’ section when you create a new site.

# Find the template name of SharePoint site using PowerShell
$web = Get-SPweb http://SiteUrl
Write-host “Web Template:” $web.WebTemplate ” | Web Template ID:” $web.WebTemplateId
$web.Dispose()

# To get a list of all web templates, use the following PowerShell code

function Get-SPWebTemplateWithId
{
     $templates = Get-SPWebTemplate | Sort-Object "Name"
     $templates | ForEach-Object {
    $templateValues = @{
     "Title" = $_.Title
     "Name" = $_.Name
     "ID" = $_.ID
     "Custom" = $_.Custom
     "LocaleId" = $_.LocaleId
      }

New-Object PSObject -Property $templateValues | Select @("Name","Title","LocaleId","Custom","ID")
      }
}

Get-SPWebTemplateWithId | Format-Table

Below is a list of the web templates and their IDs

Hope this helps.