1. Install SQL Express 2008 on the new server (download from microsoft). No need to install TMS first OK
=>Unfortunately we have already installed and uninstalled TMS13.2.2 on the new server. Can we use it?
Or should we uninstall the SQL server and re-install it?
No, it's fine you can use it. I just tried to emphasize that it was not nessecary but possible, yes, just more work.
6.Type SQL command on the new server to restore SQL Database.
Should we use SQL commnad for SQL 2008?
Or you can install SQL management studio and just restore the database from there (depending on how you like to do it, just make sure the database name is "tmsng".
=>We tried to restore tmsng using SQLMS but it failed (SQLMS couldn't read tmsng.bak).
So we will try SQL command. Should we use SQL command for SQL 2008, not for SQL 2005?
(even though the tmsng.bak is backup of SQL 2005 Express)
SQL 2008 should be backwards compatible with 2005, if you are restoring to a 2008 then you use the 2008 command. If it does not work I recommend that you download the SQL Management Studio 2008 Express and restore the database using this application on the new server.
8. Put the TMSAgent backup in the same location as before C:\Program Files\TANDBERG\TMS\wwwTMS\Data\Backup on the new server and go to the TMSAgent settings and restore it from the dropdown list of backups.
=>According to "Migrating TelePresence Management Suite (TMS) To New Server.pdf" Page10, it says "*DO NOT YET ACCESS THE TMS PORTAL*", is there no problem if we access the TMS portal before we run TMS Tools Utililty?
Well, the only thing I can see happen is that when you log in to the TMS a new user is added to TMS (the user you are currently logged in with). All the other users from the previous server you won't be able to authenticate with. This means if you have a default group with no privileges that the new user you are logging in with will see "Access to TMS Denied". This can be worked around easily if you encounter this, however if your default group includes "Site Admin" then there should be no issues since then the user is admin by default anyway. The bottom line is that this is about old permissions from the old database.
10.Run TMS Tools Utility on the new server.
・ TMS Tools > Utilities > Change Users Domain
・ Old Domain Name:
If old server's name is "OLDTMS" and it doesn't use AD or Windows domain, should this be ?
・ New Domain:
If new server's name is "NEWTMS" and it doesn't use AD or Windows domain, should this be ?
=>We use same user name "Administrator" and a workgroup "WORKGROUP" for both old and new TMS. But the name of the server changes from
OLDTMS to NEWTMS. You mean we don't have to run TMS Tools Utility in this case?
I never did it, but the way I work with the databases is probably a little different. If you are not sure, I recommend that you follow the document as described. In my opinion its several ways of doing the migration and the document explains it in a certain way.
If the usernames are the same and the workgroup is the same then I don't think you will have any problems. If you do, just send me your e-mail and I will show you how to bypass the "Access to TMS denied".
/Magnus
