Installer Options

We've listened to the feedback from partners who have encountered issues with the ClickOnce installer when installing Sage 200 to a Remote Desktop Services environment. With the Summer 2018 Enhancements release, we now offer the client application DLL’s in the form of a .zip file. This allows partners to manually install the application in a Remote Desktop Services environment or even create their own installer if they wish.

If, after installation you receive the error 'The specified module could not be found', please refer to this article.

Using the alternative installer The new .zip file is held in the Sage 200 Client ClickOnce directory. This contains all the assemblies to run the application from any directory.

1. Unzip this file to any directory of your choice.

   

2. Return to the Installers folder in the Sage share directory, typically C:\Sage\Installers. Copy the file Sage200CommonAppSettings.config.

   

3. Paste this into the extracted folder you created previously. In the above example, the file would be copied from C:\Sage\Installers to the Sage 200 Installer folder created manually on the desktop of the client PC. You have to manually copy over the Sage200CommonAppSettings.config to the location that you have unzipped the application to.
4. Run the Sage200Dektop.exe file, you can also create a shortcut icon on the desktop that points to the Sage200Desktop.exe file within that folder. From here, the program can be launched in the normal manner.
5. Remote Desktop Services (RDS)

   Please note: for RDP Servers (Remote Desktop Protocol ) that many users will log into as thin clients, you would create the Sage200cloud Installer folder (or equivalent  folder name) on the RDP Server itself.

Considerations

Before deciding to deploy the client installation following the above method you may want to consider the following:

• CRM Form Launching over RDS is not supported.
• Hotfixes and patches – there is no current delivery method for hotfixes and patches when the client install has been carried out in this way.
• Future releases and upgrading – when the client is installed using the above method there is no entry in Programs and Features in Windows Control Panel. This means the upgrade process differs slightly from the traditional installer. To upgrade you would need to remove the client install manually from the location it was originally unzipped to. After this you would unzip the most recent file from the server install to the desired location.