Proven Practices for Upgrading or Migrating to SP2016 WhitePaper Flashcards

1
Q

Ensure a detailed and agreed upon vision has been established for your new platform.

A

a. Define What is the purpose of SharePoint Online, Server, or Hybrid?

            i. Intranet
	ii. External Collaboration
	iii. Client Portal
	iv. Records Management
	v. Social Platform
	vi. Project Sites
            vii. Other
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Identify and take inventory of all legacy content, repositories and applications.

A

a. Readiness Assessment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Identify which teams/business units are ready to migrate.

A

a. Identify applications complexity
b. Identify existing workflows/in-progress
c. Identify customized sites

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Prioritize and classify all content and applications.

A

a. Content must be properly tagged with metadata, including:
i. Created by
ii. Modified by
iii. Business unit
iv. Other relevant metadata
b. Prioritize applications based on the following criteria:
i. Business Critical
ii. Important
iii. Nice to Have

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Customization and rationalizing migration content

A
  1. Are they replaced by native functionality?
    2. Are they still necessary?
    3. What is the cost of maintenance?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Archive and delete redundant and legacy data.

A

a. Classified as having no value or outdated
b. Archived for compliance purposes
c. Kept on premises due to regulatory requirements (not cloud ready)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

(Optional) Build destination information architecture.

A

a. Security
b. Structure
i. Managed paths, quotas, etc.

ii. (SharePoint 2016 Specific) Pre-Provision ODFB and SharePoint Sites
c. Configurations
i. Features, settings, templates, look and feel
7) Begin migration project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Upgrade Note 1

A

SharePoint 2016 does not support in-place or gradual upgrade methods. You should also be aware that if your current deployment is operating with in-place upgrades, you will need to have all back and front end functionality set to SharePoint 2013 in order to use Microsoft’s native upgrade option.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Upgrade Note 2

A

Microsoft-provided upgrade options do not allow upgrade beyond a single version of SharePoint at one time. Organizations that are currently running SharePoint 2010, MOSS 2007, or prior versions of SharePoint must first plan and implement an upgrade to SharePoint 2013 before being able to perform a native upgrade capabilities to SharePoint 2016.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Which SharePoint Service is Right for you?

SharePoint 2016

A

When to Select

  • Organizational policy (e.g. security, data doesn’t permit use of cloud services).
  • You have the budget, staff, data center, hardware, and software required to maintain an environment on premises.

You don’t require aces to SharePoint beyond your organization’s walls (e.g. mobile workforce or access for customers and business partners). You have customizations not supported in the cloud.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Which SharePoint Service is Right for you? SharePoint 2016

A

When to NOT Select

  • Data center capacity not available.
  • You are not equipped with a data center at all.
  • You have no available budget for servers, network, storage, and staffing.
  • You require access to SharePoint beyond your organization’s walls.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Which SharePoint Service is Right for you?

Office 365

A

When to Select

  • You don’t have available productivity tools or are using mixed toolsets and want to standardize.
  • You don’t want to manage software distribution and updates.
  • Standardized on thin client model to end user computing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Which SharePoint Service is Right for you?

Office 365

A

When to NOT Select

  • Your policy doesn’t permit use of cloud services.
  • You don’t require access to SharePoint beyond your organization’s walls.
  • You have customizations not supported in the cloud
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Which SharePoint Service is Right for you? SharePoint Online

A

When to select

  • Your policy permits the use of cloud services.
  • You don’t have the budget for staff, data center, hardware, or software.
  • You require access to SharePoint beyond your organization’s walls.
  • You don’t have customizations or third party software not supported in cloud.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Which SharePoint Service is Right for you? SharePoint Online

A

When to NOT Select

  • Policy doesn’t permit use of cloud services.
  • You don’t require access to SharePoint beyond your organization’s walls.
  • You have customizations not supported in the cloud.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Which SharePoint Service is Right for you? Hybrid

A
  • Your policy permits the use of cloud services.
  • You have budget to maintain status quo but must expand offering.
  • You require access to SharePoint beyond your organization’s walls.
  • You have customizations not required to run in the cloud.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Benefits of Independent Software Vendor (ISV) Solutions

A

Simplicity

An ISV solution is as simple to use as copy and paste.

Efficiency

You can migrate SharePoint sites, lists, and libraries between servers quickly and with full fidelity.

Active Sources

You can migrate content from live sites and unattached content databases.

Direct Migrations

There is no longer a need to upgrade the on-premises environment to match the version of the hosted service.

Legacy Migrations

You can upgrade directly from SharePoint 2003, SharePoint 2007 and SharePoint 2010 to SharePoint 2016

Re-Architecting

Migrating provides an opportunity to re-organize or re-template your SharePoint content.

