Configuring after the upgrade
Depending on your upgrade scenario, you may need to perform some configuration tasks after the upgrade. This section lists those tasks. Note that after you have completed these tasks, you must instruct users of the Content Manager Explorer interface to clear their Internet cache
- New identity of TDSE objects created by Event Handler
If your implementation contains 5.3 or 5.3 SP1 Event Handler code, reconfigure the identity of the user associated with executing this code. - Reconfiguring the Content Manager Explorer Web site
Several steps may be required to restore Content Manager Explorer. - Configuring Experience Manager on the Content Manager
If you are upgrading from an SDL Web implementation that had SiteEdit installed, perform a number of tasks to upgrade this setup to work with Experience Manager. - Optional Reconfiguring the Content Manager Explorer Web site for HTTPS
If your Content Manager Explorer Web site was originally accessible through HTTPS, you need to perform some additional configuration to make it accessible through HTTPS again. For more information, refer to the installation topics. - Optional Reconfiguring the Content Manager Explorer Web site for LDAP
If your Content Manager Explorer Web site was configured for LDAP, you need to redo a number of Web site configurations after the upgrade. - Updating default Template Building Blocks
Because some default Template Building Blocks have changed, you need to update the default Template Building Blocks in the Templates you have created for your Experience Manager implementation. - Restoring FormatAreaStyles.css
Because the file FormatAreaStyles.css has moved to a new location, restore your original from your backup location to %TRIDION_HOME%\web\WebUI\Editors\Base\Configuration\. - Upgrading 32-bit custom software components
As of SDL Web 8, all of the product's services run as 64-bit components. If you have 32-bit custom components, you have several options to make them work with SDL Web 8.5. - Hiding workflow-related GUI controls after upgrade
As of SDL Tridion 2013, by default, the Content Manager Explorer and Experience Manager GUIs show a Things To Do panel, used for workflow-related functionality. If you do not use, nor intend to use, workflow in your implementation of SDL Web, you can hide this panel. - Showing the Publishing Management node
As of SDL Web 8, the old publishing framework has been deprecated in favor of a new one, and as a result, the Publishing Management node in the Administration tab of Content Manager Explorer is hidden by default. You can make it appear again by changing a configuration setting. - Indexing or reindexing search after the upgrade
After your upgrade, (re)indexing of the search index is required. - Updating users with Permission Management rights
As of SDL Web 8.5, the ability to create, modify and delete Users and Groups is no longer a part of the Permission Management right, but is instead contained in a system privilege called Group Management Privilege. As part of the upgrade, you need to decide which users that had the Permission Management right should also have the Group Management Privilege. - Applying the SDL Web 8.5 hotfix for Safeguard
If you are using the Safeguard feature, contact SDL Customer Support to obtain and apply the SDL Web Hotfix calledXPM_8.5.0.3571. Note that this hotfix includes changes to your configuration. Follow the instructions in the Readme.txt file included in the hotfix. - Correcting the behavior configuration for ECL
If you are upgrading from SDL Tridion 2013 SP1 HR1 and you have External Content Library set up in an environment secured with LDAP and SAML, restore your old behavior configuration. - Updating or removing the DataSources.xml file for User Generated Content
If you are upgrading from SDL Tridion 2013 SP1, depending on how you upgrade UGC on the Content Delivery side, either modify or delete the file DataSources.xml, which contains Content Manager-side configuration for UGC. Depending on your setup, you will need to set up the Discovery Service and Token Service even if you are not switching to the new Content Delivery architecture. - Enabling high-availability storage for Import Export service items in a scaled-out Content Manager setup
If you are upgrading a system in which your Content Manager instance is scaled out, enable high-availability storage for import package, export packages and undo packages produced by the Import Export service.