SharePoint 2013 Software Links

SharePoint 2013 Software Links!!

Windows Server 2012    : http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012
SharePoint Server 2013  : https://technet.microsoft.com/en-in/evalcenter/hh973397.aspx
SQL Server 2012 SP1    : http://www.microsoft.com/en-in/download/details.aspx?id=35575  (Click on Download and select  SQLServer2012SP1-FullSlipstream-ENU-x64.iso )
SharePoint Designer 2013   : http://www.microsoft.com/en-in/download/details.aspx?id=35491

Collection of SharePoint 2013 Power Point Presentations

Here is a good collection of Power Point presentations (Slide Decks) on various features of SharePoint 2013:

http://www.jstevensblog.com/post/Collection-of-SharePoint-2013-Power-Point-Presentations.aspx

Content Search Web Part in SharePoint 2013

Content Search Web Part in SharePoint 2013

Introduction:

The Content Search Web Part (CSWP) is a Web Part introduced in SharePoint 2013 that uses various styling options to display dynamic content on SharePoint pages.

How the Content Search Web Part works

Content Search Web Part displays search results in a way that you can easily format. Each Content Search Web Part is associated with a search query and shows the results for that search query.

You can use display templates to change how search results appear on the page. Display templates are snippets of HTML and JavaScript that render the information returned by SharePoint. The information to be displayed gets inserted into the page in JSON format.

When to use the Content Search Web Part (CSWP) or the Content Query Web Part (CQWP)

The CSWP can return any content from the search index. Use it on your SharePoint 2013 sites when you are connecting to a search service and want to return indexed search results in your pages.

The CSWP returns content that is as fresh as the latest crawl of your content, so if you crawl often, the content that the CSWP returns is more up-to-date than if you crawl infrequently. If you need to display instant content or the refreshed version of content, use the Content Query Web Part (CQWP) instead.

Search crawls only the major versions of content, never the minor versions. If you want to display the minor versions of your content, do that by using a CQWP.

Some site collection administrators mark sites to not be indexed. Content marked in this way is not available in a CSWP. If you want to return results from a site that is marked to not index, use the CQWP instead.

Update SharePoint 2010 Farm Credentials

In SharePoint 2010, for SharePoint single server install – a common task that you have to do is to update the SharePoint Farm credentials whenever the password changes.

                                                                                     

Below are the two simple steps to update Farm Credentials:

1. Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Bin folder using cmd.exe (open it as administrator).

2. Run this command using your credentials.

stsadm –o updatefarmcredentials –userlogin DOMAIN\username –password $password$

Example: stsadm -o updatefarmcredentials -Userlogin XXXXX\xxxxxx -password xxxxxxx

Note: Please type the whole command by your own including each and everything. Sometimes copy & paste leads to text encode.

Bug Fix:
If your SQL Server service is running under your windows credentials. Please make sure that credentials updated manually. Otherwise you will get below error.
Error: Value cannot be null. Parameter name: farm
Fix:
1) Just go to services.msc and change the sql server service password to your current windows password,

2) Restart the sql server service.
3) Run the above command.

SharePoint 2013 New Event Receivers In A Nutshell

As a Programmer, knowing how to utilize event receivers is a must have skill in your toolbox. In SharePoint 2013 there were 3 major changes to Event Receivers and 2 minor ones. This blog post is an overview of what’s new.

SharePoint Event Receiver Type Enumeration

The image below shows the progression of additions to the event receiver options in SharePoint. So far nothing has been deprecated, so each progressive release includes all the previous ones.

1. Remote Event Receivers
“Remote event receivers handle events that occur on an item in the app, such as a list, a list item, or a web. These events resemble those in a traditional SharePoint solution, except that they can work with the remote components of the app for SharePoint.” – http://msdn.microsoft.com/en-us/library/office/dn456315.aspx

Here are the key takeaways for remote events.

• They can only handle a subset of events which have been traditionally available.
• They are now available for Apps.
• Because they call an external web service, they are only available in Auto-hosted and Provider-hosted Apps. They do not work with SharePoint-hosted Apps.

2. App Event Receiver
Now that you are familiar with Remote Events, we can now discuss App Events. These special events allow developers some control during the App lifecycle process. They are raised in the following three instances.

1. After an App is installed.
2. After an App is upgraded.
3. While and App is uninstalling.

They are set in Visual Studio in the properties for the App, shown here.

3. Entity Instance Events
Basically this is an event receiver that gives you developer access to three events which occur when External Content Types (registered in BCS) are added, updated, or deleted. Unfortunately there is almost no information regarding this that I can find.

