cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1210
Views
0
Helpful
9
Replies

How do I enable automatic updates of Jabber Video into TMS?

Chris Swinney
Level 5
Level 5

Hi all,

I'm just reading the Jabber Video admin guide (ver 4.6) which states on page 7:

Upgrading

When a new version of Jabber Video is available, you will get a Cisco TMS ticket if:

Procedure

Step 1 Automatic update checking is enabled. To do this:

a) In Cisco TMS, go to Administrative Tools > Configuration > Network Settings.

b) Under Automatic Software Update, set Automatically Check for Updates to Yes.

Step 2 Cisco TMS Agents are enabled. To do this:

a) In Cisco TMS, go to Administrative Tools > Configuration > General Settings.

b) Set Enable TMS Agents to Yes.

So, step one OK, but step 2 - where are the TMS agents option to enable? Can't see it in "Administrative Tools > Configuration > General Settings".

Many thanks

Chris

9 Replies 9

Jens Didriksen
Level 9
Level 9

There is no TMS Agent if you're using TMSPE - it is part of the OpenDS provisioning service.

Automatic update for JabberVideo has never worked for me, and considering 4.5 was supposed to be the very last version of JabberVideo as it is merging with Jabber, I suspect getting this to work won't be a very high priority somehow.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

ahmashar
Level 4
Level 4

say you have jabber 4.3 deployed. download a higher version e.g. 4.6 and  upload to the server and whether its TMS agent legacy or TMSPE, it  should detect and pop up a window when the user login next time to  his/her jabber client.

That is for user updates, which is simple enough to provision, however, the update url must be specified in the provisioning template(s) for each version.

I believe the original question is related to the automatic update service where TMS checks with the Cisco back-end for any new software updates - and this has never worked for JabberVideo (Movie) updates,

/jens

Please rate replies and mark question(s) as "answered" if applicable.

we have it in producion and it works fine. I just have to dig in to it to find out how it was configured.

So you are saying you have in production TMS issuing a TMS ticket when a new version of JabberVideo is released - just as it is supposed to do when new software releases are available for end-points etc?

That is something I have never seen...

/jens

Please rate replies and mark question(s) as "answered" if applicable.

       Here is the screenshot:

regards, Ahmad   

       

What you have got there is the normal update prompt individual users get  when this particular feature has been provisioned by the administrator - and that is not what's being asked about, nor is this a TMS ticket.

What I am talking about is the TMS ticket issued by TMS when a new software version is available from Cisco, just as what happens when new software versions are available for end-points etc through the "AutomaticSoftware Update" feature:

In the past TMS would issue a warning ticket and download the new software as well as the new RKs, however, this never worked with JabberVideo.

(There has been some changes to this procedure since going away from RKs, and TMS will now only issue a warning ticket advising new software is available for download from Cisco if a valid service contract is in place, however, TMS will no longer automatically download the software to the TMS server.)

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Many thanks Jens for the Input. This is indeed correct and what I was asking about.

Specifying the download URL in the provision template for the USER is fine, although it would be great if you could specify just a root set of configurations rather that a new template for each minor release. We actually run MANY institutions via our TMS, and whilst not a lot of them at the moment user Jabber, its going to be a real pain maintaining individual template setting for each institutions and each major/minor release of the software. Lets say we maintain 50 institutions , which means 50 different templates for each minor release - this is going to get out of control VERY quickly. Each template has pretty much the same info in it from the previous template, but of course all you want to do (in general) is to point the user to the new software download (as you have pointed out above). Copying the template over and over again is simple ridiculous., unless you had a need to do this (which for all intense a purposes -we don't)

But I digress.....

Hey Ahmad,

I take it that the lack of response is a No, this doesn't actually work as described in the Admin guide?

Chris