Upgrade Technical General Considerations

Owned by Knowledge Assistant
Last updated: Apr 07, 2022
3 min read





Description of Issue

Client is creating project plan for upgrade and needs general technical considerations.



Context

  • Project Plan

  • Technical Considerations



Cause

Client is creating project plan for upgrade and needs general technical considerations.



Resolution

  • Prior to install to your Test environment, it is important to run the Tyler Prerequisite Installer on all of your servers that host Tyler applications. This should be run off-hours as it may require an immediate reboot to avoid downtime.

  • Prior to the start of the engagement, exclude the following directories from your anti-virus protection plan (real-time scans including Windows Defender) during production and maintenance periods. Once added, these exclusions should not be removed; otherwise, subsequent deployments may fail. These exclusions must be made on all servers in your Munis footprint.

    • D:\Octopus\*

    • C:\Octopus\*

    • C:\Program Files\Octopus Deploy\*

    Note: your antivirus may not properly exclude a folder if you are attempting to utilize a wildcard [*] as in the examples above.
     

  • During the testing phase, there is typically no impact to the core functionality of your Munis Live/Prod environment, provided all pre-requisites are complete.

  • If there are custom objects in your database in the DBO Schema, they will be lost during the upgrade process. A report is generated for your use in recreating the objects within a custom schema if you desire to do so.

  • Starting with version 2019.1, Tyler products are deployed and updated through Tyler Deploy. The majority of MIU functions such as Munis updates and service packs are being replaced by Tyler Deploy. More information about Tyler Deploy is available in Tyler Community. Please identify the members from you organization that should have access to Tyler Deploy and provide their names and email addresses to the Tyler Deployment Team.

  • During the testing phase, you configure new user/role permissions or printer configurations, please notify the Deployment Engineer prior to the installation of the upgrade to your Production environment. If you wish, the engineer can transfer (import) those new settings from Test into Live after the installation to the Production environment. Note: If you choose to import the settings from Test into Production, all existing user and printer settings will be overwritten. Also, any new users created in Production during the testing phase-and not in the Test environment-those users would be missing after the import into Production.

  • The case-insensitive SQL instance needs to be set to a static port (typically port 1435) This does require a restart of SQL services and possible downtime, so it is recommended to do this after-hours.

  • Port Exceptions:



Additional Information