Wednesday, February 13, 2013

Configure Trusted Certification Between SharePoint 2013 Farm

 

1. Exporting and copying certificates consuming farm using PowerShell

1.1 To export the root certificate from the consuming farm

$rootCert = (Get-SPCertificateAuthority).RootCertificate

$rootCert.Export("Cert") | Set-Content <C:\ConsumingFarmRoot.cer> -Encoding byte

(<C:\ConsumingFarmRoot.cer> is the path of the root certificate)

1.2 To export the STS certificate from the consuming farm

$stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate

$stsCert.Export("Cert") | Set-Content <C:\ConsumingFarmSTS.cer> -Encoding byte

(<C:\ConsumingFarmSTS.cer> is the path of the STS certificate)

1.3 To export the root certificate from the publishing farm

$rootCert = (Get-SPCertificateAuthority).RootCertificate

$rootCert.Export("Cert") | Set-Content <C:\PublishingFarmRoot.cer> -Encoding byte

(<C:\PublishingFarmRoot.cer> is the path of the root certificate)

 

2. To import the root certificate and create a trusted root authority on the consuming farm using PowerShell

Managing trust certificates in a farm involves establishing trust. This section describes how to establish trust on both the consuming and publishing farms by using Windows PowerShell 3.0 commands.

Establishing trust on the consuming farm

2.1 To import the root certificate and create a trusted root authority on the consuming farm

$trustCert = Get-PfxCertificate <C:\PublishingFarmRoot.cer>

New-SPTrustedRootAuthority <PublishingFarm> -Certificate $trustCert

( <C:\PublishingFarmRoot.cer> is the path of the root certificate that you copied to the consuming farm from the publishing farm.

<PublishingFarm> is a unique name that identifies the publishing farm. Each trusted root authority must have a unique name.)

Establishing trust on the publishing farm

2.2 To import the root certificate and create a trusted root authority on the publishing farm

$trustCert = Get-PfxCertificate <C:\ConsumingFarmRoot.cer>

New-SPTrustedRootAuthority <ConsumingFarm> -Certificate $trustCert

( <C:\ConsumingFarmRoot.cer> is the name and location of the root certificate that you copied to the publishing farm from the consuming farm.

<ConsumingFarm> is a unique name that identifies the consuming farm. Each trusted root authority must have a unique name. )

2.3 To import the STS certificate and create a trusted service token issuer on the publishing farm

$stsCert = Get-PfxCertificate <c:\ConsumingFarmSTS.cer>

New-SPTrustedServiceTokenIssuer <ConsumingFarm> -Certificate $stsCert

( <C:\ConsumingFarmSTS.cer> is the path of the STS certificate that you copied to the publishing farm from the consuming farm. 

<ConsumingFarm> is a unique name that identifies the consuming farm. Each trusted service token issuer must have a unique name.)

Tuesday, January 8, 2013

Step 05: Overview of the upgrade process to SharePoint 2013

Upgrade My Sites

A server farm administrator upgrades the My Site host and then individual users can upgrade their My Sites or the farm administrator can upgrade them by using Windows PowerShell. The following illustration shows four stages for the My Site host and My Sites during the upgrade process.


  1. The My Site host has not been upgraded. My Sites cannot be upgraded yet.
  2. A server farm administrator has upgraded the My Site host. No My Sites have been upgraded.
  3. Some users have upgraded their My Sites.
  4. All My Sites have been upgraded.
Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can start to upgrade their sites as soon as they see a notification on their site's home page that the new version is available. The following illustration shows four stages for a site collection during the upgrade process.

Stages in upgrading site collections


  1. The site owner runs the site collection health checks to determine readiness for upgrade. The site owner addresses issues before they continue with the next step.

  1. Optionally, the site owner requests an upgrade evaluation site collection. A timer job runs to create the site collection and the site owner receives an email message when the evaluation site collection is ready. The site owner previews the new user interface. After several days or weeks, the evaluation site collection expires and is deleted by a timer job. 
