Showing posts with label Features. Show all posts
Showing posts with label Features. Show all posts

Tuesday, March 19, 2013

Features deprecated in SharePoint 2013

Visual upgrade : 

The visual upgrade feature in SharePoint Server 2010 is not available in SharePoint 2013. For the upgrade from Office SharePoint Server 2007 to SharePoint Server 2010, you could choose to use the visual upgrade feature to give site collection owners and site owners the opportunity to preserve the previous user interface temporarily while still upgrading the infrastructure and databases, site collections, and features to the latest version. This allowed site collection owners and site owners to update customizations to work in the new user interface. Once the database and site collection upgrade was complete, the user had the option to upgrade the user interface on a more granular level of the website (SPWeb object).

Document Workspace site template

When you create a site in SharePoint 2013, the Document Workspace site template is not available.  The scenario of collaborating on a document is now provided by the Team Site site template. The Document Workspace site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection.

Personalization Site site template

 When you create a site in SharePoint 2013, the Personalization Site site template is not available.  The Personalization Site site template was not a widely used site template. The Personalization Site site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection.

Meeting Workspace site templates


When you create a site in SharePoint 2013, all five of the Meeting Workspace site templates are not available. This includes the Basic Meeting Workspace, Blank Meeting Workspace, Decision Meeting Workspace, Social Meeting Workspace, and Multipage Meeting Workspace. SharePoint 2013 and Office 2013 provide other features that support meetings and collaboration. For example, you can use Lync to conduct live meetings, OneNote to take notes during meetings, and a SharePoint team site or My Site to store shared meeting notes.

Group Work site template and Group Work solution:

When you create a site in SharePoint 2013, the Group Work site template is not available. This Group Work site template provides a groupware solution that teams can use to create, organize, and share information. The Group Work site template includes the Group Calendar, Circulation, Phone-Call Memo, document library, and other basic lists. The Group Work site template and the Group Work solution are discontinued and not available in SharePoint 2013.The Group Work site template was not a widely used site template. The Group Work site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection.

Visio Process Repository site template :

When you create a site in SharePoint 2013, the Visio Process Repository site template will continue to be available. However, the Visio Process Repository site template will be removed in the next major release of SharePoint.The Visio Process Repository site template is not a widely used site template. The Visio Process Repository site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection.

Unghosting and customizing CSS files

The following methods are included in SharePoint 2013, but will be removed from the next major release of SharePoint:
  • Microsoft.SharePoint.SoapServer.Webs.CustomizeCss
  • Microsoft.SharePoint.SoapServer.Webs.RevertCss
The Webs.CustomizeCss method applies style sheet customization to a particular file.
The Webs.RevertCss method reverts style sheet customization of a file to the default style sheet.
These two methods are stored in Webs.asmx.cs and are defined in Webswsdl.asps.

The methods are outdated and are no longer needed

Imaging Web service

The Imaging Web service provides functionality for creating and managing picture libraries. The Imaging Web service will be removed from the next major release of SharePoint. The Imaging Web service is included and supported in SharePoint 2013.The Imaging Web service is not widely used. The only client application for the Imaging Web service, Office Picture Manager, is no longer included with SharePoint 2013. The Imaging Web service is being removed to reduce security vulnerabilities and to simplify the number of ways to connect to SharePoint 2013.

Excel Services — Can't edit workbooks in the browser that have external data connections

Workbooks with external data connections that use Windows authentication cannot be refreshed in the browser. Instead, you are prompted to open the workbook in the Excel client program. Workbooks that have database or Windows credentials stored either in the Secure Store Service or in the connection string can still be edited in the browser. This change applies only when Excel Web App in Office Web Apps Server is used to view workbooks, not when Excel Services in SharePoint Server 2013 is used.

This is a design limitation in SharePoint 2013

Web Analytics in SharePoint Server 2010

