Remember to import The mixing Packs that were Employed in Orchestrator 2012 R2, if you'll find nowhere to be observed, re-download them once again and sign up them to the new Orchestrator 1807. (You will discover several Integration Packs from my site)
The easiest way to do this is usually to mount up an SQL Server graphic and run the GUI installation till the tip of the installation, Notice we will not likely finish the installation, ahead of urgent Set up the SQL server set up wizard will help save the set up options we’ve selected right into a ConfigurationFile.ini
This step is not actually needed, While Should the Orchestrator database are going to be migrated without the need of uninstalling the outdated Orchestrator Management and Runbook servers it ensures that They are going to be left in the Orchestrator database in addition to demonstrated within the Runbook Designer console.
We'll start by developing the SQL configuration file that will be wanted for our unattended SQL server set up.
If we head to our place server we must always now be observing that the SQL set up folder has become developed.
We will require to configure on which pc it will operate on, the program route and the program parameters.
Now We're going to use the SQL Management studio to back again up the database. Utilizing the context menu within the Database, click on Backup and you simply’ll see a webpage similar navigate to this website to the 1 under.
We are going to begin by renaming our runbook to anything more hassle-free, like “Install_SQL_Server_2016†ideal click on your runbook and click Rename and afterwards key in a brand new title for that runbook.
Basic command to make use of when all EV databases have regular names and both SQL servers utilize the default instance
The products essential is encrypted Therefore if you move the database with no right vital, you'll be able to obtain the merchandise key once again. There is a KB about this in this article
We must always now have made our ConfigurationFile.ini file, you will notice the path to where by it had been produced at The underside of the subsequent window:
The new SQL Server ought to be working the same or bigger Variation with the earlier SQL Server. It’s feasible to possess a SQL Server which was operating the Cumulative Update four (source database) and now you’re transferring the database to some server that may be jogging Cumulative Update 6, on the other hand Should you be shifting to the same Model of the SQL server, you should attempt to maintain them alike to prevent any undesired results.  Phase three:
Now Allow’s examination our runbook to view if it works, We're going to make use of the Orchestrator Net Console to operate the runbook.
Now pick Present database and we should always obtain our migrated Orchestrator database while in the list, click on Next to continue.