Tuesday, June 9, 2015

Audit settings for a site collection



Audit settings for a site collection

You can use the audit feature of Microsoft SharePoint Server 2013 or SharePoint Online to track which users have taken what actions on the sites, content types, lists, libraries, list items, and library files within your site collections. Knowing who has done what with which information is critical for many business requirements, such as regulatory compliance and records management.

I found a very detailed article from MS on the configuration of audit. Please check the below.

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Friday, June 5, 2015

Office documents open in read-only mode in Sharepoint



Office documents open in read-only mode in SharePoint

Issue: I have a SharePoint 2013 installation and clients with IE 11 and Office 2013. When clients navigate to a document library and click to open an Office document, the document opens in read-only mode with an information bar stating "We opened this document read-only from the server" and with a button to enable editing.

Cause: there could be many reasons for the issue like Not having proper permission to user to Edit DOC in site, IE compatibility issues, Client system issues.

Solution: I am providing the solutions below to solve the problem. Ensure one should resolve the issue.

Solution 1:Ensure the user is having a proper permissions on the site to edit the documents at least the contribute.

Solution 2:Ensure the IE is in compatible with the SharePoint and no issues with the IE.IE11 having some compatible issues with the SharePoint so I would recommend to check with other browsers.

Solution 3:please follow the steps below in client computer to resolve the issue.

1.    On the client computer experiencing the issue click on "RUN" then type "RegEdit".
2.    go to this path HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\14.0\Common\Internet

Note:For sharepoint 2013 the path is 15.0
 
3.    Right click and create new "DWORD" entry and give it a name of "FSSHTTPOff"
4.    Double click the new entry and enter 1 for the value.
5.    Once done you need to reboot the computer.
 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, June 2, 2015

Search Components



Search Components

When we configure the search in SharePoint 2013,we need to assign the roles and distribute the components in between the servers, In this article I am explaining in detail the roles of the search components.

Please go through the link provided to know what are the components for search.



Crawl component
The crawl component crawls the content sources. You can crawl a wide variety of content sources, for example file shares, SharePoint content, line of business applications and many more. To retrieve information, the crawl component connects to the content sources by invoking the appropriate indexing connector or protocol handler. After retrieving the content, the crawl component passes crawled items to the content processing component.
Content processing component
The content processing component processes crawled items and sends these items to the index component. The content processing component performs operations such as document parsing and property mapping. It also performs linguistics processing such as language detection and entity extraction. The component transforms crawled items into artifacts that are included in the search index. The content processing component also writes information about links and URLs to the link database. In turn, the analytics processing component writes information related to the relevance of these links and URLs to the search index through the content processing component.
Analytics processing component
The analytics processing component analyzes crawled items, which is referred to as search analytics, and how users interact with search, which is referred to as usage analytics. Examples of search analytics are links, anchor texts and metadata. An example of usage analytics is the number of times an item is viewed. The analytics processing component analyzes search analytics and usage analytics. Search analytics information is stored in the link database and usage analytics information in the analytics reporting database.
Index component
The index component is the logical representation of an index replica. In the search topology, you have to provision one index component for each index replica. The index component receives processed items from the content processing component and writes those items to an index file. Index files are stored on a disk in an index replica. The index component receives queries from the query processing component and returns result sets. You can divide the search index into discrete portions, called index partitions. Each index partition holds one or more index replicas. The search index is the aggregation of all index partitions.
Query processing component
The query component analyzes and processes queries and results. When the query processing component receives a query, it analyzes and processes the query to optimize precision, recall and relevance. The processed query is submitted to the index component. The index component returns a result set based on the processed query to the query processing component, which in turn processes that result set, before returning it to the front-end.
Search administration component
The search administration component runs the system processes for search. This component performs provisioning, which is to add and initialize instances of the other search components.
Crawl database
 The crawl database stores tracking information and details about crawled items. For example, it stores information about the last crawl time, the last crawl ID and the type of update during the last crawl.
Link database
The link database stores information extracted by the content processing component. It also stores information about the number of times people have clicked on a search result. The information is stored unprocessed; the analytics processing component performs the analysis.
Analytics reporting database
The analytics reporting database stores the results of usage analytics and extracts information from the link database when it is required.
Search administration database
The search administration database stores search configuration data and the access control list (ACL) for the crawl component. There can be only one search administration database per search service application.
Source from: http://www.c-sharpcorner.com/UploadFile/Roji.Joy/enterprise-search-configuration-in-sharepoint-2013/
Thanks to Destin for the great Article.


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Friday, May 29, 2015

Upgrade from a SharePoint Server 2010 Standard CAL to an Enterprise CAL

Upgrade from a SharePoint Server 2010 Standard CAL to an Enterprise CAL

This article provides information and procedures on how to upgrade from a Microsoft SharePoint Server 2010 Standard client access license (CAL) to an Enterprise CAL

Enable Enterprise features on existing sites

To convert the license type to the Enterprise CAL, you enable the Enterprise features on the SharePoint Central Administration Web site. Any new sites that you create will automatically have these features. However, existing sites do not receive the Enterprise feature set until you perform the steps to enable the features on existing sites. You have to perform these procedures only one time to update all sites in the server farm.
This procedure uses a SharePoint 2010 Timer service and may take a long time to complete, depending on the number of sites in the server farm.

To enable Enterprise features for the server farm 

1.    Verify that you have the following administrative credentials:
o    To enable enterprise features, you must be a member of the Farm Administrators group on the computer that is running Central Administration.
2.    On the Central Administration Web site, click Upgrade and Migration.
3.    In the Upgrade and Patch Management section, click Enable Enterprise Features.
4.    Enter the product key, and then click OK.
After you have enabled the features for the farm, you can enable the features on existing sites in the farm.

To enable Enterprise features on existing sites by using Central Administration 

1.    Verify that you have the following administrative credentials:
o    To enable enterprise features on existing sites, you must be a member of the Farm Administrators group on the computer that is running Central Administration.
2.    On the Central Administration Web site, click Upgrade and Migration.
3.    In the Upgrade and Patch Management section, click Enable Features on Existing Sites.
4.    On the Enable Features on Existing Sites page, select the Enable all sites in this installation to use the following set of features check box, and then click OK.

To enable Enterprise features on existing sites by using Windows Power Shell
 
1.    Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2.    On the Start menu, click All Programs.
3.    Click Microsoft SharePoint 2010 Products.
4.    Click SharePoint 2010 Management Shell.
5.    At the Windows PowerShell command prompt, type the following command:

Enable-SPFeature [-Identity] <FeatureID> [-URL] <site URL>
Where:
o    <Identity> specifies the name of the feature or GUID to install.
o    <URL> specifies the URL of the Web application, site collection, or Web site for which the feature is being activated.

Verification:

Use the following procedure to verify that the enterprise features have been enabled on existing sites.
To verify that enterprise features are enabled on existing sites
1.    Verify that you have the following administrative credentials:
o    To verify that enterprise features are enabled on existing sites, you must be a member of the Farm Administrators SharePoint group on the computer that is running Central Administration.
2.    On the site collection Web site, on the Site Actions menu, click Site Settings.
3.    On the Site Settings page, in the Site Administration section, click Site features.

In the Status column for SharePoint Server Enterprise Site features, ensure that Active appears.

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

ShareThis

X