Minimal Business Disruptions

You can manage your migrations with zero downtime, no change windows, and no prior planning.

Cost Savings

You can migrate to the cloud or hosted SharePoint environments and thereby reduce infrastructure costs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Manual Migration: Benefits and Challenges

Best for…

A

Environments with a very high percentage of content that doesn’t need to be migrated. Migrating to SharePoint from a different platform. (Documentum, Lotus Notes

19
Q

Manual Migration: Benefits and Challenges

Best for… Benefits

A
  • A large number of users helping with the migration may speed up the process.
  • Migrates only relevant content to avoid import of old data.
  • Legacy environment is retained. Virtually no downtime, requiring user switch to new environment.
20
Q

Manual Migration: Benefits and Challenges

Best for… Challenges/Risks

A

Challenges/Risks

  • Manual, resource-intensive process; motivating users and enforcing migration deadlines. Does not preserve prior versions, audit history, item metadata, or unique permissions.
  • Requires willing participants and training.
  • Requires additional steps to retain original URLs
  • Requires new server farm and additional SQL Server storage space for new content
21
Q

Scripted Migration- Benefits and Challenges

A

Best for…

  • Environments that are highly customized or need very precise migration methods to preserve context between source and destination.
  • Situations where manual or third-party migration are not viable.
22
Q

Scripted Migration- Benefits and Challenges

A

Benefits…

  • Most flexibility in deciding migration details such as what content gets migrated, when, and how.
  • Can be developed to be fully automated without involving users.
  • Legacy environment can be retained.
  • Virtually no downtime, requiring user switch to new environment
23
Q

Scripted Migration- Benefits and Challenges

A

Challenges

  • Manual, resource-intensive process; motivating users and enforcing migration deadlines.
  • Does not preserve prior versions, audit history, item metadata, or unique permissions.
  • Requires willing participants and training.
  • Requires additional steps to retain original URLs
  • Requires new server farm and additional SQL Server storage space for new content
24
Q

Migration Solutions versus Integration Solutions

A

Migration

Data is available in SharePoint

Data is migrated into SharePoint

SharePoint replaces the file system

Burden of storage is on SharePoint (more expensive)

Changes are saved in SharePoint content database

Migrate and decommission

25
Q

Migration Solutions versus Integration Solutions

A

Integration

Data is available in SharePoint

Data is left in source (legacy) systems

Gives file systems a second life by increasing its value

Burden of storage is on file system (more affordable)

Changes to file are propagated back to the source system

Connect and forget

26
Q

Hardware Requirements

A

For SharePoint 2016, the absolute minimum requirements for web front-end and application servers are 12-16 GB RAM and four 64-bit cores to power small environments. In our experience, there are a few fundamental aspects of SharePoint that will not function without additional memory. Therefore, we advise you equip production servers with no less than 16-24 GB RAM. For larger environments, it’s best to increase your CPU cores up to eight.

27
Q

Software Requirements

A

SharePoint 2016 will run on a 64-bit edition of Windows Server 2012 R2 or Windows Server 2016 Technical Preview.

Windows Server 2012 R2 4.5.2

Windows Server 2016 Technical Preview 4.6

28
Q

Database Requirements

A

SharePoint 2016 requires its database server to be a 64-bit version running either Microsoft SQL Server 2014 or Microsoft SQL Server 2016.

29
Q

Database Attach: The Native Upgrade

A

The native upgrade option is only supported from SharePoint 2013. More specifically, it’s only supported for SharePoint 2013 environments that have database versions of 15.0.4481.1005 or higher. It also requires that all site collections in each attached database are in SharePoint 2013 mode, which is also known as compatibility level 15.

30
Q

Database Attach: Things to Consider

A

 A new farm must be built and any custom code or third-party solutions that are currently in use should be applied to the new farm.
 Database attach upgrade will not fix any corrupt or orphaned web sites or site collections.
 You can only upgrade from the previous SharePoint version.
 Upgrading is done on a database-by-database basis. You cannot upgrade individual sites or site collections.
 Depending on the speed of your servers – in particular your SQL server(s) – you may be able to upgrade multiple database concurrently. This process is called parallel database upgrade.
 Upgrading to SharePoint 2013 or SharePoint 2016 is done with PowerShell, using the Mount-SPContentDatabase cmdlet.
 You have the option of testing the upgrade using the Test-SPContentDatabase cmdlet. This process does not modify the source database and only reports back on the compatibility of the database against the new farm.
 To help minimize downtime between the source and destination farm, it is common to set databases in the source farm to read-only. This allows users to read content from the source farm while it is being upgraded. This can be done at the database level using SQL Server Management Studio or at the site collection level using Central Administration, provided you set each site collection in the database as read only.

31
Q

Upgrade Considerations

A

The previous methods noted for upgrading from older versions of SharePoint to SharePoint 2016 assume that organizations have already conducted the steps necessary to ensure their hardware, operating systems, and databases are already up-to-date and ready to support Microsoft’s latest platform release. If not, then there are other actions that must take place prior to any upgrade method. There may be additional steps that need to be taken, depending on the previous configuration and whether this is compatible with SharePoint 2016.

32
Q

Upgrade Considerations 2

A

 Upgrading an environment utilizing forms-based authentication
 Migrating from classic to claims-based authentication
 On SQL Server, versions earlier than 2014, SQL Express, or standalone SharePoint installations you will need to upgrade to the minimum database requirement
 Upgrading environments with heavy customizations (for example, custom master pages or CSS) or custom code
 Any SharePoint 2013 14.5 Site Collections effectively running in SharePoint 2010 mode, will need to be brought forward to SharePoint 2013 before they can be migrated to SharePoint 2016. Those SharePoint 2013 sites will then need to be migrated directly to SharePoint 2016 or you can use the database attach methodology.

33
Q

Upgrade Considerations 3

A

 Overall database size number of SharePoint items
 Hardware (in particular on the database servers)
 Pre-upgrade steps required – including health checks, cleanups or performing backups
 Post-upgrade steps required – including verifying sites, creating service applications, conducting people/search crawls, upgrading site collections, end-user training, leveraging new features such as social
 System downtime communication and coordination with end users

34
Q

DocAve Connector

A

presents and manages files (including large media files and documents) via SharePoint without the need to upload or migrating into SharePoint. At a basic level, SharePoint presents file share content to users as though they are stored inside a document library. Virtually every SharePoint function – including check-in/check-out, versioning, managing permissions, auditing, and metadata – can be applied to these files, even though the files reside in the file share. New files that are uploaded or created are stored in the file share along with the reference pointer that is placed in the SharePoint library. DocAve Connector also supports streaming of video content.

35
Q

DocAve File Share Navigator

A

With DocAve File Share Navigator, users can continue to access content located within file shares from SharePoint (and SharePoint Online through DocAve File Share Navigator Online). However, the full SharePoint feature set such as check-in/check-out and versioning is not available. This is a nimble solution that provides some features unavailable in DocAve Connector such as the ability to preview files without having to download them and a direct link to where externally hosted files live.

36
Q

Recommended Migration Methodology - Transition of customizations

A

This activity involves either re-designing, re-coding, or re-building each customization that is required in the target environment.

37
Q

Recommended Migration Methodology -Content mapping

A

This activity establishes the alignment between the format and layout of the content in the source environment, and the information architecture in the target environment. Column and content type mappings, templates, filters, and permissions are mapped as a part of this activity.

38
Q

Recommended Migration Methodology -Migration planning

A

This activity breaks the migration down into a series of batches or phases to understand the business implications of the migration. It also coordinates the necessary resources, trains the migration team, and schedules all migration activities. It also considers whether data clean-up is required and if so, whether it will occur pre-migration, in-flight during the migration, or post-migration.

39
Q

Recommended Migration Methodology -Pilot migration

A

This activity establishes a set of migration scenarios which are representative of the production data set. It then tests each scenario in a non-production environment using a representative sample of data. This confirms the technical feasibility of the migration, identifies any gaps that must be addressed, and provides the migration team to walk through an end-to-end content migration. In addition to the actual migration of content, the “end-to-end” migration tests permissions and access, verifies success, captures and addresses any errors, documents results, and gathers migration statistics. It also provides an opportunity to optimize the migration activities and should include rollback testing.

40
Q

Recommended Migration Methodology -Production migration

A

This activity migrates content to the target environment. It is repeated for each batch of the migration.

41
Q

Recommended Migration Methodology-Testing and validation

A

This activity validates the success of the migration from the perspective of whether or not the target environment meets the requirements of the business it supports. The results obtained at this time should be consistent with the results obtained during the pilot migration, and any discrepancies can be addressed at this time. This activity is repeated for each batch of the migration.

42
Q

Recommended Migration Methodology-Synchronization of changes

A

This activity captures any changes to the source environment that occurs between the initial migration and completion of the user transition, and ensures they are reflected in the target environment. This activity is repeated for each batch of the migration.

43
Q

Recommended Migration Methodology-Transition of users

A

This activity involves ‘freezing’ the source environment, performing one final synchronization of changes, and transitioning users to the target environment so it becomes their primary environment going forward. This activity is repeated for each batch of the migration.

44
Q

Technology: The Role of Migration Software

A

Provide Automation, Increase the Capability of the Migration Team, Create Consistency, Provide Visibility and Record Progress, Restructuring Content During Migration