Please follow the documentation on Technet to create the new SharePoint 2013 farm. Most of the prerequisite information must already have been recorded previously in this document.

At a high level, this includes:

1. Create new server instances on an operating system supported by SharePoint 2013. Typically, this is Windows Server 2012 R2. SharePoint 2013 hardware and software requirements are outlined here. SharePoint 2013 also requires a SQL instance on which to store database, usually SQL 2008 R2 or SQL 2014.
2. It is assumed that you are using the same service and admin accounts in the SharePoint 2013 environment that were used for the same functions in the SharePoint 2010 environments. Permissions for these accounts (in Windows, SQL, and SharePoint) should be the same, otherwise you run into permissions errors.
3. For each server in the farm, install SharePoint 2013, Service Pack 1, and the latest SharePoint 2013 Cumulative Update.
4. For each server in the farm install any SharePoint Language packs.
5. If Office Web Apps is to be used, install at this time.
6. Run the SharePoint Configuration Wizard on each server in the farm. You start with the server that is to host SharePoint Central Administration, where you can choose to create a new farm. On each subsequent server you have to run the SharePoint configuration Wizard and attach the server to the new farm.
7. Configure farm settings. These include:
   • Incoming and outgoing e-mail setting.
   • All Farm-level security permissions settings, such as users in the Farm Administrators group.
   • Blocked file settings.
   • Diagnostic logging
   • Settings and schedules for timer jobs.

Aurea Social for SharePoint 2013 requires SSL to communicate with the SharePoint object model.

Generate a digital certificate for the web application(s) that hosts Aurea Social features.

Create an Alternate Access Mapping (AAM) for each of these web applications.

The AAM does not have to be used. It is only required to communicate with the backend.

For further details, see how to create a domain server certificate in IIS 7.

Take a backup of all your SharePoint 2010 content databases recorded in the pre migration steps above.

Create a ‘Databases’ folder on your new SQL server and copy each of the .bak files to this folder.

Restore the databases to SQL Server that hosts the SharePoint and Aurea Social databases.

Create the required web applications with new databases that were recorded in step 20 of the prerequisites.

The default web application databases is deleted in the steps below as you import the content databases from SharePoint 2010.

1. Create web applications in SharePoint 2013 to match the web applications in SharePoint 2010. If your SharePoint 2010 web applications uses classic authentication (NTLM), the web application has to be created using Powershell. NTLM based web applications were deprecated in SharePoint 2013 and are considered ‘obsolete’.
   New-SPWebApplication -Name “<Name>” -ApplicationPool“<ApplicationPool>” -AuthenticationMethod“<WindowsAuthType>” -ApplicationPoolAccount“<ApplicationPoolAccount>” -Port <Port> -URL “<URL>”
2. Repeat the process for each required web application.
3. Attach the content databases from SharePoint 2010 AFTER you have installed the Aurea Social 2013 solutions, described in the next section.
4. Setup / Bind SSL certificates as required in IIS Manager on each web front end.
5. If you are using authentication other than claims with NTLM, perform additional configuration steps as needed.

Install and deploy any third-party software or customizations (such as branding) that was present in the 2010 farm.

This includes installing and deploying custom solutions. If the third-party customizations require service applications, you may create them as needed; but, remember these will later be deleted and re-created with the migrated databases.

1. The steps in this section need to be completed before attaching the content databases to the web applications.
2. Download the Aurea Social installer from the release portal along with your licensed module(s). These should match the version of Aurea Social installed in your 2010 farm.
3. Consolidate all the solution files (.wsp) in the Solutions folder of the installer.
   Important:

   Make sure that you have copied all the solution files (.wsp) that where installed on your 2010 installation or your SharePoint content database does not upgrade correctly. If you have installed any of the NewsGator modules you must put their solution files in this folder now.

4. Launch launcher.exe and
5. Go to Advanced Options > Install or Upgrade Sitrion Social with Advanced Options and check the box next to Skip Prerequisite Check.
6. Click Install or Upgrade. DO NOT choose to provision service applications. Service applications is created later.

Now that the Aurea Social solutions have been deployed, the SharePoint content databases need to be tested for compatibility with the new farm.

Use the following powershell to test each content database:

Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename

Address any errors before proceeding. Some errors may need to be addressed in your SharePoint 2010 farm, then new backups of your content databases moved over, then run through more rounds of testing with test-spcontentdabase command.

Helpful links for troubleshooting:

Once you have addressed the errors, you are ready to fully migrate the SharePoint 2010 environment to the SharePoint 2013 environment.

For Production environments, this is typically the last step that can be performed before an outage window is required for further work.

