Hi there,
Just looking for some general advice on the following:
We are a managed service provider and one of our clients is currently in the process of upgrading from Sage ERP 300 6.0A to Sage ERP 300 6.2 operating in a windows terminal server environment. They have engaged a 3rd party Sage partner to perform this upgrade but we're starting to have serious concerns about their competency as they have decided against installing the full sage client on the terminal server and instead installed the workstation version which the customer is now having major performance and usability issues with that they did not have previously.
We were asked to build a new application server and a new SQL server to facilitate this upgrade so we were working under the assumption that Sage databases would be moved to the new SQL server, any sage "server" components would be installed on the application server with the client side application being installed on the existing terminal server. However it has transpired that they have only installed the workstation install and it's being accessed via UNC path which they are adamant is "best practice" for terminal server environments.
The following is the customers infrastructure prior to the upgrade, in this model they had no performance or usability issues:
Terminal Server (Windows Server 2008 R2) with Sage ERP 300 6.0A full install.
SQL Server (SQL 2008 on Server 2008 R2) with multiple Sage databases.
The upgraded infrastructure, as recommended by the 3rd party company, is as follows:
Terminal Server (Windows Server 2012 R2) with Sage ERP 300 6.2 Workstation install that accesses accpac.exe file via UNC path.
Application Server (Windows Server 2012 R2) with Sage ERP 300 6.2 full install.
SQL Server (SQL 2014 on Server 2012 R2) with single consolidated Sage database.
Initially the existing terminal server (2008 R2) was to be used but during a clean up of the ERP 300 6.0A installation by the 3rd party .NET was broken which lead to the deployment of a brand new 2012 R2 terminal server.
Since going live and Sage workstation being installed again users have consistently had performance issues. They receive continual installation prompts when trying to run components within Sage (we were advised to disable the windows installer service by the Sage partner to "resolve" this), the application randomly closes without warning when attempting to load specific components and various other issues.
However, when users connect directly to the application server and run Sage as a local application all runs as expected and performs to the level they had expected. This to me indicates that the full sage client application should be installed on the terminal server but the 3rd party engaged by our client disagrees.
Is there a best practice for installing on a terminal server? Is anyone able to give any advice so we can attempt to resolve this issue for our customer?
Cheers,
Darren