How To: Change the OutSystems Platform Installation Path

How To: Change the OutSystems Platform Installation Path

An operational OutSystems Platform has its installation bounded to a specific location at your hard drive. There you can find most of the runtime related resources: from service executables/config files, to compiler outputs (.../shared) and the application's deployed contents (.../running). At a given point, you might face the need to change the Platform's location to a different path within your own machine. This post is a guide to accomplish that task.

The procedure
The first step in changing the platform's installation path, is to uninstall your platform. You perform this task by accessing the Windows “Add Remove Program” dialogue. After uninstalling your platform, you are now able to delete all the resources that were previously being used/generated by the Plaftorm. Stop your IIS (“iisreset –stop” at command line), and erase the old platform server folder (e.g., C:\Program Files\OutSystems\PlatformServer).

After having deleted the old installation folder, you can proceed moving the platform to the new location. Start IIS (“iisreset –start” at command line) and begin the process of reinstalling the Platform (remember to follow the Installation checklist).

After completing the above mentioned steps, you will have your Platform configured to use the new installation path. Also, your factory remains intact: all the environment's objects are stored at the Platform catalog. However, the binaries and compiled content were erase. At this point it is necessary to republish all the applications (i.e., the entire factory), in order for them to be available.

Hope this comes in handy,
Cristóvão Honorato

Hi All


Before deleting the entire content of the old Platform Server installation folder, backup the following files, so you don't need to reconfigure the Platform Server again:


  • server.hsconf
  • *.exe.config

The Server.hsconf file will hold the entire Configuration Tool settings, and the *.exe.config files will have any customization to the OutSystems services and Compiler.


If you backup the server.hsconf file and restore it onto the new installation directory location, when you run the Configuration Tool again it will automatically load the settings, so you don't need to setup the database server/catalog/users, nor the service specific settings again.


Great installations!




Miguel Simões João

If you have installed the outsystems platform allready, you can also do the following:
iisreset /stop
stop all outsystems services
move the whole C:\Program Files\OutSystems" to for example D:\Program Files\OutSystems" then on server 2008 / Vista type the following:
mklink /j C:\Program Files\OutSystems" "D:\Program Files\OutSystems"
and you're done
also take into account that the "Temporary ASP.NET Files" folder can grow VERY large.
there are 2 way's to overcome this problem.

1: modify the machine.config file to point to a different directory to host the temperary files, or do the same as is the outsystems folder.
move the whole location C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files" to D:\temp\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files"
then mklink /j "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files" "D:\temp\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files"
and you're done
for server 2003 the util "fsutil" can be used, then create a hardlink, or download linkd.exe (in the Windows 2003 Resource kit )

iisreset /start
start the outsystems services again, and you're good to go.

P.S. Tested the whole procedure on Windows 7 X64 with the outsystems community edition at home :)
bug in the forum? I edited my post, and now it's all... wierd? I removed all the wierd html markup language allready

Hi Louis


Only you to come up with a hack like this! Great show!


This is indeed a safe way to change the Platform Installation directory without having to reinstall it.


Not really sure what happen with your forum post, but it's ok now!




Miguel Simões João



Another consideration is the virtual directories in IIS.   If you have multiple applications alreadydeployed, it doesn't seem to change when you take the steps to move the OutSystems install.

I did the steps above, but also did this:

Go to the Inetsrv directory, in my case: C:\Windows\System32\inetsrv\config

Open the applicationHost.config file
Find and replce (Ctrl  H)    all instances of    C:\Program Files\OutSystems   with the new drive / diretory  D:\Program Files\OutSystems

Then restart IIS.   

The Physical Paths for the eSpace should now be showing the new directory.