Put your SharePoint 2010 environment in Read-Only mode. Take a backup of all your SharePoint 2010 content and service applications databases recorded in the pre migration steps above. Copy each of these .bak files to the SQL environment for your new SharePoint 2013 farm.

Restore the databases to SQL Server that hosts the SharePoint and Aurea Social databases. You may choose to not backup and restore the Search Service Application databases and just rebuild the indexes on SharePoint 2013.

If you are changing from one URL to another, please consult our URL migration documentation described in another document.

Provision the service applications in SharePoint 2013. Ensure that you use the correct service application databases that you restored earlier. Certain service applications requires an iis reset to be performed before the management pages can be accessed. After provisioning the service applications, ensure that you have started the corresponding services on your load balanced application servers.

As you provision the SharePoint service application, reference the Upgrade service applications to SharePoint 2013 article on TechNet for a complete set of instructions.

• Provision the Managed Metadata Service application in your SharePoint 2013 farm using the database from your SharePoint 2010 environment. Ensure you provide the correct application pool identity.
• Provision the Search Service application in your SharePoint 2013 farm using the databases from your SharePoint 2010 environment. Ensure you provide the correct application pool identity
• Provision the User Profile Service Application in your SharePoint 2013 farm using the Profile DB, Sync DB, and Social DB from your SharePoint 2010 environment. Ensure you provide the correct application pool identities. The content databases have not yet been attached to new web applications so do not yet provide the My Site Url. The User Profile Service Application requires that you perform an iisreset after it is provisioned. You also need to import the encryption key after you have started the User Profile Synchronization service on your servers. This is covered in the Upgrade service applications to SharePoint 2013 article on TechNet.
• Provision the Business Data Connectivity Service application in your SharePoint 2013 farm using the database from your SharePoint 2010 environment. Ensure you provide the correct application pool identity.

The SharePoint content databases need to be attached to the web applications that were created in the previous steps.

1. Delete the content databases that were created by the web application provisioning process. You may do this through SharePoint Central Administration > Application management > Manage Content Databases. Click on the appropriate database, then check the box next to Remove content database. Click OK.
2. Configure email settings on the web applications
3. Open a SharePoint Management Shell window (right click, run as administrator). Type the following command and then press Enter:
   Mount-SPContentDatabase -Name “DatabaseName” -DatabaseServer“ServerName” -WebApplication“URL”
4. Check the log file for any errors or exceptions.
5. Create the managed paths as they were defined in SharePoint 2010
6. Enable self-service site creation, where applicable, specifically in the My Sites web application.
7. Recreate the web application policies.
8. Recreate quota templates.
9. Create AAMs for each of your web applications.
10. Apply the digital certificate(s) in IIS.

Update your DNS records to point to the new SharePoint 2013 instance.

Aurea Social keeps a record of the farm id but when the content database is attached to the SharePoint 2013 farm, it must be updated.

Open a SharePoint Management Shell window on the 2013 farm (right click, run as admistrator), and then type out the following:

Copy the GUID that is returned.

Run the following SQL update on the SharePoint 2013 farm against the NewsGator_SocialServices database.

Verify the following Product functionality:

• Create a new post.
• Comment on the new post and an existing post.
• Like the new post, as well as an existing post.
• Mark for follow up the new post as well as an existing post.
• Create a new post with an attachment.
• Create a poll.
• @target a community in a post.
• Share a post.
• Add a new colleague.
• Follow a community.
• Trigger an instant email notification.
• Create a new community. Complete community setup.
• Use the Getting Started web part or the profile setup portion on the Lookout page to upload a new profile picture.
• Video Stream: Upload a new video to a video center. Does it encode? Can you view it?
• Video Stream: Link to a Youtube video in the Activity Stream. Can you watch it in-line?
• News Stream: Add a new rss subscription in Central Administration > Application Management > Manage Service Applications > NewsGator News Stream Services > Manage Feeds.
• News Stream: if your organization allows personal subscriptions, add a new subscription from the Activity Stream web part edit my subscriptions link.
• Spotlight: Create a new automatic rule in Spotlight Management for one microblog. Create a new badge tied to this rule. Post a microblog. Run the NewsGator Reporting Database Load job followed by the NewsGator Spotlight Processing job from Central Administration > Monitoring > Review Job Definitions. Are you awarded the badge?
• Ideas: Create a new site using the NewsGator Private Idea site template. Create a new idea. Vote on it.
• If you have Aurea Social deployed to multiple web applications, test posting a basic microblog from a NewsGator / Aurea Social web part in each web application.