Problem: Metadata navigation settings in SharePoint document library is missing! Metadata navigation makes it easier to find and dynamically filter content in large lists and libraries. Once enabled, it uses a navigation tree in the quick launch. Solution: You must activate "Metadata Navigation and Filtering" Feature from Site features page! To enable Metadata Navigation and Filtering, Login as a Site Owner or Site Collection Administrator to your SharePoint site. Click on Site Settings Icon >> Under Site Actions, click on Manage site features. In the Features Page, click Activate button next to Metadata Navigation and Filtering. Now, You can configure metadata navigation to your SharePoint list and libraries.
Requirement: We've created a custom search scope "Search All Documents" in SharePoint Central Admin and would like to include it in search scope drop downs of few site collections. SharePoint 2010 add search scope to drop down: Well, its a few-clicks job to include custom search scopes to search drop down in SharePoint. Here is how: Go to Site Actions >> Site Settings Click on "Search Scopes" link under Site collection administration Click on "Display Groups" link and choose "Search Dropdown" From here, we can include/exclude any scopes to search dropdown by simply selecting/deselecting check-boxes. Add custom scope to SharePoint Search Scope Drop downs using PowerShell While its not tedious to customize search scope dropdowns by following above steps for few site, We had to do it for all site collections under a particular managed path.(around 50!). Here is the PowerShell script to add custom search scopes to SharePoint s
What is inactive Feature in SharePoint? Well, Features which are installed but not activated anywhere! Here is the PowerShell script to find inactive features for SharePoint: Add-PSSnapin "Microsoft.SharePoint.Powershell" -ErrorAction SilentlyContinue $InactiveFeatures = @() #Get All installed features on respective scopes $WebAppFeatures = Get-SPFeature | Where-Object {$_.Scope -eq "WebApplication" } $siteFeatures = Get-SPFeature | Where-Object {$_.Scope -eq "Site" } $WebFeatures = Get-SPFeature| Where-Object {$_.Scope -eq "Web" } Write-host "Checking Web Application Scoped Features..." foreach ($WebAppFeature in $WebAppFeatures) { $Flag = $False foreach ($WebApp in Get-SPWebApplication) { if ((Get-SPFeature -WebApplication $WebApp.URL | Where-Object {$_.Id -eq $WebAppFeature.id}) -ne $null) { #We found that the Feature is active, Lets end up the loop $Flag = $True bre
Task: Generate a report for All Installed/Activated Features for the entire SharePoint Environment. Here are some nifty PowerShell scripts to find features installed on the farm as well as specific features activated on a particular scope. Get-SPFeature cmdlet: Get-SPFeature cmdlet retrieves all features installed on the environment, when "Scope" parameter's value is not supplied. It gets all activated features on the particular scope, when you provide scope parameter: (Such as : -site "http://sharepointsite.com") Get a list of all installed SharePoint features, Grouped by feature scope: Get-SPFeature | Sort-Object Scope | Format-Table -GroupBy scope Lets export to a text file: Get-SPFeature | Sort -Property Scope, DisplayName | Ft -Autosize -GroupBy Scope DisplayName, Id > D:\FeaturesReport.txt To get all features activated at a particular web application scope, Use: Get-SPFeature -WebApplication "web-app-url" #Similarly: #Get-SPFe
Requirement: PowerShell to Import XML to SharePoint List We've an utility from third-party system that generates project data in XML format. We had to import those data to a list in the PMO site. In other words: We've to import from XML file to SharePoint list. Here is a sample XML file, generated by the tool: <?xml version="1.0"?> <projects> <project id="PMO.1120"> <description>GIS upgrade 2013 </description> <manager>global\E372440</manager> <cost>$35000</cost> <startdate>1/1/2014</startdate> </project> <project id="PMO.1121"> <description>HRIT Asset Life Cycle Automation</description> <manager>AMER\E132321</manager> <cost>$63000</cost> <startdate>1/1/2014</startdate> </project> </projects> Using PowerShell, lets import XML data into SharePoint list. PowerShell script to read from
My PowerShell scripts to add list item in SharePoint: Add SharePoint list items using PowerShell The syntax to add new list item in SharePoint using PowerShell, goes like this #Get Web and List Objects $Web = Get-SPWeb "http://sharepointsite.com" $List = $Web.Lists["ListName"] #Create a new item $NewItem = $List.AddItem() #Set Column values $NewItem["ColumnName"] = "Field Value goes here!" #Update the Item, so that it gets saved to the list $NewItem.Update() Add list item in SharePoint with PowerShell Lets add new task to the task list using PowerShell: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Processing Variables $WebURL="http://sharepoint.crescent.com" $ListName="Tasks" #Get Web and List Objects $Web = Get-SPWeb $WebURL $TaskList = $Web.Lists[$ListName] #Create New Task Item $NewTask = $TaskList.AddItem() $NewTask["Title"] = "Migration Project - SOW" #
Requirement: By default, SharePoint search engine craws and indexes all documents and its associated metadata properties from lists and libraries. In our case, We keep few fields for configuration in a custom SharePoint application and don't want those fields to appear in SharePoint Search results. This is applicable only to site columns in SharePoint! How to Exclude a column from SharePoint Search? Here is how you can remove columns from SharePoint search. Navigate to the site settings page by clicking settings gear On the Site Settings page, click on "Searchable Columns" link under search group. Select the check box next to the column(s) that you want to suppress from search. Click OK to save your changes. This ensures the particular metadata column isn't picked up by the search engine in SharePoint and excludes the site column data within the current site. PowerShell Script to Exclude Field from Search: SharePoint Fields/Columns has a proper
Requirement: During a branding project, We had to deploy a logo file every time to all SharePoint servers by individually logging in to them and copy pasting given file to all SharePoint 2013 server's 15 hive. Wanted to do a bit automation with PowerShell here. Let the PowerShell do Copy-Paste for us. PowerShell script to copy files to Servers: $LogoPath = "D:\Branding\crescent-logo.png" #Define Array with List of servers $WFEServers = ("G1V-SPS13001", "G1V-SPS13002", "G1V-SPS13003", "G1V-SPS13004", "G1V-SPS13005") foreach ($Server in $WFEServers) { #Destination path $Destination = "\\$Server\C$\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\IMAGES\crescent-logo.png" #Copy File from local to destination Copy-Item $LogoPath $Destination write-host "Copied to Server:"$Server } You can run this script from your workstation. Just make su
Ever wondered how to find the user who has created or modified a particular SharePoint view? and when it was created/modified? Well, There is no SharePoint UI to get these information! But using SharePoint object model, we can retrieve these data programmatically from SPFile object's properties. Here is how I retrieved "Created By", "Created On", "Modified By", "Modified On" values using PowerShell: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Set these two variables accordingly $WebURL = "http://sharepoint.crescent.com/" $ViewURL = "http://sharepoint.crescent.com/LegalDoc/AuthorView.aspx" #Get the Web $web = Get-SPWeb $WebURL #Get the View File $ViewFile = $web.GetFile($viewURL) Write-Host "Created By: " $ViewFile.Author Write-Host "Created on: " $ViewFile.TimeCreated Write-Host "Modified By: " $ViewFile.ModifiedBy Write-Host "Modified
Requirement is to find out owners of each SharePoint site collection in the environment.We needed this data to get approvals on critical changes and to inform site owners prior to maintenance windows. Simple! Use STSADM command: On SharePoint 2007 and above, STSADM command can be used to get primary owner details of site collections: Syntax: stsadm -0 enumsites -url <web-app-url> E.g. stsadm -0 enumsites -url "http://sharePoint.crescent.com" > SitesRpt.xml This command enumerates all site collections and pulls site owner information. It also retrieves secondary owner, content database in which site collection exist and storage details of the site collection. Just open the generated XML file with Microsoft Excel. Find Site Owners for All site collections using PowerShell: Get-SPSite -Limit 'All' | select URL, Owner, SecondaryContact For SharePoint 2007 Sites, The PowerShell script to get site Owners for all Site collections would be: [void][Syst
Problem: SharePoint Number columns shows , (comma) in View/Display Forms. There are specific numeric columns, User wanted to display without commas. There is no direct way to remove comma/avoid thousand separator in SharePoint Number fields, But the below tricks help to get SharePoint 2007/2010/2013 number column values without commas. Solutions: Here are some solutions to show number fields without comma: Use "Single Line of Text" instead of "Number" column type, if possible. (But this will not stop users from entering alpha characters!) Use an another Calculated column with formula: = TEXT( Number_Column_Name, "0") . If you need sorting, you can use: =FIXED(Number_Column_Name,0,TRUE) Add Integer field programmatically (As there is no interface to do this!) #Get all site collections of the provided web application $Web = Get-SPWeb "http://projects.crescent.com/sites/Corp" $ListName = "ProjectBudget" $list = $web.lists[$L
We usually use C# console application or feature activation code to register event receivers with the target list or library in SharePoint. At times, we may have to handle event receiver associations explicitly. Of course, there are some great tools in codeplex (E.g. http://speventreceiverman.codeplex.com/ ) to manage event receivers. However, in a production environment, which didn't allow me to use any such tools for security reasons, I'm left with the option: PowerShell. Hence, I'm sharing my PowerShell code snippets to manage event receivers in SharePoint using PowerShell. Get all event receivers attached with a List: Lets find in SharePoint 2010 PowerShell to get event receivers associated with a particular list. Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Get the web $Web = Get-SPWeb "http://sharepoint.crescent.com" #Get the Target List $List = $Web.Lists["Documents"] #Retrieve all event receivers asso
We must enable NetBIOS for User Profile Service Application in SharePoint when Fully Qualified Domain Name is different than NetBIOS name. Ok. How to find NetBIOS name of your domain? Login to your Domain controller >> Open : Active Directory Users and Computers" (Shortcut: dsa.msc) Right-click on your domain in the left pane and choose "Properties" Under "General" tab, Your domain name and NetBIOS names will be listed. Your domain’s NetBIOS name is the domain name (pre-Windows 2000). What's the problem if its not enabled? Inconsistency in SAMAccountName field which could lead to many other issues such as: Some features may not work due to this inconsistency (Instead of "YourCompanyName\User" it could be "YourComp\user") , UPS Field mappings such as "Manager" field may go wrong, etc. Enable NetBIOS Name for User Profile Service Application: So, You find your NetBIOS name is different from Domain name and wan
"Getting Started" tiles are new addition to SharePoint 2013 team sites. These tiles intend to provide shortcuts to common actions, such as sharing your site, applying a theme. In SharePoint 2013, They replaces the “Getting Started” links from its previous version: SharePoint 2010. Disable Getting Started Web Part: From the home page you can remove this web part by simply clicking on "REMOVE THIS" link as shown in the above image. But it remains in the gallery in the event you would like to have it added back to the site. Just edit the page >> Insert >> Web Part >> Choose "Getting Started with your site" under "Media and Content" group, to add it back to your home page. You can also find "Getting Started" link which is pointing to "GettingStarted.aspx" page under site action menu in SharePoint 2013. This feature is automatically activated with the team site in SharePoint 2013. You can disable Getting
Requirement: For a file upload issue troubleshooting, had to call SharePoint web services to Upload a file into SharePoint document library. Upload File to SharePoint Library using Web Services - PowerShell Here is my PowerShell script to upload file to SharePoint document library using web services: $SourceFile = "D:\Reports\MonthlyRpt-Jan14.csv" $DestinationPath ="http://operations.crescent.com/Reports/MonthlyRpt-Jan14.csv" $WebServiceURL = "http://operations.crescent.com/_vti_bin/copy.asmx?WSDL" $CopyWebService = new-WebServiceProxy -Uri $WebServiceURL -UseDefaultCredential #For custom Credentials, use: #$Cred = New-Object System.Management.Automation.PSCredential -ArgumentList @($UserName,$SecurePasssword) #$UserName = "Domain\UserName" #$Password = "PASSWORD" #$SecurePasssword = ConvertTo-SecureString -String $Password -AsPlainText -Force #$CopyWebService= new-WebServiceProxy -Uri $WebServiceURL -Credential $cred #Get
If you want to upload file to SharePoint document library from client side (or remotely), Here is the nifty PowerShell code snippet. Upload File to SharePoint using Web Client PowerShell: #Variable for Source folder in Local machine & Destination in SharePoint $Source ="c:\temp\file.pdf" $Target="https://portal.crescent.com/projects/Documents/File.pdf" #Create new web client object $WebClient = new-object System.Net.WebClient $Webclient.UseDefaultCredentials = $true #upload file to sharepoint using webclient $WebClient.UploadFile($Target,"PUT", $Source) Upload All Files in a Folder to SharePoint - Web Client HTTP put method: #Variable for Source folder in Local machine $FilesLocation ="D:\Scripts\Reports\" $TargetLocation="http://Operations.Crescent.com/Reports/" #Create new web client object $WebClient = new-object System.Net.WebClient $WebClient.Credentials = [System.Net.CredentialCache]::DefaultCredentials #Use these
SharePoint doesn't provide a direct way to create alerts for groups. Alerts are always targeted to individual user accounts in SharePoint. If you have a requirement to create alerts for a group of people, create a E-mail enabled AD security group and add alert to it from SharePoint. Set alert to group in SharePoint using PowerShell: Alternatively, You can use PowerShell to create a SharePoint alert for a group. Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Variables to create group alert $WebURL="http://intranet.crescent.com/sites/sales/" $GroupName="Sales Auditors" $ListName="Documents" #Get the objects $Web = Get-SPWeb $WebURL $Group = $web.Groups[$GroupName] $List = $web.Lists[$ListName] #Loop throgh each user in the group and create new alert foreach ($user in $group.Users) { #sharepoint set alert to group $alert = $user.Alerts.Add() $alert.Title = "New Sales Proposal Alert" $ale
In SharePoint 2007, You can't save a list or site template (.stp ) file which is bigger than 10MB. MOSS 2007 gives an error message: " The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes. " When you try to save a list or site which by including its content which is more than 10 MB. Fix is simple: Just execute this stsadm command line from your SharePoint WFE server. Say, you want to allow site or list template up to 250 MB: stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 262144000 (250 MB) The above STSADM sets the property at farm level. Here the command line takes property value in bytes. Technically SharePoint compresses all content and saves with .stp extension, which can be simply renamed to .cab and extracted. SharePoint 2010 list template size limit: In SharePoint 2010 and in SharePoint 2013, list template size limit has been raised to 50MB by default. If you have a document li
Requirement: Delete a list template in SharePoint How to delete a list template SharePoint? To remove list template in SharePoint, Login to your SharePoint site collection (List templates are scoped at site collection level) >> Click on Settings >> Site Settings On Site Settings Page, Click on "List Templates" under Web Designer Galleries (http://yoursite.com/_catalogs/lt) Select the list template to delete and click on "Delete Document" from the ribbon Confirm the prompt to delete custom list template in SharePoint. Delete list template in SharePoint 2013 using PowerShell Here is how to delete SharePoint list templates using PowerShell script: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Variables for Site URL and List template name $SiteURL="http://intranet.crescent.com/sites/sales/" $ListTemplateName ="Project Health.stp" #Get Site and List Template Folder objects $site = Get-SPSite
Requirement: Copy Attachments from SharePoint List to Document Library Solution: SharePoint keeps attachments under "List >> Attachments >> 'List Item ID'" folder path. So, if you want to copy attachment from list to document library, follow these steps: Open your SharePoint site from SharePoint Designer Navigate to "All Files" view >> Lists >> Your Source List >> Attachments folder. Here, folders are created based on list item's ID. Just copy attachment files from these folders and navigate to the target document library and paste there. Well, it would be tedious to copy list attachment to document library, if you have large number of list items/attachments. So, lets use PowerShell in SharePoint to copy list attachment to document library. PowerShell script to copy attachment from list to document library: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue $WebURL = "http://share
Copy Attachment from SharePoint List to Document Library using SharePoint Designer - PowerShell
Reviewed by Salaudeen Rajack
on
February 01, 2014
Rating: 5
Recently, We patched one of our SharePoint 2013 environment and ran SharePoint products configuration wizard without any issues. However, we noticed that the server status is still in "Upgrade Available" for SharePoint application & Web front end server from Central Administration > System Settings > Manage servers in this farm page. Ideally the server status should read "No action required" if everything goes good. The "Upgrade available" simply means that there is a newer patch available at the SharePoint Updates page than the one installed on your SharePoint farm. We checked the Farm version and made sure its the latest available version. Tried: psconfig -cmd upgrade -inplace b2b -wait and then restarted servers. Made sure windows updates are up to date on these servers. Solution: Found this issue is related to either some of the content databases/sites which still needs upgrade! Run: stsadm -o localupgradestatus from any of your s
What is Proxy Group in SharePoint? SharePoint 2016 groups service applications together for consumption of the web application through proxy groups. These are simply groupings of service applications that you can deploy to different web applications. In other words, A proxy group is a link between a web application and service application proxies. Default proxy group in SharePoint 2013 SharePoint Proxy groups associates service application proxies with Web Applications. By default, SharePoint creates a proxy group called "Default" and adds new service applications to "Default Proxy Group" when created via SharePoint central administration. A Service Application Proxy can be associated with multiple Proxy Groups using PowerShell. Similarly, a Proxy Group is NOT required to host all available Service Applications within the farm. You can get the available proxy groups by going to Central Admin >> Application Management >> Manage Web Applications >
Problem: A faulty solution installed on the SharePoint farm created duplicate lists in all sites in a large site collection with 100+ sites in it. We had to remove them all! To delete a list from SharePoint, from the browser, we can go to: View All Site Content >> Click on "Remove" link from the context menu of the list. Alternatively, You can get into List Settings >> click on "Delete this list" to remove a list in SharePoint. However, There are 100+ sites where a particular list needs to be deleted. Solution: Delete SharePoint list using PowerShell PowerShell command to delete list in SharePoint: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue #Site collection URL $SiteUrl="http://your-sharepoint-site" $ListName = "List-Name-To-Delete" #Get Web and List objects $web = Get-SPWeb $SiteURL $list = $web.Lists[$ListName] #Reset the "Allow Deletion" Flag $list.AllowDeletion = $true $list
Reviewed by Salaudeen Rajack
on
February 28, 2014
Rating:
