Taken from Documentation release for
SharePoint 2013 Preview......
Features deprecated in SharePoint 2013 Preview
Visual upgrade
Document Workspace site template
Personalization Site site template
Meeting
Workspace site templates
Reason for change: SharePoint 2013 Preview and Office 2013 Preview 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.
Migration path: Existing sites that were created by using the Meeting Workspace site templates will continue to operate in SharePoint 2013 Preview. The Meeting Workspace site templates will be removed completely from the next major release of SharePoint and sites that were created by using the Meeting Workspace site templates will not be supported.
Group Work site template and Group Work solution
Description: When you create a site in SharePoint 2013 Preview, 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 Preview.
Reason for change: The Group Work site template was not a widely used site template. The Group Work site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Existing sites that were created by using the Group Work site template will continue to operate in SharePoint 2013 Preview. The Group Work site template will be removed completely from the next major release of SharePoint and sites that were created by using the Group Work site template will not be supported.
Visio Process Repository site template
Unghosting and customizing CSS files
Description: The following methods are included in SharePoint 2013 Preview, but will be removed from the next major release of SharePoint:
Imaging Web service
Excel Services — Can't edit workbooks in the browser that have external data connections
Web Analytics in SharePoint Server 2010
Features deprecated in SharePoint 2013 Preview
The following features and functionality
have been deprecated or changed in SharePoint 2013 Preview.
Visual upgrade
Description: The visual upgrade feature in SharePoint Server 2010 is not
available in SharePoint 2013 Preview. 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).
Reason for change: The visual upgrade feature is replaced with deferred site collection upgrade. The site collection upgrade process is not reversible. The deferred site collection upgrade is a more comprehensive upgrade process than visual upgrade.
Visual upgrade preserved only the old master pages, CSS files, and HTML files. Deferred site collection upgrade preserves much more, including SPFeature functionality. To achieve the deferred site collection upgrade, major changes in the architecture were required, including the removal of visual upgrade.
With deferred site collection upgrade, you can continue to use the UI from the previous version (SharePoint Server 2010) more seamlessly than is possible with visual upgrade. The master page, CSS, JScript, and SPFeatures will remain in SharePoint Server 2010 mode. One key difference is that the granularity of upgrading the user interface is per site collection (SPSite) instead of site (SPWeb). Users can still preview their site in the new SharePoint 2013 Preview user interface before committing. However, this is accomplished by creating and upgrading a temporary copy of their site collection instead of a preview in the existing instance of the site collection. The reason for previewing a copy of the site collection is because of the complexity of what occurs during site collection upgrade. Once a site collection is upgraded, it cannot be rolled back. Therefore, performing a preview would not be possible except in a copy of the site collection.
Reason for change: The visual upgrade feature is replaced with deferred site collection upgrade. The site collection upgrade process is not reversible. The deferred site collection upgrade is a more comprehensive upgrade process than visual upgrade.
Visual upgrade preserved only the old master pages, CSS files, and HTML files. Deferred site collection upgrade preserves much more, including SPFeature functionality. To achieve the deferred site collection upgrade, major changes in the architecture were required, including the removal of visual upgrade.
With deferred site collection upgrade, you can continue to use the UI from the previous version (SharePoint Server 2010) more seamlessly than is possible with visual upgrade. The master page, CSS, JScript, and SPFeatures will remain in SharePoint Server 2010 mode. One key difference is that the granularity of upgrading the user interface is per site collection (SPSite) instead of site (SPWeb). Users can still preview their site in the new SharePoint 2013 Preview user interface before committing. However, this is accomplished by creating and upgrading a temporary copy of their site collection instead of a preview in the existing instance of the site collection. The reason for previewing a copy of the site collection is because of the complexity of what occurs during site collection upgrade. Once a site collection is upgraded, it cannot be rolled back. Therefore, performing a preview would not be possible except in a copy of the site collection.
Migration path: Site
collection administrators who are using visual upgrade to continue to use
SharePoint Server 2007 must move to the SharePoint Server 2010 user interface
before upgrading to SharePoint 2013 Preview. After the content database is
upgraded, users can use deferred site collection upgrade to continue to use the
SharePoint Server 2010 experience for their site collections. Site collection
administrators can be notified by their farm administrator when a site
collection is ready for upgrade and the site collection administrators can then
choose to either perform the upgrade of their site collection or optionally
first preview the new functionality in a temporary copy of their site
collection.
Any SharePoint user interface might have dependencies on visual upgrade. The main dependency was getting the user interface version and then outputting the correct user interface (new or legacy). The visual upgrade API feature is updated so that the user interface version is remapped to the new site collection compatibility level property. This returns the same information about which version the site uses as before. Therefore, dependent code does not need to change.
Any SharePoint user interface might have dependencies on visual upgrade. The main dependency was getting the user interface version and then outputting the correct user interface (new or legacy). The visual upgrade API feature is updated so that the user interface version is remapped to the new site collection compatibility level property. This returns the same information about which version the site uses as before. Therefore, dependent code does not need to change.
Document Workspace site template
Description: When you create a site in SharePoint 2013 Preview, the Document
Workspace site template is not available.
Reason for change: 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 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Existing sites that were created by using the Document Workspace site template will continue to operate in SharePoint 2013 Preview. The Document Workspace site template will be removed completely from the next major release of SharePoint and sites that were created by using the Document Workspace site template will not be supported.
Reason for change: 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 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Existing sites that were created by using the Document Workspace site template will continue to operate in SharePoint 2013 Preview. The Document Workspace site template will be removed completely from the next major release of SharePoint and sites that were created by using the Document Workspace site template will not be supported.
Personalization Site site template
Description: When you create a site in SharePoint 2013 Preview, the
Personalization Site site template is not available.
Reason for change: The Personalization Site site template was not a widely used site template. The Personalization Site site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Existing sites that were created by using the Personalization Site site template will continue to operate in SharePoint 2013 Preview. The Personalization Site site template will be removed completely from the next major release of SharePoint and sites that were created by using the Personalization Site site template will not be supported.
Reason for change: The Personalization Site site template was not a widely used site template. The Personalization Site site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Existing sites that were created by using the Personalization Site site template will continue to operate in SharePoint 2013 Preview. The Personalization Site site template will be removed completely from the next major release of SharePoint and sites that were created by using the Personalization Site site template will not be supported.
Reason for change: SharePoint 2013 Preview and Office 2013 Preview 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.
Migration path: Existing sites that were created by using the Meeting Workspace site templates will continue to operate in SharePoint 2013 Preview. The Meeting Workspace site templates will be removed completely from the next major release of SharePoint and sites that were created by using the Meeting Workspace site templates will not be supported.
Group Work site template and Group Work solution
Description: When you create a site in SharePoint 2013 Preview, 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 Preview.
Reason for change: The Group Work site template was not a widely used site template. The Group Work site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Existing sites that were created by using the Group Work site template will continue to operate in SharePoint 2013 Preview. The Group Work site template will be removed completely from the next major release of SharePoint and sites that were created by using the Group Work site template will not be supported.
Visio Process Repository site template
Description: When you create a site in SharePoint 2013 Preview, 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.
Reason for change: The Visio Process Repository site template is not a widely used site template. The Visio Process Repository site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Not required. The Visio Process Repository site template is available in SharePoint 2013 Preview.
Reason for change: The Visio Process Repository site template is not a widely used site template. The Visio Process Repository site template was removed from SharePoint 2013 Preview to simplify the list of templates that are available when a user creates a new site collection.
Migration path: Not required. The Visio Process Repository site template is available in SharePoint 2013 Preview.
Unghosting and customizing CSS files
Description: The following methods are included in SharePoint 2013 Preview, 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.
Reason for change: The methods are outdated and are no longer needed.
Migration path: None.
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.
Reason for change: The methods are outdated and are no longer needed.
Migration path: None.
Imaging Web service
Description: 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 Preview.
Reason for change: 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 Preview. The Imaging Web service is being removed to reduce security vulnerabilities and to simplify the number of ways to connect to SharePoint 2013 Preview.
Migration path: All the functionality of the Imaging Web service is available through the client-side object model (CSOM). The CSOM provides client-side applications with access to a subset of the SharePoint Foundation server object model, including core objects such as site collections, sites, lists, and list items. Also, Web Distributed Authoring and Versioning (WebDAV) provides clients with key functionality of the Imaging Web service (for example, upload, download, and rename).
Reason for change: 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 Preview. The Imaging Web service is being removed to reduce security vulnerabilities and to simplify the number of ways to connect to SharePoint 2013 Preview.
Migration path: All the functionality of the Imaging Web service is available through the client-side object model (CSOM). The CSOM provides client-side applications with access to a subset of the SharePoint Foundation server object model, including core objects such as site collections, sites, lists, and list items. Also, Web Distributed Authoring and Versioning (WebDAV) provides clients with key functionality of the Imaging Web service (for example, upload, download, and rename).
Excel Services — Can't edit workbooks in the browser that have external data connections
Description: 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 Preview in Office Web Apps Server Preview is used to view workbooks,
not when Excel Services in SharePoint Server 2013 Preview is used.
Reason for change: This is a design limitation in SharePoint 2013 Preview.
Migration path: You can still refresh these workbooks in the Excel client program. Additionally, a service application administrator can configure that workbooks are viewed in SharePoint 2013 Preview instead of Office Web Apps Server Preview.
Reason for change: This is a design limitation in SharePoint 2013 Preview.
Migration path: You can still refresh these workbooks in the Excel client program. Additionally, a service application administrator can configure that workbooks are viewed in SharePoint 2013 Preview instead of Office Web Apps Server Preview.
Web Analytics in SharePoint Server 2010
Description: Web Analytics in SharePoint Server 2010 has been discontinued
and is not available in SharePoint 2013 Preview. Analytics processing for
SharePoint 2013 Preview is now a component of the Search service.
Reason for change: A new analytics system was required for SharePoint 2013 Preview that included improvements in scalability and performance, and that had an infrastructure that encompasses SharePoint Online. The Analytics Processing Component in SharePoint 2013 Preview runs analytics jobs to analyze content in the search index and user actions that are performed on SharePoint sites.
SharePoint 2013 Preview still logs every click in SharePoint sites and still provides a count of hits for every document. User data is made anonymous early in the logging process and the Analytics Processing Component is scalable to the service.
This analytics data is used in SharePoint 2013 Preview to provide new item-to-item recommendation features, to show view counts that are embedded in SharePoint 2013 Preview and Search Server user interface, to provide a report of the top items in a site and list, and to influence the relevancy algorithm of search.
What happens to Web Analytics after upgrade: The Web Analytics Service is not upgraded to the Analytics Processing Component in SharePoint 2013 Preview. When you upgrade to SharePoint 2013 Preview, the databases that contain the data from Web Analytics in SharePoint Server 2010 are not removed. These databases are not used by or maintained by the Analytics Processing Component in SharePoint 2013 Preview. This means that documents on sites in SharePoint Server 2010 that are upgraded will show a hit count of 0.
When you upgrade to SharePoint 2013 Preview, do not attach and upgrade the databases that contain the data from Web Analytics in SharePoint Server 2010. We recommend that you turn off Web Analytics in the SharePoint Server 2010 environment before you copy the content databases that you want to upgrade to SharePoint 2013 Preview.
Reports from Web Analytics for the top items in a site are carried forward. Reports that show browser traffic, top users of a site, and referring URL are not carried forward and are not used by the Analytics Processing Component in SharePoint 2013 Preview.
Administrative reports for the quota usage of site collections in the farm are not available in SharePoint 2013 Preview.
SharePoint 2013 Preview does not support the Web Analytics Web Part. After a farm is upgraded to SharePoint 2013 Preview, all instances of a Web Analytics Web Part will not function. The page that includes the Analytics Web Part will render and a message appears that informs the user that the Web Part is no longer supported.
Migration path: None. Data collection for Analytics Processing in SharePoint 2013 Preview starts immediately for sites, including SharePoint Server 2010 sites.
Reason for change: A new analytics system was required for SharePoint 2013 Preview that included improvements in scalability and performance, and that had an infrastructure that encompasses SharePoint Online. The Analytics Processing Component in SharePoint 2013 Preview runs analytics jobs to analyze content in the search index and user actions that are performed on SharePoint sites.
SharePoint 2013 Preview still logs every click in SharePoint sites and still provides a count of hits for every document. User data is made anonymous early in the logging process and the Analytics Processing Component is scalable to the service.
This analytics data is used in SharePoint 2013 Preview to provide new item-to-item recommendation features, to show view counts that are embedded in SharePoint 2013 Preview and Search Server user interface, to provide a report of the top items in a site and list, and to influence the relevancy algorithm of search.
What happens to Web Analytics after upgrade: The Web Analytics Service is not upgraded to the Analytics Processing Component in SharePoint 2013 Preview. When you upgrade to SharePoint 2013 Preview, the databases that contain the data from Web Analytics in SharePoint Server 2010 are not removed. These databases are not used by or maintained by the Analytics Processing Component in SharePoint 2013 Preview. This means that documents on sites in SharePoint Server 2010 that are upgraded will show a hit count of 0.
When you upgrade to SharePoint 2013 Preview, do not attach and upgrade the databases that contain the data from Web Analytics in SharePoint Server 2010. We recommend that you turn off Web Analytics in the SharePoint Server 2010 environment before you copy the content databases that you want to upgrade to SharePoint 2013 Preview.
Reports from Web Analytics for the top items in a site are carried forward. Reports that show browser traffic, top users of a site, and referring URL are not carried forward and are not used by the Analytics Processing Component in SharePoint 2013 Preview.
Administrative reports for the quota usage of site collections in the farm are not available in SharePoint 2013 Preview.
SharePoint 2013 Preview does not support the Web Analytics Web Part. After a farm is upgraded to SharePoint 2013 Preview, all instances of a Web Analytics Web Part will not function. The page that includes the Analytics Web Part will render and a message appears that informs the user that the Web Part is no longer supported.
Migration path: None. Data collection for Analytics Processing in SharePoint 2013 Preview starts immediately for sites, including SharePoint Server 2010 sites.
No comments:
Post a Comment