SharePointSupport

Out Of Box ( OOB ) Webparts These are the basic in-built components in SharePoint for displaying and managing list data without the need of any custom development. Not all of them will be available depending upon the version of SharePoint installed. List of OOB Webparts in SharePoint 2010 Following is the list of OOB webparts in SharePoint 2010 along with the category. List and Libraries Announcements – Use this list to track upcoming events, status updates or other team news Calendar – Use the Calendar list to keep informed of upcoming meetings, deadlines, and other important events Links - Use the Links list for links to Web pages that your team members will find interesting or useful Shared Documents – Share a document with the team by adding it to this document library Site Assets – Use this library to store files which are included on pages within this site, such as images on Wiki pages. Site Pages – Use this library to create and store pages on this site Ta

The 14 Hive - Folder Location The 14 Hive folder is located at the following path C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\14 The 14 Hive - Folder Structure The 14 Hive has a definite folder structure which holds the core SharePoint server files. ADMISAPI:- It contains soap services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly. Bin:- The directory contains all the core binary files, utilities which used by SharePoint Services.  command line tools such as STSADM.EXE also present in this folder. Config:- This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application will not function correctly. HCCab:- This directory has a set of cab files which has content information used by the SharePoint help system. Help:- The folder contains html help file (.chm

One of the new additions to Microsoft's SharePoint Server 2010 platform is the Chart Web Part (CWP), which allows you to create static and dynamic charts for your site without a line a code. One of the complaints from MOSS 2007 was that users wanted to be able to drop a chart onto their site to create dashboard or display information from Excel documents, or provide metrics to other users in a graphical way. So now that the Chart Web Part is available, let see how we can use it. To drop a Chart Web Part on your page, go to Site Actions > Edit Page. From there, click "Insert" from the Editing Tools menu. The "Chart Web Part" is available under the "Business Data" category, then you can click on the CWP option and add to a content area. Once added to the page, you will see "Data & Appearance" and "Advance Properties" options. There are a couple of ways you can go once you click the "Data & Appeara

One of the features of SharePoint that has been around is the ability for users that need access to a site, and are denied access, through the “Request Access” process . To enable or review these settings, * go to “ Settings ” > “ Site Settings ” > “ User and Permissions ” and click “ Access Request Settings ” . In the “ Access Request Settings ” dialog box, select the check box next to “ Allow access requests ” then provide an email address of the individual you’d like to manage this feature. * If a site has multiple groups with the same permission levels (Owners, Members and Viewers) but there is not an assigned default group, then you will see the problem where access requests will either not display for the impacted user or an owner will not be able to approve requests. Here’s a Windows PowerShell script to change each of the groups for a site so that each is identified as the default group for Members, Owners and Visitors You’ll need to a the “ Microsoft.S

* Recently, I was asked exactly how the Site Confirmation and Deletion feature works in SharePoint? * Does the timer restart when a user visits the site? * Does the feature look at the some field and then reset the value in a service?  It was a simple question that made me think about how the process worked from an Administrator     point-of-view. * The simple answer is that once a user adds content to a site, a field in a content database is updated and then when a timer job is run, it will review that field and notify site owners appropriately to ensure that they are notified that their site is on “the chopping block”. * Based on your configuration, it will notify you after 90 days (by default) of site collection creation or confirmed use. You can change the amount of notifications sent or you can automatically delete the site collection if use is not confirmed after 28 notices. To access this feature, go to Central Administration > Site Collections > Site U

* If you want to expose the same content in a Web application to different types of users by using additional URLs or authentication methods , you can extend an existing Web application into a new zone. * When you extend the Web application into a new zone, you create a separate Internet Information Services (IIS) Web site to serve the same content, but with a unique URL and authentication type . * An extended Web application can use up to five network zones (Default, Intranet, Internet, Custom, and Extranet). For example, if you want to extend a Web application so that customers can access content from the Internet, you select the Internet zone and choose to allow anonymous access and grant anonymous users read-only permissions. Customers can then access the same Web application as internal users, but through different URLs and authentication settings. For more information, see Logical architecture components (SharePoint Server 2010) , Configure anonymous access for a cla

Intro to Host Name Site Collections (HNSC) * Host Name Site Collections are the answer to simplifying and consolidating SharePoint Farm/s.   Let’s assume a SharePoint Farm has 5 web applications each mapped to a unique application pool.   While this gives you a nice separation for security purposes, it adds unnecessary strain on each WFE.   E ach time an application pool is spun up, it must load all of the assemblies from memory.  * So in this case, each WFE is consuming 5x memory right off the bat.   The costs increase by having to procure beefy machines with lots of memory to support this requirement. * For many of our customers, this led to many multifarm environments due to hitting a cap in physical memory.   Also as you’ve experienced, the sheer # of web applications can lead to long patching cycles with PSConfig . * By consolidating web applications, your essentially cutting operations costs (faster patching times) and reducing infrastructure costs (additiona

You may have noticed that the hardware requirements for SharePoint 2013 Server are quite hefty. Many SharePoint 2013 performance issues have been attributed to lack of resources.  Although meeting the minimum performance specs is highly recommended, you can tweak SharePoint 2013 to work with less resources. The following tips are some that I have collected while looking for ways to improve SharePoint 2013 performance. Some of these will help SharePoint’s performance however, my experience has been that unless you have a server that meets the minimum SharePoint 2013 requirements, the Search function will still bring your SharePoint server to a crawl. The only way that I have been able to run SharePoint efficiently on a less than ideal server is to completely disable the search feature . If however, you want to try and tweak SharePoint before completely turning off the search service, be aware that performance results will vary depending on your server’s RAM and CPU speed

UI Customization Recommendation:     Don’t alter SharePoint master pages and basic structure of aspx pages     Don’t modify default CSS file but user can attach new custom CSS and make changes accordingly     Users can create html pages as special landing pages. Example for special drives     Modification can perform at CSS file, not at source code     Users can change design Theme, Color, Font style, Background etc. Other SharePoint Development customization Recommendation:     Code Customization shall be done using Sandbox solutions     Platform Don’t prefer to have Business Data Connection based solutions, however support will be provided on need basis     Performance Point solutions are not supported     Infopath forms can be used but KM team support will not be available for Customization and maintenance/migrations     Default form size will not be changed     List and Libraries shall not have more than 5000 records in single view. Alternatively, create logical folders in such a

I recently ran across an interesting issue where InfoPath forms were calling OOB SharePoint 2010 web services. In particular, these forms contained one or more fields which called SharePoint OOB web service. These forms were published to web applications configured with Claims Authentication . Opening this form works fine as long as you open the form using InfoPath on the client. When attempting to view the form in the browser the following error occurs: Subsequently, you will see an error like the following in the ULS logs: The following query failed: GetUserProfileByName (User: 0e.t|exo-sts|user1@consoto.com, Form Name: otherForm, IP: , Connection Target: , Request: http://wfe1.contoso.com/_layouts/FormServer.aspx?XsnLocation=https://wfe1.contoso.com/sites/siteA/FormServerTemplates/IT WAR.xsn&SaveLocation= https://wfe1.contoso.com/sites/siteA/ITWARdir&ClientInstalled=t=1 , Form ID: urn:schemas-microsoft-com:office:infopath:FormLib:-myXSD-2012-07-12T16-05-43