What is sharepoint 2013 on premise and online

HI
what is sharepoint 2013 on premise and online
what is the concept in onpremises
adil

This is really basic stuff, have you searched for it at all? There is, quite literally, hundreds of articles on this such as:
http://redmondmag.com/articles/2013/04/01/key-piece.aspx
SharePoint On-Premises is where you own the servers and install SharePoint on them and manage it. SharePoint online is where Microsoft own and run the hardware and give you a section of it to use.

Similar Messages

ADFS SSO and SharePoint 2013 on-premise Hybrid outbound search results from SharePoint Online - does it work?

Hi,
I want to setup an outpund hybrid search for SharePoint 2013 on-premise to SharePoint Online.
But I'm not shure if this works with ADFS SSO.
Has somebody experience with this setup?
Here's my guide which I'm going to use for this installation:
Introduction
In this post I'll show you how to get search results from your SharePoint Online in your SharePoint 2013 on-premise search center.
Requirements
User synchronisation ActiveDirectory to Office 365 with DirSync
DirSync password sync or ADFS SSO
SharePoint Online
SharePoint 2013 on-premise
Enterprise Search service
SharePoint Online Management Shell
Instructions
All configuration will be done either in the Search Administration of the Central Administration or in the PowerShell console of your on-premise SharePoint 2013 server.
Set up Sever to Server Trust
Export certificates
To create a server to server trust we need two certificates.
[certificate name].pfx: In order to replace the STS certificate, the certificate is needed in Personal Information Exchange (PFX) format including the private key.
[certificate name].cer: In order to set up a trust with Office 365 and Windows Azure ACS, the certificate is needed in CER Base64 format.
First launch the Internet Information Services (IIS) Manager
Select your SharePoint web server and double-click Server Certificates
In the Actions pane, click Create Self-Signed Certificate
Enter a name for the certificate and save it with OK
To export the new certificate in the Pfx format select it and click Export in the Actions pane
Fill the fields and click OK Export to: C:\[certificate
name].pfx Password: [password]
Also we need to export the certificate in the CER Base64 format. For that purpose make a right-click on the certificate select it and click on View...
Click the Details tab and then click Copy to File
On the Welcome to the Certificate Export Wizard page, click Next
On the Export Private Key page, click Next
On the Export File Format page, click Base-64 encoded X.509 (.CER), and then click Next.
As file name enter C:\[certificate
name].cer and then click Next
Finish the export
Import the new STS (SharePoint Token Service) certificate
Let's update the certificate on the STS. Configure and run the PowerShell script below on your SharePoint server.
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
$X64CertPath = "c:\[certificate name].cer"
# get the encrypted pfx certificate object
$PfxCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# import it
Set-SPSecurityTokenServiceConfig -ImportSigningCertificate $PfxCert
Type Yes when prompted with the following message.
You are about to change the signing certificate for the Security Token Service. Changing the certificate to an invalid, inaccessible or non-existent certificate will cause your SharePoint installation to stop functioning. Refer
to the following article for instructions on how to change this certificate: http://go.microsoft.com/fwlink/?LinkID=178475. Are you
sure, you want to continue?
Restart IIS so STS picks up the new certificate.
& iisreset
& net stop SPTimerV4
& net start SPTimerV4
Now validate the certificate replacement by running several PowerShell commands and compare their outputs.
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
# get the encrypted pfx certificate object
New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# compare the output above with this output
(Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
[/code]
## Establish the server to server trust
[code lang="ps"]
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
Import-Module MSOnline
Import-Module MSOnlineExtended
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
$X64CertPath = "c:\[certificate name].cer"
# set the onpremise domain that you added to Office 365
$SPCN = "sharepoint.domain.com"
# your onpremise SharePoint site url
$SPSite="http://sharepoint"
# don't change this value
$SPOAppID="00000003-0000-0ff1-ce00-000000000000"
# get the encrypted pfx certificate object
$PfxCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# get the raw data
$PfxCertBin = $PfxCert.GetRawCertData()
# create a new certificate object
$X64Cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2
# import the base 64 encoded certificate
$X64Cert.Import($X64CertPath)
# get the raw data
$X64CertBin = $X64Cert.GetRawCertData()
# save base 64 string in variable
$CredValue = [System.Convert]::ToBase64String($X64CertBin)
# connect to office 3656
Connect-MsolService
# register the on-premise STS as service principal in Office 365
# add a new service principal
New-MsolServicePrincipalCredential -AppPrincipalId $SPOAppID -Type asymmetric -Usage Verify -Value $CredValue
$MsolServicePrincipal = Get-MsolServicePrincipal -AppPrincipalId $SPOAppID
$SPServicePrincipalNames = $MsolServicePrincipal.ServicePrincipalNames
$SPServicePrincipalNames.Add("$SPOAppID/$SPCN")
Set-MsolServicePrincipal -AppPrincipalId $SPOAppID -ServicePrincipalNames $SPServicePrincipalNames
# get the online name identifier
$MsolCompanyInformationID = (Get-MsolCompanyInformation).ObjectID
$MsolServicePrincipalID = (Get-MsolServicePrincipal -ServicePrincipalName $SPOAppID).ObjectID
$MsolNameIdentifier = "$MsolServicePrincipalID@$MsolCompanyInformationID"
# establish the trust from on-premise with ACS (Azure Control Service)
# add a new authenticatio realm
$SPSite = Get-SPSite $SPSite
$SPAppPrincipal = Register-SPAppPrincipal -site $SPSite.rootweb -nameIdentifier $MsolNameIdentifier -displayName "SharePoint Online"
Set-SPAuthenticationRealm -realm $MsolServicePrincipalID
# register the ACS application proxy and token issuer
New-SPAzureAccessControlServiceApplicationProxy -Name "ACS" -MetadataServiceEndpointUri "https://accounts.accesscontrol.windows.net/metadata/json/1/" -DefaultProxyGroup
New-SPTrustedSecurityTokenIssuer -MetadataEndpoint "https://accounts.accesscontrol.windows.net/metadata/json/1/" -IsTrustBroker -Name "ACS"
Add a new result source
To get search results from SharePoint Online we have to add a new result source. Run the following script in a PowerShell ISE session on your SharePoint 2013 on-premise server. Don't forget to update the settings region
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
# region settings
$RemoteSharePointUrl = "http://[example].sharepoint.com"
$ResultSourceName = "SharePoint Online"
$QueryTransform = "{searchTerms}"
$Provier = "SharePoint-Remoteanbieter"
# region settings end
$SPEnterpriseSearchServiceApplication = Get-SPEnterpriseSearchServiceApplication
$FederationManager = New-Object Microsoft.Office.Server.Search.Administration.Query.FederationManager($SPEnterpriseSearchServiceApplication)
$SPEnterpriseSearchOwner = Get-SPEnterpriseSearchOwner -Level Ssa
$ResultSource = $FederationManager.GetSourceByName($ResultSourceName, $SPEnterpriseSearchOwner)
if(!$ResultSource){
Write-Host "Result source does not exist. Creating..."
$ResultSource = $FederationManager.CreateSource($SPEnterpriseSearchOwner)
$ResultSource.Name = $ResultSourceName
$ResultSource.ProviderId = $FederationManager.ListProviders()[$Provier].Id
$ResultSource.ConnectionUrlTemplate = $RemoteSharePointUrl
$ResultSource.CreateQueryTransform($QueryTransform)
$ResultSource.Commit()
Add a new query rule
In the Search Administration click on Query Rules
Select Local SharePoint as Result Source
Click New Query Rule
Enter a Rule name f.g. Search results from SharePoint Online
Expand the Context section
Under Query is performed on these sources click on Add Source
Select your SharePoint Online result source
In the Query Conditions section click on Remove Condition
In the Actions section click on Add Result Block
As title enter Results for "{subjectTerms}" from SharePoint Online
In the Search this Source dropdown select your SharePoint Online result source
Select 3 in the Items dropdown
Expand the Settings section and select "More" link goes to the following URL
In the box below enter this Url https://[example].sharepoint.com/search/pages/results.aspx?k={subjectTerms}
Select This block is always shown above core results and click the OK button
Save the new query rule

Hi Janik,
According to your description, my understanding is that you want to display hybrid search results in SharePoint Server 2013.
For achieving your demand, please have a look at the article:
http://technet.microsoft.com/en-us/library/dn197173(v=office.15).aspx
If you are using single sign-on (SSO) authentication, it is important to test hybrid Search functionality by using federated user accounts. Native Office 365 user accounts and Active Directory Domain Services
(AD DS) accounts that are not federated are not recognized by both directory services. Therefore, they cannot authenticate using SSO, and cannot be granted permissions to resources in both deployments. For more information, see Accounts
needed for hybrid configuration and testing.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Sharepoint 2013 on premises Tags & Notes button in List and Document library is disabled.

Hi,
In My Sharepoint 2013 on premises installation Tags & Notes button in List and Document library ribbon is appearing as greyed out.
I have checked that managed metadata service, User profile services are running. Also have given required permissions to the logged in user.
As I came to know that Tags & Notes feature has been retired in Sharepoint online. Is this happening because of same reason as I have downloaded the Sharepoint 2013 on premises version recently or do I need to change some settings.
Please advice.

Hi Saurav,
pls check below
What version of SharePoint 2010 "SP 2010 Foundation or SP 2010 Server" you need to have SP 2010 server and to have the "User Profile service application".
How do you configure the "User Profile service application" did you add the "Social Tagging Database"
Create, edit, or delete a User Profile service application (SharePoint Server 2010)"
http://technet.microsoft.com/en-us/library/ee721052.aspx
When you access to "Application Management>Manage service applications>User Profile Service Application>Manage User Permissions" validate if the all authenticated users Group have the "use Social Features" checked.
Also validate in Central Administration in Farm Features if you have social tags and notes activated.
http://sharepoint.stackexchange.com/questions/17546/tagging-feature-not-working
https://social.technet.microsoft.com/Forums/office/en-US/c11cda96-091b-4b96-91bc-ccd8000238f4/tags-and-notes-sharepoint-2010-not-visible?forum=sharepointadminprevious
Please remember to click 'Mark as Answer' on the answer if it helps you

Cannot share documents between On-Premises and Online Users by email invitation

We have a hybrid setup, no problems with email communications between on-premises and Microsoft Online users. We have also activated online Onedrive/sharepoint to start testing. One interesting thing is that users Online can share their documents by inviting
users who are on Microsoft Online, On-premises and outside this two systems. But the problem is with the users who are on-premises cannot share their documents by email invitation with the other users who are also on-premises, they can share the documents
with the users who are online only. When they try to share documents by email invitation they get error messages it their emailboxes saying that;
A communication failure occurred during the delivery of this message. Please try resending the message later. If the problem continues, contact your helpdesk.
Generating server: SMT947322-001.YLO001.MSOPRD.MSFT.NET
#< #5.5.0 smtp;550 Denied by policy> #SMTP#
It seems some kind of relay should be granted on my CAS servers or something like that but I am not sure of what should be added. I am just stuck as to what next step and where to start looking for the problem
Exchange 2010/2013 with Microsoft Online Office 365 Hybrid

No, just wanted to share documents using the invitation by mail in sharepoint/onedrive. We can share the documents normally without the email notification. Sorry to mention that even the users who are Online cannot share documents in sharepoint/onedrive
between themselves, so not between user on-premises and online users. For example a user selects a document in the library, click share and tick on by email, just gets an error
"#< #5.5.0 smtp;550 Denied by policy> #" , No RMS enabled yet.
Hi,
Sorry for my delay.
According to your further posting, the sending Denied cause is No RMS enabled yet. If that is the case, please activate Azure Rights Management (RMS) to check whether the issue persits.
When you activate Azure Rights Management (RMS), you turn on this feature for all rights-enabled services and applications. You must activate Rights Management before you can begin to use the information rights management (IRM) features within Office, SharePoint,
and Exchange. For details about how to activate RMS, please refer to:
http://technet.microsoft.com/en-us/library/jj658941.aspx
Regards,
Winnie Liang
TechNet Community Support

SharePoint 2013 on premises vs Microsoft Azure Cloud Migration

Hi All,
we do have SharePoint 2010 on premises environment and now company wants to upgrade it to SharePoint 2013.
what is best way to approach means should we migrate SharePoint 2010 to on premises SharePoint 2013 environment or to Microsoft azure cloud?
if we do Microsoft azure then what are pron and cons about using azure cloud for SharePoint 2013 environment ?
if you say not to use Microsoft azure then why should we use SharePoint 2013 on premises environment?
Thanks ,,,
Deepak Patel

Azure, one of the larger cons is disk performance. Compared to on-premises, disk performance may not be enough without going to a higher level of VM (e.g. G series), which can turn out to be $1000+/month.
In addition, you'll need to establish a Site-to-Site VPN or leverage ExpressRoute to Azure in order to extend Active Directory to your SharePoint servers (for the servers and for your Active Directory users). You'll also need to consider adding one or more
Domain Controllers in Azure in order to have performant People Picker performance as well as Active Directory authentication for end users.
On-premises, these costs may be significantly reduced when spread out over a 3 - 4 year depreciation schedule, specifically for hardware.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Steps to configure Information Rights Management in SharePoint 2013 On-Premise

Hi,
What are the steps to configure Information Rights Managment [IRM] on SharePoint 2013 On-Premise.
Regards,

2. PHases
1. you will have to configure a IRM server
2. You will have to integrate IRM iwth sp server.
Below article should explain all
http://msmvps.com/blogs/ivansanders/archive/2012/06/08/check-out-the-weather-forecast-for-teched-2012.aspx

Add SharePoint 2013 On-Premise to Add a Place in Office 2013

We are in the process of rolling out SharePoint 2013 on-premise to all users in our organization. As part the roll-out we are also upgrading users to Office 2013. Unfortunately, we have difficulty explaining to users how to Save As to SharePoint the first
time. Until a user saves to SharePoint the first time this option is not available from the Save As screen. Per the post here:
http://social.technet.microsoft.com/Forums/office/en-US/12a2fd07-a5db-4637-b4bd-ed9711542ea3/option-save-as-sharepoint-missing-in-office-2013?forum=officesetupdeploy
The "solution" is to have a user open an existing file and save back to SharePoint. This is all well and good if there is content to access unfortunately this is not a manageable process for new users on a blank site. Is it possible to Add an entry
through GPO, GPP, or directly to the registry to provide the Save to SharePoint, Save to Network Location or alternatively to the Add a Place options?
I understand that Microsoft is pushing for everyone to move to the cloud but this user experience between two Microsoft products (Office and SharePoint) is extremely cumbersome. I appreciate any assistance anyone can provide. Thank you.

did you check this link:
http://social.technet.microsoft.com/Forums/office/en-US/54ab0283-de8e-474a-9381-96044369f37a/office-2013-default-save-location-group-policy?forum=officeitpro
Other option i am thinking,
Map a Drive to SharePoint site and then set that location as default location. May be this work.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Provider hosted app installed on SharePoint 2013 on premises is returning internal 500 error !

Hello,
I have deployed the basic provider hosted app on sharepoint 2013 on premises.
However when I try to run the app, its throwing an error on following as mentioned in screen:
It seems an authentication issue, would you please tell me how can I resolve it ?
Thank you in advance.
Kind Regards,
Dipti Chhatrapati

Hi,
According to your description, my understanding is that when you run provider hosted app in SharePoint 2013 on premise, the app occurs internal 500 error.
For using Managed .NET Client Object Model in Provider hosted app, it will need
TokenHelper.cs to get the ClientContext object like below:
private void RetrieveWithCSOM(string accessToken)
if (IsPostBack)
sharepointUrl = new Uri(Request.QueryString["SPHostUrl"]);
ClientContext clientContext =
TokenHelper.GetClientContextWithAccessToken(
sharepointUrl.ToString(), accessToken);
//Load the properties for the web object.
Web web = clientContext.Web;
clientContext.Load(web);
clientContext.ExecuteQuery();
//Get the site name.
siteName = web.Title;
//Get the current user.
clientContext.Load(web.CurrentUser);
clientContext.ExecuteQuery();
currentUser = clientContext.Web.CurrentUser.LoginName;
//Load the lists from the Web object.
ListCollection lists = web.Lists;
clientContext.Load<ListCollection>(lists);
clientContext.ExecuteQuery();
//Load the current users from the Web object.
UserCollection users = web.SiteUsers;
clientContext.Load<UserCollection>(users);
clientContext.ExecuteQuery();
foreach (User siteUser in users)
listOfUsers.Add(siteUser.LoginName);
foreach (List list in lists)
listOfLists.Add(list.Title);
More information:
https://msdn.microsoft.com/en-us/library/office/fp142381.aspx
Thanks
Best Regards,
Jerry Guo
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint 2013 On premises provider hosted app - Logged in user info

As per my understanding, following scenario is not possible in a provided hosted app deployed for SharePoint 2013 on-premises.
1) User clicks the button of app on a SharePoint Site. Remote Web app page opens
2) Remote app page shows the message "Welcome [User Name]" (without authenticating user again)
3) If that user has contributor permissions in originating SharePoint site, the app should display "Welcome Contributor" otherwise it should display "Welcome Visitor"
Please let me know if above functionality could be achieved?
Hammad Arif EPM Advice Blog

