Lock Site Collection or make a it read-only in SharePoint

If you are planning to migrate a site collection in SharePoint to a newer version or simply lock site collection for some maintenance, you can do it through Central Administration. Remember this is possible only at site collection level.

Go to Central Admin -> Select Application Management -> Under Site Collections select Configure quotas and locks

Configure quotas and locks

By default it says site collection is not locked. You have the following options availablelock site collection

  • Adding content prevented – prevents users from adding new content, old content can still be accessed and edited
  • Read-only(blocks additions, updates and deletions)
  • No access – prevents access for every user. Even for site collection admin. Use this if you want to lock site collection.

You also have quotas setting available here to set max storage email alert settings.

This setting can be accessed at same location in Central admin for SharePoint 2010 and 2013. In MOSS 2007 it is available at32
Central Admin -> Application Management – Under SharePoint Site Management select Site collection quotas and locks

Article from: http://sharepointviews.com/lock-site-collection-or-make-it-read-only-in-sharepoint/

How to Export a ALL SharePoint User List to Excel

We almost all faced this question from our users, “can you extract me the list of accounts we have in our site collection?”.

You can easily display the list of users by going in Site Actions > Site Settings > People And Groups, but there is no easy way under WSS 3.0, MOSS 2007, SharePoint Foundation and Server 2010 to export user list.

Here is the trick to export the list of users:

  1. The following url will make the extraction:


You just need to replace the [site], [LISTID] and [VIEWID]. You may guess what [site] is 🙂

  1. To get the other elements, go on Site Actions > Site Settings > People and Groups and click on All People on the quick launch.
  1. Go to Settings > List Settings
  1. Go down to Views section and click on List View. This will bring you to the Edit List page.
  1. If you check on the page url, you can identify the “List=” and “View=”. Copy those ID’s and replace placeholders on the url given in step one.
  1. Navigate to this created url. You will be prompted to open or save the Internet Query Fileiqy file that can be opened with Excel.

Note that this technique is not only limited to the user list, you can use it with any other list.

Article from: http://www.jeremycottino.com/2012/10/how-to-export-sharepoint-2007-user-list.html

How to revive your Windows 10 installation with System Image Recovery

Your hard disk just went belly up, but all is not lost. Armed with a recent system image and the System Image Recovery tool, you’ll be back in business before you know it.

In a recent series of blog posts, I’ve shown you how to reset your Windows 10 system using the Keep My Files option and the Remove Everything option. While the latter will allow you to essentially start from scratch and the former will allow you to install a new copy of the operating system while retaining your data, you may also want to create a backup of your full system—data and applications—just in case you encounter a catastrophic hard disk failure. If you do, you’ll be glad to know that the tried-and-true System Image tool still exists in Windows 10. As long as you have created a system image of your hard disk, you can use the System Image Recovery tool from the Recovery Drive to restore your entire system in the event of a hard disk failure. In other words, if your hard disk goes south, you can purchase a new one and use the System Image Recovery tool to restore your system to the state it was in when you created the image.

Now, keep in mind that for this type of backup to be truly effective, you need to regularly create new system images so that you’ll have a recent version of your system if you need to recover it.

In this article I’ll show you how to use the System Image Recovery tool from the Recovery Drive to restore your hard disk. As I do, I’ll show you how to create a system image on an external hard drive.

What you need

To run the System Image Recovery tool as I’ll describe in this article, you’ll need to have created a Recovery Drive as I showed you in the article Be prepared: Create a Windows 10 Recovery Drive. You’ll also need an external drive or a set of optical discs on which to create a system image of your hard disk. (Unfortunately, you can’t create a system image on a USB flash drive.)

You can find 1TB and 2TB external hard disks in brick-and-mortar and online computer stores for under $100. For example, at the time of this writing, you can pick up a Seagate 1TB external USB hard drive at Best Buy for $59.99 or a Western Digital 1TB external USB hard drive on Amazon Prime for $53.99.

For this article, I’m using a Seagate FreeAgent GoFlex Desk 1 TB USB 3.0 External Hard Drive, which I picked up Best Buy several years ago.

