Delete a service application in SharePoint 2013

 Delete a service application in SharePoint 2013

service applications can be deleted by using the SharePoint Central Administration website or by using Windows Power Shell 3.0 cmdlets.

Before deleting a service application, verify that its removal will not adversely affect users. As a best practice, you should ensure that no web applications are currently consuming the service application that you are going to delete. 

When you delete a service application, you have the option of also deleting the service application database. Some service applications do not have databases. If you plan to create the service application again in the future, do not delete the service application database. If the service application is temporary, you will most likely want to delete the database during this operation.

How to delete by the CA: Please follow the steps below to delete the Service Application by the GUI in CA.

1.    Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.

2.    On the SharePoint Central Administration website, click Application Management, and then click Manage service applications.

3.    On the Manage Service Applications page, click the row that contains the service application that you want to delete. The ribbon becomes available.

4.    On the ribbon, click Delete.

5.    In the confirmation dialog box, select the check box next to Delete data associated with the Service Applications if you want to delete the service application database. If you want to retain the database, leave this check box cleared.

6.    Click OK to delete the service application, or click Cancel to stop the operation

How to delete by using the Power Shell: Please follow the steps below to delete by using the power shell commands.

1. Ensure  that you meet the following minimum requirements:

·         You must have membership in the securityadmin fixed server role on the SQL Server instance

·         You must have membership in the db_owner fixed database role on all databases that are to be updated.

·         You must be a member of the Administrators group on the server on which you are running the Windows Power Shell cmdlet.

2.Start the SharePoint 2013 Management Shell.

2.    To retrieve the service application that you want to delete, type the following command: 

$spapp = Get-SPServiceApplication -Name "<Service application display name>"

3.    To delete the selected service application, run either of the following commands. In both cases, you are prompted to confirm the deletion. 

·         To delete the selected service application without removing the service application database, type the following command:

Remove-SPServiceApplication $spapp

·To delete the selected service application and also delete the service 

application database, type the following command:

Remove-SPServiceApplication $spapp -RemoveData

 

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.

Issue, if we continue to use Classic Mode in SharePoint 2013.

Issue, if we continue to use Classic Mode in SharePoint 2013.

Question: I am getting this query from some of the SharePoint community people that what is the issue if we use classic mode authentication only In SharePoint 2013,why not we use classic if it supports in SharePoint 2013.

Answer: I am trying to explain the answer as I know and per my experience. Please provide if anything that I missed.

As we all know that the default authentication in SharePoint 2013 is claims mode only. There is no Classic authentication on SharePoint 2013 by Default, If we want to use the classic we can use but we should keep in mind that the below functionalities will not work with Classic in SharePoint 2013.

1.    Office Web Apps services(OWA)

2.    SharePoint Apps like S2S

3.    Hybrid feature of SharePoint.

Please check the link below that shows on how to change the authentication from classic to claims.

http://expertsharepoint.blogspot.my/2013/10/how-to-change-sharepoint-authentication.html

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.

Difference between psconfig.exe and products and technologies wizard running in GUI

Difference between psconfig.exe and products and technologies wizard running in GUI

Most of the administrators think that, both running the GUI configuration Wizard and Running the Psconfig.exe-cmd command will do the same after the install of CU or SP. But in reality, Both are not same and there is a much difference in running those in GUI and command.

In this article I am trying to explain the things what made the difference between and which is recommended to run after the install of CU or SP

products and technologies wizard:

1.     PSCONFIGUI.EXE( products and technologies configuration wizard) is the UI based configuration wizard which performs several tasks one after the other after installing fixes.

2.     It will perform all the operation including  setup, standalone config,  config db, help collections, secure resources services,installfeatures,adminvs,upgrade,evalprovision,applicationcontent,quiet

PSCONFIG.EXE:

1.     PSCONFIG.EXE is the command line tool which gives users granular control over all tasks that are executed and which is therefore quicker than PSCONFIGUI.EXE.

2.     Most of us just ran the following command

PSCONFIG -cmd upgrade -inplace b2b -wait

But that command only performs a subset of operations performed by PSCONFIGUI.EXE. E.g. it will not update the files in the _app_bin directory of the web applications! 

I would recommend to run the Products and technologies configuration wizard to set everything is perfect after the installation of CU or service pack. If you still need to include the PSCONFIG.EXE in any of the script, you include the below

PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources

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.

What changes does SharePoint configuration wizard do?

What changes does SharePoint configuration wizard do?

This is a common question for most of the administrators, asking me the same by different SharePoint Admins, Most of the times after we install any CU or SP we must run the Products and Technologies configuration wizard, why? Here is the answer.

Answer:

1.      When we run the “Configuration Wizard “ it updates the database schema to the latest version

2.     When we run the “Configuration Wizard “ it fixes security settings on the file system to match what SharePoint needs

3.     When we run the “Configuration Wizard “ it will copies required binaries from the install location into the _app_bin directories of the web applications

4.     When we run the “Configuration Wizard “ it updates features registrations with SharePoint

Note: It is also recommended to run the PSConfig wizard once the security patches is installed, but most of the times we don’t run.

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.

September 2015 CU for SharePoint 2010 is Released.

September 2015 CU for SharePoint 2010 is Released.

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

The KB articles for September CU should be available at the following locations in a couple of hours:

• KB 3085530 - SharePoint Foundation 2010
• KB 3085521 - SharePoint Server 2010
• KB 3085517 - Project Server 2010

The Full Server Packages for September 2015 CU are already available through the following links:

• Download SharePoint Foundation 2010 September 2015 CU
• Download SharePoint Server 2010 September 2015 CU
• Download Project Server 2010 September 2015 CU

Note:

1. Be aware that CU is a Post-SP2 hotfix. It is required to have SP2 installed before installing the CU.
2. It is required to have SP2 installed for the base product and all installed language packs to install September 2015 CU for SharePoint 2010.
3. This CU includes all SharePoint 2010 fixes (including all SharePoint 2010 security fixes) released since SP2. The CU does not include SP2.
4. After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
5. Be aware that the SharePoint Server 2010 CU contains the SharePoint Foundation CU.
6. 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.

SQL high available failover

SQL high available failover:

Description: Most of the administrators think that the failover should do in SQL HA by the Windows Cluster, but it’s not true. we need to do the failover by the HA method which is configured in SQL.

In this article I am providing the steps to do the failover.

Steps: Please follow the steps below to do failover in HA.

As per below screen ,Secondary Don’t have any resources so patch first in secondary.

                                 

 Once patching done successful in secondary do failover resources to secondary, then  primary becomes secondary.

Do patch in other secondary now.

Failover steps:

1.      Logon to the SQL server with SQL account

2.      Go to SQL management studio.

3.      Expand availability groups as per the screen below.

4.      Right click the DB

5.      Click on Failover

6.      Click on next in introduction

7.      Select a new primary replica->next

8.      connect to replica->click next.

9.      successful

                                 

 

 
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.