A server farm administrator can determine the length of time before expiration.

  1. When the site owner is ready, the site owner starts the upgrade process. The site collection health checks are run again automatically. The site owner must address issues before upgrading. If health checks return no issues, the upgrade starts.
  2. When upgrade is complete, the site owner sees the Upgrade Status page that contains the status and a link to the upgrade logs. The site owner reviews the site to make sure that everything works correctly.

Step 04: Upgrade content databases to SharePoint 2013


  1. Verify that you have the following memberships:
    • securityadmin fixed server role on the SQL Server instance.
    • db_owner fixed database role on all databases that are to be updated.
    • Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.


  1. Start the SharePoint 2013 Management Shell.
    • For Windows Server 2008 R2:
      • On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.
    • For Windows Server 2012:
      • On the Start screen, click SharePoint 2013 Management Shell.
If SharePoint 2013 Management Shell is not on the Start screen:
      • Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

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

Test-SPContentDatabase -Name DatabaseName -WebApplication URL

Mount-SPContentDatabase -Name DatabaseName -DatabaseServer ServerName -WebApplication URL

Step 05: Overview of the upgrade process to SharePoint 2013

Step 03: Upgrade service applications to SharePoint 2013

To start service application instances from Central Administration

1. Start SharePoint 2013 Central Administration.

•For Windows Server 2008 R2:
Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.

•For Windows Server 2012:
On the Start screen, click SharePoint 2013 Central Administration.                           
If SharePoint 2013 Central Administration is not on the Start screen:
Right-click Computer, clicks all apps, and then clicks SharePoint 2013 Central Administration.

For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.

2. In SharePoint 2013 Central Administration, on the Application Management page, in the Service Applications section, click Manage Services on Server.

3. Next to the Business Data Connectivity service, click Start.

4. Next to the Managed Metadata Web Service, click Start.

5. Next to the PerformancePoint Services service, click Start.

6. Next to the Secure Store Service, click Start.

7. Next to the User Profile Service, click Start.

The Search service instance must be started by using Windows PowerShell because you cannot start it from Central Administration unless a Search Service application already exists.


To start the Search service instance by using Windows PowerShell

1. Verify that you have the following memberships:
•securityadmin fixed server role on the SQL Server instance.
•db_owner fixed database role on all databases that are to be updated.
•Administrators group on the server on which you are running the Windows PowerShell cmdlets.


2. Start the SharePoint 2013 Management Shell.

•For Windows Server 2008 R2:
•On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.

•For Windows Server 2012:
•On the Start screen, click SharePoint 2013 Management Shell.
•Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.


3. To start the Search service instance, at the Windows PowerShell command prompt, type the following commands and press ENTER after each one:

$SearchInst = Get-SPEnterpriseSearchServiceInstance
# Stores the identity for the Search service instance on this server as a variable
Start-SPServiceInstance $SearchInst
# Starts the service instance


To upgrade the Secure Store service application by using Windows PowerShell

1.  $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'

2.  $sss = New-SPSecureStoreServiceApplication -Name 'Secure Store' -ApplicationPool $applicationPool -DatabaseName 'SecureStore_Upgrade_DB' -AuditingEnabled

3.  $sssp = New-SPSecureStoreServiceApplicationProxy -Name ProxyName -ServiceApplication $sss DefaultProxyGroup
 
4.  Update-SPSecureStoreApplicationServerKey -Passphrase <Passphrase> -ServiceApplicationProxy $sssp


To upgrade the Business Data Connectivity service application by using Windows PowerShell

1.  $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'
 
2.  New-SPBusinessDataCatalogServiceApplication -Name 'BDC Service' -ApplicationPool $applicationPool -DatabaseName 'BDC_Service_DB'


To upgrade the Managed Metadata service application by using Windows PowerShell

1.  $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'
 
2.  $mms = New-SPMetadataServiceApplication -Name 'Managed Metadata Service Application' -ApplicationPool $applicationPool -DatabaseName 'Managed Metadata Service_DB'
 
3.  New-SPMetadataServiceApplicationProxy -Name ProxyName -ServiceApplication $mms -DefaultProxyGroup