Hi,
According to your description,my understanding is that you want to show user information when clicking the app without asking credentials .
By default, SharePoint Provider hosted app is hosted outside SharePoint web application, so it needs credentials to get OAuth.
I suggest you can use SharePoint hosted app, it hosted at the same web application as SharePoint, then when you click the app, it will get the current logged in user without without asking credentials.
Here are some detailed articles for your reference:
Choose patterns for developing and hosting your app for SharePoint
How to: Create a basic SharePoint-hosted app
How to Check User permission for the web, list or SharePoint Item in SharePoint JavaScript Object Model
Thanks
Best Regards,
Jerry Guo
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Best logging option for SharePoint 2013 on-premise application

What is the best logging option for SharePoint 2013 on-premise application?

Hi,
According to your post, my understanding is that you want to know the logging option in SharePoint 2013.
SharePoint has its own logging system called “Unified Logging System (ULS)“, we can use the ULS log to see if anything unexpected occurred, we can use the
ULSViewer for more convenient log viewing experience.
Or we can log information programmatically.
There are some logging classes can be used, such as
SPMonitoredScope , SPDiagnosticsService, or create your own “Diagnostics Service” – which is technically just a new class inherited
from SPDiagnosticsServiceBase.
We can also utilize diagnostics.asmx web service for the client side applications.
For more reference:
http://www.codeproject.com/Articles/620996/Five-suggestions-to-implement-a-better-logging-in
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Network Load Balancing between SharePoint 2013 App server and WFE

