TMS 14.6.1 and TMSPE 1.1

Similar Questions

• TMS in favor BBFRR and direct office

  Hello Experts,

  I just need help to know if TMX XE will support all the features of CTS Man. We are currently stuck with our current version of the CTS 1.6 and who won't support integration with Exchange 2010 EWS. We do have a TMS XE 3.0 and need to know if it will support BBFRR, direct office and all the other features. Could someone help me please?

  Thank you

  Shine

  Hi, shine,

  About the BBFRR Yes its support. !!! However for the functionality of direct office if you are looking for a feature of 'concierge' as a Manager for CTS then I don't think that we have something like this in TMS.

  But you can have a speed dial to achieve this goal, but it is not related to MSDS. I hope it clarifies.

  Thank you

  Alok

• Systems supported for TMS 13.2.1 and Release 14

  Hello, I would like to know if there is a document somewhere showing what are the systems could be registered with TMS 13.2.1 and TMS 14, because we thought the upgrade of TMS or not, we have also a lot of systems, the 'old' too, which we are not sure if can be saved as a type system instead of a room.

  We had this band:

  Tandberg 1000MXP, 3000MXP, 75MXP, 770MXP, 880MXP, 95MXP, 990MXP, Maestro.

  Polycom Viewstation 128, Viewstation, VSX7000A.

  LifeSize MX.

  I think that the MXP series can be recorded without any problems, but I'm not sure of the Polycom VSX, Viewstations, Lifesize MX and Tandberg Maestro (even if it's still a Tandberg).

  Kind regards.

  Hello

  Here is the document for at least 13

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/interoperability/Cisco_TMS_Product_Support.PDF

  / Magnus

• Removing VCS of TMS and TMSPE migration problem

  We prepare to start using TMSPE, however it must first disable replication on all VCS via MSD MSD Agent.  There is a VCS that have failed has been deleted afterwards, but we cannot delete TMS because TMS Agent replication is enabled.  We cannot have the Agent MSDS tab to disable the replication because the VCS is offline (i.e. it was removed) - it just goes to the 'Connection' tab whenever I try.

  So, how can we migrate to TMSPE if TMS don't delete us the VCS in offline mode or at least turn Replication Agent MSDS for it?

  Hey Nick

  Try to run this SQL query:

  USE TMSNG

  UPDATE field_SystemField SET BolValue = 0 WHERE field_Field_Id = 1072

  UPDATE Cluster SET EnforceTMSAgentDataReplication = 0

  This should clear the replication on all VCs added to the TMS (even the zombie ones like the one you have), once it is executed, you can try to purge the VCS.

  / Magnus

• Interval synchronization and TMSPE

  The fact that the LDAP/time synchronization interval is static, TMS causes a lot of headaches for organizations that deploy quickly end points configured to their user base.  Only they that must wait for the nightly synchronization or manually connect to TMS and this kickoff, which does not fit well when dealing with many wish someday and strong demand.

  In the TMS Agent model there was formerly a SQL, stored procedure, you can use to trigger synchronization, is there a similar way to trigger by LDAP Sync program under the TMSPE model?

  Hi, Frédéric

  I asked about this and was told that is not possible in TMSPE that the interval is embedded in the code. I know that it was possible for the TMS Agent Legacy.

  I guess a feature request is the way to go in order to get this configurable setting.

  / Magnus

• VCS 7.2 + TMS 13.2.1 + version TMSPE Movi/Jabber compatibility

  Hi, if I switch to 7.2 VCS + TMS 13.2.1 + TMSPE.

  Jabber/Movi will work with version 4.1 and 4.2?

  This is essential information as Jabber (4.4) update is not possible right now on all PCs.

  Tom br.

  Yes.

  We have everything from 4.0.1 to 4.5 Movi on the system we use in the office, I work in and run with TMS 13.2.1 X7.2

• 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

• Help with Jabber AD auth and TMSPE

  Can someone point me in the right direction to obtain the documents that cover the VCSC auth TMSPE operation device and available Jabber and auth users.

  I have the TMSPE guide and the auth VCS guide, but I'm looking for clarity on how the users who have been auth with AD via VCS would get provided by TMSPE when the users are not in TMSPE right now?

  Thanks in advance

  Tim

  Sent by Cisco Support technique iPad App

  Hi Tim,.

  Successful commissioning, you import these users AD in TMSPE.

  Initial authentication for the user of jabber will be through VCS to AD, but after the authentication for a commissioning successful that the user must be in the TMSPE database.

  If the user is not present, then you will get an error message.

  For TMSPE, set the default zone to check the credentials only.

  Thank you

  Alok

• 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

• TMSPE & Java compatibility

  In the process of migrating from former officer of TMS TMSPE 1.0, I was prompted to install Java 6 on Win Server 2008R2.  Also fix TMS 14.2.1 and TMSPE 1.1.

  Since Java 7 is the latest version that I prefer to install that.  Are TMSPE 1.0 and 1.1 compatible with Java 7 or should I stay with Java 6?

  Thank you

  Mike

  Mike-

  TMSPE 1.0

  • Java version 6, update 4-33 is supported.
  • / Cisco_TMSPE_Deployment_Guide_1 - 0.pdf

  TMSPE 1.1

  • Java version 7, 17 & 40 updates is supported.
  • / Cisco_TMSPE_Deployment_Guide_1 - 1.pdf

  See the prerequisites and recommendations of two guides for more details.

  I'd stick to the recommended Java version regardless of the version of TMSPE you plan to install at this time here.