Web Analytics in SharePoint Server 2010 has been discontinued and is not available in SharePoint 2013. Analytics processing for SharePoint 2013 is now a component of the Search service.A new analytics system was required for SharePoint 2013 that included improvements in scalability and performance, and that had an infrastructure that encompasses SharePoint Online. The Analytics Processing Component in SharePoint 2013 runs analytics jobs to analyze content in the search index and user actions that are performed on SharePoint sites

Organization Profiles

The Organization Profiles feature is deprecated in SharePoint Server 2013. Organization Profiles contain detailed information about an organization such as teams, divisions, and other information that describes the organization’s hierarchy. SharePoint features related to identities continue to evolve around the core concepts of users and groups, and SharePoint will not be investing further in OrgID.

Some Search features deprecated from Foundation 2010

The search capabilities of SharePoint Foundation 2013 have changed, and are now based on the same search implementation as SharePoint Server. This provides many improvements, but also means that the search configuration is very different.

and in Server 2010. 

 SharePoint 2013 uses the web-based interface to show the current status of the topology. You change the topology by using Windows PowerShell. SharePoint Server 2010 also included a web-based option for changing the topology

The thesaurus replacement mode is deprecated in SharePoint 2013.

Search Query web service 

In SharePoint Server 2010, the Search Query web service exposes the SharePoint Enterprise Search capabilities to client applications. This enables you to access search results from client and web applications outside the context of a SharePoint site.

Search RSS and search from Windows  

The search RSS feature is deprecated in SharePoint 2013. The functionality for performing enterprise searches from Windows 7 depends on search RSS and this element has also been deprecated in SharePoint 2013. The RSS link no longer appears on the results page. This link is replaced by the Search Alerts link.

 Custom word breaker dictionaries

 
The format of the custom word breaker dictionaries has changed in SharePoint 2013. In SharePoint 2013, you can only create one language-independent dictionary. In SharePoint Server 2010, you can create language-specific custom dictionaries (one dictionary for each language) to edit the word breaker behavior of enterprise search. The word breaker behavior for East Asian (CJK) languages has not changed in SharePoint 2013.

Configuration of stemming in the registry

The configuration of stemming in the registry is no longer supported in SharePoint 2013. Modifying stemming entries in the registry has no effect during search. In SharePoint Server 2010, you can turn stemming on or off, or you can replace it with a third-party stemmer by changing the registry. In SharePoint 2013, you cannot use a third-party stemmer.

SharePoint Search SQL syntax

In SharePoint Server 2010, you could construct complex search queries by using SQL syntax. 

Shallow search refiners

SharePoint Server Search in Office 2010 supported shallow search refiners. FAST Search Server 2010 for SharePoint supports shallow refiners and deep refiners. InSharePoint 2013, only deep search refiners are supported.

FAST Search Server 2010 for SharePoint deprecated features

 FAST Search database connector
 
The FAST Search database connector is not supported in SharePoint 2013.

FAST Search Lotus Notes connector

  The FAST Search Lotus Notes connector is not supported in SharePoint 2013.

FAST Search web crawler

The FAST Search web crawler is not supported in SharePoint 2013.
The SharePoint 2013 crawler provides similar functionality to the FAST Search web crawler. 

FAST Query Language (FQL) deprecated features

 The FQL features are aligned with the features of the SharePoint Keyword Query Language (KQL) syntax

URL Query syntax

