Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Cisco Employee

TMS 13.2 + Provisioning extension is out

The software we all been waiting for is now released

http://www.cisco.com/cisco/software/release.html?mdfid=283613664&catid=280789323&softwareid=280886992&release=13.2&relind=AVAILABLE&rellifecycle=&reltype=latest

Can be dowloaded here. The provisioning extension is also released side by side with 13.2.

Found here

http://www.cisco.com/cisco/software/release.html?mdfid=284330317&catid=280789323&softwareid=280886992&release=1.00&relind=AVAILABLE&rellifecycle=&reltype=latest

Enjoy

Sent from Cisco Technical Support iPhone App

1 ACCEPTED SOLUTION

Accepted Solutions

Re: TMS 13.2 + Provisioning extension is out

Hi Juergen!

Ah, yes, forgot to give a feedback here :-)

For me the fix was that I specified the port manually in the address field like:

127.0.0.1:1433

or what ever you have set up as the ip/port it listens to on TCP.

I also had disabled named pipes:

Addon: if I remember it right you also see a syn to 1434 or something like that, so not sure why the instller behaves like that)

Good success and please rate the message using the stars below!

Please remember to rate helpful responses and identify

75 REPLIES
New Member

TMS 13.2 + Provisioning extension is out

about time! thanks for the heads up, Magnus!

D.

Cisco Employee

TMS 13.2 + Provisioning extension is out

Thanks Martin

New Member

Re: TMS 13.2 + Provisioning extension is out

When is 14.0 coming out?  This looks to me llike nothing more than a maintenance release.  I am very disappointed to say the least with this.  I was really looking forward to the next version.  Currently running 13.1.2 and looks like it's not worth it to upgrade because it would break more things than it fixes.

New Member

Re: TMS 13.2 + Provisioning extension is out

there are definitely some more functionality surrounding the provisioning agent. Alot of back-end went into developing a more robust provisioning experience. The old LDAP opends was sometimes flakey and very in-consistant.

But yes, if you dont experience any issues, i would suggest waiting til TMS 14.0.

Cisco Employee

Re: TMS 13.2 + Provisioning extension is out

Hi Michael

Indeed the 13.2 is a minor release which has introduced some minor fixes/changes to TMS it self. The most important thing with TMS 13.2 is the new provisioning model TMSPE (Provisioning Extension) which is a major upgrade in terms of stability and scalability for the provisioning part of TMS.

This is the main reason that TMS 13.2 has been a version many have been waiting for because it introduces support for the new provisioning model as Darren is mentioning above.

Is there anything specific the TMS 13.2 will break compared to TMS 13.1.2?  Any functionality you are waiting for in particular for TMS 14.x?

/Magnus

TMS 13.2 + Provisioning extension is out

Hi Magnus,

TMSPE Deployment Guide says

Prior to installation and deployment of Cisco TMSPE, we recommend upgrading all endpoints to the latest software version available.

which is fair enough, however, I will most probably have a number of users still on JV 4.2 when I implement TMSPE next week-end - will this cause provisioning problems for these users?

/jens

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

TMS 13.2 + Provisioning extension is out

I have a similar question to Jens above;

We do not currently use TMS Agent provisioning, but we are looking at rolling out Jabber/Movi.  I was waiting until TMS 13.2 came out so I could use provisioning extension mode;  can I continue to use templates etc for my video endpoints (many of which are on old software) while I use TMSPE for Jabber/Movi only?

Cisco Employee

TMS 13.2 + Provisioning extension is out

Hi Nick

You are talking about the configuration templates for the video endpoints? If so then yes you can continue using the configuration templates along side with the Jabber using the TMSPE.

Just so I have not misunderstood you here is a screenshot of the feature I think you are talking about:

/Magnus

Cisco Employee

TMS 13.2 + Provisioning extension is out

Hi Jens

You will be able to login with JV 4.2 with the new provisioning extension yes. But you need to have a 4.2 configuration template installed.

/Magnus

TMS 13.2 + Provisioning extension is out

Thanks Magnus, very much appreciated.

/jens

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

TMS 13.2 + Provisioning extension is out

Jens / Nick: like I wrote before, test it upfront you deploy it do better understand which impact

it might have on your deployment. The major showstopper for me is the missing user level configuration

and the changed capability to inherit settings to child folders and that you might end up with way

to many configuration templates which then get out of sync.

There are some clear benefits of the new model, like better scaling (not a full-mesh replication anymore).

