Export (0) Print
Expand All
2 out of 6 rated this helpful - Rate this topic

Perform post-upgrade steps for a database attach upgrade (SharePoint Server 2010)

Published: May 12, 2010

After you have upgraded the content in your environment to Microsoft SharePoint Server 2010, you must perform some additional steps to make sure that the infrastructure supporting that content is ready to start servicing user requests again. This article describes how to complete these tasks.

In this article:

Reapply administrator permissions for services

By default, farm administrators have permissions to all services when you perform a database attach upgrade. If you want to apply more restrictive permissions, do so now.

Upgrade profile properties to taxonomy data and update the photo store for Profile Services

Multi-value profile properties data from Microsoft Office SharePoint Server 2007 was stored in the Shared Services Provider (SSP) database as part of the Profile Services data. For SharePoint Server 2010, this data must now be converted to taxonomy data and be stored in the managed metadata database. To move and upgrade the data, you must have created a service application for the Managed Metadata service. After that is complete, you can use a Windows PowerShell cmdlet to upgrade the profile and taxonomy data and move it to the Taxonomy database. This cmdlet reconnects the data to the Managed Metadata and User Profile service applications. You must run this cmdlet for each Managed Metadata property that you want to upgrade; there is no option to specify all properties. Note that the Managed Metadata service does not accept certain characters (such as semicolons, angle brackets, pipes, quotation marks, or tab characters) that were allowable in user profile properties based on choice lists in Office SharePoint Server 2007. If a term or term set uses a character that is no longer accepted, the character is removed and replaced with a space when it is upgraded.

Important Important:

To upgrade and use taxonomy data, the User Profile service application proxy and Managed Metadata service application proxy must be in the same proxy group.

Before you upgrade the taxonomy data, look up the ID for the User Profile service application proxy (called the SPServiceApplicationProxyPipeBand in Windows PowerShell), locate the list of the managed metadata properties, and then choose the properties you want to upgrade.

To find the User Profile service application proxy ID by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2010 Products.

  4. Click SharePoint 2010 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    Get-SPServiceApplicationProxy
    

    This returns a list of service application proxies. Copy the ID for the User Profile service application proxy.

For more information, see Get-SPServiceApplicationProxy.

To view the name of a managed metadata property

  1. On the SharePoint Central Administration Home page, click Application Management.

  2. Under Service Applications, click Manage Service Applications.

  3. Click the User Profile service application for your environment to open the Manage Profile Service: Service name page.

  4. Under People, click Manage User Properties.

  5. Click a property name, and then click Edit.

  6. Copy the string from the Name box.

    This is the name to use as the identity for the managed metadata property when you upgrade the taxonomy data.

Important Important:

You must be an administrator for the Managed Metadata to upgrade taxonomy data. You use the Move-SPProfileManagedMetadataProperty cmdlet to upgrade the taxonomy data. This cmdlet can take a long time to run, depending on how many profiles are in your environment.

To upgrade taxonomy data by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin. You must also be a member of the Term store administrator role for the Managed Metadata service. For more information, see Managed metadata roles (SharePoint Server 2010).

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2010 Products.

  4. Click SharePoint 2010 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    Move-SPProfileManagedMetadataProperty -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> -Identity <Identity> [-AvailableForTagging Yes] [-TermSetName]
    

    Where

    • <SPServiceApplicationProxyPipeBind> is the ID for the User Profile service application proxy

    • <Identity> is the name of the managed metadata property you want to move

    • AvailableForTagging determines whether the terms in the resulting term set can be used for managed metadata tagging. The default value is No. Do not mark term sets that include more than 20,000 terms with this property. This is because terms marked as available for tagging are cached on the client side and if you have thousands or millions of terms marked as available for tagging, it can significantly reduce client performance.

    • TermSetName specifies whether to create the term set name. If this parameter is not specified, the property is mapped to the Keywords term set.

For more information, see Move-SPProfileManagedMetadataProperty.

When you upgrade, any photos that were stored as profile pictures must be updated. If you do not update the photo store data, either no photos will be displayed or some photos might appear distorted. To update the photo store, you use the Update-SPProfilePhotoStore Windows PowerShell cmdlet. This cmdlet might take a long time to run if you have many profiles and many photos. The cmdlet copies the user photos from wherever they are stored (usually in the Shared Pictures library on their My Site) and puts them in the User Photos library on the My Site host. The process also generates small, medium, and large thumbnail sizes of the pictures that are the correct sizes to be used in the various controls and Web Parts for My Site profile photos. Before you run this cmdlet, check the quotas for your My Sites and make sure there is plenty of space available for storing the photos — you must have at least 10 KB of space per user.