Creating a system image

As I mentioned, to use the System Image Recovery tool you must have created a system image of your hard disk. So I’ll begin by walking you through that process.

To create a system image in Windows 10, you’ll start by accessing the Backup And Restore (Windows 7) tool. To do so, select Settings from the Start Menu/Screen. When the Settings screen appears, select the Update And Security tile, choose the Backup tab, and select Go To Backup And Restore (Windows 7), as shown in Figure A.

Figure A

Figure A
Accessing the Backup tab from the Start screen is easy.

In a moment, you’ll see the Windows Backup And Restore (Windows 7) tool. Select the Create A System Image command on the left side of the screen, as shown in Figure B.

Figure B

Figure B
Select the Create A System Image command to get started.

When the first screen in the Create A System Image wizard appears, you will need to choose where to create the system image. For my example, I am going to create the system image on an external hard disk, so I selected the On A Hard Disk option, as shown in Figure C.

Figure C

Figure C
On my test system, I’ll create the system image on an external hard disk.

Click Next, and you’ll be prompted to confirm your backup settings, as shown in Figure D. On this system, two other sections of data will be backed up in addition to the main partition: the EFI System Partition and the Windows Recovery Environment (System). As you can see, the system is indicating that the image will take up 50 GB of space.

Figure D

Figure D
The Confirm Your Backup Settings page shows you which drives will be backed up.

When you’re ready, click the Start Backup button and the backup operation will commence, as shown in Figure E.

Figure E

Figure E
Click the Start Backup button to launch the backup operation.

Once the backup is complete, click the Close button. Now that you have a System Image backup, you’re ready for an emergency situation.

Launching System Image Recovery

In the case of a hard drive failure, you can restore Windows 10 by running the System Image Recovery tool from the Recovery Drive. After your system boots from the Recovery Drive, connect your external hard drive containing the system image backup. When you get to the Choose An Option screen, select the Troubleshoot tile as shown in Figure F.

Figure F

Figure F
When you are prompted to choose an option, select the Troubleshoot tile.

From the Troubleshoot screen, shown in Figure G, select the Advanced Options tile.

Figure G

Figure G
From the Troubleshoot screen, select the Advanced Options tile.

When the Advanced Options screen appears, select the System Image Recovery tile as shown in Figure H.

Figure H

Figure H
From the Advanced options screen, select the System Image Recovery tile.

At this point, you’ll be prompted to choose the operating system that you want to recover, as shown in Figure I. It may seem redundant to select the OS when performing a system image recovery operation, but you must click the Windows 10 tile to get started.

Figure I

Figure I
Click the Windows 10 tile to start the recovery process.

The recovery process

As soon as you click the Windows 10 tile, you’ll see the Re-image Your Computer wizard. The tool will immediately locate the external hard disk containing the system image, as shown in Figure J. To continue, click Next.

Figure J

The Re-image Your Computer wizard will locate the external hard disk.

The Re-Image Your Computer wizard will now open the screen shown in Figure K. This screen provides several options.

Figure K

Figure K
The second screen in the Re-Image Your Computer wizard provides you with a number of options.

If you’re restoring to the same hard disk, you don’t need to select the Format And Repartition Disks check box. (For my example, I selected the check box just to see whether that changed the process in any way. Other than possibly adding a little time, the steps and the end result were the same.)

If you’re restoring to a new hard disk, chances are that the Format And Repartition Disks check box will be selected by default and will be unavailable. If that is the case, there is nothing to worry about as long as the new hard disk is of the same or greater capacity than the old one.

If you have multiple drives you can click the Exclude Disks button and choose the drive(s) you want to leave untouched. You can also click the Advanced button to open a dialog box that offers two additional options. The Automatically Restart check box will be selected by default and you can choose to enable a disk check operation as a part of the procedure. (If the options in this dialog box are unavailable, you may have to install drivers for the disks you’re restoring by clicking the Install Drivers button.)

When you click Next, you’ll see the confirmation screen of the Re-Image Your Computer wizard, as shown in Figure L. To continue, just click Finish.