If you had multiple vcs with the provisioning agent running (also multiple clusters) then you might know

what I am talking about. The replication of specific sub levels to a vcs or different provisioning phonebooks

based on groups.

Jens: you can still use the same xml device templates you had used before, so the movi/JV version

itself is not an issue. In addon what Magnus said, you could also log in with a Jabber 4.4 profile.

Nick: the devices which can be provisioned did not change and also the old style  "System Navigator"

incl "the provisioning templates" (not to be mixed up with the provisioning directory) still exist in 13.2-

Its  the provisioning directory backend and its user-frontend which is new.

TMS13.2 will work with the old style open-ds provisioning as well, so at least there is no force to use TMSPE.

If you don't have enormous trouble with the old provisioning and you are not dependent on new functionality

then it might make sense just to wait what other new functionality will be introduced with the next version.

Nick/Jens: whats the reason why you "desperatly" want to upgrade to it?

Michael: what are the features you were hoping to see?

Please remember to rate helpful responses and identify

TMS 13.2 + Provisioning extension is out

Thanks Martin/Magnus.

The reason I want to upgrade;

We currently don't have any Movi/Jabber users but we want to roll this feature out.  Up until now, we haven't used provisioning, but it was enabled however not working properly (like that since before I started here).  There seem to be lots of issues with the way our old provisioning/TMS agent configuration that seemed like more hassle than it was worth to fix it as I had no users or anything to migrate anyway, so I decided to wait for TMSPE.

TMS 13.2 + Provisioning extension is out

Hi Martin,

Oh, I don't "desperately" want to upgrade to it as the  existing provisioning method doesn't give us too many problems in  general.

