26 March, 2013

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?

24 March, 2013

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.

19 March, 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

17 March, 2013

Recently published content for SharePoint 2013

Published the week of March 11, 2013
New articles
Understanding result sources for search in SharePoint Server 2013   Use a result source in SharePoint Server 2013 to specify a provider to get search results from, and optionally to narrow a search to a subset of those results.
Enable apps in AAM or host-header environments for SharePoint 2013   Learn how to enable app domains for alternate access mappings or host-header web application environments after installing the March 2013 Public Update.
User profiles for SharePoint Sever 2013 learning roadmap   Use this learning roadmap to gain expertise about user profiles and associated technologies in SharePoint Server 2013.
Configure and use the Documentum connector in SharePoint Server 2013   Describes how to install and configure the Microsoft SharePoint 2013 Indexing Connector for Documentum.
Overview of SQL Server in a SharePoint environment (SharePoint 2013)   Learn about the SharePoint Server 2013 relationship with SQL Server 2008 R2 with Service Pack 1 (SP1) and SQL Server 2012 and how you can interact with the databases.
Updated articles
Use Windows PowerShell to update alerts in SharePoint 2013   Learn to use Invoke-AlertFixup to update the e-mail alerts associated with a URL.
Published the week of March 4, 2013
New articles
Create a high availability architecture and strategy for SharePoint 2013   Describes how to combine farm architecture and technology to create a highly available environment in a single SharePoint 2013 farm.
Blog: Stage 3: How to enable a list as a catalog   New post in a series that describes how you can use SharePoint 2013 to set up a website that is based on product catalog data.
Updated articles
Software boundaries and limits for SharePoint 2013   Revised limits for maximum file size and security scopes.
Installing and configuring workflow for SharePoint Server 2013   Added information about least-privilege configuration.