How to migrate your RocketSCAN system (scan only, Titan Integration)

How to migrate your RocketSCAN system (scan only, Titan Integration)

Districts are encouraged to contract with Image One for migration of the RocketSCAN system to a new platform.
Support for incorrectly migrated systems is limited to restoration of the database and application images on the original machine.
This guide assumes that the RocketSCAN database and service modules are installed on a single server and the Integration Configuration is set to Titan.
For other configurations, please consult Image One Support.

Pre-migration Checklist

To complete a RocketSCAN migration, you will need the following:

  1. The new server meets or exceeds the RocketSCAN server machine requirements.
  1. You are currently logged in as an administrator on the old server as well as the new server.
  1. The new server has access to the shared folders on the old server. You need to be able to transfer files from the old server to the new server.
  1. The new server has SQL Server and SQL Server Management Studio (SSMS) installed.
  1. You can login to the old SQL Server and new SQL Server as a sysadmin user.
  1. Ensure all users are logged out of the RocketSCAN system.
  1. You have the most up-to-date installers for the RocketSCAN client and RocketSCAN FMA Service.

Procedure

Configure the new server environment

On the new server, create a new user that will be used to run the RocketSCAN FMA Windows Service. Check the box for Password never expires.

 Windows Computer Management interface for creating a new user.

Add the RocketSCAN Service User to the Administrators group.


Consider providing these user credentials to Image One Support and adding this user to the Remote Desktop Users group. This should allow our support technicians to troubleshoot most server-related issues from a user’s workstation.

Navigate to the Local Security Policy > User Rights Assignments and grant the following to the RocketSCAN Service User:

  1. Act as part of the operating system
  1. Allow log on locally
  1. Log on as a service
  1. Replace a process level token
  1. Take ownership of files or other objects


In the desired location on the new server, create the "RocketSCAN" and "RSImages" folders.

If your RocketSCAN system utilizes the Save Images In Database feature, you do not need to create the “RSImages” folder on the new server.


Share the "RocketSCAN" folder.





Share the "RSImages" folder and set the share name to "RSImages$" to make it hidden.





Share the folders with the RocketSCAN service user, the user that is running the SQL Server service, and (if known) the users that use the RocketSCAN system. Set the permission level to Read/Write.





Use SQL Server Management Studio to ensure the SQL server security property is set to use "SQL Server and Windows Authentication mode" and Facet for Surface Area Configuration has XPCmdShellEnabled set to “True”. If these settings need to be adjusted, you will need to restart the SQL Server service for it to take effect.

In the SSMS Object Explorer pane, right-click the server and select Properties. Go to the Security page to view the Server authentication.



In the SSMS Object Explorer pane, right-click the server and select Facets. Select Surface Area Configuration from the Facet drop-down menu. Ensure that the setting for XPCmdShellEnabled is set to True.



If the RocketSCAN database will be the only database on the new server, you may want to follow the steps below to allow the RocketSCAN Service User to log in to the SQL Server as a sysadmin.

In the SSMS Object Explorer pane, expand Security and right-click Logins, then select New Login… Select the option for Windows authentication then click Search… and select the RocketSCAN Service User.



On the Server Roles page, check the box for sysadmin.



When finished, click OK.

 

Transfer files

Copy and paste the contents of the "RSImages$" folder from the old server to the new server.

If your RocketSCAN system utilizes the Save Images In Database feature, you might not have any “RSImages” files to copy but will need to follow these steps to copy the files from the “RocketSCAN” folder on the old server to the new server.





Do the same steps to copy and paste the contents of the "RocketSCAN" folder from the old server to the new server.

You do not need to wait for the files to finish transferring to start the next steps.

Migrate database

On the old server, launch Services.msc and navigate to the Properties for the RocketSCAN FMA Service.



Stop the service and set the Startup type to Disabled.



On the old server in SSMS, ensure the RocketSCAN database is selected and start a New Query. Type TRUNCATE TABLE Services then click Execute. This should clear out the data in the RocketSCAN “Services” table.



Right-click the RocketSCAN database in the Object Explorer pane and select Tasks then Back Up…



Perform a Full database backup. Set the Destination to Disk and set the path and filename so that you will be able to easily navigate to it.



Right-click the RocketSCAN database in the Object Explorer pane and select Tasks then Take Offline.



Check the box for Drop All Active Connections and click OK to take the database offline.



In the Object Explorer pane, expand Security and Logins. Right-click the “rocketscan” user and select Properties.



On the Status page, Deny the permission to connect to the database engine and Disable the login. Click OK.



On the old server, navigate to the SQL database backup file you created and copy it.



Paste the backup to the new server.



If you have access to the “pre-“ and “post-rollover” backup files of your RocketSCAN database, it is recommended that you also transfer those to the new server.



DO NOT proceed to the next step until the backup file transfer is completed.

On the new server, right-click Databases in the Object Explorer pane and select Restore Database…



