SharePoint 2010 upgrade checklist: Part 3

Below are some more upgrade checklist as shared in the Part 1 and Part 2

Component	Recommendations
People and Asset Picker
Verify that People picker works as it did in SP2007 farm
Verify that Asset picker works as it did in SP2007 farm
Web Parts
Do all the Web Parts from your original site appear in your upgraded site?	If a Web Part zone exists in a customized page, but not in the site definition, the Web Parts from that Web Part zone may have been moved into the bottom zone on the page during the upgrade.
	Either in Edit Mode for the page in the browser or in Microsoft SharePoint Designer 2010, look for missing Web Parts in the bottom zone or other zones, or check to see whether the Web Parts have been closed. For more information about how to work with Web Parts and Web Part zones in SharePoint Designer 2010, see the SharePoint Designer Help system.
Are the Web Parts displayed correctly (in the correct zone, location and size) ?	Either in Edit Mode for the page in the browser or in SharePoint Designer 2010, drag the Web Part into the correct zone or modify the Web Part properties to correct any sizing or positioning problems.
Are there any extra or missing Web Parts?	Open the page either in Edit Mode for the page in the browser or in SharePoint Designer 2010. If you see extra Web Parts on your page, look for closed or inactive Web Parts on the original version of the page. Were the closed or inactive Web Parts opened by the upgrade process? If so, you can modify the Web Part properties to close these Web Parts.
	If Web Parts are missing, look for errors in SharePoint Designer 2010 such as "Error Rendering Control" or "Missing Assembly." These errors indicate that the Web Part was not installed or was configured incorrectly for the new environment and must be reinstalled or reconfigured.
Do the Web Parts work correctly?	Open the page either in Edit Mode for the page in the browser or in SharePoint Designer 2010, and look for errors that indicate that a component or service is missing. Make sure that any components or services that the Web Parts rely on exist in the upgraded site. Particularly for the database attach upgrade approach, you must make sure that you have installed all the components or services that you must have for your Web Parts, and that you have configured them correctly (for example, you have configured the Web.config Safe Controls list).
	Update and redeploy any Web Parts that exist but no longer function correctly.
Are any Web Parts pages still checked out?	If you check out a page to make changes, make sure that you check in the page again.
Are your Excel Web Access Web Parts working correctly? Did you re-create your connections correctly? Are external data sources still working?	Verify all connections and external data sources.
Large Lists
Check any large lists, and have the site owner or list owner address the issue	For example, create indexed columns with filtered views, organize items into folders, set an item limit on the page for a large view, or use an external list….
Style and appearance
Are all images on your pages displayed correctly?	Fix the links
Are the appropriate cascading style sheet colors and styles used in the appropriate location?	Fix links to the cascading style sheet file.
	Verify link to master page.
Scripted controls not working?	Fix links to the controls.
Pages displayed correctly in web browsers?	Check scripts/links and move HTML to XHTML mode.
Permissions
Appropriate people and groups still have the correct level of permissions?	Check:
	a. Sites
	a. Pages
	a. Lists
	a. Items
	Use "check permissions" button on the ribbon
Does SharePoint Groups exists in	Does SharePoint Groups works , AD Security group works.
Customizations
Customizations still in correct locations?
Can you still access the editing controls on the pages?
Are your customizations still appropriate in the new environment, or do you want to update to the new functionality and look?	If you want the new functionality and features, you must reset any customized pages to use the template. Use the Reset to Template command in SharePoint Designer to reset the page to the default version . After you have restored it, you can then reapply your customizations in the browser by applying a different master page, or by reapplying the customizations in SharePoint Designer.
Are any pages still checked out?	Make sure you check in the page again, after changes were made.
Code
Timer jobs	Test any timer job deployed at the farm, web app, site collection, or site level in the new environment.
Workflows	Create instances of all workflows and validate the status
Server Controls	Test any server controls
Event Receivers	Test any even t receivers deployed at the site collection, web, list, field, item, and workflow in the new environment.
Permissions
Check for limited access, read, contribute, design, and full control permissions
Check for Full Control, Full Read, Deny Write, and Deny All permissions. And if any custom permission level was created as well.
Web services
Check existing javaScript call to web service (asmx)
New code to test client.svc and listdata.svc
Email enabled lists
Document uploaded to doc library?
Settings from '07 environment preserved?
Alerts
Existing alerts properly working?
Can new alerts be created/deleted?
BB browser access
Can site be accessed from BB browser?
Recycle Bin
Basic functionality works? Delete a document, is it in the recycle bin?
Can administrator delete from first and second stage recycle bin?
Auditing
Audit reports available?
Settings from '07 environment preserved?
Manage content structure
All existing reports available?
Functionality available?
Outlook sync
Are docs being sync'ed?
SharePoint Designer
Can SPD be enabled and disabled?
CRUD operations on sites
Create a site
Delete a site
Modify a site
CRUD operations on document library
Create a document
Delete a document
Edit/Modify a document
CRUD operations on lists
Create a list
Delete a list
Create a list item
Delete a list item
Edit a list
Edit a list item
Backup/restore
Backup working?
Restore working?
Sites and lists export/import
Site export working properly?
Site import working properly?
List export working properly?
List import working properly?

