• Office and the Mobile Landscape

    About a year ago we put out a mobility poster covering the SharePoint space. We’ve just released a follow-up that extends into Exchange 2013, Lync 2013, and Office Web Apps 2013. It’s not an exhaustive list of everything available for devices (Windows Phone, iOS, Android). However, it’s a good end-to-end peek at the Office mobile landscape, both Office 365 and on-premises.  Some highlights:

    • Apps/browser-based Mobile Experiences – A selection of downloadable apps and mobile browser views for SharePoint 2013, Exchange 2013, Lync 2013, and Office Web Apps 2013.
    • Mobile Deployments – Some considerations for deploying a mobile infrastructure in your company. Cloud-based and on-premises topologies/guidance for phones and tablets.
    • Device Management/Software Distribution – Windows Intune is a cloud-based management platform for mobile devices. It can either be used by itself, or coupled with System Center 2012 R2 Configuration Manager, to manage your devices.

     

    So again it’s a good look into Office mobility, and ideal for ITPro decision makers needing to know more about Microsoft offerings here. You can get or view a copy of the poster at:

     

     

     

      

    Other Useful Articles for SharePoint Mobility

     

     

     

     

     

  • How to create a Search Center Site Collection and enable crawling of your content in SharePoint 2013

    This is a blog post in the series “Set up a Search Center in SharePoint 2013”. 

    In this blog post, you’ll learn:

      

    How to create a Search Center Site Collection
    To create a Search Center Site Collection, go to Central Administration --> Create site collections, and then enter details for the site collection. Here’s what you need to enter:

    1. A title for the website.
    2. The website’s URL.
    3. Select 2013 for the experience version.
    4. From the Enterprise tab, select Enterprise Search Center.
    5. In the field Primary Site Collection Administration, enter the site admin’s user name.

    Create a Search Center Site Collection

    Now that you have your Search Center Site Collection, you can move on to crawling content.

     

    How to start a full crawl in Central Administration
    Before you can start a full crawl in Central Administration, you have to specify the content source that you want to crawl. When you run a full crawl, all content in the content source is crawled even if that content has already been added to the search index.

    In a scenario where you only have SharePoint content, you can select to crawl the Local SharePoint sites content source.

    1. Go to Central Administration --> Manage service applications --> Search Service Application --> Content Sources.
    2. On the Manage Content Sources page, hover over the Local SharePoint sites content source, and select Start Full Crawl from the menu.

    Start Full Crawl in Central Administration

    The status of the crawl is shown in the Status column.

    1. Refresh this page until you see that the value in the Status column is Idle. That means that the full crawl has finished.

    Idle crawl status

    1. Optionally, you can verify that your items have been added to the search index by clicking Crawl Log.

      In my scenario, I could see that there were 157,297 items in the search index.

    Information in crawl log

     

     How to enable continuous crawls in Central Administration

    By default, content is automatically crawled every 4th hour.  However, when changes are made to your content, you probably would like it to be crawled as soon as possible so that users can find it on the Search Center. Nobody wants to manually start a full crawl every time a change is made to their content, as this is neither an efficient nor practical way to work. So, to avoid this overhead, you can simply enable a continuous crawl of the content source that contains your content.

    Continuous crawls start automatically at 15-minute intervals. Any changes that have been made to your content since the previous crawl are picked up by the crawler and added to the search index.

    To enable continuous crawls:

    1. Go to Central Administration --> Manage service applications --> Search Service Applications --> Content Sources.
    2. On the Managed Content Sources page, click the content source that you want to enable continuous crawl for.

      In my scenario, this was Local SharePoint sites.
    3. Select Enable Continuous Crawls.

    Enable Continuous Crawls in Central Administration

     

    How to set the continuous crawl interval
    The default interval for continuous crawls is 15 minutes. However, you can set shorter intervals by using Windows PowerShell. The code snippet below sets the continuous crawl interval to 1 minute.

    $ssa = Get-SPEnterpriseSearchServiceApplication
    $ssa.SetProperty("ContinuousCrawlInterval", 1)

    So, by enabling continuous crawls, your search index is automatically updated with the latest changes. However, there are some types of changes, for example, if you enable managed properties as refiners (I will show you how to do this in a later blog post), where continuous crawls are not sufficient to update the search index. For these changes to be updated in the search index, you have two options:

    • Do a full crawl.
    • Do something called reindexing.

    The reason why you have two options is that people working with content (let’s call them content managers) are not likely to have Search service application administration level rights, that is, they don’t have access to Central Administration where they can start a full crawl. However, content managers are likely to have Site Owner rights, and Site Owners can do reindexing.

     

    How to reindex a list
    To mark a list or library for reindexing, here’s what to do:

    1. On your list or library click the LIST or LIBRARY tab --> List Settings or Library Settings --> Advanced Settings.
    2. On the Advanced Settings page, click Reindex List or Reindex Document Library.

    Select to Reindex list

    The list will be reindexed during the next scheduled crawl.

    So, all in all, content managers can be happy because their content is added to the search index at short intervals, and Search service application administrators can be happy because they are not bothered by content managers constantly asking them to start a crawl.

    And now that we have done all that “boring” stuff, it is time to move on to the exciting stuff: configuring the Search Center.

     

    Next blog article in this series
    How to configure the Search Results Web Part to use a new result source

  • Set up a Search Center in SharePoint 2013

    A Search Center is a portal where you can search for content on your organization’s intranet. In this blog series we'll help you plan, set up and manage a Search Center in SharePoint 2013. But before we dive into the details, we’ll give you some background information and a few planning tips and tricks.

     

    What’s a Search Center and how do I plan it?

    A Search Center is similar to an internet search page like Bing: it has a starting page where you can enter queries. It has search result pages where you can drill into and refine search results, or you can run a new query.

    On the internet, you want search to be easy, fast, and give you relevant results, and you should expect the same when you’re trying to find information on your company’s intranet. 

    You'll easily get fast and relevant results with the standard Search Center in SharePoint. And if you also have a good understanding of the content on your intranet and know how people will be searching it, you can make your Search Center really shine.

    Throughout this blog series, we’ll use examples from a Search Center that we in the content publishing team in Microsoft use to search for articles and other media that we have published on MSDN, TechNet and Office.com. Because we know the content, and because we know what we want to find and how we want to search for it, we’ve been able to set up the Search Center so that it suits our needs well.

    This is what an empty Search Center looks like, before you start working on it:

    And this is what our content publishing Search Center looks like after we set it up to fit our needs. Here, I've searched for "relevance", just as an example.

     You can see that we get results that show articles that we've published, but you can also see that we have added refiners that are meaningful to us, such as Writer and Editor. We also added several search pages, or search verticals, like Art and Interop. Later, we’ll show you how you can add search verticals and refiners to your Search Center, but before we dive into the practicalities, here are some considerations to help you plan your Search Center.

    What kind of content and information is on your intranet?

    When you think about your intranet, is there content that people probably want to search differently or separate from other content?

    As an example, in our content publishing Search Center we have a separate search vertical to search through the illustrations, or "Art" files, that we use in our articles. So when I want to see if we already have any illustrations of a server farm, I type "server farm" as my query in the search box. On the search results page, I can simply click "Art" to view only the art results for that query.

    Is the content tagged with good and consistent metadata?

    Setting up your Search Center is much easier if content is well organized and consistently tagged with good metadata. It’s often well worth investing time in content quality before you crawl it, so that people can more easily find what they’re looking for in the Search Center.

    In our content publishing Search Center, we work with SharePoint lists. Each content item that we publish, such as an article or an art file, has its own entry on the list. We've made sure that all the entries are consistently tagged with metadata that is important to us, for example to help us determine which product variants an article applies to. For our articles we also have rules around the titles and short descriptions we use. We’re capturing these metadata in site columns and site column values, and we have set up our Search Center so that we can easily use these values to refine on search results and quickly find exactly the information we’re looking for.

    Who works with the intranet content?

    Some content can benefit from being searched separately or differently than other content. Likewise, it is useful to think about the categories of people who search and how their interests differ. For example, if you work in Human Resources and you search for "vacation", you're probably looking for content related to the company's rules and regulations around holidays. If you don't work in HR and you search for "vacation", you probably want to find a SharePoint site where you can log when you're away or use a tool to request a day off.

    You can create search verticals in the Search Center to display subsets of the search results that are of particular interest for certain groups of people, such as teams or departments. Or, you can create separate Search Centers. It all depends on the people who use the intranet in your organization: think about what they are searching for and how you can make it easier for them to find it.

     

    Store most of the content in SharePoint

    It’s an advantage if the content in your intranet is stored in SharePoint, because the SharePoint content source is different from all other types of content sources when it comes to search.

    Site collection administrators have a lot of configuration and management options for content stored in SharePoint, such as adding new managed properties and editing existing ones. If you add a new managed property or make certain changes to it, you have to re-crawl the content. This is where it helps to have content in SharePoint: you can re-index individual SharePoint lists and libraries without having to crawl all SharePoint content.

    Also, the SharePoint content source is the only source that you can crawl continuously. When the content changes, a continuous crawl will pick up the change and you don’t have to wait until the next incremental or full crawl completes.

     

    A few words about how search works

    Before you can show any search results in a Search Center, you have to crawl the content. After crawling, the content and related metadata are processed and stored as managed properties in the search index.
    This is what it looks like under the surface:

    1. Our content is stored in SharePoint 2013 lists and libraries. We use site columns to store metadata about each item.
    2. When we crawl the content and the metadata, the information is processed and added to the search index.
    3. In the search index, managed properties represent the content and metadata that we crawled.
    4. The queries that we enter in our Search Center are sent to the search index, where the system tries to find matching results.
    5. Any matching results are displayed in the Search Result Web Part in the Search Center.

    In the next blog posts in this series, we’ll walk you through how you can set up your own Search Center, using examples from our own experience with the Search Center for content publishers.

    Upcoming blog posts in this series:

    Other blogs and documentation that you may want to read:

     

     


     

     

  • SharePoint Gaining Momentum on Windows Azure

    At the recent SQL PASS Summit, Mark Russinovich (Technical Fellow in the Cloud and Enterprise Division at Microsoft) presented a session titled Windows Azure Deep Dive, featuring SharePoint. His session is a great primer on using Windows Azure IaaS platform to host a SharePoint farm. 

    Fast forward to 1:13:00 for a description of this beautiful poster — Windows Azure: Deploy SharePoint with SQL Server AlwaysOn (Zoom image, PDF). This poster also includes logical architecture illustrations for publishing Internet sites using SharePoint Server 2013 in Windows Azure, including making use of Azure AD for customer accounts.

    Here are some other resources for learning about running SharePoint in Windows Azure. 

    Blogs:

    Blog and scripts: Automating SharePoint Deployments in Windows Azure using PowerShell

    Whitepaper: SharePoint 2013 on Windows Azure Infrastructure Services by David Aiken & Dan Wesley

    Channel 9 Video: SharePoint on Windows Azure with Paul Stubbs

    Now is a great time to let us know what other types of resources you would like to see.

    - Brenda Carter

  • Search Engine Optimization (SEO) in SharePoint Server 2013

    If you're a website owner, you know how important it is that users can easily find your website by using Internet search engines such as Bing or Google. The higher your website is shown in the search results list, the more likely it is that users will click on it. Just think of your own behavior when looking at search results. When was the last time you clicked to view the second page of search results?

    In the white paper, Optimizing SharePoint Server 2013 websites for Internet search engines, you can find out how you can apply SEO features to your SharePoint Server 2013 website, so that Internet search engines will display it high in their search results list. The white paper covers subjects such as:

    • SEO activities that you can do in the planning phase of setting up a new website.
    • New SharePoint Server 2013 SEO features and how you can use them.
    • SEO for websites that use cross-site publishing.
    • How to handle common SEO challenges.

    Edit SEO Properties in SharePoint

     The white paper is written by Waldek Mastykarz, Microsoft SharePoint Server MVP.