TMS 13.2 + Provisioning extension is out

[Magnus Ohm]

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

[Magnus Ohm]

Hi Michael

I don't know if you are hitting this but it might be worth checking.

From the deplyment guide:

Windows Server

If using the Named Pipes protocol for database connection, the following security updates/hotfixes to Windows Server are required : n

Windows Server 2003: http://support.microsoft.com/kb/958687

n

Windows Server 2008 R2: http://support.microsoft.com/kb/2194664 and http://support.microsoft.com/kb/2194664

Note that the default connection protocol is TCP/IP. If this protocol is used, no hotfixes are required.

/Magnus

[Magnus Ohm]

Was in a webex with Michael and the "Unable to establish SQL connection through Java runtime. Check your SQL protocol settings." error that he was experiencing seems to have resolved after we turned on the SQL browser service. I did not confirm if the SQL server was listening to a custom port but the browser will help resolve that port anyhow and make a successful connection.

So if you see this error / check if the SQL browser is running, if not try to enable the service and try again.

At least this got us past this error.

/Magnus

[Jens Didriksen]

Looks like I'll have to open a TAC case to get TMSPE to work;

installed fine, no problems at all, but it won't talk to the VCS-C properly; getting "connection refused", "error 111" on the TMSPE config page on the VCS-C itself for the services such as users, phonebooks etc.

/jens

[Martin Koch]

I assume you followed:

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

Can I assume correct that you still have not added https support to your TMS?

(think I pointed that out some time ago on an other case :-)

Check out page 26, "Setting up communication between Cisco TMS and Cisco VCS". Could this be what hits you?

If you do not have https=TLS, try "off" instead of TLS and see if you are more lucky afterwards.

If not, provide a screenshot where you see your error, or like you said open a TAC case.

Martin

[Jens Didriksen]

VCS-C is talking to TMS in general, it's just the TMSPE side which doesn't - turning off TLS doesn't make any difference at all.

I've reverted back to TMS Agent, so screenshots below from VCS-C with TMSPE disabled, however, the errors are the ones I get with TMSPE enabled.

[Martin Koch]

You are still pointing to 443 which is https. You need to point it to 80 which is http without encryption.

[Jens Didriksen]

Well, doh!

Never thought about that "little" detail.....

I'll give that a try tomorrow morning as I only have a couple of hours every morning to try test this before the traffic starts. Really wish I didn't have to do this on a live box, but there you go...

If it works with port 80, then I'll at least have something to take back to our firewall/security admin as I was assured there was nothing blocking TLS between VCS-C and TMS server when I checked with him yesterday.

/jens

[Martin Koch]

There is most likely nothing blocking as you get a connection refused, this looks more like you just

do not have https enabled on the IIS of the TMS, ...

I would more recommend that you use your and the security guys time to see that you get https up and running

on the TMS!

[Jens Didriksen]

Mmm, that made me think...the 13.2 install guide states

"At the end of the install/upgrade procedure a message appears stating that HTTPS is not enabled for Cisco TMS, and asks if you would like to enable it." etc etc.

I was never presented with that option, so don't know what happened there, but that's something I'll have to look at.

/jens

[Darren Lapierre]

Did you install on windows 2003 or 2008 r2?

D.

[Jens Didriksen]

Our current production box is 2003, also in process of moving across to a VM, and just installed TMS 13.2 on that which is running 2008 r2, neither of these gives me the option of turning on https at the end of install.

Edit: Hmm, looks like this option is only for 2008, so that would at least explain why I didn't get it in 2003...

Anyways, enabled it on the 2008 r2 VM box since that's where everything will be moved to in the very near future.

Meanwhile, I'll be happy if I can get TMSPE to work on the 2003 box for now - even without https and tls, so I can test to see if TMSPE resolves our outstanding Mac JV issue. Guess I'll find out in the morning.

/jens

[Darren Lapierre]

Jens,

Check your PM.

I did run this through in my lab (TMSPE), but when it came time for my production server, it all went south over the weekend. I did manage to get everything up an going. A lot of what was mentioned, I did go through and was eventually able to resolve (port 80 was one of them when in non-TLS mode, as well as the VCSC wasn’t actively turning on TMSPE, and I had to force it on from the TMS Extension Page on the VCSC).

If you want a second set of eyes to look at it, let me know. I am free for a bit tomorrow.

D.

[Jens Didriksen]

All good now - found an hour where I wouldn't upset too many users...and went through the whole lot again in the peace and quiet of my lounge room with no interruptions - what would I do without VPN and RDP...

So it's now working using http, after initially refusing that connection too, giving me 403.

Turned out it didn't like the user account I was using for authentication, despite this being member of Site Admins, so I'll have to get that one fixed by our AD manager.

I'll be looking at https tomorrow, and there was an issue there as well with the original box having ended up in the wrong zone in the Palo Alto, so TLS was being refused. Been some strange things happening with that box lately, late last week it lost its domain overnight, and nobody have been able to explain how that happened.

Now that TMSPE is working, I found to my delight that I can indeed get most of my "low b/w" users provisioned with lower b/w than the rest, so it's looking up.

/jens

[Jens Didriksen]

I spoke too soon - not getting phone books now all of a sudden...so off I go to TAC...

[Jens Didriksen]

3 hours on Webex with Cisco engineer - and I'm pleased to say TMSPE is now finally working as it should - yay