Consultancy Soup

If you are having load balancer and you want to create host named site collection that is forcing https instead of http so what you need is the following 1-create host named site collection with https or add zone for https if you already created the site collection with http 2-Ask the load balancer team to force ssl from their side and ask them to add custom header as referenced in the below link http://technet.microsoft.com/en-us/library/cc424952(v=office.15).aspx#section2g

To test that Distributed cache is working as required, run the following Power shell commands in SharePoint Management Shell: use-cachecluster get-cacheclusterhealth get-cachehost

To add Alias to SharePoint 2013 Host Named Site Collection: $site = Get-SPSite "http://x.com" Set-SPSiteURL -Identity $site -Url "http://x1.com"  -Zone Default and you can add up to 5 aliases and zone can be: Default, Intranet, Internet, Extranet and Custom Reference:  http://technet.microsoft.com/en-us/library/jj219633(v=office.15).aspx

In environment where Sharepoint is in AD forest and the users are in another trusted forest, the people picker will not work directly and will not pick the users from the other forest until we do the following:   Log to the SharePoint server as admin Run that command    stsadm -o setapppassword -password <NewPassword>   Then for each web application that you need the people picker pick users from other trusted forests stsadm -o setproperty -url < Web_App_URL > -pn peoplepicker-searchadforests -pv "domain:<domain1FQDN>,<account_domain_1>\user,<password>; domain:< domain2FQDN >,<account_domain_2>\user,<password>" http://technet.microsoft.com/en-us/library/gg602075.aspx

    $Site  =  Get-SPWeb –Identity <URL> $List  =  $Site.Lists[" List Name "] $List.EnableThrottling =  $false $List.Update()

  Steps for migration from from 2010 to 2013: Perform a SQL Server full backup of the content database(s) in the 2010 farm. Restore DB(s). Create new web application in the 2013 farm. Deploy any Custom solutions. Test content DB to make sure that it has no issues (if issues found try to resolve them). Test-SPContentDatabase -name <SP DB Name> -WebApplication <web app url> Add the new content database restored to the target web application. Mount-SPContentDatabase -Name <db name> -DatabaseServer <db alias> -WebApplication <web app url> Verify that the site opens.

  To Migrate SharePoint DBs from SQL Server to another either same version or to a new version (2008 to 2008 or 2008 to 2012) you can follow the following steps:   Stop all SharePoint and IIS Related Services. Stop IIS. Detach all related SQL Server databases. Configuration database Central Administration content database Content databases Service application databases   Move all database files (.mdf, .ldf, and .ndf) to the new server. Set up same user permissions on the new SQL server. Attach your databases to the new SQL Server. Verify ports in your new SQL server. Go to your SharePoint server and create your SQL Server Alias. Start all your SharePoint services.