Product Review – Kernel Migrator for SharePoint

SharePoint is a great content management system, especially for large enterprises. It can be used to store documents, sheets, sites, and other essential data. But users often need to migrate their SharePoint data either to a newer version or to SharePoint Online cloud, which is not that simple.

I faced a similar scenario when I needed to upgrade from SharePoint 2013 to SharePoint 2016. Trust me, the process is not that simple as it looks. First of all, the manual process is too complicated, and the outcome will be not be as good as one would expect. That’s why I preferred to move to third-party software – Kernel Migrator for SharePoint.

The minimum supported patch level for the SharePoint 2013/2016

sharepoint-logo

The minimum supported patch level for the SharePoint 2013/2016 was updated:

  • SP2013: Minimum supported patch level is April 2018 CU
  • SP2016: Minimum supported patch level is May 2018 CU

New release: SharePointDsc v3.0 is here!

sharepoint-logo

The SharePointDsc PowerShell module (formerly known as xSharePoint) provides DSC resources that can be used to deploy and manage a SharePoint farm.

This new major release contains many improvements/fixes, including several breaking changes! So, if you are upgrading from an earlier version of SharePointDsc, please make sure you update your existing configurations

Links

Changelog

Installation

SharePoint Migration Tool v2 is not able to run under Administrator

I was writing about this tool before here and just experience the issue where I’ve realized it doesn’t work under Admin account and looks like there is no way to fix that. So, in my case, the tool wasn’t able to create logs folders because of this issue and I was able to do that using a separate box where another user account wasn’t limited by UAC.

Note: this issue was verified for version 2.1.101.6 and could be fixed later but there is no any guarantee on that.

 

SharePoint workflows stop working after you install .NET security updates for CVE-2018-8421

Symptoms


After any of the September 2018 .NET Framework security updates to resolve CVE-2018-8421 (.NET Framework Remote Code Execution Vulnerability) are applied, SharePoint out-of-the-box workflows stop working. When the problem occurs, an error that resembles the following is logged:

<Date> <Time> w3wp.exe (0x1868) 0x22FC SharePoint Foundation Workflow Infrastructure 72fsUnexpected RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1"…

The error suggests that System.CodeDom.CodeBinaryOperatorExpression is not included in the authorized types.

For more information about the September .NET Security updates, go to this Microsoft blog page.

Cause


Workflow Foundation (WF) will only run workflows when all dependent types and assemblies are authorized in the .NET config file (or added explicitly through code) under the following tree:

<configuration>

<System.Workflow.ComponentModel.WorkflowCompiler>

<authorizedTypes>

<targetFx>

However, after the update, some types that are used by SharePoint out-of-box workflows that were not previously required are now required.

Resolution

The official KB is here and MSFT blog post is here

[Q&A] Как проверить файлы на возможные ошибки при миграции в SharePoint Online или OneDrive for Business

qanda

Q: Как можно быстро и бесплатно проверить файлы на возможные ошибки при миграции в SharePoint Online или OneDrive for Business?

Continue reading