Preparing for Your Flex Server Replacement

Adam McCartney and Mike Vicchrilli

Agenda

Server Migration (Motorola Solutions) ● Interfaces

● Scheduled tasks ● Schedule timeline

Server Hardware (Agency/Vendor) ● Sizing / configuration options ● Networking ● SMB/Windows shares ● OS customizations ● Drive/VMDK/Volume configuration

Flex Server Migration Process

Migration preparation

● Log table cleanup ● Documenting interfaces ● Cron reports/scheduled tasks ● Server certificate ● Basic migration schedule ● Other important information ● Account discovery

Log Table Cleanup Tables and corresponding reports for 2023.1 & Prior

Table name

Purge time frames Dump report

Delete report

sylog

> 6 months

rpsldump

rpsldel

radiolog

> 6 months

rprldump

rprldel

ecsnllog

> 6 months

rpecsmdmp

rpecsdel

ecrtrlog

> 6 months

rpecrdmp

rpecrdel

mslog

> 1 year

rpmsdump

rpmsdel

cdreclst

> 1 year

rprudmp

rprudel

Log Table Cleanup LogArchive tool for 2023.2 and newer

Spillman Standalone https://[FQDN of your server]:4443/Spillman/LogArchive/

Log Table Cleanup LogArchive tool for 2023.3 and up

Document Interfaces B eyond the core modules on your server (Jail, CAD, Law Records, Mobile, etc.), we require a list of all third party vendors connecting to the server to query or send data, especially those that utilize Data Exchange or ODBC.

Examples

● Vine ● Keefe ● ImageTrend ● StateLink ● E911 ● Livescan ● ESO

Cron Reports/Scheduled Tasks

All crons/tasks currently being utilized should be documented, especially crons ran under another user besides sds or root.

This is a great time to cleanup the list of ones no longer being used or standardizing their naming schemes.

We will assist in moving Flex related crons/tasks from the source server to the destination server.

Flex Server Certificate Please ensure that the certificate being used for your new Flex server is valid and up to date. The certificate must contain the entire certificate chain. agency > intermediate(s) > root We cannot create a certificate for you, but can assist in loading a certificate to the new server.

Basic migration schedule **Subject to change

Timeline

Description of Events

Involved Parties

Prior to Migration Week

New server access and prep

Agency IT and MSI SA

Day 1 of Migration Week

1-4 hours* of downtime. Users log back in on the source server. Data is transferred and loaded onto the destination server 1-6 hours* of downtime. Transaction logs from the previous day are transferred and loaded onto the destination server. Users log in on the destination server. Interfaces are brought over.

Agency IT/SAA and MSI SA

Day 2 of Migration Week

Agency IT/SAA and MSI SA

Remainder of Migration Week Interface and issue troubleshooting

Agency IT/SAA and MSI SA

Following the Completion of the Migration

Transition back to regular support

Agency SAA and MSI Support

Other Important Information Software

● Windows clients need to have .NET 8.0 framework installed for 2024.3 and above. ● We strongly suggest that your Windows clients have recent Windows updates completed. ● The defaults.txt files for users can not be transferred during the migration process for

migrations from Windows to Linux or Linux to Windows. ● OS-level network printers will no longer be supported. ● Crons will be moved under a new crontab.

● User account passwords for xmluser, agencyadmin, and ODBCUSER will be updated. It is recommended to use this opportunity and create unique accounts for various third party vendors who query your data. ● Any vendors/users running ODBC queries will need to update their drivers to match the current version of Ctree.

Other Important Information Hardware

● An OVA containing Flex and either Windows 2022 or RHEL 9 will be provided for VMware/ESXI, or the agency/vendor can provide a flat install of RHEL 9/Windows 2022 ● The OVA has disk partitions defined and they may need to be adjusted based on your agency’s needs. We can provide example configurations if necessary. ● The OVA comes with minimal hardware allocations (CPU/RAM) to cut down on size. You will need to adjust this to match our hardware requirements for your agency’s size. ● Agency size is determined by concurrent logins and number of interfaces. Flex, Mobile, and Touch would be considered a login on their own. So, a user in Flex w/ Message Center would be considered two simultaneous logins. ● This will be our last version of Flex to have a prebuilt OVA supplied from MSI. In the future, we will only work in Flat Installs. ● If there are any networking changes you plan to make, please let us know. We anticipate, and recommend, that we will be moving the destination Flex server to the source Flex server IP following the completion of the data transfer. ● Be aware of any drives or Samba/Windows Shares that are mounted or configured on or two the source Flex server that will need to be added to the destination Flex server.

Questions?

Thank you! We want your feedback We use attendee feedback to provide a better experience that is tailored to our customers and what they want out of Summit. Your feedback about this class will help us know if there is anything we can improve for future conferences.

You can easily submit a class survey via the Summit Mobile App.

Information on how to download the app can be found in your registration bag.

Page 1 Page 2 Page 3 Page 4 Page 5 Page 6 Page 7 Page 8 Page 9 Page 10 Page 11 Page 12 Page 13 Page 14