To upgrade the User Profile service application by using Windows PowerShell

1.  $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'

2.  $upa = New-SPProfileServiceApplication -Name 'User Profile Service Application' -ApplicationPool $applicationPool -ProfileDBName 'User Profile Service Application_ProfileDB' -SocialDBName 'User Profile Service Application_SocialDB' -ProfileSyncDBName 'User Profile Service Application_SyncDB'

3.  New-SPProfileServiceApplicationProxy -Name ProxyName -ServiceApplication $upa -DefaultProxyGroup


To import the encryption key for User Profile service application

1. Verify that you have the following memberships:

•Administrators group on the server on which you are running the command.

2. Open the Command Prompt window, and then change to the following folder:
%Program Files%\Microsoft Office Servers\15.0\Synchronization Service\Bin\

3. To import the key, type the following at the command prompt, and then press ENTER:

miiskmu.exe /i Path {0E19E162-827E-4077-82D4-E6ABD531636E}

•Path is the path and file name for the key that you want to import.
You might also have to enter a user name and password. These are the credentials for the farm administrator.


Start the User Profile Synchronization service


  1. Start SharePoint 2013 Central Administration.
    • For Windows Server 2008 R2:
      • Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
    • For Windows Server 2012:
      • On the Start screen, click SharePoint 2013 Central Administration.
If SharePoint 2013 Central Administration is not on the Start screen:
      • Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.

  1. In Central Administration, on the System Settings page, under Servers click Manage services on Server.
  2. Next to the User Profile Synchronization Service, click Start.
  3. In the Select the User Profile Application section, select the User Profile service application that you upgraded.
  4. In the Service Account Name and Password section, type the account name and password to use for the User Profile Synchronization service.


To upgrade the PerformancePoint Services service application by using Windows PowerShell

1.  $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'

2.  $pps = New-SPPerformancePointServiceApplication -Name 'PerformancePoint Service' -ApplicationPool $applicationPool -DatabaseName 'PerformancePoint Service Application_DB'

3.  New-SPPerformancePointServiceApplicationProxy -Name ProxyName -ServiceApplication $pps -Default


To upgrade the Search service application by using Windows PowerShell

1.  $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default'


$searchInst = Get-SPEnterpriseSearchServiceInstance -local
# Gets the Search service instance and sets a variable to use in the next command
Restore-SPEnterpriseSearchServiceApplication -Name '<SearchServiceApplicationName>' -applicationpool $applicationPool -databasename '<SearchServiceApplicationDBName>' -databaseserver <ServerName> -AdminSearchServiceInstance $searchInst

2.  $ssa = Get-SPEnterpriseSearchServiceApplication

3.  New-SPEnterpriseSearchServiceApplicationProxy -Name ProxyName -SearchApplication $ssa 
 
4.  $ssap = Get-SPEnterpriseSearchServiceApplicationProxy 
 
5.  Add-SPServiceApplicationProxyGroupMember –member $ssap -identity " "

Monday, January 7, 2013

Step 02: Copy databases to the new farm for upgrade to SharePoint 2013

To set a database to read-only by using SQL Server tools

1. Verify that the user account that is performing this procedure is a member of the db_owner fixed database role for the databases.

2. In SQL Server Management Studio, in Object Explorer, connect to an instance of the Database Engine, expand the server, and then expand Databases.

3. Find the database that you want to configure to be read-only, right-click the database, and then click Properties.

4. In the Database Properties dialog box, in the Select a page section, click Options.

5. In the details pane, under other options, in the State section, next to Database Read-Only, click the arrow, and then select true.


Back up the SharePoint 2010 Products databases by using SQL Server tools

You back up the databases in SQL Server Management Studio. A backup copy of the database guarantees that you have the data in a safe state if you must enable the original farm again and is required for a database-attach upgrade. Repeat the procedure for the following databases in the SharePoint 2010 Products server farm:

·         All content databases (default database name: WSS_Content_ID)
·         The following service application databases