In FAST Search Server 2010 for SharePoint, the URL-related managed properties (such as site, or path) are tokenized as a text string, and you can query any subpart of the URL. This includes STARTS-WITH, ENDS-WITH, PHRASE and proximity queries on URL properties. Special characters such as “/”, “_” and “-”are handled as word delimiters.
In SharePoint 2013, the entire URL is tokenized as one word. This includes special characters such as “/”, “_” and “-”. You can query these managed properties by:
  • Searching for the full string for the site or path.
  • Searching for the leading part of the site or path.
  • Omitting the protocol part (http, https), and omitting the leading part of the domain address in the query expression, for the site managed property.

    Specific search scope filters

      In SharePoint 2013, search scopes are automatically converted to result sources.

    Anti-phrasing 

      The search anti-phrasing feature in FAST Search Server 2010 for SharePoint is not supported in SharePoint 2013. 

    Offensive content filtering
     
    The filtering of offensive content in search is deprecated in SharePoint 2013.

    Substring search

    The substring search feature was removed in SharePoint 2013.

    Person names and location extractions

    In SharePoint 2013, you cannot extract person names and locations from documents by using predefined extractors.

    Number of custom entity extractors
     
    In SharePoint 2013, the number of custom entity extractors that you can define is limited to 12.

    Supported document formats

    SharePoint 2013 no longer supports rarely used and older document formats that are supported in FAST Search Server 2010 for SharePoint by enabling the Advanced Filter Pack. Both the ULS logs and the crawl log indicate the items that were not crawled.
    In SharePoint 2013, the set of supported formats that are enabled by default is extended, and the quality of document parsing for these formats has improved.

    Content processing extensibility

    The FAST Search Server 2010 for SharePoint content processing extensibility feature has changed in SharePoint 2013. Content processing prepares an item from a content source for indexing and searching. The FAST Search Server 2010 for SharePoint content processing extensibility feature uses a sandbox where your custom code runs. 

    Custom XML item processing

    FAST Search Server 2010 for SharePoint includes a custom XML item processing feature as part of the content processing pipeline. Custom XML item processing is not supported in SharePoint 2013.

    Adding a test item to the index 

    DocPush is a test and diagnostic command-line tool that submits test documents to the FAST Search Server 2010 for SharePoint index. A similar command-line tool is not available in SharePoint 2013 
http://technet.microsoft.com/en-in/library/ff607742.aspx#section2

Monday, January 21, 2013

Sharepoint 2010 Search from the Administrative prospective

New features and functionality for administrators

SharePoint Server 2010 includes new ways for administrators to help provide the most benefits for end users who are searching for information.

Improved administrative interface

SharePoint Server 2010 has the new Central Administration interface that was first available for organizations that deployed Office SharePoint Server 2007 and then installed the Infrastructure Update for Microsoft Office Servers. This new interface centralizes the location for performing administrative tasks. With SharePoint Server 2010, administrators have an interface that provides the following advantages:

    A single starting point for all farm-wide administration tasks, including search administration. The most common search tasks are highlighted.

    A central location where farm administrators and search administrators can monitor server status and activity.

Farm Configuration Wizard

The Farm Configuration Wizard runs automatically after a Server Farm installation finishes. This wizard helps simplify deployment of small farms. It provides the option to automate much of the initial configuration process with default settings. For example, when you use the Farm Configuration Wizard to deploy the first server in a farm, the wizard automatically creates a fully functional search system on that server, which includes:

    A search topology that can support an index of up to 100 million crawled documents.

    A Search Center from which users can issue queries. This Search Center is created automatically if the person installing the product selects this option in the wizard.

The search system can crawl local SharePoint sites (sites in the server farm) immediately after the Farm Configuration Wizard finishes running.
Search service administration independent of other shared services

In Microsoft Office SharePoint Server 2007, the Office SharePoint Server Search service was bundled with other shared services (such as Excel Calculation Services) in the Shared Services Provider (SSP). In that architecture, you could not create a new Search service without creating a new SSP. In contrast, in SharePoint Server 2010, you can create and manage Search service applications independently of one another and independently of other service applications.
Expanded support for automating administrative tasks

You can automate many search administration tasks by using Windows PowerShell 2.0 scripts. For example, you can use Windows PowerShell 2.0 scripts to manage content sources and search system topology.
Increased performance, capacity, and reliability

SharePoint Server provides many new ways to configure and optimize a search solution for better performance, capacity, and reliability.
Scalability for increased crawling capability

You can increase the number of crawl components to do the following:

    Increase crawl frequency and volume, which helps the search system to provide more comprehensive and up-to-date results.

    Increase performance by distributing the crawl load.

    Provide redundancy if a particular server fails.

Index partitioning enables subsecond latency over an index that contains up to 100 million items, depending on the item sizes and types and other factors.
Scalability for increased throughput and reduced latency

