<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Answers to: Migration Ivy Server to another Machine</title><link>https://answers.axonivy.com/questions/2994/migration-ivy-server-to-another-machine</link><description>&lt;p&gt;Hello, Ivy Team,&lt;/p&gt;
&lt;p&gt;We are planning to move one existing installation of Axon.Ivy Server to another machine. What are the pitfalls in such scenarios? &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;We will copy-paste the whole installation folder to the new server (the file system paths will be the same)&lt;/li&gt;
&lt;li&gt;We will attach the AxonIvySystemDatabse to the new server (p.s. we will also migrating to different db server)&lt;/li&gt;
&lt;li&gt;We need to change the license file&lt;/li&gt;
&lt;li&gt;We need to update the configuration to point to the new db server&lt;/li&gt;
&lt;li&gt;Probably we need to update the server name in the Admin UI &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All should be straightforward, right ? Are we missing something ?&lt;/p&gt;
&lt;p&gt;Best Regards,
Yordan&lt;/p&gt;</description><atom:link href="https://answers.axonivy.com/questions/2994/migration-ivy-server-to-another-machine" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 22 Nov 2017 02:42:42 -0500</lastBuildDate><item><title>Answer by Reguel Wermelinger</title><link>https://answers.axonivy.com/questions/2994/migration-ivy-server-to-another-machine/2996</link><description>&lt;p&gt;Yeah you got the main points. &lt;/p&gt;
&lt;p&gt;If you migrate into a new network environment you might have to check that third parties are still accessible. SMTP; ExternalDbs, SystemDB, WebServices, ... But thats all project specific. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reguel Wermelinger</dc:creator><pubDate>Wed, 22 Nov 2017 02:42:42 -0500</pubDate><guid>https://answers.axonivy.com/questions/2994/migration-ivy-server-to-another-machine/2996</guid></item></channel></rss>