For the most part, Sage applications need to be manually installed and configured on each individual workstation. Due to the unique needs of each customer as well as the licensing entitlement. The workflow example below is for Sage 300 ERP but would be the exact same for other Sage products.

  •  Customer Sage ERP Demo, customer code ettt needs Sage 300 ERP installed and published out to their users.
  • You log in as your Partner admin account at and browse to the appropriate workspace, Sage ERP Demo and click on the company name.

Scroll down to the Server module, click on the cogwheel, and connect to the customers server.

  • Please note when using the cogwheel to connect, you are always logged in as a local administrator. Do not use your local administrator account to run services, as the password is generated at each logon. You can make a local service account user with a non-expiring password to accomplish this.
  • Download the software you want to install (in our case Sage 300 ERP) from the appropriate web location.
  • Install the software as you normally would.
  • The default install location for Sage 300 CRE, Sage 300 ERP, Sage 100 ERP, and Sage 100 Contractor are all fine to use. As we do full system backups, we will be getting the data files no matter where they are stored.
    • On all of our images, we create a folder called data at the root of C:\. This will have a subfolder with the company code as the folder name. Everything that exists under this sub folder will be visibly available in the H:\ drive mapping that the end users get. Everything at the same level as the company code folder will be visibly hidden, but still accessible to the end user. If you want to segregate the application data from the default location this is a good place to keep Sage or similar applications data.
  • Once you have installed the application and configured it to be ready for the end-user to launch. The next step is publishing it out through the Cloud Workspace portal.

Under the Apps module, select Add

  • Search the Application list by typing the application name and select your application. Specify the version of the application as well as check the Remote App enabled box. You can add more than one application at a time. If your application is not listed here, notify us and we can add it.

  • Once all the applications you want to add have been selected, Select Add Apps.
  • The status will change to Pending and notify our support team to finalize the install. We will verify the application is installed and point it to the appropriate shortcut and then publish it out.

  • Please note that our architecture looks at C:\ProgramData\Microsoft\Windows\Start Menu\Programs for program shortcuts. Programs that appear in the start menu will appear here by default, but some third-party applications will need a shortcut of their executable moved here so we can publish out the application properly.

By default, we will make the application available to all existing and new users. If you want to limit the user access, click on the application name and modify the user list.

  • You can select the top grey checkbox next to automatically add all existing users, and new users.
  • Select the users who should have access to the application and then select Update Users

Allow about 5 minutes, and the application icon will provision out to the users RemoteApp client as well as to their username within the Cloud Workspace desktop client.

Once this takes place, users will be able to launch the applications.



Article is closed for comments.