4. Security Event Receiver
I have briefly covered this topic before and now it is being discussed in the larger context of all the event receiver updates to SharePoint 2013. This server side only event receiver (SPSecurityEventReceiver) has received almost no fanfare since SharePoint 2013 was released. It can; however, be utilized in a variety of fashions that are extremely useful. The following are the list of events available to developers in theSPSecurityEventReceiver.

• GroupAdded – Specifies an event that occurs after a security group is added.
• GroupAdding – Specifies an event that occurs before a security group is added.
• GroupDeleted – Specifies an event that occurs after a security group is deleted.
• GroupDeleting – Specifies an event that occurs before a security group is deleted.
• GroupUpdated – Specifies an event that occurs after a security group is updated.
• GroupUpdating – Specifies an event that occurs before a security group is updated.
• GroupUserAdded – Specifies an event that occurs after a user is added to a security group.
• GroupUserAdding – Specifies an event that occurs before a user is added to a security group.
• GroupUserDeleted – Specifies an event that occurs after a user is deleted from a security group.
• GroupUserDeleting – Specifies an event that occurs before a user is deleted from a security group.
• InheritanceBreaking – Specifies an event that occurs before an inheritance is broken.
• InheritanceBroken – Specifies an event that occurs after an inheritance is broken.
• InheritanceReset – Specifies an event that occurs after the role inheritance is restored.
• InheritanceResetting – Specifies an event that occurs before the role inheritance is restored.
• RoleAssignmentAdded – Specifies an event that occurs after a role assignment is added.
• RoleAssignmentAdding – Specifies an event that occurs before a role assignment is added.
• RoleAssignmentDeleted – Specifies an event that occurs after a role assignment is deleted.
• RoleAssignmentDeleting – Specifies an event that occurs before a role assignment is deleted.
• RoleDefinitionAdded – Specifies an event that occurs after a role definition is added.
• RoleDefinitionAdding – Specifies an event that occurs before a role definition is added.
• RoleDefinitionDeleted – Specifies an event that occurs after a role definition is deleted.
• RoleDefinitionDeleting – Specifies an event that occurs before a role definition is deleted.
• RoleDefinitionUpdated – Specifies an event that occurs after a role definition is updated.
• RoleDefinitionUpdating – Specifies an event that occurs before a role definition is updated.

http://msdn.microsoft.com/en-us/library/sharepoint/microsoft.sharepoint.spsecurityeventreceiver_members.aspx

5. List Item Version Events
Lost in all this, is a small update to the SPItemEventReceiver class. There is now a way to handle events when an item or file version is deleted (ItemVersionDeleted) or is being deleted (ItemVersionDeleting). This can be helpful for records management or archival purposes.

Conclusion
The evolution of event receivers patterns the overall evolution of SharePoint itself. There are some “under the hood” (server side) enhancements but the biggest features are App related and cloud compatible. There are many positives to this evolution, my personal favorite is the emergence of the “bring your own web service” architecture. Please leave comments for discussion, any good links, or a reference for the Entity Instance events.

SharePoint Autohosted Application Model Retired>>microsoft trends

In SharePoint 2013, there are three types of application hosting models:

• SharePoint Hosted
• Provider Hosted
• Autohosted

The goal of the Autohosted app model was to provide an easy way for developers to provision Azure resources such as web sites and SQL databases when deploying their custom apps. 

As of Friday, Microsoft has discontinued the Autohosted app model.  The program will officially end June 30, 2014 and if you have developed an Autohosted app, you are encouraged to move it to a provider hosted app model instead.

Incidentally, If you look for information on MSDN on Autohosted apps, you’ll see the following error:

Building a SharePoint 2013 BI Environment Setup!!

http://blogs.lessthandot.com/index.php/datamgmt/dbadmin/mssqlserveradmin/sharepoint-2013-bi-part-1/
http://sharepointdemobuilds.codeplex.com/

Thanks,
Venkata

SharePoint 2013 Site Template ID List for PowerShell

