13.2.2 to 14.5.0 TMS upgrade path

Similar Questions

• TMS upgrade, the OS and DB Migration

  Hello

  We currently use TMS 12.6.1 on Server 2003 with SQL 2005, but we intend to move to 13.2 TMS on Server 2008 with SQL 2008. I can't find a specific documentation on the management of OS and DB updates just in place upgrades to MSDS.

  Are the steps below for a migration to that action plan we aim the right?

  -New server made available with SQL2008 (same host, same IP address, but obviously disconnected name)

  -Move tmsng database from the old server to new server.

  -Install the TMS 12.6.1 on the new server by selecting a custom installation and specifying the existing database.

  -Perform to upgrade in place on the new server to 13.2 TMS.

  -Disconnect the old server, connect to the new server.

  Thank you

  Mark

  Hello

  Yes these steps only seems that you don't need to install 12.6.1. Once the database is moved to the new server, you can install 13.2.1. The installation program will detect the 12.6.1 data bases and update accordingly.

  Also remember that when you upgraded, check the settings in MSD since a large part of the old server settings will reside in the database. But you will notice...

  Good luck.

  / Magnus

  Sent by Cisco Support technique iPhone App

• TMS upgrade error code 1902

  Hello!

  Facing a problem with an TMS14.2.x upgrade.  The upgrade keeps bombing during the updating of the database.  Initially, it was to have null values in PlannedEndTime.  After you run the script to fix the client runs in a new error;

  Error code 1902 to line 1: cannot create more than one index cluster on the table ' dbo. AclUser'. Remove the clustered index existing 'ix_clust_temp' before creating another.

  Is it simply a question of the removal of the existing "ix_clust_temp" and re-run the installation program?

  Thank you!

  I think I fell on this before. What I did was set a SQL set to clear statistics so that they can be reconstructed correctly. Like any other action that makes a deletion. Be sure to get a solid backup of the database before anything else, as it is attempted.

  DECLARE @ObjectName sysname

  DECLARE @StatsName sysname

  DECLARE StatsCursor CURSOR FAST_FORWARD

  FOR

  SELECT

  "[' + OBJECT_NAME (object_id) +"] "as"ObjectName. "

  "[" + [name] +'"] ' as 'StatsName'"

  OF sys.stats

  WHERE

  (INDEXPROPERTY (object_id, [name], 'IsAutoStatistics') = 1

  OR INDEXPROPERTY (object_id, [name], 'IsStatistics') = 1)

  AND OBJECTPROPERTY (object_id, 'IsMSShipped') = 0

  OPEN StatsCursor

  THEN the EXTRACTION OF StatsCursor

  IN @ObjectName, @StatsName

  WHILE @FETCH_STATUS = 0

  BEGIN

  EXEC ("DROP STATISTICS" + @ObjectName + "." + @StatsName)

  THEN the EXTRACTION OF StatsCursor

  IN @ObjectName, @StatsName

  END

  CLOSE StatsCursor

  DEALLOCATE StatsCursor DECLARE @ObjectName sysname
  DECLARE @StatsName sysname
  DECLARE StatsCursor CURSOR FAST_FORWARD
  FOR
  SELECT
  "[' + OBJECT_NAME (object_id) +"] "as"ObjectName. "
  "[" + [name] +'"] ' as 'StatsName'"
  OF sys.stats
  WHERE
  (INDEXPROPERTY (object_id, [name], 'IsAutoStatistics') = 1
  OR INDEXPROPERTY (object_id, [name], 'IsStatistics') = 1)
  AND OBJECTPROPERTY (object_id, 'IsMSShipped') = 0
  OPEN StatsCursor
  THEN the EXTRACTION OF StatsCursor
  IN @ObjectName, @StatsName
  WHILE @FETCH_STATUS = 0
  BEGIN
  EXEC ("DROP STATISTICS" + @ObjectName + "." + @StatsName)
  THEN the EXTRACTION OF StatsCursor
  IN @ObjectName, @StatsName
  END
  CLOSE StatsCursor
  DEALLOCATE StatsCursor

