- 02 Jun 2022
- Print
- PDF
Migrate SysAid from a 32 bit to 64 bit Installation (Windows)
- Updated on 02 Jun 2022
- Print
- PDF
If you are running a 32 bit version of the SysAid server (version 14.1- 17.2.04) on a 64 bit machine, it is highly recommended to migrate to the 64 bit version of SysAid to improve its performance.
Read all of the instructions before you begin this process. If you do not understand any step, contact SysAid support. Be sure to leave a 1-2 hour maintenance window for performing this procedure.
Migrate the installation
- If SysAid is installed on a VM, take a snapshot of the VM.
- Backup the SyAid database.
- Stop the "SysAid Server" service.
- Copy the ...\SysAidServer folder to a backup location.
- Navigate to Windows Control Panel > Programs > Uninstall a Program, and uninstall SysAid Server.
- Create an empty temporary database on the DB server.
- Download the full SysAid Server installation at the following URL: http://cdn3.sysaid.com/SysAidServer64.exe
- Run the installation.
- When prompted for the license, copy the activation.xml file from the backup copy of ...\SysAidServer\root\WEB-INF\conf folder.
- When prompted for the database type, please choose the correct type, and point the installation to the temporary empty database created in step 6.
- For the Email integration step, select Skip. This is already configured in your backed up database.
- When prompted for the port make sure you enter the original port that the SysAid server was listening on. If SSL is enabled, you must use the default port for SysAid and follow the Instructions in the Restore SSL section below.
- For the Active Directory step, select Skip. This is already configured in your backed up database.
- When prompted for Main User and password, enter "sysaid" as the main user and "changeit" as the password.
Note: This is only for temporary usage to test that the server works before reconnecting your database.
- When the installation process is complete, confirm that SysAid Server is available by logging in to http://localhost:port_number with the default user and password you entered.
- Stop the "SysAid Server" service.
- Open your ...\SysAidServer\root\WEB-INF\conf folder.
- Rename the serverConf.xml file to "serverConf_original.xml".
- Copy the backup version of...\SysAidServer\root\WEB-INF\conf\serverConf.xml file to the new installation directory.
- If you made any translation changes, copy the …\SysAidServer\root\WEB-INF\classes directory from the backup version of the folder to the same location in the new folder.
- In …\SysAidServer\root\WEB-INF, copy the reportsConf and reportsResults from the backup folder to the same location in the new folder.
- Start the SysAidServer service.
Restore SSL
If SSL is enabled, you must restore SSL for it to work properly in the new installation.
- Stop the "SysAid Server" service.
- Open the server.xml file located at ...\SysAidServer\tomcat\conf.
- Find the connector with the keystore file location by searching for the text "keystoreFile" and navigate to the path in the parameter on the backup server.
- Copy that file to the identical location on the new server.
- in the new server.xmlfile find the following lines:
<!-- <Connector executor="tomcatThreadPool" port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" /> -->
Note:If you are running Tomcat version 7 till 9 , the displayed protocol is "org.apache.coyote.http11.Http11Protocol". If you are running version 9 or higher, the protocol is "org.apache.coyote.http11.Http11NioProtocol"
- Remove the comment code ("<!--" and "-->").
- If your keystore file is a .pfx file add the following string before the closing bracket:
keystoreFile="C:\Program Files\SysAidServer\name.pfx" keystoreType="PKCS12" keystorePass="password"
Make sure that the path accurately reflects the file location on the new server and the keystorePass is identical to that in the backup server.xml file.
- If your keystore file is a .keystore file add the following string before the closing bracket:
keystoreFile="C:\Program Files\SysAidServer\name.keystore" keystorePass="password"
Make sure that the path accurately reflects the file location on the new server and the keystorePass is identical to that in the backup server.xml file.
- Start the "SysAid Server" service.
- If you would rather redo the entire certificate configuration, follow the instructions in the SSL Configuration Guide.
Now you should be able to login to your new installation with your domain credentials. Check that all your tickets are in place, and that everything is working properly.