Wednesday, September 10, 2014

How to Increase of Quota templates



How to Increase of Quota templates

Please follow the below steps to change the quota templates in sites.

1.    Verify that you have the following administrative credentials:
·         You must be a member of the Farm Administrators group.
2.    On the Central Administration home page, click Application Management.
3.    On the Application Management page, in the Site Collections section, click Specify quota templates.
4.    On the Quota Templates page, in the Template Name section, in the Template to modify list, select the template that you want to change.
5.    In the Storage Limit Values section, specify the values that you want to apply to the template.
·         If you want to modify the amount of data that can be stored in the database, leave the Limit site storage to a maximum of check box selected, and then type the new storage limit, in megabytes, in the box.
·         If you want an e-mail message to be sent to the site collection administrator when a storage threshold is reached, select the Send warning E-mail when site storage reaches check box, and then type the threshold, in megabytes, in the box.

6.    In the Sandboxed Solutions With Code Limits section, specify the values that you want to apply to the template.

·         If you want to limit the maximum resource usage points per day for sandboxed solutions that contain code, type the new limit in the Limit maximum usage per day to box. The default limit is 300 points.
·         If you want an e-mail message to be sent to the site collection administrator when the usage per day threshold is reached, select the Send warning e-mail when usage per day reaches check box, and then type the threshold, in points, in the box.
7.    Click OK.


 

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.

The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases



The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

Issue: The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

Cause: This means that the cache accounts for your web application aren’t properly set and that there will be a lot of cache misses. If a cache miss occurs the page the user requested will have to be build up from scratch again. Files and information will be retrieved from the database and the file system and the page will be rendered. This means an extra hit on your SharePoint and database servers and a slower page load for your end user.

Solution: The domain\super user account needs to have a User Policy set for that gives it Full Control to the entire web application. In order to do this you perform the following steps:

1.     Go to Central Administration
2.     Go to Application Management
3.     Go to Manage Web Application
4.     Select the web application we’re talking about
5.     Click User Policy
6.     Add Users
7.     Click Next
8.     Fill in domain\superuser
9.     Select Full Control
10.  Click OK 

The domain\super reader account needs to have a User Policy set for that gives it Full Read to the entire web application. In order to do this you perform the following steps:

1.     Go to Central Administration
2.     Go to Application Management
3.     Go to Manage Web Application
4.     Select the web application we’re talking about
5.     Click User Policy
6.     Add Users
7.     Click Next
8.     Fill in domain\super reader
9.     Select Full Read
10.  Click OK

1.    If you are using classic mode authentication run the following cmdlets on one of your SharePoint servers:

$w = Get-SPWebApplication "http://<server>/"
$w.Properties["portalsuperuseraccount"] = "domain\superuser"
$w.Properties["portalsuperreaderaccount"] = "domain\superreader"
$w.Update()
2.    If you are using claims based authentication run these cmdlets on one of your SharePoint servers:

$w = Get-SPWebApplication "http://<server>/"
$w.Properties["portalsuperuseraccount"] = "i:0#.w|domain\superuser"
$w.Properties["portalsuperreaderaccount"] = "i:0#.w|domain\superreader"
$w.Update()
After you've run these Power Shell cmdlets you need to perform an IISRESET to finish it off.


 


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.

Monday, September 8, 2014

Rename the User Profile service application databases in SharePoint Server 2013



Rename the User Profile service application databases in SharePoint Server 2013

You typically rename service application databases to remove the GUID from the database name after the databases were created by the SharePoint Products Configuration Wizard, or to bring the databases into alignment with your organization's naming standards.

You can rename a User Profile service application database by using SQL Server tools.

Please check the below Article 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.

Friday, September 5, 2014

Account Deletion issues in SharePoint 2010 User Profile Synchronization



Account Deletion issues in SharePoint 2010 User Profile Synchronization


I found a Very good article on This from Harbar. Please find the link below.
Thanks to Harbar.
 

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