SharePoint Migration Tool (SPMT) – A Quick Look

SharePoint Migration Tool (SPMT) – A Quick Look

  • Basically a GUI wrapper for PowerShell scripts to migrate content to SharePoint Online provided by Microsoft themselves
  • The PowerShell script are also able to be referenced by available cmdlet after loading the module (Import-Module Microsoft.SharePoint.MigrationTool.PowerShell )
  • Designed to be used for migrations ranging from the smallest set of files to a large scale enterprise migration
  • Officially only support SharePoint Server 2010 and 2013, also network and local file shares – Though is possible to make it work for 2016
  • Created By, Modified By, Date Created and Date Modified details will be copied where possible
  • Possible to tee up bulk migrations

Migration Tips

  • Scan source first using SharePoint Migration Assessment Tool
  • Split migrations into small chunks to improve speed (about 250MB per transfer)
  • For a larger than 100TB migration, please submit a support request

SharePoint Migration Assessment Tool – 2016 Support

  • Now you won’t get any support from Microsoft with this mod, but hey is there really any difference between 2013 and 2016
  • Open regedit.exe where you are running spmtsetup.exe and add the following
    • Create Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MigrationTool
    • New Multistring: SupportedSPVersions
    • Value: 15 16 (on separate lines)
SharePoint Migration Tool: Regedit

Executing

  • Download exe and run, Site Collection administrator is required at both sources and destination
  • Can perform full site collection or individual list/library migrations
  • Can tee up multiple jobs to run or save for later
  • Enough migration settings to manipulate to your needs
  • Option to perform a scan of content before actual migration take place
SharePoint Migration Tool: Settings
SharePoint Migration Tool – Progress

Great tool for migrating content, it won’t provide 100% coverage especially when you’re looking at classic features like master pages and the like.

Reference

SharePoint Migration Assessment Tool (SMAT): A Quick Look

SharePoint Migration Assessment Tool (SMAT): A Quick Look

  • Simple cmd line tool that scans the content of on-premises farm to identify issues with migration to online
  • Slow running as it should be run against production and not cause usage degradation
  • Outputs log file for review and analysis
  • 2 modes, Assessment and Identity Mapping
  • Officially only supports SharePoint 2010 and 2013, but it worked fine for me on 2016

Running Assessment

  • Run As: farm or SP admin account, needs full access to farm
  • Config
    • SiteSkipList.csv – use to exclude sites
    • ScanDef.json – user to exclude scan functionality
  • Execution
    • Cmd console as administration
    • Smat.exe /help – for list of options
    • –t – Maximum number of thread (default 3, ramp it up to 6 max)
SharePoint Migration Assessment Tool - Running
SMAT: Running via cmd line

Output

  • Summary and detailed csv report outputs are generated to review and analysis
  • A lot of “issues” are really non-issues, but may cause longer migration times, such as files with lots of versions and larger in size
  • Basically produces a bunch of stats and details to future investigate, or to base migration estimate times off
SharePoint Migration Assessment Tool - Output
SMAT: Output text files

Identity Mapping

  • Required Office 365 Global Admin permission to run to access resources
  • Smat.exe –configureidentitymapping – run by Tenant Admin to grant required permissions first if required
  • Smat.exe -generateidentitymapping
  • Essentially tries to map all user and group profiles in the SharePoint Server User Profile service application to what in the target tenant Azure Active Directory

References

Chrome Extensions for SharePoint Development

Chrome Extensions for SharePoint Development

With Chrome still being the dominant bowers now days, and no doubt a longer time to come with Edge about to switch to Chromium with support for existing Chrome extension, I wanted to list some of my go to extensions which enable a range or enhancements when working with either SharePoint Server or SharePoint Online.

If you know of any other possibly unlisted in the Chrome Extension gallery or have great use cases please comment below.

SP Editor

Access via the developer console, a comprehensive tool for development, with functionality that covers such things as PnPjs console, Search Query tool, file and page editor editor, webhook, graph, site design, site scripts and AppCatalog explorer.

SP Insider

Create page overlay tool for inspecting current site object properties, and also simply running REST Api And Search Api queries with table displayed results.

CamlJS

No one enjoys Camel queries, and thankfully it is becoming less needed, though if you do this will save you some hair.


Chrome SP Dev Tools

Nice little side bar that allow the exploration and modifying of the property bag, site features. Also allows you to perform quick site search queries

Other Notable Extensions