Figure L

Figure L
To complete the Re-Image Your Computer wizard, just click Finish

Almost there. But we still have to work through one more confirmation, shown in Figure M. Just click Yes to get started.

Figure M

Figure M
Click Yes in the final confirmation dialog box.

In a moment, the restore operation will begin and you’ll see a progress bar that keeps you apprised of the status of the restore operation, as shown in Figure N. Depending on how big your hard disk is, the restore operation can take a few hours.

Figure N

Figure N
A progress bar shows the status of the restore operation.

When the restore operation is complete, you’ll be prompted to click the Restart Now button. If you happen to be away from your desk when this occurs, your system will restart on its own, as shown in Figure O.

Figure O

Figure O
If you’re not at your desk when the restore operation is complete, your system will restart on its own.

When, your system restarts, you’ll see the familiar logon screen.

What’s your take?

Now that you know how a System Image Recovery procedure works in Windows 10, you will be prepared if you ever need to restore your computer. Have you have performed a System Image Recovery procedure before? if so, what was your experience? Share your comments and advice with fellow TechRepublic members.







Article from: https://www.techrepublic.com/article/how-to-revive-your-windows-10-installation-with-system-image-recovery/

Step-by-Step Configure SharePoint Incoming Email

First, Install SMTP Server


  • Verify that the user account performing this procedure is a member of the Administrators group on the front-end web server.
  • Open Server Manager.
  • In Server Manager, click Add Roles and Features.
  • Click Next to skip role in installation
  • On the Features screen, select SMTP Server




  • In the Add Roles and Features Wizard dialog box, click Add Features, and then click Next.




  • On the Confirm Installation Selection page, click Install.
  • On the Installation Results page, ensure that the installation finished successfully, and then click Close.


Configure SMTP Server


  • Open Internet Information Services (IIS) 6.0 Manager.
  • In IIS Manager, expand the server name that contains the SMTP server that you want to configure.
  • Right-click the SMTP virtual server that you want to configure, and then click Start.
  • Right-click the SMTP virtual server that you want to configure, and then click Properties.
  • On the Access tab, in the Access control area, click Authentication.
  • In the Authentication dialog box, verify that Anonymous access is selected.

Click OK.

  • On the Access tab, in the Relay restrictions area, click Relay.
  • To enable relaying from any server, click All except the list below.
  • To accept relaying from one or more specific servers, follow these steps:
    • Click Only the list below.
    • Click Add, and then add servers one at a time by IP address, or in groups by using a subnet or domain.
    • Click OK to close the Computer dialog box.
    • Click OK to close the Relay Restrictions dialog box.
    • Click OK to close the Properties dialog box.


Set SMTP Service to start Automatically


  • Open Services.
  • In Services, right-click Simple Mail Transfer Protocol (SMTP), and then select Properties.
  • In the Simple Mail Transfer Protocol (SMTP) Properties dialog box, on the General tab, in the Startup type list, select Automatic.
  • Click OK.


Create an OU in AD DS


  • Verify that the user account that is performing this procedure is a member of the Domain Administrators group or a delegated authority for domain administration on the domain controller that is running DNS Manager.
  • Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  • In Active Directory Users and Computers, right-click the folder for the second-level domain that contains your server farm, point to New, and then click Organizational Unit.

Type the name of the OU, and then click OK. In my scenario, I used the name as “SharePoint Contacts


Delegate Permission to Create and Delete all child objects


  • Verify that the user account that is performing this procedure is a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration.
  • Right-click the OU, and then click Delegate control.
  • In the Delegation of Control Wizard, click Next.


  • Click Add, and then type the name of the application pool identity account for Central Administration.
  • Click OK.
  • Click Next.

clip_image0044On the Tasks to Delegate page of the Delegation of Control Wizard, select Create a custom task to delegate, and then click Next.

  • Click This folder, existing objects in this folder, and creation of new objects in this folder, and then click Next.
  • In the Permissions section, select Create all Child Objects and Delete all Child Objects.
  • Click Next.



  • On the last page of the Delegation of Control Wizard, click Finish to exit the wizard.


