Moving OutSystems Hub / Platform Server to a new location on your server

• Your server has the OutSystems Platform Server installed in the C: drive, but it is running out of disk space and you have a D: drive which holds a lot of disk space, so you wish to move it there;
• OutSystems Platform Server 4.0 or above installed;
• You are using the .NET stack.

• OutSystems Hub Server installer;
• (optional) OutSystems Service Studio installer (if you wish to move it too);
• (optional) OutSystems Integration Studio installer (if you wish to move it too);

1. Access Service Center, navigate to Factory | Solutions;
2. Create a new solution;
3. Add all the components of the factory to the solution, in the Components tab. To ease up the task, insert a dot (.) in the Associate Components to Solutions field and choose components from the drop-down that shows up. Remember to check the include dependencies checkbox, to minimize the number of times you need to do this. Select 4 or 5 components at a time and press Associate. Repeat this until no more options appear.
4. Press the Create version button. Choose a name for it, and press Save.
5. Your solution is created. This is the solution with the versions that will be redeployed.

1. Stop all the OutSystems Services;
2. Make a backup copy of files server.hsconf and of all files *.exe.config found in the Hub Server installation folder;
   New! since 9.0.1 Back-up file private.key as well!
3. Uninstall the OutSystems Platform Server;
   • (optional) If you wish to move Service Studio to the new location, uninstall and reinstall Service Studio to the new location (e.g. D:\OutSystems\Service Studio);
   • (optional) If you wish to move Integration Studio to the new location, uninstall and reinstall Integration Studio to the new location (e.g. D:\OutSystems\Integration Studio);
4. Install the OutSystems Platform Server to the new desired location (e.g. D:\OutSystems\Platform Server);
5. Place the backup copies of server.hsconf and of the *.exe.config files in the new location (e.g. D:\OutSystems\Platform Server);
   New! since 9.0.1 Also put file private.key in the same folder!
6. In the Windows Services console, disable all 5 OutSystems Services to prevent errors during the next few steps.
    
7. Run the Configuration Tool, press all the Test Connection buttons and make sure that they don’t give any error; after this, exit the Configuration Tool by pressing Apply and Exit. Do not run Service Center installation.
    
8. Confirm in the database (OSSYS_PARAMETER table) that all settings with a folder name (column VAL) point to the correct place. If you have multiple front-ends, only update the lines for the correct server (column HOST).
   You can locate the settings which contain folder locations by searching by the old path, e.g.
   select * from ossys_parameter where val like '%C:\Program Files\OutSystems\Platform Server%'
   
   If you are not comfortable editting values in the database, request help from someone who is.
   If you do something wrong, you will need to restore the database from a backup.
    
9. In the Windows Services console, set all 5 OutSystems Services to automatic start.
10. Run the Configuration Tool, press Apply and Exit and wait for Service Center install, After it is complete, you should be able to successfully access Service Center.
11. Access Service Center with the admin user;
12. Navigate to Factory | Solutions, choose the solution you created before, and publish the version you created.

As indicated by support following steps are also needed (I had to clean these records twice):

To overcome the error that you are experiencing, you should indeed proceed with the Clean up of the Environment security context as suggested in this forum post.

Clean up the Environment security contexts, as follows:

• Open SQL Server Management Studio (or another query editor), connect to the restored database and execute the following SQL statement:

• delete from ossys_parameter where name = 'ClientApplicationToken';
• delete from ossys_parameter where name = 'privateKeyValidation';
• delete from ossys_Parameter where name = 'OutSystems.HubEdition.MobileLogin_AuthenticationHMACKey';
• delete from ossys_Parameter where name = 'OutSystems.HubEdition.MobileLogin_AuthenticationEncryptKey';

Hi Team!

I would like to know if I can follow this same procedure when I will do to change the installation to other machine. Eg. I have a on-premises machine and I would to transfer the installation to other machine. The database will continue the same.