SharePoint 2010 Upgrade checklist: Part 2

Below are some more upgrade checklist as shared in the Part 1:

Search

Run a crawl, and review the log files.

Run search queries, and verify that the queries work as expected and provide appropriate results. Twenty-four hours later, view the query reports and look for issues.

Search for people and profiles.

Check any Search customizations to make sure that they work as expected.

My Site Web sites

Are all the Web Parts working?

Are all features associated with the My Site Web sites working?

Can users access the sites, or are they seeing "Access Denied" errors?

If the My Site host that they are visiting is not the default My Site host, they may see this error. Check that the service application and proxy associations are correct, and then check that the My Site host is referenced correctly in the User Profile service application. Reset Internet Information Services (IIS) to apply any changes.

User Profile, InfoPath and Excel Services

Are they configured correctly?

Are the service application proxies configured the way that you want?

Do you have to create new connections between farms?

Make sure that all existing content such as documents are accessible in the upgraded Personal site.

Check all services have administrator permissions or reapply as needed.

For Excel Services, if using SSS (Secure Store Service) create a new unattended service account to interact with Excel Services.

For InfoPath Forms Services, update any links that are used in the upgraded form templates by using the Update-SPInfoPathAdminFileURL.

SharePoint 2010 upgrade checklist.

Some time you may wonder after upgrade, one should have a check list handy to test if the all OOB functionalities are working fine. Below listed are some of the Server and Site level checklist you can perform in your environment.  

Data Access ( on Lists and Sites)
	CRUD Operations on Standard Features
	Blogs
	Discussion Forums
	Wikis
	Calendar View
	Surveys
	Sites and Workspaces
	All sites load?
	Create/Edit/Delete a Site
	OOTB Components
	Workflows on List/Libraries
	Large Lists
	Check lists with more than 8 lookup values
	Check any large lists
	Email enabled lists
	Document uploaded to doc library?
	Settings from '07 environment preserved?
	Alerts
	Existing alerts properly working?
	Can new alerts be created/deleted?
UI and Navigation on Publishing  Pages
	Style and appearance of Publishing page (e.g. Home Page of site)
	Are all images on your pages displayed correctly?
	Are the appropriate cascading style sheet colors and styles used in the appropriate location?
	Scripted controls working?
	Pages displayed correctly in web browsers?
	OOTB Web Parts
	Do all the Web Parts from your original site appear in your upgraded site?
	Are the Web Parts displayed correctly (in the correct zone, location and size) ?
	Are there any extra or missing Web Parts?
	Do the Web Parts work correctly?
	Are your Excel Web Access Web Parts working correctly? Did you re-create your connections correctly? Are external data sources still working?
	KPI Web Parts
	Do all the Web Parts from your original site appear in your upgraded site?
	Are the Web Parts displayed correctly (in the correct zone, location and size) ?
	Are there any extra or missing Web Parts?
	Do the Web Parts work correctly?
	Is all the information being pulled from the right data source?
	Is the information accurate and correct according to the input values?
	Navigation
	List Navigation
	Quick launch
	Breadcrumb
	Navigate Up
	Tree
	Top Link Bar
	All Site Content
Customizations & Integration with Other System
	Customizations
	Customizations still in correct locations?
	Can you still access the editing controls on the pages?
	Are any pages still checked out?
	People and Asset Picker
	Verify that People picker works as it did in SP2007 farm
	Verify that Asset picker works as it did in SP2007 farm
Site Administration
	Recycle Bin
	Basic functionality works? Delete a document, is it in the recycle bin?
	Can administrator delete from first and second stage recycle bin?

Lync Server Control Panel: Insufficient access rights to perform the operation

Issue: Unable to provision for Lync, getting error message “Insufficient access rights to perform the operation”

Problem Statement:

This is a known and common issue with Domain Administrators or Enterprise Administrators. The user account that is part of the Lync Server move or enable operation is a member of an Active Directory, directory service protected domain security group. Since the user account belongs to a protected domain security group it is unable to keep the RTCUniversalUserAdmins and RTCuniversalUserReadOnlyGroup Universal Security groups and their permissions as Access Control Entries (ACEs) to the protected domain security group's default Access Control List (ACL).

NOTE: The Lync Server Control Panel is not designed to delegate the permissions that are needed to complete the user account move or enable operation for power user.

Also provision Lync for power (Domain Admin and Enterprise Admin), you should have same access addition RTCUniversalServerAdmin and RTCUniversalUserAdmin privilege.

Resolution:

Follow the below steps in order to resolve above issue-

1.    Open AD Users and Computers and turn on Advanced Features on in ADUC. (ADUC -> Views -> Advanced Feature)

2.    Locate the user that is a Domain Admin or Enterprise Admin, select the Security tab, clickAdvanced and select "Include Inheritable Permissions from this object's parent" on the user object you then be able to add them for Lync.

3.    Got to Lync Server, Open Lync server Management Shell. Type command to enable user for Lync. E.g.

4.    Verify the user status. e.g.

PS C:\> Get-CsUser -Identity "BaluIlag"

You will see the exact status with SIP address and your RegistrarPool server.

 

Thank you.

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