Create Send Connector in Exchange Server


clip_image0064Browse to Exchange Control Panel https://ExchangeServer/ecp (Both my SQL and Exchange runs on same server).

Click on Mail Flow then Send Connectors.

Click on New Send Connector Icon and give it meaningful name and choose Internal.clip_image0074

  • Choose “Route mail through smart hosts” and click on Add and provide SharePoint Server FQDN.clip_image0084



    Choose None as the Authentication method.


  • Provide the FQDN of the SharePoint Server where SMTP role is installed and click on Save and then Next.

clip_image0114clip_image0124On the Source Server screen add the exchange server and click Finish



  • status shows as Enabled.




  • On the Source Server screen add the exchange server and click Finish.






  • Ensure that the Connector status shows as Enabled.




Configure SharePoint Incoming Email


  • Make sure Microsoft SharePoint Incoming Email service is started. If it has stopped, Start the service.




Then in Central administration System Settings > Configure Incoming Email Settings set the settings as below.

  • Settings Mode: Advanced
  • Directory Management Service: Yes
  • AD Container: OU=SharePoint Contacts, DC=AD2012, DC=Loc
  • SMTP Server: FQDN of the Front End Server: SP2013Srv.AD2012.Loc






Configure Document Library to Receive Email


  • Browse to a library > Library Settings > Incoming Email Settings to enable.




  • Under Document Library Settings you can check the mail address.




  • You can see that it works.





Article from: blog.techoneglobal.com/step-by-step-configure-sharepoint-incoming-email/

Introduction to PowerShell Scheduled Jobs

Microsoft Scripting Guy, Ed Wilson, is here. In all the hubbub about all the great features introduced in Windows PowerShell 3.0, one (actually more than one) feature was somewhat overlooked. With Windows PowerShell 3.0 bringing features such as workflow, PowerShell Web Access, support for disconnected sessions, CIM cmdlets, updatable Help, module auto loading, and improved Windows PowerShell ISE, it was really understandable that the scheduled job feature was simply overlooked by nearly everyone. This is not because the feature is bad—it is just that all the other way cool stuff left little room on the plate of the average IT pro.

Note  I have written quite a bit about scheduled tasks and Windows PowerShell over the years. I have written about the classic scheduled tasks and the newer task scheduler. For more information, see this collection of blog posts.

It’s a job, it’s a scheduled task…

Windows PowerShell scheduled jobs rely on the background jobs feature that was introduced in Windows PowerShell 2.0. But unlike a plain old background job, Windows PowerShell 3.0 added the ability to schedule the background job. This makes Windows PowerShell scheduled jobs like a cross between a Windows PowerShell background job and Task Scheduler tasks.

Because Windows PowerShell scheduled jobs are, at their very heart, background jobs, it means that they run asynchronously in the background. It also means that I can use the *job cmdlets to manage Windows PowerShell scheduled jobs. Thereby, I protect my investment in learning Windows PowerShell in the first place. Start-Job, Get-Job, Stop-Job, and Receive-Job can be used to manage the Windows PowerShell scheduled jobs.

In addition to the generic *job cmdlets, Windows PowerShell 3.0 introduces a PSScheduledJob module that contains the following 16 cmdlets:

PS C:\> Get-Command -Module PSScheduledJob | sort verb

CommandType     Name                                               ModuleName

———–     —-                                               ———-

Cmdlet          Add-JobTrigger                                     PSScheduledJob

Cmdlet          Disable-ScheduledJob                               PSScheduledJob

Cmdlet          Disable-JobTrigger                                 PSScheduledJob

Cmdlet          Enable-ScheduledJob                                PSScheduledJob

Cmdlet          Enable-JobTrigger                                  PSScheduledJob

Cmdlet          Get-ScheduledJobOption                             PSScheduledJob

Cmdlet          Get-ScheduledJob                                   PSScheduledJob

Cmdlet          Get-JobTrigger                                     PSScheduledJob

Cmdlet          New-ScheduledJobOption                             PSScheduledJob

