Sharepoint 2013 Tutorials

https://technet.microsoft.com/en-us/office/dn756397.aspx
https://msdn.microsoft.com/en-us/library/office/fp142384.aspx

https://channel9.msdn.com/Events/Build/2013/3-603

Search not Indexing Webpart Content

Search not Indexing Webpart Content

Problem

You have a SharePoint 2010 farm.  You use unique permission settings in some sites for some pages and web parts.  You create new pages and content, using Dataview, Content, and other web parts.  You run a SharePoint 2010 Search crawl of the new content. You check the crawl and discover that the pages are being crawled, but discover that the new content is not being indexed. You investigate this further and find that all new content on all pages is not being crawled.

Solution

The problem likely involves the site settings Search and Offline Availability.  The setting can be found here:

Site Actions > Site Settings > Site Admin > Search and offline availability

By default, the Indexing ASPX Page Content setting is set to Do not index Web Parts if this site contains fine-grained permissions. OOTB, this settings causes no problems.  However, once you begin to implement unique permissions for some sites, such as for example, hiding content on some pages from some user groups, this setting becomes problematic.  Once unique permissions are implemented, the NOINDEX property is set for web parts.

The solution is simple: set the Search and offline availability setting to Always index all Web Parts on this site.  Then re-run the crawl.

References

• SharePoint 2010 Search : not showing any results for anonymous users?
• Search and offline Availability in SharePoint 2010

Article from:http://alstechtips.blogspot.in/2013/06/search-not-indexing-webpart-content.html

Sharepoint OnPremises VS O365

If you’re having a hard time selecting between Sharepoint On – Premises, and SharePoint online of Office 365, this next article is for you.

This article provides a basic overview of the primary differences between SharePoint Online and SharePoint On Premises. So let’s begin by taking a look at the different environments needed to run Online vs On Premises:

SharePoint Environments

As with any on-premise vs cloud based discussion, one of the most significant differences is the impact on internal resources. On-premise solutions require an internal IT support structure including people, hardware and software, or the use of a Managed Service Provider (MSP). Cloud based solutions reduce the dependency on internal resources and typically provide better globally deployed failover and redundancy features.

On Premises	Online
The SharePoint server farm is within the corporate network. The IT Support team maintains the SharePoint farm and regularly applies Microsoft patches and updates. On premise Active directory is used for authentication. Full access to use and customize any SharePoint feature as needed. Availability of Enterprise level services such as BCS, Performance Point, etc.	The SharePoint sites reside in the Microsoft Data Centre (MDC). Microsoft applies the patch regularly. Microsoft’s SLA ensures 99.9% availability. Microsoft’s global network of data centers provides reduced latency and high network bandwidth. Support for Client Side Object & App model.

Feature Comparisons

While the basic functionality of SharePoint remains the same, there are a number of significant feature differences between On Premises and Online:

Category	On Premises	Online
Cost Involved	Purchase/Maintain Hardware, Software licenses etc.	Annual subscriptions for Office 365 Plans billed on a per user basis.
Infrastructure deployment & maintenance	IT Support Team to deploy/manage farm, latest updates or patches not always deployed.	Microsoft manages the environment and ensures all updates and patches are deployed.
Business Continuity (BC)	Dependent on internal capabilities.	Microsoft built-in redundancy and failover for data centers, but does not provide end user backups or data recovery.
Product Features	Support for enterprise feature, Office web App (OWA) needs to be installed	Missing or limited features, pre-configured features
Customization Options	Full support for server side code and client side code, App usage from OAC and SAS	Full Support- Client Side, Limited Support-Server side, Can use Apps from OAC or SAS
Information Security	Dependent on internal capabilities.	Information in MDS meets industry-specific security standards
Compliance Standard	Dependent on internal capabilities.	Verified by third party authors
Storage needs	Expensive storage devices, Site Collection -More than 100GB, Scalable Storage Size	Cheap storage cost, Site Collection- up to 100Gb, Maximum content in single tenant -O365 plan based
Development	Full trust solution can be deployed- Features in farm solutions can have scope as wide as the site collection, web application, or whole farmPublic facing website with much of customization is possibleCustom “Managed Path” allowedMore control can be delegated to power users	Full trust solution cannot be deployed- Only Sandbox solutions possible with scope up to the site collection levelPublic facing website with much of customization is not possibleCustom “Managed Path” allowedMore control cannot be delegated to power users and maxim privilege level is Site Collection level.

Technical Comparisons

In addition to business features, there are differences in the technical features available to both options:

Services	Online	On Premises
Search	Limited access to query	Full text Query
InfoPath Form Services	Only in E3, E4 and K1 plans	Required License to use InfoPath Form Services
Claim Bases Authentication	N/A	Can use SQL , LDAP and AD authentication
Managed Accounts	N/A	Provides a Managed Account to user at access the SP Admin Services
Usage reporting and Logging	N/A	Provides LOGS and Reporting to check the exceptions and System Report.
Alternate Access Mapping	N/A	Provides a map requests where the URL of a Web request received by Internet Information Services (IIS) differs from the URL that was typed by a user
SharePoint Health Analyser	N/A	Site collection pre-upgrade health check examines a site collection and then generates a report listing ay potential upgrade issues and how to address the issues