• Downgrade 14.4 to 14.3 TMS

  Hi all

  As stated in my previous post, Cisco seem to have withdrawn in favour of TMS upgrade VCS to 14.4, we have a whole bunch of them, whereas makes life very difficult and frustrating.

  I've recently upgraded to TMS from 14.2 to 14.4 to relieve another upgrade question, that we have been see in the CODECs of TC relation, but it is still more of a problem.

  I suspect it is not simple to 14.3 14.4 decommissioning, but I was wondering if there was a procedure to do this?

  See you soon

  Chris

  We run TMS app and tmsng.db on the separate virtual machines, so take us a snapshot of each just before any upgrade and can very quickly return to the previous version if necessary by restoring snapshots.

  Only the hassle I have had so far on the odd occasion, we had to do that, was when we had to do the restore, a day or more after the snapshot has been taken, as the AD credentials for the SMT server would be more valid, then first remove it from the domain, reboot, add the back and restart again.

  Has worked well in other well. :)

  /Jens

  Please note the answers and score the questions as "answered" as appropriate.

• GUID value for 14.4 TMS must be configured on F5.

  How get the 14.4 TMS GUID value must be configured on F5. 14.4 TMS upgrade guide, the value of the GUID of the TMS must be entered in the string to send to probe.

  #CREATE MONITOR for TMS KEEPALIVE THE GUID IS FOUND in TMS GUI tmsh create ltm monitor https mn-TMS-HTTPS {DEFAULT cipherlist: + SHA: + 3DES: + kEDH compatibility enabled by default - https destination *: 443 interval 5 past drifting recv 200 recv - disable 503 send "HEAD /tms/public/IsAlive.aspx/? '} {"Guid =\\r\\n" time - until line-up 0 timeout 16 username 'DOMAIN\rname'}

  Are you referring to a redundant deployment of TMS?

  If so, take a look at page 31 under the section "Configuring network load balancing."

  You will find the URL Probe in TMS with a specific GUID to this knot here:
  Administrative Tools > TMS Server Maintenance > TMS redundancy > probe URL