Cmdlet          New-JobTrigger                                     PSScheduledJob

Cmdlet          Register-ScheduledJob                              PSScheduledJob

Cmdlet          Remove-JobTrigger                                  PSScheduledJob

Cmdlet          Set-ScheduledJobOption                             PSScheduledJob

Cmdlet          Set-ScheduledJob                                   PSScheduledJob

Cmdlet          Set-JobTrigger                                     PSScheduledJob

Cmdlet          Unregister-ScheduledJob                            PSScheduledJob

So, how does it work (or step-by-step)

Using the Windows PowerShell scheduled job cmdlets to create a scheduled job involves the following steps:

  1. Decide when to run the scheduled job.
  2. Decide how often to run the scheduled job.
  3. Decide what command to run.
  4. Create and configure the scheduled job.

Note  To create and schedule a Windows PowerShell scheduled job requires elevated permissions.

I create a trigger, but when I try to register the scheduled job, if I have not opened Windows PowerShell with admin rights, the following error message appears:

Image of error message

To launch with admin rights, right-click the Windows PowerShell icon and click Run as Administrator. The menu is shown in the following image:

Image of menu

After I open the Windows PowerShell console with admin rights, I create the trigger, and I register the scheduled job. The script to do this is:

$trigger = New-JobTrigger -Once -At 13:45

Register-ScheduledJob -Name GPS -Trigger $trigger -ScriptBlock {GPS}

This time, the command returns a ScheduledJobDefinition object. This object contains the name of the scheduled job, the job trigger, job ID, and the command itself. The command and the returned object are shown in the following image:

Image of command output

I can now use the Get-ScheduledJob cmdlet to check the status of the scheduled job as shown here:

PS C:\> Get-ScheduledJob -Id 1

Id         Name       JobTriggers     Command            Enabled

—         —-            ———–        ——-                    —–

1          GPS             1               GPS                             True

If I want to see what job options were used when creating the scheduled job, I use the Get-ScheduledJobOption cmdlet. This command and associated output are shown here:

PS C:\> Get-ScheduledJobOption -Id 1

StartIfOnBatteries     : False

StopIfGoingOnBatteries : True

WakeToRun              : False

StartIfNotIdle         : True

StopIfGoingOffIdle     : False

RestartOnIdleResume    : False

IdleDuration           : 00:10:00

IdleTimeout            : 01:00:00

ShowInTaskScheduler    : True

RunElevated            : False

RunWithoutNetwork      : True

DoNotAllowDemandStart  : False

MultipleInstancePolicy : IgnoreNew

JobDefinition          : Microsoft.PowerShell.ScheduledJob.ScheduledJobDefinition

If I want to see what trigger was used for the scheduled job, I first get the scheduled job, and then I pipe it to the Get-JobTrigger cmdlet. This command is shown here:

PS C:\> Get-ScheduledJob -Id 1 | Get-JobTrigger

Id         Frequency       Time                   DaysOfWeek              Enabled

—         ———       —-                   ———-              ——-

1          Once            5/8/2014 1:45:00 PM                            True

To see if the job ran, I use the Get-Job cmdlet as shown here:

PS C:\> get-job

Id     Name            PSJobTypeName   State         HasMoreData     Location

—     —-            ————-   —–         ———–     ——–

2      GPS             PSScheduledJob  Completed     True            localhost

3      GPS1            PSScheduledJob  Completed     True            localhost

I see there are two jobs that completed. So I look at the first job. Notice that this number is a different ID number than the one I received from Get-ScheduledJob:

PS C:\> get-job -Id 2

Id     Name            PSJobTypeName   State         HasMoreData     Location

—     —-            ————-   —–         ———–     ——–

2      GPS             PSScheduledJob  Completed     True            localhost

To receive the results of the job, I use the Receive-Job cmdlet. To keep the results, I use the –Keep parameter. This will enable me to look at the results a second time. If I do not use the –Keep parameter, I will not be able to see the results a second time (unless I store the results in a variable or some other mechanism).

Receive-Job -Id 2 -Keep