To update photo store data by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin. You must also be a site collection administrator for the My Site host, and you must be a User Profile service application administrator with the Manage Profiles permission.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2010 Products.

  4. Click SharePoint 2010 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    Update-SPProfilePhotoStore -MySiteHostLocation <URL of the My Site Host>
    

For more information, see Update-SPProfilePhotoStore.

Create and configure the Secure Store service application and migrate SSO data to the Secure Store service

The Single Sign-on (SSO) service that was available in Office SharePoint Server 2007 has been replaced with the Secure Store service in SharePoint Server 2010. There is no direct upgrade path for the data and settings from SSO to the Secure Store service, but you can migrate data from the SSO database to a new Secure Store database. Excel Services Application must have the Secure Store service account to function correctly. To upgrade SSO data to the Secure Store service for use with Excel Services Application and Business Data Connectivity services, you perform the following steps:

  1. Provision a Secure Store service application and provision the new, unattended service account for use with Excel Services Application.

    You must provision the Secure Store service before you can upgrade data from the SSO service. And you must configure an unattended service account for Excel Services Application to function correctly. For detailed steps to create and configure the Secure Store service application and create the unattended service account, see Use Excel Services with Secure Store (SharePoint Server 2010).

  2. Use the Windows PowerShell Upgrade-SPSingleSignOnDatabase cmdlet to migrate the application definitions from the SSO database to the Secure Store database as target applications.

  3. Use the Windows PowerShell Disable-SPSingleSignOn cmdlet to disable the SSO service on an upgraded farm server (in-place upgrade only).

To upgrade SSO data to the Secure Store service by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin. You must have read access to both the old SSO database and the new Secure Store service database to run this cmdlet.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2010 Products.

  4. Click SharePoint 2010 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    Upgrade-SPSingleSignOnDatabase -SSOConnectionString <SSOConnectionstring> -SecureStoreConnectionString <SecureStoreConnectionstring> -SecureStorePassphrase Passphrase>
    

    Where:

    • <SSOConnectionString> is a valid connection string to the SSO database.

    • <SecureStoreConnectionstring> is a valid connection string to the Secure Store database.

    • <Passphrase> is the passphrase to use when connecting to the Secure Store service.

For more information, see Upgrade-SPSingleSignOnDatabase.

To disable the SSO service by using Windows PowerShell (in-place upgrade only)

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2010 Products.

  4. Click SharePoint 2010 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    Disable-SPSingleSignOn -ServerName <ServerName>
    

    Where:

    • <ServerName> is the name of the server running the SSO service.

For more information, see Disable-SPSingleSignOn.

Upgrading solutions that depend on the Business Data Catalog

If you used the database attach method to upgrade and you want to continue to use the external data that is accessed through one or more application definitions, you must complete the following tasks:

  1. In your previous environment, export the application definitions (models) that are required by your solution from the Office SharePoint Server 2007 Business Data Catalog. For more information, see Export application definition.

  2. Update the solution to use the object model and features of the Microsoft Business Connectivity Services. This includes updating the application definition file to be compatible with Microsoft Business Connectivity Services. For information about the Business Data Connectivity service object model, see Microsoft SharePoint 2010 Software Development Kit (http://go.microsoft.com/fwlink/p/?LinkId=166117).

  3. In your new environment, after upgrade, import the updated model into the Business Data Connectivity service. For more information, see Manage BDC models (SharePoint Server 2010).

Update links that are used in any upgraded InfoPath form templates

For a database attach upgrade, you exported and imported any InfoPath form templates in your environment when you created the new environment. After upgrade, you can now update the links that are used in those upgraded form templates to point to the correct URLs by using a Windows PowerShell cmdlet. Note that this cmdlet does not update any links that were hard-coded into scripts, data connections, or assemblies.

To update InfoPath form template links by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.

  2. On the Start menu, click Administrative Tools.

  3. Click SharePoint 2010 Management Shell.

  4. At the Windows PowerShell command prompt), type the following command:

    Update-SPInfoPathAdminFileURL -find <OldUURLtoReplace> -replace <NewURL>
    

For more information, see Update-SPInfoPathAdminFileUrl.

Have users migrate private My Links to private tags (Optional)

The My Site feature in Office SharePoint Server 2007 included a bookmarking feature known as My Links. In SharePoint Server, this functionality is replaced by private tags. Users can continue to use the My Links Web Part, or they can migrate their links manually to their set of private tags. This is a manual process that each user can perform on his or her My Site.

To convert a private link to a private tag

  1. Navigate to the following URL: http://my_site_url/_layouts/myquicklinks.aspx.

  2. Select the check box next to the link or links that you want to convert.

  3. Click Create Tag from Link.

To view the tags, on your Profile page (http://my_site_url/Person.aspx), click Tags and Notes, and then under Refine by type, click Private.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.