SP Rest Client – Simple full tab over lay REST Api query testing client
Cisar – Client Site Rendering customisation inline and live
Page Diagnostics for SharePoint – By Microsoft for SharePoint Online testing
FlyView – Site navigation tool
SPPush – auto save scrips/css on the fly via developer console
SP REST JSON – Modify request header for api call to get JSON no XML

Nintex Workflow Fails to Publish with Soap Error

Started getting the error below pop-up when attempting to publish Nintex Workflows in a SharePoint Server 2016 environment.

soap:ServerServer was unable to process request. ---> 
Failed to publish workflow: <Error><CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingHeaderActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ContextDataActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" Column="-1" Text="Type Nintex.Workflow.Activities.ReportingActivity is not marked as authorized in the application configuration file." />
<CompilerError Line="-1" ...

Environment changes before this occurred was modifying the service topology for the SharePoint Web Service and SharePoint Workflow Timer Services.

This error looks very similar to the publishing error introduced by a Windows Server security patch in 2018, though is unrelated.

Resolution was to re-activate Nintex Workflow in Central Administration on all web applications required.

Nintex Workflow DocuSign Integration Overview and Notes

Nintex Workflow DocuSign Integration Overview and Notes

There are three primary ways that you can integrate Nintex Workflows with DocuSign digital signatures. Below are some quick notes to hopefully save you time discoverying them and chosing the right option to meet your requirements.

DocuSign template passing through fields from a workflow

  • No support for rich/enhanced text, DocuSign will not render HTML in it’s a template, it will just display the HTML text. Also no support for repeating sections
  • No support for auto-height text fields in DocuSign. You need to set a text allowance in capture form or allow max space in DocuSign template, which means there could be blank pages
  • Support for multiple signatures in a single envelope, though they are statically defined in the DocuSign template and not able to be passed through by workflow
  • Able to create a draft, and manually add attachments and check recipients before sending
  • Not able to query stages during DocuSign process, it’s either Draft, In Process and then Completed (there are successful or in-valid statuses), which mean a multi-stage process can’t be tracked back in SharePoint interface

Nintex Document Generation file passed through to DocuSign

  • Signees have to drag signature to the required spot in the document
  • Support for single signature only, as they are set in the connector not DocuSign UI

DocuSign REST API Integration

  • This is also an option to go down, and though it comes with greater flexibility the complexity if through the roof, and defeats the point of aquriing Nintex Workflow for it’s integration capabilites out-of-the-box

References

Outgoing Email Configuration for SharePoint Server

Outgoing Email Configuration for SharePoint Server

Four options to choose from to meet you requirements and email server configuration

Anonymous Email Relay Server

  • works with all versions of SharePoint Server
  • simply enter SMTP address or IP, most commonly uses port 25, and generic from and reply to addresses such as [email protected]
  • Set exchange to allow unauthenticated send as any users, deny relay outside domain, or to groups which require authentication

SMTP Relay Service

  • Required for SharePoint Server 2016 and below when all you have is a secured email relay server
  • Install SMTP service on a server, setup relay to a secure email server (can be Gmail, Exchange, Exchange Online e.t.c) and allow to access anonymous relay from SharePoint. Point SharePoint Outgoing E-mail settings at the SMTP service
  • Configure outgoing email for a SharePoint Server farm

Externally Secured Exchange Receive Connector

SMTP Authentication for Outgoing Email

Other Great Reference Posts

SharePoint 2016 Outgoing Email Configuration settings
Plan outgoing email for a SharePoint Server farm

SharePoint Server 2019 Preview

SharePoint Server 2019 Preview

Microsoft has just released the public preview of SharePoint server 2019, with the final RTM version expected before the end of 2018.

I thought I would spin up a quick single server farm in Azure to take a quick look-see, few thoughts below with some reference blog posts also linked.

Features to Note

  • Modern SharePoint – Communications Sites, Team News and Sites
  • OneDrive Modern Sync, On-demand file and push notifications for SharePoint
  • Large File Support, Character Restrictions, and File/Folder Names
  • Hybrid Configuration enhancements
  • PowerApps and Flow have deeper hooks through a gateway
  • Smaller backend footprint and resource efficiencies
  • Upgrade from 2016 using Content Database Attach (not direct SP2013 upgrade)

My Quick Thoughts

  • Great to see on-going investments in SharePoint Server, on-premises deployments will still seeing the growth I predict
  • The modern interface will need some adjusting to for an on-premises business to are used to the same interface and customisation options of the previous few versions
  • It certainly feels weird with SharePoint Designer 2013 still being the official tool for management of the 2019 version
  • Deprecation of feature generally falling in line with what has occurred in Office 365

Blogs to Check out