Moving Timeslips 2011 to new Server

We recently upgraded from TS 2008 to 2011 without any problems.  We purchased a new server and I want to setup TS 2011 on this server. 

 

We currently run the TS database on Windows Server 2003 Standard with 15 clients.  We are updating to a Windows Server 2008 R2 Standard - 64-bit. 

 

Since we did the upgrade from 2008 to 2011 can I still use the same disk to install on the new server? 

 

Do I just need to backup the database and move it to the new server and then map each clients network drive to the new database location?  Or do I need to reinstall each client starting with their new mapped drive to the new server?

 

Sorry if this has been asked before.  If there are any documented instructions from Sage on this type of transfer please point me in the right direction.

 

Thanks in advance for any help.

  •  


    mzoeller wrote:

    We recently upgraded from TS 2008 to 2011 without any problems.  We purchased a new server and I want to setup TS 2011 on this server. 

     

    We currently run the TS database on Windows Server 2003 Standard with 15 clients.  We are updating to a Windows Server 2008 R2 Standard - 64-bit. 

     

    Since we did the upgrade from 2008 to 2011 can I still use the same disk to install on the new server? 

     

    Do I just need to backup the database and move it to the new server and then map each clients network drive to the new database location?  Or do I need to reinstall each client starting with their new mapped drive to the new server?

     

    Sorry if this has been asked before.  If there are any documented instructions from Sage on this type of transfer please point me in the right direction.

     

    Thanks in advance for any help.


     

    Usually not that complicated.

     

    IF (and that is a BIG if) your server itself does not need to run Timeslips (for example to allow linking with a case management program), then all I would do is copy the entire Timeslips folder to the new server.  Then rename/kill the share to the old server.  remap the workstations so that they "see" the new server as the same path as the old server.  Should then work fine from the workstations with no reinstalling necessary.

     

    Hope this helps.  

    Folks for us, it's all about the Kudos.  If you think this suggestion was especially helpful, please consider clicking the KUDOS! (yellow) icon in this message.  Thanks.

    Nancy Duhon, Esq.
    Certified Consultant for Timeslips and Amicus Attorney
    Duhon Technology Solutions, LLC
    duhon@duhon.biz
    404-325-9779
    Providing personalized local and remote online support for Timeslips users for over 16 years.

  • Thank you Nancy.  I will give this a try once I have the new server ready to go live.  I will report back my results.

  • Did copying the folder work?  I'm doing the same thing this weekend & just realized I have to do the same thing...

  • If you want to do it as a fresh install - especially important if there are links - you can use your most recent program disk and the reisntall codes. I always recommend going to help - about Timeslips and then support information to get the reinstall codes as this guarantees the most current version of the codes. I recommend copying and pasting into a notepad document as the reinstall code can be a nuisance and type. Make sure you reinstall any service releases before dstarting the local computers.

    If the workstations will use the same path as previously then you don't need to do anything to the workstations.

  • With regard to the "big if",  how do I know if timeslips is doing linking with a CMS?  Time Matters is used, and time slips appears to be installed on the server, but I'm not sure thats necessary.  Is there an easy way to check?

More Content