For some reason SharePoint 2013 doesn’t include the Navigate Up function previously available to SharePoint 2010. This function is important when navigating up a site hierarchy. To get it back you must open SharePoint Designer 2013.
1. Click on Master Pages and create a copy of the seattle.master (the new default master page).
2. Right click on the seattle_copy(1).master and select Open. Search for:
class=”ms-breadcrumb-dropdownBox” – it should be on line 369.
3. Delete the style=”display:none;” at the end of the line.
4.Delete the Visible=”false” a couple of lines underneath.
5. Save the seattle_copy(1).master.
6. On the Master Pages list, right-click on the seattle_copy(1).master and select Set as Default Master Page.
7. Check that the seattle_copy(1).master is applied to the site collection as the default Site Master Page by clicking on Master Page (under Look and Feel) in Site Settings.
8. Refresh the sub-site to see the Navigate Up icon to the left of the global navigation menus.
This link explains how to add profile pictures to Active Directory using PowerShell, and how you can import these pictures into user profiles in SharePoint 2010 or 2013:
You can get sample contoso user accounts and images from the Codeplex site here: http://sharepointdemobuilds.codeplex.com/releases/view/101674
This Microsoft Knowledgebase article explains how you can sign in to Internet Explorer as a different user to get round this omission: http://support.microsoft.com/kb/2752600
1. Start Internet Explorer by using the Run as different user option, and then go to the SharePoint site.
Note: The Run as different user option is visible if you hold the Shift key when you right-click a program icon.
2. Access the SharePoint site by using the URL as http://siteurl/_layouts/closeConnection.aspx?loginasanotheruser=true
This option uses an unsupported browser feature which is unreliable and causes other issues. Currently this option does not work in IE 10 and Safari.
The URL path of a newly created site collection will include “/_layouts/15/start.aspx” To avoid this it is necessary to deactivate the following site feature:
1. Go to Site Settings – Site Features page.
2. Deactivate the “Minimal Download Strategy” feature.
Why is the Minimal Download Strategy available by default on various site collection templates including the Team Site? This is a new feature for SharePoint 2013 that is designed to increase the performance of the SharePoint site.
For a full explanation please read Wictor Wilen’s Blog post here: http://www.wictorwilen.se/sharepoint-2013—introduction-to-the-minimal-download-strategy-mds
Here are some commonly used PowerShell commands:
1. Add-SPSolution “<file location\Name.wsp>”
e.g. Add-SPSolution “c:\customsolution.wsp”
2. Install-SPSolution -Identity <Name.wsp> -WebApplication http://name -GACDeployment
e.g. Install-SPSolution -Identity customsolution.wsp -WebApplication http://sp10/sites/finance -GACDeployment
3. Uninstall-SPSolution -Identity <Name.wsp> -WebApplication http://name
e.g. Uninstall-SPSolution -Identity customsolution.wsp -WebApplication http://sp13/sites/hr
4. Remove-SPSolution -Identity <Name.wsp>
e.g. Remove-SPSolution -Identity customsolution.wsp
How to change a site collection’s URL
1. Backup the site collection using PowerShell or the menu option available in Central Admin.
2. To restore, use PowerShell. Here is an example:
Restore-SPSite -Identity http://thehub.harrogate.local/bussupport/procurement -Path c:\backup\SharePoint\[BackupFileName.bak] -DatabaseServer [DatabaseServerName] -DatabaseName [ContentDatabaseName] -Force
How to create a new site collection assigned to a new content database
$db=New-spcontentdatabase –name “Marketing_ContentDB01” –webapplication http://sp10; new-spsite –url http://sp10/sites/marketing -name “Marketing Site” –description “Welcome to the Marketing Site” –owneralias “contoso\driscollm” –contentdatabase $db –template “STS#0”
“Sorry, this site hasn’t been shared with you.” This seems to be a common message SharePoint 2013 users are seeing if things aren’t configured correctly. There may be a variety of reasons why you are seeing this message. In my case it was happening when I tried to go to particular site admin (_layouts) pages and seemed to be caused by the site collection not being correctly provisioned. To overcome the problem it was necessary to do the following:
1. Go to Central Admin. Click on the “Application Management” heading.
2. Click on “Manage services on server”.
3. Stop the service “Microsoft SharePoint Foundation Web Application”. This will take a little while to stop.
4. Start the above service again.
This should resolve the problem.
From a SharePoint Governance perspective it is sometimes useful to hide particular lists and libraries from a site’s Create Lists and Libraries page.
You can disable each list or library’s feature. To unregister the document library list template from the site disable the feature by entering in PowerShell:
Disable-SPFeature <FeatureID> -Url <URL name>
Go to http://blogs.msdn.com/b/mcsnoiwb/archive/2010/01/07/features-and-their-guid-s-in-sp2010.aspx to see a definitive list of Feature ID’s for different library and list types.
A colleague of mine – Andy Burns has offered a useful tip if you want your SharePoint 2010 deployment to benefit from using the Publishing Navigation features, without the added baggage provided when the site collection’s Publishing Infrastructure feature is enabled. He discovered that there is a “Navigation” feature nestled in the Publishing Infrastructure set of features. If only the Navigation feature is enabled you can work with the Publishing navigation for your top link bar and current navigation.
Using STSADM or Powershell you can activate the hidden feature. The Feature’s name is Navigation and it has a GUID of 89E0306D-453B-4ec5-8D68-42067CDBF98E
The STSADM command is: stsadm -o activatefeature -name navigation -url <url to site>
SharePoint’s Enterprise Search Center and Basic Search Center are based on a minimal.master Master Page. This means that you cannot easily integrate a Search Centre into your standard global navigation deployment. To get around this problem you can either open the Search Centre in a new browser window, or implement a fix. My company Deltascheme offer a simple fix for the Basic Search Center. If you choose to install the solution you can create a revised version of the Basic Search Center that integrates with your standard v4.master global navigation.
Follow this link to download the fix: http://www.deltascheme.com/deltascheme-products/basic-search-center-with-navigation-for-sharepoint/
To display metadata on a SharePoint 2010 search results page please follow these instructions: http://msdn.microsoft.com/en-us/library/ms560074.aspx