Hi Amanda. It sounds like your users are currently connecting to the data on your server via a CRE300 client on the user desktop. My understanding is that this connection involves joining the user desktop to the domain on the server. With this network configuration, your desktop computer hardware/software is vulnerable to upgrade pressure whenever Sage decides that "old" desktop technology should no longer support new CRE300 client software (usually when Microsoft decides to discontinue support for old desktop operating systems). One method of escaping this financially burdensome loop is to have your desktops connect to the server via RDP. Under this method, the CRE300 client is not run on your user desktops. Therefore, the only compatibility that is required is between the server operating system and the RDP client (both of which are maintained by Microsoft). With the RDP scenario, you would need to purchase RDP licenses to run on your server, and I believe that you would need to have windows professional running on your desktops. You might also have to bump up the memory on your server to allow for extra processing requirements. Having said that, I do not know whether the CRE300 "desktop" screen will run well within an RDP connection. Prior to version 17.1 the TS.exe file could be run in RDP without starting this desktop screen. However, in 17.1, Sage has determined that the desktop screen must be used in order to access any modules. Hope this helps.    

Hi Amanda. It sounds like your users are currently connecting to the data on your server via a CRE300 client on the user desktop. My understanding is that this connection involves joining the user desktop to the domain on the server. With this network configuration, your desktop computer hardware/software is vulnerable to upgrade pressure whenever Sage decides that "old" desktop technology should no longer support new CRE300 client software (usually when Microsoft decides to discontinue support for old desktop operating systems). One method of escaping this financially burdensome loop is to have your desktops connect to the server via RDP. Under this method, the CRE300 client is not run on your user desktops. Therefore, the only compatibility that is required is between the server operating system and the RDP client (both of which are maintained by Microsoft). With the RDP scenario, you would need to purchase RDP licenses to run on your server, and I believe that you would need to have windows professional running on your desktops. You might also have to bump up the memory on your server to allow for extra processing requirements. Having said that, I do not know whether the CRE300 "desktop" screen will run well within an RDP connection. Prior to version 17.1 the TS.exe file could be run in RDP without starting this desktop screen. However, in 17.1, Sage has determined that the desktop screen must be used in order to access any modules. Hope this helps.    

Thanks skmark for the information.  Do you know if we have to install the SQL Replicator?  We do not use any mobile applications and don't want to have to upgrade computers or buy licenses.  We are just users. 

Rhonda V: I do not know if an upgrade to 17.1 automatically includes installation of the SQL replicator or if the replicator install is optional as part of that upgrade.

Even of this is included in the install I do not expect it will be hogging resources unless you configure the replication

Thank you for all the information.  I will have to look more closely into what we can do to avoid upgrading so many computers.