When we are creating a new Site Collection or Web Application by PowerShell, we have the option to apply the Site Template Directly. However, for PowerShell to accept it, you must give it the Template ID (EX: #STS1). Here is the SharePoint 2013 Site Template ID List for PowerShell.

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	Records Center
OSRV#0	Shared Services Administration Site
PPSMASite#0	PerformancePoint
BICenterSite#0	Business Intelligence Center
SPS#0	SharePoint Portal Server Site
SPSPERS#0	SharePoint Portal Server Personal Space
SPSPERS#2	Storage And Social SharePoint Portal Server Personal Space
SPSPERS#3	Storage Only SharePoint Portal Server Personal Space
SPSPERS#4	Social Only SharePoint Portal Server Personal Space
SPSPERS#5	Empty SharePoint Portal Server Personal Space
SPSMSITE#0	Personalization Site
SPSTOC#0	Contents area Template
SPSTOPIC#0	Topic area template
SPSNEWS#0	News Site
CMSPUBLISHING#0	Publishing Site
BLANKINTERNET#0	Publishing Site
BLANKINTERNET#1	Press Releases Site
BLANKINTERNET#2	Publishing Site with Workflow
SPSNHOME#0	News Site
SPSSITES#0	Site Directory
SPSCOMMU#0	Community area template
SPSREPORTCENTER#0	Report Center
SPSPORTAL#0	Collaboration Portal
SRCHCEN#0	Enterprise Search Center
PROFILES#0	Profiles
BLANKINTERNETCONTAINER#0	Publishing Portal
SPSMSITEHOST#0	My Site Host
ENTERWIKI#0	Enterprise Wiki
PROJECTSITE#0	Project Site
PRODUCTCATALOG#0	Product Catalog
COMMUNITY#0	Community Site
COMMUNITYPORTAL#0	Community Portal
SRCHCENTERLITE#0	Basic Search Center
SRCHCENTERLITE#1	Basic Search Center
SRCHCENTERFAST#0	FAST Search Center
visprus#0	Visio Process Repository

Index of Windows PowerShell cmdlets for SharePoint 2013

List of PowerShell cmdlets for SharePoint 2013

http://technet.microsoft.com/library/ff678226%28office.15%29.aspx
 

An introduction to cross-site publishing>>SharePoint 2013

To build our Contoso website, we'll be using cross-site publishing, a new publishing method that's just been introduced with SharePoint Server 2013. Before we start however, let's get a bit more familiar with how cross-site publishing works.
Note: most of features described in this series are not available in SharePoint 2013 online.

What is cross-site publishing?
Cross-site publishing's a publishing method. It lets you create and maintain content in one or moreauthoring site collections, and publish this content across one or more publishing site collections, by using Search Web Parts.

When should you use cross-site publishing?
Use cross-site publishing when you want to store and maintain content in one or more authoring site collections and display this content in one or more publishing site collections. Cross-site publishing will make life easy for you as it:

• Can be used across site collections, web applications, and even across farms.
• Separates content authoring from branding and rendering, meaning how you author content has nothing to do with how it is displayed to users.
• Allows you to mix pages and catalog content.

How does cross-site publishing work?
Cross-site publishing uses search technology to retrieve content. Here's how it works in four simple steps:

1. You create content in libraries and lists in a site collection where cross-site publishing is enabled. You enable these libraries and lists as catalogs.
2. You crawl the content in your catalog-enabled libraries and lists. This will add the catalog content to the search index.
3. You add one or more Search Web Parts to the site collections where you want to display your catalog content.
4. When users view a page, the Search Web Parts issue queries to the search index. Query results are returned from the search index, and shown in the Search Web Parts.

When you decide to change content in an authoring site collection, the changes you make are shown across all publishing site collections that are using that same content.

You can also add search-driven features like faceted navigation, query rules and usage analytics, all of which we'll be talking about soon.

Configure Data Retrieval Service in SharePoint 2013

Configure Data Retrieval Service in SharePoint 2013

In SharePoint, Data retrieval service implements data-binding feature. This allows communicate data consumers and data sources. We can install/run data retrieval service in SharePoint running machines. SharePoint includes the default set of data retrieval services to work with SharePoint lists, OLEDB and XML data sources. Data bound webparts, Spread sheets can use data provider services to get the data from data sources. We can configure data retrieval settings in SharePoint Central Administration.

We can configure data retrieval settings in SharePoint 2013 by using following steps,

Navigate to Application Management in SharePoint central Administration and click on Configure the data retrieval service.

We'll navigate to Data Retrieval Service configuration page. In Configuration page, We have to choose the web application. To configure the settings for farm level, select "Global Settings" in web application drop down or we want to configure web application level, we can choose the web application. By default it is "Global Settings".

To enable the data retrieval service we have to check "Enable these data retrieval services" check box. 

We can specify the maximum number of kb's allowed in response from OLEDB data source in Response size limit box in Limit Response Size section. By default it is 10000.

By checking "Enable update query support" check box in Update Support section, queries will support for updating. We need to enter the number of seconds that the data retrieval service will wait to get a response from a data source in Data Source Time-out section Request Time out box. By default this value is 30 sec.

By checking "Enable these data source controls" check box in "Enable Data Source Controls" section we can enable the queries to the data source types. Click on Ok button to Save the configuration settings.