Skip to main content

SP2013 Web Apps: Create Web Applications in Classic Authetication Mode

As you may already be aware, when you create a new web application in SharePoint 2013, it by default creates in claims authentication mode. If you are under going a migration and upgrade from SP2010 to SP2013 and you would first want to create classic authentication web apps to attach the DBs to, here is how:

Create your web application from PowerShell using the following script:

New-SPWebApplication -Name “<WebAppName>” -ApplicationPool “<WebAppPoolName>” -AuthenticationMethod “NTLM” -ApplicationPoolAccount (Get-SPManagedAccount “DOMAIN\SPManagedAccount”) -DatabaseName “<DBName>” -Port <PortNo> -URL http://URL​

Note that if you indicate the port number in the parameter, you don't need to include it in the Url Parameter.

My next blog post talks about converting a web application from classic to claims authentication mode, in SharePoint 2013.
Labels:

Comments

Post a Comment

Popular posts from this blog

Zambia's first Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an ...
7 comments
Read more

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.
8 comments
Read more

How to implement a SharePoint "Change Management Process"

Not so much from the technical point of view, SharePoint Change Management is the process of monitoring and controlling changes within a SharePoint project. By managing the implementation of change, you can: • Reduce the impact of changes to the SharePoint project • Identify new issues and risks as a result of changes raised • Ensure that changes do not affect the SharePoint project's ability to achieve its desired objectives • Control the cost of change within the SharePoint project Change Management is comprised of the following processes: Step 1: Identify Change: The first step in the change process is to identify the need for change. Any team member can suggest a change to the SharePoint project, if he or she believes it is needed to keep the SharePoint project producing deliverables to the customer's specified requirements. After identifying a need for change, the team member records relevant information on a Change Request Form (commonly called a CRF), describing the chan...
2 comments
Read more