Select Device for the Source and navigate to the backup file you copied from the old server. Restore the database.



On the new server, create a new "rocketscan" SQL Server authentication login. Do not enforce password policy.



On the User Mapping page, map the user to the RocketSCAN database with "dbo" as the Default Schema. Select “db_owner” as the role membership.



If you are getting an error that the user already exists in the database, you need to delete or rename the “rocketscan” user in the database before you can map it.
In the Object Explorer pane, expand the database, Security, then Users. Select the user that has the identical name to your “rocketscan” SQL user and delete or rename it.

At this point, you may want to configure SQL maintenance plans for daily database backup and weekly maintenance. We recommend the following tasks for weekly maintenance:
  1. Check Database Integrity
  2. Shrink Database
  3. Rebuild Indexes
  4. Update Statistics
  5. Cleanup history and backup files older than 14 days

Configure RocketSCAN

On the new server, install the RocketSCAN FMA client.



If it is not already installed, install Microsoft Visual C++ 2010 x86 Redistributable.

Launch the RocketSCAN FMA client from the icon on the desktop of the new server.


The Connection Information window should open. Enter the SQL Server connection information as follows:

  1. Server: The name of the server hosting the SQL database.
  1. Database: The name of the RocketSCAN database. For most customers, the name is “RocketScanFMA”.
  1. Username: The SQL user login name.
  1. Password: The SQL user password.

Click OK.



If the connection is successful, the window will close and then the RocketSCAN client login screen will display.




A successful connection also creates "C:\ProgramData\RocketScan\Settings.XML". You may copy this file to workstations to update their connection settings instead of having to fill out the Connection Information prompt.


If the connection is unsuccessful, the Connection Information prompt will briefly appear to be frozen before displaying a database connection error message.

After the database connection is established, install the RocketSCAN FMA Service on the new server.



During the installation, you will be prompted to Set Service Login. Enter the login credentials for the local Windows user you created to run the RocketSCAN FMA Windows Service.



When the installation is finished, launch Services.msc on the new server. Start the RocketSCAN FMA Service.



Log in to the RocketSCAN client and launch the Admin module.



Navigate to Administration > Database/Services...





Under the section labeled Services, uncheck the box for Online Updater and set the value for Sync to 1. Click Save then Close.

On the new server, navigate to the folder properties for the RSImages folder and copy the Network Path.



Return to the RocketSCAN Admin module and navigate to Settings > Global Settings.



Paste the RSImages Network Path to the value labeled ImagePath then click Save.



After all files that you copied from the old server have finished transferring, you may check that this was configured correctly by navigating to Application Management or Previous Year Applications and attempt to view any application.
If users are unable to open any applications in RocketSCAN after the migration, then verify that the RSImages folder on the new server is shared with them with Read/Write permissions.

Navigate to Administration > Integrations…



Click Edit.



Click Custom Values…



If connection to the Titan API from the new server is successful, then the Custom Values window will open without error. If an error occurs, then you will need to troubleshoot the ability to connect to the Titan API from the new server.



When finished, close the Custom Values and Integration Configuration windows without making any changes.

Post-Migration

Congratulations! You have completed the migration for your RocketSCAN system. Please connect with your users and update their database connection info.

On each workstation, delete or rename an existing “C:\ProgramData\RocketScan\Settings.XML” file. Attempt to launch the RocketSCAN FMA client on their workstation so that the Connection Information prompt will appear. Enter the SQL server connection information for the new server.

Notify Image One support (support@image-1.com) that you have completed your server migration so that we may update our customer notes for your district.


    • Related Articles

    • Get Started with RocketSCAN

      Introduction Thank you for choosing RocketSCAN FMA — Image One Corporation's innovative, automated solution for processing meal applications and income forms for your district. Say goodbye to manual, time-consuming tasks and hello to a more ...

    • RocketScan Income Form Guide

      Welcome Welcome to RocketScan’s Income Form add-on! Image One’s RocketScan software has been a reliable scanning solution for processing family meal applications for almost 20 years. With our add-on, you may utilize RocketScan’s capabilities to ...

    • Quick Start Guide: Scan

      This is a quick reference guide on how to prepare, scan, and save a batch of documents to be processed by RocketSCAN. Before you scan Check that the scanner is connected to power, is powered on, and that the USB cable is connected to the scanner and ...

    • New in RocketSCAN 4.13

      New features and changes released in update packages for RocketSCAN version 4.13 are listed below. New Features Student Lookup Search now includes Income Form data If your district uses RocketSCAN to process income forms, the Student Lookup Search ...

    • RocketScan Knowledge Base Contents

      Get Started with RocketSCAN District Machine Requirements for RocketSCAN New in RocketSCAN 4.14 Articles in this knowledge base are divided by module and purpose. The "purpose" categories are: Best Practices Advice on getting the most from RocketSCAN ...