Having said that, Cisco recommends the upgrade  to fix an outstanding TAC case we have which involves JabberVideo 4.3  and 4.4 not playing nice on Macs running L...n 7.3 (can't spell it out as the Cisco spam filter then blocks post) - and as we are  getting more and more L...ns prowling our network, it needs to get fixed  sooner rather than later.

After a lot of testing, log  traces etc - Cisco believes our issue is caused by the current  provisioning method and we should not see it with TMSPE.

Upgrading  from 13.1.2 to 13.2 doesn't worry me at all, it was the TMSPE that I  wasn't too sure about. However, seeing that I can turn off TMSPE and go  back to TMS Agent should I need to, and the fact I can still use the old  templates for the few users I still have on 4.2, makes me feel a lot  better about it.

/jens

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

TMS 13.2 + Provisioning extension is out

Ok, yes, thats not good. Interesting, did not notice Mac issues here.

Yes, you can go back, but then you loose the changed data.

You can only migrate data from OpenDS to TMSPE but not reverse, so be aware of that.

Please remember to rate helpful responses and identify

Re: TMS 13.2 + Provisioning extension is out

Martin Koch wrote:

The major showstopper for me is the missing user level configuration

and the changed capability to inherit settings to child folders and that you

might end up with wayto many configuration templates which then get out of sync.

Yup, not having the user level configuration is not good at all - don't really understand the thinking behind not having that in this release.

I import all of our users from AD, which is divided into groups based on ORG, which is Faculties, Shools, Disciplines, Services etc - and I have some users within some ORGs where I have to provision max and default b/w as 512kbps, whereas all other users are provisioned with 4Mbps. Not sure how I can easily achieve this with TMSPE.

I've upgraded to  13.2 but had to go back to the legacy TMS Agent as I'm having some comms issues between VCS-C/TMSPE and the TMS server,

I'll look at it again when back at work on Tuesday.

(See Martin; open/close - inside joke )

/jens

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

TMS 13.2 + Provisioning extension is out

Guess I would go with AD groups like ORG1-512kbit, ORG1-4MBit, ... and then map

them to specific folders/templates/importfilters in the TMSPE.

If you or somebody else finds an easier way (besides using the old provisioning :-P ) please post it here!

Please remember to rate helpful responses and identify

TMS 13.2 + Provisioning extension is out

Martin Koch wrote:

Guess I would go with AD groups like ORG1-512kbit, ORG1-4MBit, ... and then map

them to specific folders/templates/importfilters in the TMSPE.

If you or somebody else finds an easier way (besides using the old provisioning :-P ) please post it here!

Won't work as we would then have to add these to AD itself each time we need one within a specific ORG, it just ain't going to happen.

Each ORG is unique and is determined by where they sit in the organisational structure, i.e. a top level for a Faculty, then a sub-level for School within this faculty, then another sub-level for Discipline within this School etc.

And we have a lot of these, and since they are all within specific ORGs based on the above and not on their geographical location, and as we have a number of locations..well...it would get real messy very quickly.

/jens

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

Re: TMS 13.2 + Provisioning extension is out

I fully acknowledge what you say and I would assume that many TMS admins will not have

AD admin access to even be capable of moving users / groups by that.

And am also  sceptic if we end up double up groups for TMSPE for each unique setting parameter

we will most likely run out of sync of our configurations, ...

There definitely will be use cases where the new TMSPE will be an exact fit and makes admin life much more

easy, but at least not for the two of us, ...

So I guess its just hope and wait for the next release(s) of TMSPE and stick with OpenDS.

Jens: did you see my private message?

Please remember to rate helpful responses and identify

Re: TMS 13.2 + Provisioning extension is out

Heh - if I went to our Computing Systems & Architecture Manager and told him we need to make changes to the AD structure because TMS can't do certain things, then I would be told to sober up and come back when I have a real problem...

Might still have to go ahead with TMSPE though as it should fix our Mac problem, and if it does that, then that's more important to get fixed than provisioning issues with some users at some remote sites - which I then will have to see if I can get around somehow by other means.

Was so nice and simple - and quick - being able to that by using individual user settings. /sigh

/jens

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

TMS 13.2 + Provisioning extension is out


Thanks Magnus - I would love to see better integration between TMS and the Codian products.  Also, if the TMS messages could appear on the displays rather than the T3 touch panels.  I've had calls timeout because they can't see the warnings, especially if there is content.

Cisco Employee

TMS 13.2 + Provisioning extension is out

Hi Michael

Are you talking about the extend conference? There is a new feature for this in TMS 13.2 which extends the conference automatically until it cannot be extended any longer.

This can at least work around the problem with the conferences timing out.

When you say better integration between TMS and the Codian products it's not very specific could you point at some features your not satisfied with?

Best Regards

Magnus Ohm

Cisco Employee

Re: TMS 13.2 + Provisioning extension is out

That's a feature request you have to raise against the T3 people. All TMS does is to send the notification, TMS does not control where it is displayed.

Regards,

Kjetil

Sent from Cisco Technical Support iPhone App

New Member

TMS 13.2 + Provisioning extension is out

Auto-Extended Feature.
  Im very excited about this new feature as it's could be the fix for no "end conference" notification from the Codian when intergrate with TMS.  Documentation says this can be extended upto 16 15-minute sessions.  Is there a way to just default to only 1 15-minute session?  Thanks

New Member

Re: TMS 13.2 + Provisioning extension is out

How do I determine the SQL Instance Name so that I can continue installing TMSPE?

Cisco Employee

Re: TMS 13.2 + Provisioning extension is out

How do I determine the SQL Instance Name so that I can continue installing TMSPE?

Check the SQL Server Configuration Manager on your database server. Go to "SQL Server Services", and you'll see the instance name next to the "SQL Server" service.

-Kjetil

New Member

Re: TMS 13.2 + Provisioning extension is out

OK, that seems to have worked.

Unfortunately, now it is telling me:

"Unable to establish SQL connection through Java runtime. Check your SQL protocol settings."

Also, how do I set the user privilege db_owner as required in the deployment guide when the SQL database is not on the same box as the TMS application itself?

New Member

Re: TMS 13.2 + Provisioning extension is out

You would most likely require access to your SQL server (but you might not have credentials). If you are pointing your TMS to a SQL cluster, speak to your SQL admin, and set the same permissions on your tmsng database as your tmspe.

New Member

Re: TMS 13.2 + Provisioning extension is out

I don't mean to be rude, but shouldn't the guide assume that the person installing it knows nothing about SQL?

I would suggest that this section of the guide should have a step-by-step guide for how to do this.

I say this because my "SQL Admin" tells me that his SQL server experience is from the 1990s, and you can't always assume that the customer is going to have the expertise to assist with these installation tasks.

With this, as with other Cisco products, the customer expects us to come to the table with a complete, step-by-step set of instructions to deploy these services, and it really doesn't help when we get a somewhat vauge set of guidelines and a basic requirement to get an expert of whatever discipline is needed to deploy the technology.

Having said that, most times the customer does have competent people to assist us from their side, but when they do no, we as the vendor are expected to bring all expertise required to execute on the assigned tasks.

9066
Views
40
Helpful
75
Replies