Sunday, December 21, 2014

How to change the session timeouts in SharePoint sites

How to change the session timeouts in SharePoint sites

SharePoint  allows you to set timeout of the user session so that your users are logged out after certain time of inactivity. Also, SharePoint allows you to configure the timeout for the current page state to expire. This is handy for forms which have to be filled within certain period of time before they expire.
Alternatively, if you want to extend the timeout – you can do that.

let’s take a look at how you can expire page content after a given time using Power Shell:

Open SharePoint Management Shell as administrator and execute the following:
$SPSite = Get-SPSite("[your site collection]")
$webApp = $SPSite.WebApplication
$webApp.Enabled = $true
$webApp.Expires = $true
$webApp.Timeout = New-TimeSpan -Hours 2 -Minutes 30
$webApp.Update()

This will effectively enable expiration and set page content to expire after users leave it hanging for over 2 hours and 30 minutes.

if you’re using claims authentication and would like for your provider to expire sessions after certain period of inactivity, here is how to do that with Power Shell:

$sts = Get-SPSecurityTokenServiceConfig
$sts.UseSessionCookies = $true
$sts.LogonTokenCacheExpirationWindow = New-TimeSpan -Minutes 5
$sts.Update()

This will set our logon expiration to 5 minutes.


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.

Sunday, December 14, 2014

Add, edit, or delete custom properties in SharePoint Server 2013 user profiles



Add, edit, or delete custom properties in SharePoint Server 2013 user profiles
 

The Manage Profile Service page of a User Profile service application in SharePoint Server 2013 is a central location for managing available user profile properties and creating new properties. For more information, see Overview of the User Profile service application in SharePoint Server 2013.

You can supplement default user profile properties with additional properties to track key information that is not otherwise available. Key business needs might encourage you to create new properties that associate users with important business processes. For example, a sales department can create a specific sales role property to share with a particular audience or audiences. Custom user profile properties can be edited to better suit business needs or they can be deleted when no longer needed.

The Manage Profile Service page cannot be accessed until an instance of a User Profile service application exists. You can use the SharePoint Central Administration website to create and manage User Profile service applications and other service applications for non-hosted environments. (For hosted environments, you do this on the Tenant Administrator page.) You can delegate administration of a User Profile service application to someone who does not have permissions to manage other services or settings contained in Central Administration. For more information, see Delegate administration of User Profile service applications in SharePoint Server 2013

Reference MS Article: http://technet.microsoft.com/en-us/library/cc262327%28v=office.15%29.aspx

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, December 12, 2014

User profile service application is missing to import AD groups



User profile service application is missing to import AD groups

Issue: I configured the User Profile Service and I did a full synchronization. Everything works fine.

I used FIM tool miisclient.exe to view results. I find that the number of results in this tool is different from result as in CA "Number of User profiles”. In fact, with CA I can't found profile for groups AD. Furthermore, wit miisclient tool I can see users and groups from AD.

Cause: Probably the groups are being imported (these are required by things such as audiences). They will not be displayed however in manage user profiles (or anywhere else), this is by design. Try creating an audience based on group membership and compiling it, this will prove if the groups are imported or not.

Solution: You can still check Active directory groups in miisclient tool at, for SharePoint 2013 it is 15.0 instead of 14.0

C:\Program Files\Common Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe

1.    Run the MIISclient.exe as Administrator

 0109

2.    Click on the Management Agents button on the top menu bar
3.    Right-click on “Active Directory Connector” and choose Run from the context menu.

 0110
4.    Highlight “Full Import Full Sync” and choose OK.
 0111

5.    The State will change to Running. The bottom half the screen will give information on any changes that it makes during the run as well as any errors encountered.

 0112

Here you would be able to see the number of groups imported

Reference MS articles:


http://technet.microsoft.com/en-us/library/cc262327.aspx
http://technet.microsoft.com/en-us/library/ee721054.aspx
 

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.

Wednesday, December 3, 2014

Manage the search schema in SharePoint Server 2013



Manage the search schema in SharePoint Server 2013

Crawled properties are metadata that is extracted from documents during crawls. Metadata can be structured content (such as the title or the author from a Word document), or unstructured content (such as a detected language or extracted keywords). 

Users can only search on managed properties and not on crawled properties. To make a crawled property available for search queries, you must map the crawled property to a managed property. You can map multiple crawled properties to a single managed property or map a single crawled property to multiple managed properties.

Link from MS: 

 


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.

Manage the search topology in SharePoint Server 2013



Manage the search topology in SharePoint Server 2013

The following articles on Tech Net provide information about how you manage search components in SharePoint 2013

  http://technet.microsoft.com/en-us/library/jj219705%28v=office.15%29.aspx


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