The command and the output from the command are shown here:

Image of command output

That is all there is to playing around with Windows PowerShell scheduled jobs. Scheduled Job Week will continue tomorrow when I will talk about more cool stuff.

Article from: https://blogs.technet.microsoft.com/heyscriptingguy/2014/05/12/introduction-to-powershell-scheduled-jobs/

SharePoint 2013: Site in Read only mode after an interrupted backup using Backup-SpSite

I came across an interesting issue recently where a customer was backing up a site collection via SharePoint Management shell using the Backup-spsite.  The backup process was abnormally terminated. This resulted in the Site being in Read only mode and the following message would show up when users browsed to the site.

“We apologize for any inconvenience, but we’ve made the site read only while we’re making some improvements.”


Possible Solutions:

Under Site Collection Quotas and locks, set the database back to Not locked and save your settings which didn’t work for me.

You can also run the following command in powershell to set this attribute:

stsadm -o setsitelock -url http://server_name -lock none which didn’t work for me.

Go to “Site collection Quota & locks” in Central Admin and here is how the Status looks like. It is locked as “Read only” & all settings were grayed out. So I couldn’t select the Not Locked option.

If you are running an older version try this solution.  Another method has worked for me in Central Administration >Quotas & Locks apply (or in this case re-apply) the option to lock the file or even no access and then toggle it back to unlock and it has worked for me to release the file back to read/write mode


Solution: Here is more on this behavior & how to get out of this situation which ONLY worked for me

In SharePoint 2013, we introduced a property MaintenanceMode for Spsite object which indicates the site is undergoing a Maintenance & is read only. SPSite.MaintenanceMode flag can be set on a site for several reasons like content database is in read only state, or site collection is being upgraded, backed up or moved.

If a site gets into a state where the action that set this has terminated in a way where this is still set, we run into this situation.

The way to clear this flag is use the ClearMaintenanceMode method in SpSiteAdministration object. Here is how it can be done via SharePoint Management Shell


# $Admin = new-object Microsoft.SharePoint.Administration.SPSiteAdministration(‘http://weburl/sites/sitecollectionurl’)



The SpsiteAdministration.ClearMaintenanceMode method was introduced in April 2013 CU for SharePoint 2013. So you would need to upgrade the environment to March 2013 & April 2013 update available at Update Center for SharePoint 2013

Article from: https://blogs.msdn.microsoft.com/spses/2013/05/16/sharepoint-2013-site-in-read-only-mode-after-an-interrupted-backup/

Error: Search encountered problem that prevents results from being returned


Had a problem today with a search issue:

I tried to stop and restart the search service

net stop osearch15

net start osearch15

But that didn’t work

I then went to checked Central admin -> Service applications – > Search Service application for status on search components and I noticed an RED X next to query processing

So I rebooted the search server and then everything was back and running again.  Note you need to REFRESH the page and then you will get the new green status.

Aside: Yesterday, I got a request to check on one our SharePoint 2013 applications which has not been modified in last couple of months. The users were getting an error related to search…

Search has encountered a problem that prevents results from being returned. If the issue persists, please contact your administrator.

Correlation ID: 85a0bd9c-3615-f0f4-b26f-38cd545f34eb

Below are the debugging steps for such an error message:

1) Looked up the correlation id in ULS logs and found an error related to query processing
Saw an error related toaccess denied for the crawler account ( I knew this was not correct because we did not update or change any security related to this account)
2) Looked up event viewer for any error messages and the below showed up
w3wp.exe: All query processing components are in ‘Failed’ status.
w3wp.exe: Query processing component ‘net.tcp://nameoftheserver/D30C5C/QueryProcessingComponent1/ImsQueryInternal’ changes its status to ‘Failed’.
3) Checked Central admin -> Service applications – > Search Service application for status on search components
4) Notice an yellow exclamation mark next to query processing
5) Restarted SharePoint Administration, SharePoint Timer Service and SharePoint Administration services through services mmc
6) Went back to Central administration to see if the exclamation mark was gone. Nope. Was still there.
7) Went back to services and restarted the Search Host Controller service
8) Opened command prompt and ran the below commands
net stop osearch15
net start osearch15
9) Went back to Central admin and refreshed the search application page
10) Saw exclamation marks on all Search related components – did not feel good at this point
11) Refreshed the page and saw that each of the components were turning green now – felt better at this point
12) After few minutes all components were in green – felt really good at this point
13) Went to the actual site and performed a search – results came back and problem solved

