This is the second of a two-part blog series on SharePoint Online migration planning and “traps and tricks.” Part 1 focused on some of the major planning items that need to be addressed (http://patoffice365.blogspot.com/2017/07/office-365sharepoint-online-migration.html).
Part 2 will focus on some of the “traps and tricks” that we need to take into consideration as part of a SharePoint Online/Office 365 migration. At PSC Group, we have run across many of these issues in various migrations.
Here are the topics we’ll focus on in this post:
Custom Script Setting
One of the items that can cause unexpected results is the “Custom Script Setting” that is controlled in the SharePoint Admin Center:
The default setting is: “Prevent users from running custom scripts,” both on personal and self-service created sites. This can have significant impact and restrict several items that we might need to migrate from our legacy SharePoint sites. Here is just a sampling of items that will be rendered inoperable with the default setting:
Here is a link that provides more details on the Custom Script setting: https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off
Adjusting the Custom Script Setting requires the following settings:
Requires either Global Administrator or SharePoint Administrator to adjust
Go to Admin Center then SharePoint Admin
Once in SharePoint Admin, go to Settings and scroll down to ‘Custom Script‘, then change the setting to ’Allow users to run custom script” both on personal sites and self-service created sites’:
After the setting is saved, allow 24 hours for this change to occur in the portal.
SharePoint List and Library New Experience
The default setting is to use the “New Experience.”
It is a fundamentally different user experience than what users will be used to when coming from legacy sites with classic lists and libraries. It is possible to reset them back to classic experience, but that is only temporary as Microsoft will soon be removing that option.
As a result, we need to plan for end user orientation to the new experience during our migration. Here is a link that provides additional details on the new user experience for lists and libraries: http://sharepointpals.com/post/New-SharePoint-Online-New-Look-and-Feel-experience-Part-1
Office 365 Portal Office Software Install
Depending on the Office 365 licenses enabled, one of the options that is provided by default is the option to install Office 2016:
Do we want this option available to our end users? If IT has deployed, managed and/or imaged desktops, it may be advisable to control Office 2016 install through IT and turn this option OFF.
Here’s how to address this option:
Requires Global Administrator
Go to Admin Center
Go to Software Download Settings
Turn off 2016 desktop and mobile apps
Wait approx. five minutes and this option will be turned off in the system.
Here’s a link that provides additional details:https://practical365.com/clients/office-365-proplus/configure-software-download-settings-end-user-byod/
Depending on the browser(s) we might be supporting in our environment (I.E., Chrome, Edge, etc.) our user experience is liable to be quite different for each of our users, even when viewing- the same site, lists, or libraries.
Here’s a couple of links with some references information:
What versions of MS Office are we supporting?
We may need to review the versions of MS Office that are presently deployed to our users and update if needed. Here are some items to consider:
Here are some other tips: http://ericatoelle.com/2016/manage-save-as-locations-in-office-2016/
Many thanks to various contributors for content and to my teammates at PSC Group.
Categories: SharePoint,SharePoint Online,SharePoint Workflow,Office 365