• Cannot add the conductor on the model of CMR TMSPE

  We strive to set up video-conference planning. Conductor and vTS are already integrated. Conductor is also integrated through the trunk SIP CUCM, for both ad hoc and permanent meeting. We were able to add the conductor on TMS as a device and TMSPE CMR model. But when we turn on HTTPS and signed a driver's certificate, unable to connect the driver TMSPE. We tried to create, sign and load the certificate for TMS, but still not able to connect. I hope you can help us. TMS is running on license eval. Conductor is essential and STM have 5 licenses of the screen. I've seen some answers on a few forums about Java version used with TMSPE.

  15.2.1 TMS

  TMSPE 1.7

  Update Java 8 102

  Conductor XC 4.2

  4.3.1.14 vTS

  Have you enabled 4096-bit encryption on the server where it is installed TMSPE by doing the required Java software changes indicated in the Notes of version 1.7 TMSPE? If you do not, TMSPE will not be able to communicate to the driver.

  You mention that you are trying to set up a schedule with TMS and conductor, generated TMSPE CMRS are not able to be used for planning. To set up planning, you need to configure Conference models/alias etc. on driver as well as in TMS, refer to the 'Conference on-demand management' section of the CMR premises Deployment Guide Release 7.0 - primary (for Unified CM) on pg 41.

• Error TMS agent Portal

  Hi all

  I have exactly the same problem as described in this discussion: tmspe-tms-aent-page.  If I try to connect to http://TMS/tmsagent/tmsportal (or https).  I get the error message "an error has occurred. ' Reload the page and try again.  See the attached file.

  With TMS 14.6.1 and TMSPE 1.4 installed on Windows 2008 R2 server standard edition server.

  TMS is running for a couple of months with this version very well. Recently, I've implemented CMR after conductor and new mm410v has been added to you video below. A model was created and applied to a group of users. This group has the authorization requested to the meeting of the book.

  I got the same error message when I click on the button "Edit CMR in the portal".

  If I try as http://tmsipaddress/api/v0/version suggested link I get a page not found error.

  Default Web site also has an HTTPS binding.

  I'm stuck because I am not able to solve problems more.

  Cisco TAC after webex session ask me follow up with Microsoft!

  Any suggestion or advice is welcome.

  Thanks in advance.

  Ahmed

  TMSPE working before trying to add CMR, or is this a new installation?

  Java has been updated recently? TMSPE 1.4 requires Java 7 update 51, I know that's not far from the version you use, but it is worth it to try the version that offers the deployment guide.

  It could also be that Windows is missing a required service pack, see tms-agent-ui - error message.

• Authentication failure TMS while improving the TMSPE to 1.4

  Same problem as https://supportforums.cisco.com/discussion/12333951/tms-authentication-error-while-installing-tmspe here

  But while trying to TMSPE of 1.3 to 1.4 after completing the MSDS go to 14.6

  1.4 deployment guide mentions "Cisco TMSPE has been tested with Java 7, updated 51, 32-bit and 64-bit versions"

  Which is the same as TMSPE 1.3

  If the doc is fake or this time, it's a different question than the Java version

  I had the same problem as you, improved TMS to 14.6 and then tried to update TMSPE to 1.4.  One thing I did and it solved my problem is to reboot the server after that updated MSDS to level, before attempting to upgrade TMSPE.

• Upgradeing TMS using TMSPE

  What is the process of upgrading of TMS which currently uses the TMSPE?  I know with TMS Agent Legacy, you had to Devil replication with VCS, but I'm not familiar with TMSPE at the moment and how to upgrade of MSDS.

  Simply upgrade the tms regularly according to the documentation. No need to turn off the mark.

  / Magnus

  Sent by Cisco Support technique iPhone App

• TMS, VCS and Jabbber "impossible to connect to the TMS on the VCS agent".

  Dear,

  We have Cisco TMS, VCSC and jabber deployment, we did before commissioning the VCSC and TMS and jabber worked well, but after the upgrade the VCSC v7.2 to jabber version 8.2 has stopped working and I can not connect more and when I go to the TMS and connect to the VCS I get "unable to connect to the TMS on the VCS agent" Please notify

  What TMS version do you use?  And you are using Extension of provisioning of the TMS (TMSPE)?

  Looks like you are using TMS Agent Legacy, which has been supported in VCS X7.2 and has since been removed from X8.1.  You will need to migrate to TMSPE and very probably upgrade your server TMS as well if you do not meet the minimum version.

  Cisco TMSPE 1.0 Deployment Guide

  Here's the guide deployment for TMSPE 1.0, there are newer versions, but 1.0 is one that you want to migrate from legacy Agent TMS.  Once installed and migrate your data, you can then go to the most recent version, which is 1.4 (see below).

  Cisco TMSPE with VCS 1.4 Deployment Guide