How to migrate to a new server
Jitbit Helpdesk is just a basic web app. It consists of two components – the database and the app itself. It does not have any external services or something else you'd have to install separately. Therefore, nothing about the migration is specific to Jitbit. Any system administrator should be able to do this. Here are the steps.
1. Move the files. By default, the web app files are located in c:\inetpub\wwwroot\helpdesk. Just copy them over to your new server.
2. Create an application in IIS. Once the files are moved, you need to convert the "helpdesk" folder to application in IIS.
If you are also switching database server, you also need to perform these steps:
3. Backup your old database. After the backup is done, move the resulting ".bak" file to your new database server.
4. Restore the backup on your new server.
5. Open the appsettings.json file from the root directory of help desk in a text editor. You need to change the "DBConnectionString" setting at the top of the file to use your new database server.
You may get a "Login for JitbitHelpdeskUser failed" error. If that's the case, you will need to create the database user manually. You can find the sample code to use in "sql/CreateEmptyDB.sql" file in the help desk directory.
1. Move the files. By default, the web app files are located in c:\inetpub\wwwroot\helpdesk. Just copy them over to your new server.
2. Create an application in IIS. Once the files are moved, you need to convert the "helpdesk" folder to application in IIS.
If you are also switching database server, you also need to perform these steps:
3. Backup your old database. After the backup is done, move the resulting ".bak" file to your new database server.
4. Restore the backup on your new server.
5. Open the appsettings.json file from the root directory of help desk in a text editor. You need to change the "DBConnectionString" setting at the top of the file to use your new database server.
You may get a "Login for JitbitHelpdeskUser failed" error. If that's the case, you will need to create the database user manually. You can find the sample code to use in "sql/CreateEmptyDB.sql" file in the help desk directory.