This article describes how to migrate ServiceDesk to a new server and also how to migrate the SQL Server to a new SQL Server. There are situations where moving the applications to new hardware or other servers may be necessary.
From a very high level, this process stops services, provides steps to backup existing customized workflows, backs up the existing Ensemble database in SQL, provides for re-installation of Servicedesk, and then restarts the services. It also outlines some caveats based on server names changes, etc. How to Migrate the ServiceDesk Microsoft SQL Server
To start, on the ServiceDesk server, close Workflow Designer and Process Manager if they are open.
How to Migrate the ServiceDesk server
Use the above instructions but with the following changes:
Troubleshooting
If the name of the ServiceDesk server is changed and the original database is kept, this will result in issues. For example, e-mail messages with URLs will all be broken. Other references to the old server name will also no longer be valid. This will then require manual changes in various areas, such as Application Properties.
Hi nande1965,
I want to be assured that you are not performing a change that is not supported. We do not recommend nor do we support sharing the Servicedesk server with the SQl database and application on the same server. To make the move that you want is not difficult, and while the specfics of some file names and folder structures is different between 7.5 and 7.0, and 7.1, the overall theme is the same. Do you have specific questions?
Hello,
I realize this is a two year old conversation, but might there be an updated set of instructions for moving ServiceDesk 7.5 MP1 application and database from one server to another?
Thanks
Alex
Hi BRING!
Is it possible to just move the database to a new server without reinstalling ServiceDesk?
If so, where do I set the new database server? I have tried to use dbtool.exe but it does not move everything...
Thanks!