• TMS - page Free Busy preview deleted in TMS 14

  Hi people,

  I am aware that Cisco has removed Free Busy overview of TMS 14. Butterfly last night that I had to abandon two TMS upgrade just because of this big changing in 14 of the TMS, the customer preferred version 13 to lose the page.  =(

  Well, now I have a few very dissatisfied customers of the TMS 14, including those who have abandoned the upgrade and new customers who just purchased TMS a few days. Some clients really need to have 14 MSD, because integration driver and Smart Scheduler.

  I opened a folder of TAC just ask "why this page removed if it's so useful? The response was:

  "(...) I checked with the developers and this page has been deleted because it was very heavy database and therefore killed performance of TMS. Unfortunately there are no plans to introduce a similar or equivalent page in the future (...) »

  Couldn't Cisco offer other hardware requirements for MSDS instead of deleting the page? Cisco has really no plan to add a page as a preview held for free? Is there an other customers around the world require the same thing? Because in Brazil, most of the customers are demanding. What are the additional options should I (except outlook calendar and the integration of MS Exchange)? Can I create my own free animated presentation page using the API of reservation or something else?

  Thanks in advance.

  Concerning

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

  Hi Paulo, I ask of you reach out to the Cisco account/sales in your area Member to access this feature back in the next future version of TMS, as they join respective team in Cisco further on that.

  BR/Mahesh Adithiyha

• TMS of Cisco 'Unable to access Cisco TMS' error

  Hello

  I have another problem with the server of TMS as well! On my Web interface, I get the message "Unable to access Cisco TMS - TMS Incorrect database version" detected! Someone has an idea?

  What TMS version?

  Is it a new installation or you migrate TMS and TMSPE?

  This error is usually visible with the TMS upgrades/migrations when the SQL database is running an earlier version.

  Difficulty, uninstall TMS and then reinstall it.

  During the re - install, you will receive a prompt to upgrade the database.  This should fix the problem.

• TMS - DB Login Username = undefined (?)

  Hello everyone,

  After a TMS upgraded 13.2.1 in 14.1.1 I see not under TMS > administration tools > Extension Analytics Login username is "undefined". (See attached screenshot)

  Although I have the impression (after several tries), everything works fine...

  Anyone know how / if this affects the service or how to fix it?

  It makes me a little nervous

  Greetings,

  Mounir

  Magnus Ohm wrote:
  [...] Not 100% sure if this is removed on purpose when upgrading to 14.1.1 [...]
  

  No, it has nothing to do with anything specific 14.x.

  It is a known problem, the Tandberg 80893 reference number. It is purely cosmetic and will not affect the product in some way.

  Kind regards

  Kjetil

• Question about MSD + upgrade and migration applications

  Hi all

  I am running:

  TMS 13.2

  TMSPE 1.0

  The two co reside on a Windows 2003 server, pointint in an external box of SQL.

  We also organize TCX 2.3 on our Exchange.

  Now that our server guys have * finally * installed the service pack required on the Exchange, we are ready to migrate to TMSXE but also to upgrade the TMS and TMSPE.

  So we want ot go to:

  TMS 14.2.1

  TMSPE 1.1

  TMSXE 3.1

  In addition to migrate a Windows server 2008R2 TMS + TMSPE.

  I know the different individual guides to upgrade as well as the dependencies between TMS and TMSPE/TMSXE versions.  I'm hoping to do the upgrade and migration all in one and am hoping to get some tips on the best order to do everything.

  My first question - decomission the 13.2/TMSPE server 1.1 TMS, that I can install TMS 14.2.1 and TMSPE 1.1 on the Windows Server 2008, they point to the relevant databases and allow upgrading from there? Or do I need install the new versions TMS/TMSPE on the old server, first of all, upgrade the databases and then migrate?

  Second question - before all this, I run the TMSXE migration tool to extract the data 2.3 TCX, uninstall TCX of Exchange, TMS upgrades and then install TMSXE 3.0/3.1 at the end?

  As all this is running on the virtual machine I'll instant just in case.  Advice on the issues listed above, or general advice about these upgrades would be appreciated

  Hi Nick, IMHO, I suggest you first migrate your 2.3 TCX to TMSXE 3.0.2 by this TMSXE 3.0 installation guide, and then pass the TMS and PE later.

  Yes, VM snapshot backup option before any upgrade is fine.

  BR, Mahesh Adithiyha

• Not enough question resources MSDS-driver-TelepresenceServer

  Hi all

  We have a solution with TMS (14.6.2), conductor (XC3.0.3) and GST (4.1 (2.33)).

  Since we went from the TMS to 14.6.2 (from 14.2.1), we get this error:

  tpsfail.PNG

  

  We get this error when we have another time and both get more than 12 participants. We tried to change patterns of conductor (720/30 and no content should be allowed 1/2 screen) to use less than one license per participant but we always get this error.

  Before the tMS upgrade we have no problem with that, we can plan and execute the GST conferences with more than 12 participants, regardless of what quality we choose.

  Best regards

  David.

  There should be a '1280 x 720 p 5 fps' option under the quality of the scrollable content.

• TMS follow-up Conference does not work after update of Java

  Just installed Java 7 update 51 and now I am not able to enter the CCC in TMS 13.2.2.

  This is the dump of Java:

  Java plug-in 10.51.2.13

  With the help of 1.7.0_51 - b13 version JRE Java hotspot Client VM

  Home Directory user = C:\Users\lhamilton

  ----------------------------------------------------

  c: clear console window

  f: finalize objects on the finalization queue

  g: garbage collection

  h: display this help message

  l: dump classloader list

  m: print memory usage

  o: trigger logging

  q: Hide console

  r: reload the policy configuration

  s: dump system and deployment properties

  t: dump thread list

  v: dump thread stack

  x: delete the cache of class loaders

  0-5: set the trace level

  ----------------------------------------------------

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Attribute of manifest missing application name for: http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  I had similar problems yesterday when I updated to 7u51 (with TMS 14.1.1).  I rolled back to the previous version, I had installed and it worked fine.

  Pursuit of the investigation, it seems to happen due to new security measures in the new version of Java.  You can move with the latest version of Java 7u51 by adding your server TMS in the security exception list:

  (1) Control Panel Java Open

  2) click the Security tab

  3) click on the button "change the list on the Site."

  4) click Add and type the URL of your server TMS in the location area (IE http://tmserver/tms/)

  (5) to continue beyond the warning about sites http if you use http instead of https

  6) click OK on the control panel

  Then you should be able to hit the Java pages in TMS without any problem.

  Wayne

  --

  Remember the frequency responses and mark your question as answered as appropriate.