Pros and Cons

SharePoint On Premises

Pros	Cons
Control Performance	Cost of internal resources (staff, hardware, software, etc)
Scale Up and Scale Out	Additional Geographic redundancy costs
Reduces Bandwidth requirements	Disaster Recovery dependent on internal capabilities
Fully Customizable	Scale Up/Out Cost( SW/HW)
Full Server and SQL Database	Patching Servers/farms
Migrate as Needed	Extra configurations for External Collaboration
Seamless Single Sign on with Corporate Active Directory

SharePoint Online

Pros	Cons
Uptime 99.99%	More ISP Bandwidth
Multiple Data centers	Limited Customizations
Geographically redundant	Possible Storage Costs
Shorted release cycle	Recovery SLAs
Managed Services ( SaaS)	No Server access
Pay as you go ( Low Cost )
Reduced impact on internal IT resources
Scalability

No matter which solution you decide on using: The one on premises or  SharePoint Online, you need to make sure you backup your data. No matter where your data is, you need a backup.

One thing is for sure: it’s much easier to backup cloud data using a third party solution which enables you to automatically backup your cloud data on a daily basis, and that is always accessible for you when you need it in case of data loss.

Read more about “how to backup SharePoint online” HERE.

 Article From :http://www.cloudally.com/sharepoint-on-premises-vs-sharepoint-online-2013/

Setup and Start the SharePoint 2013 User Profile Service (UPS)

Setup and Start the SharePoint 2013 User Profile Service (UPS)

Start the User Profile Service:

1. Open "Central Administration"
2. Login as the SharePoint Install account
   This account must have dbcreate and securityadmin server roles on the SQL Server  {SQL Server 2012 Name}
3. Click “Manage services on server”, under “System Settings”
   
4. Find "User Profile Service" 
5. Click "Start", on the right 
   

Create the User Profile Service (UPS) Application:

1. Open "Central Administration"
2. Click “Manage service applications”, under “Application Management”
   
3. Click "New"
   
4. Select "User Profile Service Application"
   
5. Fill in the related fields
   (If I haven't mentioned the field, it has the default settings)
   
   a.  Name:  User Profile Service
   b.  Application Pool:  Use existing application pool:  Shared Services
   
   c.  Profile Database:
        i.  Database Server:  {SQL Server 2012 Name}
        ii. Database Name:  {Database}_UserProfile
   
   d.  Synchronization Database:
        i.  Database Server:  {SQL Server 2012 Name}
        ii. Database Name:  {Database}_UserProfile_Sync
   
   e.  Social Tagging Database:
        i.  Database Server:  {SQL Server 2012 Name}
        ii. Database Name:   {Database}_UserProfile_Social  
   
   f.  Profile Synchronization Instance: {SharePoint Server Name} (default - current server)
   
   f.  My Sites. If you don't have, in this example we done, you can leave it blank, as default.
   
6. Click "Create"
   
7. Click "OK"
8. See full here: User Profile Service Application Settings

Start the User Profile Synchronization Service:

Make sure the SPFarm account has local admin access to the SharePoint Server the UPS synchronisation will be running on. This then needs to be removed once the synchronisation is complete.

1. Open "Central Administration"
2. Click “Manage services on server”, under “System Settings”
   
3. Find "User Profile Synchronization Service"
4. Click "Start", on the right
   
5. Fill in the Share Point Farm account
   
6. Click "OK" 

Reset the IIS:

1. Open "Command Prompt", as Administrator
2. Type and enter:  iisreset
   
3. Close "Command Prompt"

Create the Profile Synchronization Connection:

1. Open "Central Administration"
2. Click “Manage service applications”, under “Application Management”
   
3. Find and Select "User Profile Service"
   
4. Click "Configure Synchronization Connection", under Synchronization
   
5. Click "Create New Connection"
   
6. Fill in the related fields
   (If I haven't mentioned the field, i have left in the default settings.)
   
   a.  Connection Name:  User Profile Synchronisation
   b.  Forest name:  {DomainName.com} or {DomainName.local}
   c.  Account Name:  Share Point UPSync account
       This account must have "Directory replication rights" in AD (active directory)
   d.  Click "Populate Container"
   
   e.  Select the User Accounts you want to add
   f.  Click "OK"

Start the Profile Synchronization for the first time:

1. Open "Central Administration"
2. Click “Manage service applications”, under “Application Management”
   
3. Find and Select "User Profile Service"
   
4. Click "Start Profile Synchronization", under Synchronization
   
5. Select "Start Full Synchronization"
   
6. Click "OK"
   This will take a few minuets     
7. Source from http://jaxsharepoint.blogspot.in/2013/08/setup-and-start-sharepoint-2013-user.html