There are times when it might be necessary to move your SureSync installation to a new machine. For instance, if the machine you have SureSync installed on is being replaced by newer hardware you would need to move SureSync to the new machine.Please note that special care must be taken when moving a database to a new machine to ensure that the users are not locked out of the SureSync database due to lack of permissions on the Group Folder(s) in the database. If the old machine and the new machine are both members of the same domain and you use domain user accounts and domain groups for the Group Folder permissions in SureSync then there is no additional work to be done. The same user accounts and groups will be recognized on the new machine. If you are using local groups only then you must change the permissions on the Group Folders in your database before copying it to the new machine. You can end up using local groups either by choice when in a domain (you decide not to use domain accounts for the Group Folder permissions) or because one or both of the machines are standalone and do not have access to domain accounts. You can also have problems if the machines are members of different domains and there is no trust established between them. In these cases you must add the "Everyone" group to each Group Folder in your database and grant that group "Full Control" before copying the database to the new machine. This will allow you to open the database on the new machine and then you should immediately redefine your security for each Group Folder on the new machine and then remove the "Everyone" group to prevent unauthorized access to the SureSync database.
To move SureSync to a different machine you would do the following:
- It is recommend to place all schedules and real-time monitors on hold using the old SureSync installation first. This makes sure that the jobs don’t launch on the new machine before you’ve verified everything is configured correctly on the new machine. Once this is done make copy of the SureSync.mdb database file (or any other .mdb file you’re using with SureSync) and the SureSync5.lic file. If you’re using a SQL database you just need to know the name of the SQL server and the name of the SQL database to open it from the new machine.Install SureSync on the new machine. Copy the database into C:\Documents and Settings\All Users\Application Data\Software Pursuits\SureSync and copy the license file into the SureSync directory. Open SureSync and make sure to open the database you copied from the old machine. If your database is named the default SureSync.mdb and is in the C:\Documents and Settings\All Users\Application Data\Software Pursuits\SureSync directory it will be opened automatically. If it is something else you must open it by going to File | Database | Open.
- You will want to look through your relations and make sure all of the paths are still relevant and correct. If you removed a machine you will want to remove any reference to that machine from all the relations. Then go to Tools | SPIAgent Setup, select that machine, and click delete to remove it from the installation. This can’t be done if there are any references to paths on that machine remaining in the database. You would then want to add the paths on the new machine to the relations. Be sure to check the Roots tab of the rule to verify that the Root Paths are correct.
- You will want to install a SureSync Scheduler on the new machine. This is done by going to Tools | Schedulers... and clicking on Install. You can also remove the old Scheduler from the list.
- After you have finished modifying the relations it is recommended that you preview each Relation before running them the first time on the new machine to make sure everything is behaving as expected. Once this is done you can take your schedules and real-time monitors off of hold and let them run your relations in an automated fashion as you did on the old machine.