Move TimeSlips 2016 to a new server

We have 10 users under TimeSlips 2016, and I'm running it on Windows Server 2008 R2.  The server is failing, and I need to move the database over to a new server.  There is a need to have TimeSlips installed on the server, as we're looking into connecting it to Quickbooks via TAL.

The new server has a different name than the old server.

I exported the license info from the old server, and I'm ready to install TimeSlips on the new server. Is there a guide that discusses how to move the license?

I understand that I will need to go around to all the client PCs and remove the CFG file, so that they can be re-pointed to the new server.  Is there an alternative to this, say, just edit the file and place the new server name and share name in the file?

  • 0
    Not sure what you mean by exported license information so let me try to give steps.
    1. On any computer go to help - about Timeslips - support information. There you will see Reinstall code and a serial number. This is the information you will need.
    2. Make a backup of the database.
    3. Download (if needed) and install Timeslips v2016 on new server. Use the Reinstall code from step 1.
    4. Download and install latest service release for Timeslips v2016
    5. Restore your backup on to the new server where you want the database.
    6. Open Timeslips on the server and verify the database.
    7. Clear the license from the server if you don't want it used there. If you will open Timeslips on the server at the same time as on the workstations you need to do a local install using a path like you will use on the workstations.
    8. On the workstations go to start - all programs - Timeslips - station administrator - options - change install path. Browse to the new server and click on the Timeslip.cfg file. I recommend using UNC path. You must use the same path on all workstations.
    9. Open Timeslips and go to work!
  • 0 in reply to Caren2
    Thank you, Caren! That is exactly what I needed. I feel much more confident about moving the database and application now.
  • 0

    You can find an article in the Sage Timeslips Knowledgebase at http://support.na.sage.com that addresses this precise issue. Article 57767 holds specifics.