TMS appliance 13.2 to 14

[felixroot]

Hi all.

My costumer have appliance TMS software version 13.2.2

Now have trouble with Russian time zone.

I am read Release_Note to 14-2 end find resoulve my problerm:

CSCtx39000 Corrected the issue where Russian time zones were displayed incorrectly in Systems >

Navigator > select a system > Settings tab >Time Zone field.

But system requirement to upgrade to 14.2 not correct to appliance TMS. (small memory, OS Windows 2003 server)

You can think of to fix the problem?

[daleritc · Accepted solution]

The TMS Appliance should be able to handle an upgrade to 14.2.1...although we are removing support for Windows 2003 Server soon and the TMS Appliance is EOS/EOLed.

Therefore, I would recommend you migrate the TMS application and TMS SQL db (aka tmsng) to a customer owned server, i.e. either HW or VMware.

And if you do the "migrate", note that you will require to obtain new release key for the TMS since the TMS release keys for the former TMS Appliance began with 80Bxxxxx and the sw itself begins with 80Axxxxx. To do this, see the following instructions:

1. Customer must first order a base copy of TMS using CTI-TMS-SW-K9. This will provide them with a non-appliance/software-only serial number that will begin with 80Axxxxx. As it is the base-software, it will come with 10 system licenses. So, they are effectively purchasing 10 additional systems from what they had before.

2. Once they have the new serial number, call TAC and ask for an SR to be raised with GLO (Global Licensing Operations). This is a re-hosting request for the options on their TMS Server appliance, with a serial number that begins with 80Bxxxxx, to be re-hosted to the new software-only serial number (again, begins with 80Axxxxx).

3. GLO will forward the request on to the TMS PLM. The TMS PLM typically approves most, if not all of the items on the request.

4. Customer will receive back a new PAK (Product Authorization Key) to run against their 80Axxxxx serial number from the cicso.com/go/licensing page. They can then update their existing TMS install with the new release key. After pressing Save, this will update the serial number at the bottom right corner of the web browser. Then all they have to do is add the option keys one by one and press Save when done.

rgds,

Dale

[Simon Taylor]

Hi Dale

I have a similar situation, we have a client running an appliance that needs to go the latest version of TMS

Quick Question:

Can the two systems co-exist for a while?

I would like to say to the client "Your old TMS appliance will still work whilst we perform the migration. If we encounter problems during or after the migration we can go back to the appliance"

How long can we keep the appliance running?

Regards

Simon

[daleritc]

No, you cannot have two TMSs in the mix.

/dale

[asafayan]

Folks,

I read the following language on page 8 of the following Cisco Deployment Guide:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tmspe/install_guide/Cisco_TMSPE_Deployment_Guide_1-0.pdf

Cisco TelePresence Management Server

Cisco TMSPE may be installed on the now discontinued Cisco TelePresence Management Server, but note that system resources are limited to 2 GB RAM, which will reduce performance. We recommend using the server for small deployments only and ultimately migrating to hardware with more resources available.

Is this viable short-term while the SKU CTI-TMS-SW-K9 is being ordered?

Thanks,

Amir

[daleritc]

Hi Amir,

As it states, if its a small deployment, then you may get away with it but I'd strongly recommend migrating to hw with more or appropriate resources, including later MS OS systems, i.e. MS Server 2008 R2

Dale