Best Practices for Moving from Extra

Use these guidelines to avoid problems when you are upgrading to Extra!.

	Set up Trusted Locations The Trusted Locations feature provides a way to differentiate safe files from potentially harmful files. When a file is in a trusted location, it's files are assumed to be safe. Reflection enforces trusted locations by default, so if you want to save sessions in directories that are not default trusted locations, you'll have to define these directories or disable trusted locations. See Add Trusted Locations in the Reflection Deployment Guide.
	Set up API and Macro Security for Extra! If you plan to run Extra! macros, set up API and Macro Security to use Extra! for the Legacy API preference.
	Install Extra! compatibility Make sure that the Extra! compatibility feature is selected in the installer.
	Test setting with a user account If you deploy to custom user data or machine data folders, make sure that you test your settings with a user account instead of just your administrator account.
	Determine which Reflection interface works the best for your users Determine whether to set up Reflection with a Classic user interface that is very similar to Extra! or with a more modern Ribbon interface (the default). (Reflection provides optional interfaces designed to meet different needs and preferences.)
	Consider using compound session documents, especially for centralized environments If you are deploying to Citrix or another centralized environment, consider saving sessions and related files in compound session document files.
	Follow Best Practices for Planning a Reflection Deployment