SharePointSupport

In this article we learn how to configure a user profile and My Site configuration in SharePoint 2013. In earlier versions of SharePoint, each user had a profile and a personal site (e.g., My Site). The 2013 version of SharePoint splits My Site into three sections: Newsfeed, SkyDrive, and Sites. A global navigation bar provides access to each section. These social features are tightly integrated into SharePoint 2013, so you no longer need to launch a web browser to access them. Use the following procedure to create a My Site Host site collection:     1. Verify that the user account that is performing this procedure has the following credentials:         The user account that performs this procedure is a farm administrator         The user account that performs this procedure is a member of the Administrators group on the computer that is running SharePoint Server.         2. First we have to create a web application for My Site; see: 3. On Central Ad

 Why Apps? For far too long both IT Pros and Developers have relied solely on full trust solutions, whether speaking about SharePoint or another platform.  Having full trust to the box at all times just isn’t the way we want to do things nowadays!  As we all know, the flexibility of full trust solutions makes for unpredictability of a platform.  That model can make IT Pros feel like their fate is in the hands of the developers and often require them to clean up the mess come upgrade time or after an outage.  I’ve lost count of the number of times I’ve been onsite for critical situations (a.k.a. critsits) involving custom code and memory leaks.  Of course we shouldn’t tarnish all developers with that brush.  Furthermore, full trust solutions are unfeasible on a hosted platform such as Office 365 . SharePoint 2010 took a step in the right direction with sandboxed solutions.  Sandboxed solutions provided a way to isolate code execution in both on-premis

There are many great articles that talks about how to configure your SharePoint 2013 farm for apps development . At the end of this article I will list a lot of these great references. I’m going to try to summarize the important things you need to know and also cover few FAQs along the way. First of all, you need to know that there are two main types of SharePoint apps you can develop on prim in your local SharePoint 2013 farm: SharePoint hosted apps SharePoint provider hosted apps The third type SharePoint Auto hosted (Azure auto hosted apps) is only available on SharePoint online tenants part of Office 365 . Also it’s important to note that if you plan to publish your SharePoint app into the SharePoint store to make some money the above mentioned types (Hosted & provider hosted) are the only allowed ones as long as they don’t request full control permission. For more details about the submission requirements check this link . In order to make your SharePoint 20

Template ID Title GLOBAL#0 Global template STS#0 Team Site STS#1 Blank Site STS#2 Document Workspace MPS#0 Basic Meeting Workspace MPS#1 Blank Meeting Workspace MPS#2 Decision Meeting Workspace MPS#3 Social Meeting Workspace MPS#4 Multipage Meeting Workspace CENTRALADMIN#0 Central Admin Site WIKI#0 Wiki Site BLOG#0 Blog SGS#0 Group Work Site TENANTADMIN#0 Tenant Admin Site APP#0 App Template APPCATALOG#0 App Catalog Site ACCSRV#0 Access Services Site ACCSRV#1 Assets Web Database ACCSRV#3 Charitable Contributions Web Database ACCSRV#4 Contacts Web Database ACCSRV#5 Projects Web Database ACCSRV#6 Issues Web Database ACCSVC#0 Access Services Site Internal ACCSVC#1 Access Services Site BDR#0 Document Center DEV#0 Developer Site DOCMARKETPLACESITE#0 Academic Library EDISC#0 eDiscovery Center EDISC#1 eDiscovery Case OFFILE#0 (obsolete) Records Center OFFILE#1 Rec

What is the search schema? The search schema is a mechanism in SharePoint search that controls: Which aspects (properties) of items are to be indexed How and with what indexing structures particular pieces of data are indexed Which aliases can be used when querying using property restrictions What does this mean really? It means that the search schema controls  what  can be searched for,  how  it can be searched for and  how  the results can be presented in your search sites. Main schema concepts The most important concepts in search schema are  crawled properties  and  managed properties . The typical data flow is illustrated by this figure: So a crawl component reads items from the content database (or other content sources) and sends documents and metadata to the content processing component in the form of  crawled properties . A lot of magic then happens inside the content processing component: the text of the item is extracted, language detected, spell-checkin