Sharepoint 2013 Installation on windows 2012 R2

As sharepoint 2013 first service pack has been released so there is no need to follow these steps but if you don't want to download 1.03 GB data (size of the Service pack 1). You can follow following steps to run SHAREPOINT 2013 on your Windows server 2012 R2.


1. Login to your R2 server as Administrator. Start Power Shell as Administrator and execute following statements:

Import-Module ServerManager

Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source D:\Sources\sxs

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer -Source D:\Sources\sxs

D:\ is your windows installation path.

2. Download all prerequisites from the Internet and save it on local disk of the server, e.g. C:\SP2013Prereq:
SQL Server 2008 R2 SP1 Native Client
Microsoft WCF Data Services 5.0
Microsoft Information Protection and Control Client (MSIPC)
Microsoft Sync Framework Runtime v1.0 SP1 (x64)
Windows Identity Extensions
Windows Identity Foundation (KB974405)
Windows Server AppFabric
CU 1 for AppFabric 1.1 (KB2671763)

3. Install all prerequisites directly from the prerequisites folder in the download sequence, except the last two (AppFabric and CU 1 for AppFabric).
4. AppFabric requires special configuration, therefore installing it usual way is not be enough for SharePoint. Install it using following statement from command line

WindowsServerAppFabricSetup_x64.exe /i CacheClient","CachingService","CacheAdmin /gac

6. Restart your server

Congratulations! Now you will be able to start SharePoint 2013 installer directly and to continue with SharePoint 2013 installation and configuration.
 

Customize Application pages top navigation bar

As known that in SharePoint 2010 the application pages have a new property
called DynamicMasterPageFile that enable them to use the site master page
instead of using the OOB application.master. But it would maintain the default
top navigation control although the one in site master page changes.

The reason it maintains the default top navigation is that application pages override
content inPlaceHolderTopNavBar with a user control called TopNavBar.ascx where
it contains the default top navigation control (AspMenu).

To have the application master use our top nav control, we need to find the
PlaceHolderTopNavBar and PlaceHolderHorizontalNav in the master page, set it Visible = false
and make sure they don’t enclose any controls.

<asp:ContentPlaceHolder id="PlaceHolderTopNavBar" runat="server" Visible="false" />

<asp:ContentPlaceHolder id="PlaceHolderHorizontalNav" runat="server" Visible="false"/>

Add BackConnectionHostNames to the registry via PowerShell

BackConnectionHostNames is a server stuff and not a SharePoint stuff, SP2010 will still have issues trying to hit a FQDN from the server. So here is the solution:

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0 -Name “BackConnectionHostNames” -Value “intranet.contoso.com”,”mysites.contoso.com” -PropertyType multistring

if you are getting 401 error while logging into your port 80 site on server please follow following steps:

Method 1: Specify host names (Preferred method if NTLM authentication is desired)

To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:

1. Set the
   DisableStrictNameChecking
   registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
   281308  Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key:
   
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
4. Right-click MSV1_0, point to New, and then click Multi-String Value.
5. Type BackConnectionHostNames, and then press ENTER.
6. Right-click BackConnectionHostNames, and then click Modify.
7. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
8. Quit Registry Editor, and then restart the IISAdmin service.

Method 2: Disable the loopback check (less-recommended method)

The second method is to disable the loopback check by setting the DisableLoopbackCheck registry key.

To set the DisableLoopbackCheck registry key, follow these steps:

1. Set the
   DisableStrictNameChecking
   registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
   281308  Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key:
   
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
4. Right-click Lsa, point to New, and then click DWORD Value.
5. Type DisableLoopbackCheck, and then press ENTER.
6. Right-click DisableLoopbackCheck, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. Quit Registry Editor, and then restart your computer.

Ref: http://support.microsoft.com/kb/896861

Configure Developer Dashboard in Sharepoint 2010

How to enable/disable it on the specific site?
Method 1: [STSADM]
'On' Mode :
STSADM –o setproperty –pn developer-dashboard –pv On

'Off' Mode:
STSADM –o setproperty –pn developer-dashboard –pv Off

'OnDemand' Mode:
STSADM –o setproperty –pn developer-dashboard –pv OnDemand

Suppose you'd like to only display the developer dashboard if one or more acceptable values are exceeded, there's a way to do that too by running:
STSADM –o setproperty –pn developer-dashboard –pv expensiveoperationsonly

Once you executed the command the output is "Operation executed successfully."

Method 2: Windows Powershell script:
You need to open the windows power shell prompt and copy the below script and hit enter.
$DevDashboardSettings = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings;
$DevDashboardSettings.DisplayLevel = 'OnDemand';
$DevDashboardSettings.RequiredPermissions = 'EmptyMask';
$DevDashboardSettings.TraceEnabled = $true;
$DevDashboardsettings.Update();

ref:

http://praveenbattula.blogspot.com/2010/05/developer-dashboard-in-sharepoint-2010.html