Hi,
Can we do NLB between SharePoint 2013 App server and WFE Server ?
Below is our Architecture,
1. WFE Server (1)
2. APP Server (1)
3. Database Server
4. Domain Controller
We have configured NLB but, when we stop IIS on APP server, SharePoint 2013 web app link is not working.
is it possible ?
Please help us

You can do NLB between WFE and APP server however make sure that web application service is started from central admin which host sharepoint sites.
Why do you stop IIS on APP server, definitely it will not be able to host web app sites. rather you can just disable APP node on NLB to test it.

How to view and restore sharepoint 2013 designer workflows and how to redeploy with newer version to environments

how to view and restore sharepoint 2013 designer workflows and how to redeploy with newer version to environments
MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

Hi,
In SharePoint Designer 2010, we could not save the workflow as a template directly except the reusable workflow.
However, in SharePoint Designer 2013, we can just save all the types workflow as a template, then you can import the workflow into the new environment.
http://blogs.msdn.com/b/workflows_for_product_catalogs/archive/2012/11/02/deploying-a-workflow-on-a-different-server.aspx
In SharePoint Designer 2013, every time we publish the workflow, we would get a newer version workflow, and the old workflow version would be overwritten.
So, when you deploy the workflow in the environment, the workflow would the newer version.
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Conditional formatting and extensibility in Power View for SharePoint 2013 on-premises