• TC cannot connect to TMS on demand conference

  Hello community,

  I sent TCS in our video conference infrastructure and SIP Trunk to CUCM.

  I can do by opening a web session of the TCS for manual registration and dial points endpoint or lectures on the conductor using SIP.

  But if I do the Conference planning on recording of the Conference, the TCS and TMS don't auto connect to the Conference. Registration (SIP URI) alias are configured on TCS.

  I see on the connection of conference TMS setting the driver calls the CHT by using the h.323 protocol but TCS is not registered with the h.323 Gatekeeper. It's using a SIP trunk to CUCM. Is this a limitation if the TCS uses SIP trunk?

  tcs_error.jpg

  

  Thank you.

  ACCOUNT that is configured with CUCM planning only is not supported yet in TMS using the recording during a conference booking. See cisco-tms-cant-schedule-sip-recordings-tcs for more details, the solution is to add the alias to record with a participating entry model or the phone book.

• TMS and AVAYA scopia endpoint interoperability

  Hello

  I have the management console of the TMS version 13.2. It is not the latest version, but I wonder if AVAYA SCOPIA XT-4300 products are compatible for integration in the TMS. It's like the product POLYCOM HDX?

  Y at - it a document on which products are supported?

  Thank you very much!

  For TMS 13.2, you can take a look at the Documentation of integrated systems, specifically Product Support and documents using the feature to see what Cisco and 3 third-party products are supported.

  Note, for the most recent releases TMS, you will need to look at the admin guides as well as Telepresence interoperability of data because there are no available detailed compatibility document, similar to those mentioned above, for the version beyond TMS 13.2.

• Cluster TMS

  Hello

  I have 2 servers TMS lab facility. I need to make the combination between these servers with the same SQL database. I checked in google, all documents are mentioned with infront network load balancing. Because I don't have a material I don't know how the grouping between the TMS servers.

  When I asked my manager said, there is another way to do grouping without using NLB and he won't tell. BCZ I need to know about mine... which i have no idea... Please someone tell me... Here are the details...

  Primary server for the TMS (15.1) - 10.66.204.45

  Secondary server of MSDS (15.1) - 10.66.204.46

  SQL 2014 - 10.66.204.40

  Hello

  You can use the LB which is the recommended method and other could be DNS (not so great)

  Please see the link below.

  https://supportforums.Cisco.com/discussion/11921901/TMS-redundancy

  Please see page 30 for the detailed explanation.

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/TMS...

  Kind regards

  RACLOT

• TMS IP address changing

  Built a new setver 15.0 TMS in the laboratory and I now have to move to its real end IP address.

  I remember that there was a document that tells what to change to make this happen, but I can't.

  Can someone tell me the document?

  Thank you

  Either before or after you change address IP of TMS on the server itself, you need to update the field "TMS Server IPv4 address" listed under administrative tools > Configuration > network settings and use the settings option management apply on the same page under the heading Services MSDS to update IP address on all systems managed at the time. You can also go to each system managed on their settings page and use the settings option apply management it update each system one by one.