When you have installed the SAGE Line 200 server component onto a different machine it is not immediately clear that you have to do anything with the client installs. It does become clear however when you switch off the old server and all SAGE Line 200 clients stop working.
After the SAGE Line 200 server component is moved/re-installed to a new location and the SAGE data is moved you then need to go round and remove the SAGE clients from each machine. You can do this via Active Directory if you initially deployed it this way by uploading a new MSI for pushout. If you are like me and only have a few clients it is relatively easy to do this manually.
- Remove Sage from each machine, then optionally run something like CCleaner to remove any files left over.
- Install the Sage client on each machine, taking care to ensure that \Spool\ and \Logon\ have trailing \ and that you are using a UNC path rather then a mapped drive. (I copied the data from the old server to a SAN to ensure backups and better access to the data).
- Patch the Sage client to the same version as your server / database otherwise Sage Line 200 will not load and will give an error. You can update this from the Help menu when you login or acquire the update from the Sage website or your provider if your organisation uses a proxy.