Good day,
Is there a way we could apply conditional formatting in table objects, specifically at cell level (green, yellow and red) to a Power View dashboard in SharePoint 2013?
If not, is there a way to extend Power View to support these requirements. I know that SSRS and PowerPivot provide a wide range of customization tools, unfortunately so far the only customization capabilities that I've found in Power View are themes , fonts
and backgrounds but nothing that could allow this level of formatting. What are the available options, only SSRS and PowerPivot?
Thanks in advance for your help,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hi Marcelo,
As you know, generally themes , fonts and backgrounds are supportted in power view, more details information:Format Power View reports
Currently, there is no way to extend Power View to support these requirements. I recommend you to submit
an wish at https://connect.microsoft.com/SQLServer/
If the suggestion mentioned by customers for many times, the product team may consider to add the feature in the next SQL Server version. Your feedback is valuable for us to improve our products and increase the level of service
provided.
Thanks for your understanding.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

SharePoint 2013 - On Premise App model Configuration

Hi,
configuring App Service on-Premise SharePoint 2013.
difficulty in AppDomain-which I am deploying both Certificates on same server VM - but the urls are not working even for the original websites.
I having two wild Card certificates.
1st-which is domain ( contoso.com ) and
2nd-subdomain ( apps.contoso.com)
Can any suggestion /-