If you see error messages related to search, do not reset the index or re-provision the search application. Sometimes a simple reboot might actually fix the problem.

Find an item Search Box has disappeared in a SharePoint 2013 Web Part

This one was a little frustrating and not altogether obvious, so I thought I’d share the result.

Display Search Box nowhere to be found in a SharePoint 2013 Web Part


SharePoint 2013 has an amazing inline search feature for lists and libraries. I love it and it won’t be long before it is the one thing folks without 2013 moan about… The idea of being able to search within a list or library and not be taken away to a search page but rather show the results, inline with your columns (metadata) is awesomesauce.

It looks like this…


And it is enabled by this…


So What

The problem is, if you have migrated existing libraries with customizations or you have played with views in new SharePoint 2013 libraries, you might have changed the “style” from Default, to something like “Shaded” or one of the other styles (I often chose Shaded to help my users with readability).


As such, if the view is anything but Default, you won’t find this option “Display Search Box” under “Miscellaneous” in your web part (er, app part now…). It will be missing.



Now What

Pretty simple really as I’ve already given the clue up above:”

  • When creating views and you want to display the Search Box, stick with the “Default” Style for your view
  • Or if you have a library you have migrated into SharePoint 2013 that was using anything but “Default”, put it back and you will be good to go




Article from: http://itgroove.net/brainlitter/2012/12/31/display-search-box-nowhere-to-be-found-in-a-sharepoint-2013-web-part/

How to: (Unexpectedly) Block the usage of the list/library search box in SharePoint


SharePoint has a nifty search box above a list or library which can be used to quickly filter items for that library. So how do you make sure it doesn’t work?

Well…. for some reason you might have decided to change the default Result Source for the web or site collection. The why is most likely related to convenience where you have perhaps chosen to include content by some business requirement. All items tagged as “Public” for example with the query template: {searchTerms} category:”Public”


If you now try to search in your list/library you will only get hits if the list has a column named category and items are set to be Public.
And..boom.. your smartness with a new default Result Source has killed local list/library search.


Lessons learned:

  • Leave Local SharePoint Results as the default source – makes your life easier
  • If you want a different result source on your search site or via API, specify the result source explicitly – makes your life easier

Article from: https://www.techmikael.com/2015/03/how-to-unexpectedly-block-usage-of.html


What makes a SharePoint column searchable?

By searchable I mean a user searches for a term, and get a search result if that term exists in a SharePoint column (without specifying a property query). Basically typing keywords in a search box.

By default when you create a SharePoint column on a list, it will generate a crawled property which is marked with Include in full-text index. This checkmark ensures you will get a hit for terms in this column. The naming of the crawled property is ows_internalColumnName.

If you look at managed properties, they have a corresponding property called Searchable. This means if your crawled property is mapped to a managed property marked as searchable, you will get recall on the column. However, if the managed property is not marked as searchable, even though the crawled property is marked with “Include in full-text” index, it will NOT be searchable.

To put it all in a table.

Crawled Property Managed Property
Included in
Full text-index
Not included in
Full text-index
Searchable Not
x x
x x
x x
x x


If a crawled property is mapped to two managed properties, where one of them is searchable, then the value will be searchable.

If a column is hidden or marked via column properties as “NoCrawl”, then it will not be searchable.

If the crawled property is from a number/currencly column, you need to map it to a searchable managed property in order to get full text index recall.


In order to make a column in SharePoint not searchable, you either have to uncheck the option on the corresponding crawled property to include it in the full-text index, or map it to a managed property which is not marked as searchable.

Article from: https://www.techmikael.com/2014/07/what-makes-sharepoint-column-searchable.html