J3qx

information archive

Example SharePoint Intranet migration and downgrade from ENT to STD

Posted by j3qx на Апрель 2, 2016

Example SharePoint Intranet migration and downgrade from ENT to STD.

Overview

This document describes steps for successful data migration from SharePoint 2013 Server Enterprise farm (source) to SharePoint 2013 Server Standard farm (destination). Roughly, here are the steps that will need to be done (detailed instructions will be in sections below):

  • Ensure both farms have consistent version updates
  • Backup databases on source farm via MSSQL
  • Restore databases on destination farm via MSSQL
  • Perform prerequisite steps on the destination farm
  • Attach content databases via powershell
  • Create Managed Metadata Service Application (and proxy) using powershell and database from source farm
  • Create User Profile Service Application (and proxy) using powershell and databases from source farm
  • Deploy code packages
  • Create Search Service Application from scratch and configure it
  • Apply finalizing steps and actions
  • What is left undone?

Ensure both farms have consistent version updates

Just run the Windows Update Service on the destination farm, select to search for updates in other Microsoft products and let it install updates. Destination farm version can be higher than source farm, but not lower, otherwise attachment of content databases will fail.

Backup databases on source farm via MSSQL

Databases that we will need:

  • PROD_WSS_Content_80
  • PROD_WorkflowContent
  • PROD_UserProfileSync_DB
  • PROD_UserProfileSocial_DB
  • PROD_UserProfile_DB
  • PROD_ManagedMetadataService

Restore databases on destination farm via MSSQL

Restore those databases mentioned in previous step in the MSSQL instance of destination farm.

Perform prerequisite steps on the destination farm

