Monday, June 29, 2015

Adding a content DB in SharePoint 2013



Adding a content DB in SharePoint 2013

You can add a content database to a SharePoint 2013 farm by using the SharePoint Central Administration website or Windows Power Shell

You can use the procedures that are described in this article to create a new content database and attach it to a web application. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server dbcreator fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have dbcreator permission on the SQL Server instance where the database will be created.

To add a content database to a web application by using Central Administration 

1.    Verify that the user account that is performing this operation is a member of the Farm Administrators SharePoint group.
2.    Start SharePoint 2013 Central Administration.
o    For Windows Server 2008 R2:
§  Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
o    For Windows Server 2012:
§  On the Start screen, click SharePoint 2013 Central Administration.
If SharePoint 2013 Central Administration is not on the Start screen:
§  Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.
3.    On the SharePoint Central Administration website, click Application Management.
4.    In the Databases section, click Manage content databases.
5.    On the Manage Content Databases page, click Add a content database.
6.    On the Add Content Database page:
1.    Specify a web application for the new database.
2.    Specify a database server to host the new database.
3.    Specify the authentication method that the new database will use and supply an account name and password, if they are necessary.
ImportantImportant:
The account name and password must already exist as a SQL Server login.
4.    Specify the name of the failover database server, if one exists.
5.    Specify the number of top-level sites that can be created before a warning is issued. By default, this is 2,000.
6.    Specify the total number of top-level sites that can be created in the database. By default, this is 5,000.
7.    Click OK.

To add a content database to a web application by using Windows Power Shell 

1.    Verify that you have the following memberships:
o    securityadmin fixed server role on the SQL Server instance.
o    db_owner fixed database role on all databases that are to be updated.
o    Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 Products cmdlets.
NoteNote:
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin

2.    On the Start menu, click All Programs.
3.    Click Microsoft SharePoint 2013 Products.
4.    Click SharePoint 2013 Management Shell.
5.    At the Windows PowerShell command prompt, type the following command:
New-SPContentDatabase -Name <ContentDbName> -WebApplication <WebApplicationName>
Where:
o    <ContentDbName> is the name of the content database to create.
o    <WebApplicationName> is the name of the web application to which the new database is attached.

 


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, June 14, 2015

June 2015 CU for SharePoint 2010 is available is released



June 2015 CU for SharePoint 2010 is released

The product group released the June 2015 Cumulative Update for the SharePoint 2010 product family.

For June 2015 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

Be aware that CU is a Post-SP2 hot fix. It is required to have SP2 installed before installing the CU.

It is required to have SP2 installed for the base product and all installed language packs to install June 2015 CU for SharePoint 2010.

This CU includes all SharePoint 2010 fixes released since SP2. The CU does not include SP2.

The KB articles for June CU are available at the following locations:
  • KB 3054847 - SharePoint Foundation 2010 - This is also a security fix!
  • KB 3054880 - SharePoint Server 2010
  • KB 3054877 - Project Server 2010
The Full Server Packages for June 2015 CU are available through the following links:
After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.
 


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.

June 2015 CU for SharePoint 2013 is Released



June 2015 CU for SharePoint 2013 is Released

For June 2015 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

Note:


Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first. 

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hot fix Download Available link in the KB article for the release.
This CU includes all SharePoint 2013 fixes (including all security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.
The KB articles for June CU are available at the following locations:
  • KB 3054864 - SharePoint Foundation 2013 June 2015 CU
  • KB 3054866 - SharePoint Server 2013 June 2015 CU
  • KB 3054865 - SharePoint Server 2013 with Project Server June 2015 CU
  • KB 3054863 - Office Web Apps Server 2013 June 2015 CU
The Full Server Packages for June 2015 CU are available through the following links:
After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU. 

Build:  15.0.4727.1001



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.

Thursday, June 11, 2015

Removing quick launch from SharePoint 2013



Removing quick launch from SharePoint 2013

I am getting more questions about the quick launch on how to remove that from the existing site. I am writing this article with steps to shown how to do that.

To enable or disable Quick Launch through the user interface
a.    Click Site Actions, and then click Site Settings.
b.    Under Look and Feel, click Tree view. 
c.    To display the control, select the Enable Quick Launch check box. Or, to hide Quick Launch, clear the check box.

    To enable or disable Quick Launch using SharePoint Designer

a.    Open the website in SharePoint Designer 2010.
b.    On the site settings page, under Settings
c.    Select the Display Quick Launch check box to enable the menu.
d.    To hide the menu -> clear the check box
e.    Click File, and then click Save to save the change.


 


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