You can increase the number of query components to do the following:

    Increase query throughput — that is, increase the number of queries that the search system can handle at a time.

    Reduce query latency — that is, reduce the amount of time it takes to retrieve search results.

    Provide failover capability for query components.

Topology management during normal operations

You can tune the existing search topology during regular farm operations while search functionality remains available to users. For example, during usual operations, you can deploy additional index partitions and query components to accommodate changing conditions.
Operations management

SharePoint Server 2010 provides new capabilities for monitoring farm operations and customizing reports.
Health and performance monitoring

Health and performance monitoring features enable an administrator to monitor search operations in the farm. This can be especially helpful for monitoring crawl status and query performance.

SharePoint Server 2010 includes a health analysis tool that you can use to automatically check for potential configuration, performance, and usage problems. Search administrators can configure specific health reporting jobs to do the following:

    Run on a predefined schedule.

    Alert an administrator when problems are found.

    Formulate reports that can be used for performance monitoring, capacity planning, and troubleshooting.

Report customization

You can customize reports that help you analyze search system operations and tune the search system to provide the best results for search queries. For example, reports can include information about what terms are used most frequently in queries or how many queries are issued during certain time periods. Information about peak query times can help you decide about server farm topology and about best times to crawl.
Searches of diverse content by crawling or federating

SharePoint Server 2010 can search content in repositories other than SharePoint sites by crawling or federating. For example, the search system can do the following:

    Crawl content in repositories such as file shares, Exchange public folders, and Lotus Notes.

    Use federation for access to search results that are gathered by other crawlers or search engines. An administrator might federate search results from www.bing.com or from a geographically distributed internal location, for example.

http://technet.microsoft.com/en-us/library/ee667266%28office.14%29.aspx#BKMK_RESULT

Whats New in Sharepoint search 2010 ?

All of us know that Search plays an integral part of any successful SharePoint deployment and is an area that Microsoft continues to invest in with each new release of SharePoint.

Microsoft went ahead and acquired FAST some years back which now offers as a separate add-on to SharePoint for those willing to invest in high end enterprise search.  In addition to FAST, SharePoint 2010 search comes in a number of flavors each offering their own feature set and capabilities.

New features and functionality for end users.

New search query capabilities

  • Boolean query syntax for free-text queries and for property queries

    SharePoint Server 2010 supports use of the Boolean operators AND, OR, and NOT in search queries. For example, a user can execute a query such as the following:

    ("SharePoint Search" OR "Live Search") AND (title:"Keyword Syntax" OR title:"Query Syntax")
  • Prefix matching for search keywords and document properties

    Search queries can use the * character as a wildcard at the end of a text string. For example, the search query "micro*" would find documents that contain "Microsoft" or "microchip," and the query "author:bi*" would find documents that contain "Bill" or "Bing." Therefore, the query "micro* author:bi*" would find documents that contain both "Microsoft" and "Bill Gates."
  • Suggestions while typing search queries

    As a user types keywords in the Search box, the Search Center provides suggestions to help complete the query. These suggestions are based on past queries from other users.
  • Suggestions after users run queries

    The Search Center provides improved "did you mean" suggestions in case keywords in a search query appear not to be what the user intended. In addition, when the search system returns results for a query, the Search Center provides suggestions for related searches.
  • Federated search connectors for searching the enterprise from Windows 7

    After SharePoint Server 2010 returns results for a search query, a Windows 7 user can create a federated search connector shortcut for that search scope in Windows Explorer. This enables the user to search that scope at any time from Windows 7. The search results and associated metadata are displayed in Windows Explorer, where the user can take advantage of Windows features such as file preview and drag-and-drop. For any given search query, the search results that are displayed in Windows 7 are exactly the same as those that are displayed in the Search Core Results Web Part when the search is conducted directly in SharePoint Server 2010.

 

http://technet.microsoft.com/en-us/library/ee667266%28office.14%29.aspx#BKMK_RESULT
 

Users cannot see the checked out files in the folder/ library

I Came across a Issue today wherein the user opened a ticket for the below issue Issue : Users cannot see the checked out files in the fo...