Service application
Default database name
Business Data Connectivity
BDC_Service_DB_ID
Managed Metadata
Managed Metadata Service_ID
PerformancePoint
PerformancePoint Service Application_ID
Search Administration
Search_Service_Application_DB_ID
Secure Store
Secure_Store_Service_DB_ID
User Profile: Profile, Social, and Sync databases
User Profile Service Application_ProfileDB_ID
User Profile Service Application_SocialDB_ID
User Profile Service Application_SyncDB_ID



To back up a database by using SQL Server tools

1. Verify that the user account that is performing this procedure is a member of the db_owner fixed database role for the databases.

2. In Management Studio, in Object Explorer, connect to an instance of the Database Engine, expand the server, and then expand Databases.

3. Right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.

4. In the Source area, in the Database box, verify the database name.

5. In the Backup type box, select Full.

6. Under Backup component, select Database.

7. In the Backup set area, in the Name box, either accept the backup set name that is suggested or type a different name for the backup set.

8. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.

9. Click OK to start the backup process.


To restore a backup copy of a database by using SQL Server tools

1. Verify that the user account that is performing this procedure is a member of the db_owner fixed database role for the databases.

2. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.

3. Right-click Databases, and then click Restore Database.
The Restore Database dialog box appears.

4. In the Restore Database dialog box, on the General page, type the name of the database to be restored in the to database list.


5. In the To a point in time text box, keep the default (Most recent possible).

6. To specify the source and location of the backup sets to restore, click from device, and then use the ellipsis (...) to select the backup file.

7. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.

8. In the Backup location area, click Add.

9. In the Locate Backup File dialog box, select the file that you want to restore, click OK, and then, in the Specify Backup dialog box, click OK.

10. In the Restore Database dialog box, under select the backup sets to restore grid, select the Restore check box next to the most recent full backup.

11. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.

12. Click OK to start the restore process.


To set a database to read-write by using SQL Server tools

1. In SQL Server Management Studio, in Object Explorer, connect to an instance of the Database Engine, expand the server, and then expand Databases.

2. Select the database that you want to configure to be read-write, right-click the database, and then click Properties.

3. In the Database Properties dialog box, in the Select a page section, click Options.

4. In the details pane, under other options, in the State section, next to Database Read-Only, click the arrow, and then select False.

Step 03: Upgrade service applications to SharePoint 2013

How to migrate SharePoint 2010 My Site to 2013 My Site

Step 01: Export the Encryption Key & Create the SharePoint 2013 farm

To export the encryption key for the User Profile service application

1. Verify that you have the following memberships:
•Administrators group on the server on which you are running the command.

2. Open the Command Prompt window, and then change to the following folder:
%Program Files%\Microsoft Office Servers\14.0\Synchronization Service\Bin\

3. To export the key, type the following at the command prompt, and then press ENTER:
miiskmu.exe

4. In the Microsoft Identity Integration Server Key Management Utility wizard, verify that Export key set is selected, and then click next.

In the Account Name box, type the account name for the farm administrator.
In the Password box, type the password for the farm administrator.
In the Domain box, type the domain that contains the farm administrator account, and then click next.

5. In the Specify export file name and location box, type or click browse to select the path and file name to use for the exported key, and then click next.
The key is exported as a file that has a .BIN file name extension.

6. Verify the information, and then click Finish.
A message appears indicating that the key was successfully exported.

Install SharePoint 2013 in a new environment

1. Run the Microsoft SharePoint Products Preparation Tool to install all required software.

2. Run Setup to install the product.

3. Install all language packs that you want in your environment.

4. Run the SharePoint Products Configuration Wizard to configure your server or servers.
Configure service applications

You must create the service applications on your new farm before you upgrade your content databases. There are some service applications that can be upgraded from SharePoint 2010 Products to SharePoint 2013. The steps in Install SharePoint 2013 describe how to use the Farm Configuration Wizard to enable all service applications. However, you should not use the Farm Configuration Wizard to enable the service applications that you want to upgrade.

The following service applications can be upgraded by performing a services database upgrade:

ü  Business Data Connectivity service
ü  Managed Metadata service
ü  PerformancePoint services
ü  Search
ü  Secure Store service