What changes you did in order to browse the issue
1. You need to have IISbinding with URL and select certificate for both web applications
2. Update the proper URL in AAM
3. Make sure all certificate and its sub certificates are installed on all SP servers
4. Check if you are able to ping the URL. Perform a NSlookup as well
If this helped you resolve your issue, please mark it Answered

SharePoint 2013 On-Premises - Search not crawling Korean content, but all other languages

We are facing an issue in a SharePoint 2013 site where I have lots of PPT files with different languages and also managed metadata tags tagged with them.
We are facing issue with Korean content PPT files where We are not able to search these files by their managed properties. Somehow SharePoint search is not able to crawl these Korean content PPT files with managed properties.
if we remove content from these files and do a crawl and search the file with managed property we get the result but if I put a small paragraph of Korean language and do the crawl it doesn't appear in search results with same query after the crawl.
Following are the server and site configuration details we are using:
Windows Server 2012 standard with SharePoint 2013 Enterprise Server installation
All our tags and managed properties are in English language only.
We are using SharePoint search API where I am passing query to SharePoint to fetch the result for example below is the query we are sending:
Ex.
( parentlink:"site URL*”)AND ( owstaxIdLanguage:"Korean"))
Following is the search result with different scenarios
Content in PPT file
Search using
Result
English
File name in search box
Worked
English
Using managed property
Worked
Korean
File name in search box
Sometimes works
Korean
Using managed property
No result
Following are the list of scenarios we tried to fix the Korean content issue:
Did a full crawl on all libraries multiple times
Did a full crawl on individual libraries
Changed library level settings to allow items to appear in search result, followed by a full crawl on individual library
Tried changing font for Korean content to generic font (Arial Unicode MS) per suggested by our PPT expert and crawled the content.
Installed Korean language pack on CM2 server and did a full crawl after uploading Korean content PPTs on UAT site

http://social.technet.microsoft.com/Forums/exchange/en-US/ec9febf7-8d69-42e9-b2dc-b6e5b0b46a89/sharepoint-2013-search-crawl-not-working-properly-with-korean-content?forum=sharepointsearch
Enabled "Always index all Web Parts on this site" in site settings > site visibility
Do we see some error in crawl logs in search
Is it a variation site? If yes, was the managed property data manually updated or it was done by system
What if you create a new list\column and check if crawl works on that column
If this helped you resolve your issue, please mark it Answered

What is sharepoint 2013 on premise and online

Similar Messages

Maybe you are looking for