Create a Web Application on 80 port, do not extend it, and do not create any site collections in it. Create appropriate alternate mappings for it, edit the Web Site Bindings in IIS. (let’s say http://intranet, or http://intranet2)

Attach content databases via powershell

Let’s assume, that the server name of SQL Server is TD-SRV-44V and that we are using the default instance. Then in all powershell commands below I will use «td-srv-44v» as database server – replace it with what is needed when you perform this step. Also, web application parameter should be url of your default value in the alternate mappings collection for the 80 port web application (below I will use http://intranet – replace according to your needs)

From the SharePoint 2013 Management Shell which should be run as Administrator (I will reference this as management shell for brevity) run following commands:

  • Mount-SPContentDatabase «PROD_WSS_Content_80» -DatabaseServer «td-srv-44v» -WebApplication http://intranet
  • Mount-SPContentDatabase «PROD_ WorkflowContent » -DatabaseServer «td-srv-44v» -WebApplication http://intranet

Create Managed Metadata Service Application (and proxy) using powershell and database from source farm

From management shell run following commands:

  • Create new service application pool à New-SPServceApplicationPool –Name ManagedMetadataAppPool –Account test\s-sharepoint-01
  • New-SPMetadataServiceApplication -Name «Managed Metadata Service» -ApplicationPool » ManagedMetadataAppPool» -DatabaseName «PROD_ManagedMetadataService»
  • New-SPMetadataApplicationProxy –Name «Managed Metadata Service Proxy» –ServiceApplication «Managed Metadata Service»

Create User Profile Service Application (and proxy) using powershell and databases from source farm

From management shell run following commands (change http://intranet to default alternate access mapping name is needed):

  • Create new service application pool à New-SPServceApplicationPool –Name UserProfileAppPool –Account test\s-sharepoint-01
  • New-SPProfileServiceApplication –ApplicationPool «UserProfileAppPool» –MySiteHostLocation http://intranet/my -Name «User Profile Service Application» –ProfileDBServer «td-srv-44v» -ProfileDBName «PROD_UserProfile_DB» –ProfileSyncDBName «PROD_UserProfileSync_DB» –SocialDBName «PROD_UserProfileSocial_DB»
  • New-SPProfileServiceApplicationProxy –Name «User Profile Service Application Proxy» –ProfileServiceApplication «User Profile Service Application»

Deploy code packages

In archive there are 5 folders, each contains a code package and a file named deploy.ps1. With management shell navigate to each folder and execute deploy.ps1 file without any parameters

Please deploy in following order:

  1. BlobCacheManager
  2. CalendarWithResources
  3. CustomFields
  4. Intranet
  5. Workflows

After deploys run these commands:

  1. iisreset
  2. net stop sptimerv4
  3. net start sptimerv4

Create Search Service Application from scratch and configure it

Create new search service application (SSA) from central administration. Click on newly created SSA.

  • In «Global Search Center URL« write http://intranet/search/pages
  • Go to «Content Sources». If local SharePoint sites content source has not been automatically created – wait 10 minutes and check again
  • Go inside Local SharePoint sites content source
  • Add Incremental and Full Crawl schedules. Incremental – check also «Repeat within the day»
  • Go to Crawl Rules and add rule with Path: http://intranet/personal/* and options «Exclude all items in this path» and tick checkbox below «Exclude complex URLs»
  • Make a first Full Crawl
  • After first Full Crawl is ended (will take ~50 minutes) go to «Search Schema»
  • Check that Schema contains properties that are in the picture below. Some of them are there by default, but with different settings – please go through each one of them and make sure the settings are correct:

    Also, in PictureURL property add Crawled Property «ows_Image»
  • Make a second Full Crawl

Apply finalizing steps and actions

Here you will do various steps in different places, to complete the functionality.

  • Go to Central Administration -> Application Management -> Configure service application associations. Click on in the «Application Proxy Group» column click on «default». In the popup check all checkboxes
  • Go to Central Administration -> Application Management -> Manage services on server. Make sure «User Profile Service» and «Managed Metadata Service» are started
  • Go to Central Administration -> Application Management -> Manage web applications. Click on the main web application (the on with 80 port). In the ribbon the will be one (or two, — minor bug – don’t pay attention) buttons «BlobCache Management». Click and in the popup tick the «Enabled» checkbox and press OK.
  • Go to Central Administration -> Application Management -> Manage web applications. Click on the main web application. In the ribbon click «Blocked File Types» button. Remove lines «ashx» and «svc», click OK.
  • Go to Central Administration -> Application Management -> Manage web applications. Click on the main web application. In the ribbon click «Manage Features». If activated, deactivate feature «Example SharePoint Intranet Infrastructure». Activate it.
  • Go to Central Administration -> Application Management -> Manage service applications. Permission for different modules:
    • Highlight Managed Metadata Service. Click Permissions in ribbon. Add DOMAIN\domain users with Full Access to Term Store. In ribbon click Administrators. Select farm account and app pool account for web application and add them with Full control permissions.
    • Highlight Managed Metadata Service Connection. In ribbon click Properties. Tick all tick-able checkboxes.
    • Highlight Search Service Application. In ribbon click Permissions. Add farm and 80 port web application pool accounts with Full Control permissions. In ribbon click Administrators and add those two accounts with Full Control permissions.
    • Highlight User Profile Service Application. In ribbon add farm and web application app pool accounts with permissions Full Control. In ribbon click Administrators. Add farm and with All Permissions. Add account that is for search service query application pool with permission Retrieve People Data for Search Crawlers.
  • Open C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN\OWSTimer.EXE.Config file. Delete or comment out the line <NetFx40_LegacySecurityPolicy enabled=»true» />
  • Go to C:\inetpub\wwwroot\wss\VirtualDirectories. Inside folder(-s) that correspond to main web application (port 80) edit the web.config file:
    • Change <SafeMode MaxControls=»200″ to <SafeMode MaxControls=»500″
    • Change <trust level=»Full» originUrl=»» legacyCasModel=»true» /> to <trust level=»Full» originUrl=»» legacyCasModel=»false» />

What is left undone?

Adding a User Profile Synchronization Connection is not covered in this document.

Реклама

Добавить комментарий

Заполните поля или щелкните по значку, чтобы оставить свой комментарий:

Логотип WordPress.com

Для комментария используется ваша учётная запись WordPress.com. Выход / Изменить )

Фотография Twitter

Для комментария используется ваша учётная запись Twitter. Выход / Изменить )

Фотография Facebook

Для комментария используется ваша учётная запись Facebook. Выход / Изменить )

Google+ photo

Для комментария используется ваша учётная запись Google+. Выход / Изменить )

Connecting to %s

 
%d такие блоггеры, как: