1. CloudM
  2. Migrate
  3. Source and Destination Configuration Guides
  4. Other Supported Source Platforms

Configuring SharePoint 2013/2016

Dave Whitby
Updated

Web Application Authentication Providers.

  1. Only Web applications with Windows Authentication, Integrated Windows authentication with NTLM enabled can be migrated. This can be checked by doing the following :  

    1. Login to SharePoint ‘Central Administration’
    2. Click on ‘Application Management’ and then 'Manage web applications'
    3. Select the web application from the list and click on 'Authentication Providers'
    4. Click on 'Default' under the 'Zone' header

    5. Both  'Enable Windows Authentication' and 'Integrated Windows authentication' should be checked.

                 

      1. Enabling Windows Authentication with Integrated Windows Authentication
        NOTE : When enabling multiple authentication providers for a web application end users will be presented with the following screen. If you prefer the user's login experience not to change then you will need to extend the web application.
         

      2. Login to SharePoint ‘Central Administration’
      3. Click on ‘Application Management’ and then 'Manage web applications'
      4. Select the web application from the list and click on 'Authentication Providers'
      5. Click on 'Default' under the 'Zone' header and check the box next to  'Enable Windows Authentication' and the box next to 'Integrated Windows authentication'
      6. Click 'Save'

                           

Extending existing web application

In the following example the web application to be extended url is 'http://sp-2016:10515' and only uses 'Claims Authentication Types > Enable Forms Based Authentication (FBA)'. This will be extended to 'Claims Authentication Types > Enable Windows Authentication > Integrated Windows Authentication > NTLM' with the following url  'http://SP-2016:48113'. 

When populating the 'User/Resources' tab in CloudM Migrate any site collection that resides under 'http:sp2016:10515' will need to be added with 'http://SP-2016:48113' eg 'http:sp2016:10515/site name' would be 'http://SP-2016:48113/site name'

  1. Login to SharePoint ‘Central Administration’
  2. Click on ‘Application Management’ and then 'Manage web applications'
  3. Select the web application to be extended.
  4. Select 'Create a new IIS Site' and populate the 'Name' with a descriptive title. In this example 'My Sites Extended' and check boxes next to 'Enable Windows Authentication' and 'Integrated Windows Authentication', scroll to the bottom and select 'Custom' for the 'Zone'. As an additional option you can add host header if required otherwise this can be left empty.
  5. Scroll to the bottom of the dialog box and make a note of the url. This Url will be required to migrate sites from this web application
  6. Click 'OK'. This will now create an additional IIS website with the required authentication setup. More information can be found here Extend claims-based web applications in SharePoint 2016.

Site Collection Access

Before 'Adding a Policy for a Web Application' you should consult your SharePoint administrator and review any implications for this change.

In order to access data in SharePoint (Team Sites or My Sites/OneDrive) the account configured in CloudM Migrate must be able to access the site collection being migrated. This can be accomplished three ways and is recommended that your consult your SharePoint Administrator :

  1. Adding a Policy for a Web Application
  2. Manually adding site collection administrators to each site collection

  3. Add Site Collection Administrator using PowerShell

Adding a Policy for a Web Application

  1. Login to SharePoint ‘Central Administration’
  2. Click ‘Application Management > Manage web applications’
  3. Select the web application from the list and click 'User Policy'
  4. Select '(All zones)' if not already select from the dropdown and click 'Next >'. 
  5. Enter the administrative user that will be used in CloudM Migrate and check 'Full Control - Has full control' and click 'Finish'
     

Manually Add Site Collection Administrator

  1. Login to SharePoint ‘Central Administration’
  2. Click on ‘Application Management’ and then ‘Change site collection administrators’
  3. Add the account to the ‘Secondary site collection administrator’ and then click ‘OK’
  4. To change site collection click on the arrow to the right of ‘Site Collection’ and then ‘Change Site Collection’
  5. Select the site collection and click ‘OK’ and follow step' c' to add ‘Secondary site collection administrator’

Add Site Collection Administrator using PowerShell

    1. The following script will need to be ran on the SharePoint server with administrative rights to SharePoint. The script will generate a .csv file containing the url each site.

      1. Specify a location for outputted .csv file by populating $saveSites or leaving the default 'c:\\sites.csv'

        try
{ 
    $saveSites = "c:\\sites.csv";
    if($saveSiteListLocation -ne $null -AND $saveSites -ne "")
    {
        [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
        $farm = [Microsoft.SharePoint.Administration.SPFarm]::Local
        $websvcs = $farm.Services | where -FilterScript {$_.GetType() -eq [Microsoft.SharePoint.Administration.SPWebService]}
 
        [Microsoft.SharePoint.SPSecurity]::RunWithElevatedPrivileges(
        {
            $output = foreach ($websvc in $websvcs)
            {
                foreach ($webApplication in $websvc.WebApplications)
                {    
                    foreach($siteCollection in $webApplication.Sites)
                    {
                            New-Object -TypeName PSObject -Property @{
                                Url = $siteCollection.Url
                            } | Select-Object Url
                            Write-host  $siteCollection.Url
                    }
                }
            }
            $output | Export-Csv $saveSites -force -notypeinformation
        });
    }
    else
    {
        Write-host "Save Site List Location has not been entered.";
    }
}
catch
{
    Write-Host $error[0].Exception.Message -foreground red
}

    2. Review the .csv file and remove any sites you do want to update with the site collection administrator. Populate the following :

      1. $userId - SharePoint administrator UserId of the user entered in the CloudM Migrate e.g. "contoso\cloudmmigrate"

      2. $userEmail - email address associated to the UserId entered above e.g. "cloudmmigrate@contoso.com"

      3. $userName - name of the user e.g."cloudmmigrate"

      4. $removeAdmin - remove the above user from specified site collections default "N"

      5. $savedSites - location of the file specified in step 1;

        try
{
	Set-ExecutionPolicy Unrestricted
	if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) 
	{
		Write-Host "Adding Microsoft.SharePoint.PowerShell Snapin" -ForegroundColor White
		Add-PSSnapin "Microsoft.SharePoint.PowerShell"
	}
	else
	{
		Write-Host "Microsoft.SharePoint.PowerShell Snapin already added" -ForegroundColor White
	}

	$userId = "contoso\cloudmmigrate"
	$userEmail = "cloudmmigrate@contoso.com"
	$userName = "cloudmmigrate"
	$remmoveAdmin = "Y"
    $savedSites = "c:\\sites.csv";

	$importedSites = Import-Csv $savedSites 
	$userId = New-SPClaimsPrincipal -Identity $userId -IdentityType WindowsSamAccountName
	$userId = $userId.ToEncodedString()

	[Microsoft.SharePoint.SPSecurity]::RunWithElevatedPrivileges({

		foreach($siteDetail in $importedSites) 
		{ 
			try 
			{ 
				$siteUrl = $siteDetail.Url;
				
				Write-host "Processing $siteUrl"
				$site = New-Object Microsoft.SharePoint.SPSite($siteUrl) 
				$web = $site.Rootweb 

				
				if($remmoveAdmin -eq "N")
				{
					$web.SiteUsers.Add($($userId), $($userEmail),$($userName), "") 
					$adminUser = $web.EnsureUser($($userId)) 
					$web.Update() 

					if($adminUser.IsSiteAdmin) 
					{ 
						Write-Host "$($userName) is already a site collection administrator: " $web.Url -ForegroundColor DarkYellow
					} 
					else 
					{ 
						$adminUser.IsSiteAdmin = $true 
						$adminUser.Update() 
						write-host "$($userName) added as site collection administrator: " $web.Url -ForegroundColor Green 
					} 
				}
				else
				{
					$adminUser = $web.EnsureUser($($userId)) 
					if($adminUser.IsSiteAdmin) 
					{
						$adminUser.IsSiteAdmin = $false 
						$adminUser.Update() 
						write-host "$($userName) removed as site collection administrator: " $web.Url -ForegroundColor Green 
					}
					else
					{
						Write-Host "$($userName) is not site collection administrator:" $web.Url -ForegroundColor DarkYellow
					}
				}

			} 
			catch 
			{ 
				Write-Host $error[0].Exception.Message $web.Url -foreground red 
			} 
		} 
	});
}
catch 
{ 
	Write-Host $error[0].Exception.Message -foreground red 
}

Where to find Team Sites Url

  1. Login to SharePoint ‘Central Administration’

  2. Click on ‘Application Management’ and then ‘View all site collections’ select the web application that contains the sites you would like to migrate. Make a note of the web application as this will be required for the ‘Team Site Url’ in CloudM Migrate. 
     

Where to find My Sites Url

    1. Login to SharePoint ‘Central Administration’

    2. Click on ‘Application Management’ and then ‘Manage Service Applications’’

    3. Click on ‘User Profile Service Application’

    4. Click ‘Setup My Sites’ under ‘My Site Settings’

    5. Make a note of ‘My Site Host location’ as this will be required for ‘My Site Url’ setting in CloudM Migrate.

User Profile Service Application

  1. SharePoint 2010/2013/2016 may require this extra step. To allow CloudM Migrate to get users with ‘My Sites’ the account entered in ‘Account Details’ requires the following permissions.

    1. Login to SharePoint ‘Central Administration’

    2. Click on ‘Application Management’ and then ‘Manage Service Applications’’

    3. Click to the right ‘User Profile Service Application’ so the row is selected and the menu ‘Administrators’ menu option is enabled.

    4. Click on ‘Administrators’ add the account you will be using to perform the migration if the account is not already present.

Generating the Team Sites list

  1. The 'Central Administration Url' is required for generating a list of Team Sites/Subsites and the details entered in the 'Admin Details' section will need to be an administrator.

  2. To generate a list of all Team Sites and Subsites the account in the 'Admin Details' should have already been added as a site collection administrator or given access to each site to be migrated.

Was this article helpful?
2 out of 2 found this helpful