Tms

[Andrew_B]

Can TMS or Tandberg Scheduler be installed on a server and then accessed by clients not part of the same domain, over the Internet?

[Sean Lessman]

Can TMS or Tandberg Scheduler be installed on a server and then accessed by clients not part of the same domain, over the Internet?
Yes, just set up local accounts on the machine.

Sean

[Andrew_B]

Ok. I got it to work. But I have another question. TMS/IIS uses NTLM as it's default authentication (or so I believe). The problem is the TMS server needs to be installed on the other side of our proxy server. Our proxy server doesn't allow NTLM authentication.

Is there any way to change the authentication to clear text? I'm not worried about the security issues too much. I tried to set the authentication in IIS to basic, but TMS seemed to stop working.



Andrew

[Sean Lessman]

Ok. I got it to work. But I have another question. TMS/IIS uses NTLM as it's default authentication (or so I believe). The problem is the TMS server needs to be installed on the other side of our proxy server. Our proxy server doesn't allow NTLM authentication.

Is there any way to change the authentication to clear text? I'm not worried about the security issues too much. I tried to set the authentication in IIS to basic, but TMS seemed to stop working.



Andrew
Hi Andrew,

Basic authentication should work fine, just make sure you have the TMS directory set for basic.

Sean

[Andrew_B]

Just the TMS directory? There are a bunch of other directories with Integrated Windows Auteh check off.


Andrew

[Andrew_B]

What happens if the systems that I have configured in TMS use dynamic IPs and they change? Before TMS it worked just fine because we used a gatekeeper. If I get the Tandberg gatekeeper does it integrate with TMS?

[Morgan81]

We use dynamic IP's too and it's a pain in the butt. TMS sorts data by IP so if that changes, you have to reload the entire unit into TMS and you lose all of your history of that unit. Not fun, especially when your DHCP server fails and EVERYTHING gets a new address. I'm pretty sure it doesn't matter if you have a gatekeeper or not, even if it's a Tandberg.

[Andrew_B]

I talked to a guy from Tandberg (sales rep), he said that it should be ok with a gatekeeper. I responded asking if it needed to be Tandberg. He also said there was some way of doing it with DNS. He didn't go into any detail about it.

[Sean Lessman]

What happens if the systems that I have configured in TMS use dynamic IPs and they change? Before TMS it worked just fine because we used a gatekeeper. If I get the Tandberg gatekeeper does it integrate with TMS?
There are some improvements to mobility and device tracking to the next dot release of TMS that should address your needs, hopefully :) . Please give feedback when you get it, it helps us to improve the product.

TMS does manage the TANDBERG Gatekeeper.

Sean

[Sean Lessman]

Just the TMS directory? There are a bunch of other directories with Integrated Windows Auteh check off.


Andrew
If you make the change for the main directory and the ones below it, should work. We have basic running in the lab and integrated running in the corporate TMS.

Sean

[Andrew_B]

So as of right now TMS can manage the Tandberg gatekeeper. But it can't use the gatekeeper to do a E.164 -> IP translation in order to do configuration changes.

When would this new version be released? I heard there is 9.5 coming out next week. Is that the version you talk of?


Andrew

[Andrew_B]

TMS v9 run on W2k, W2K server, and Win XP. I assume it'll run on 2003 server.

What would you recommend in a ~20 endpoint environment?

[Morgan81]

Depends on what those endpoints are.
If it's all Tandberg, you should probably go for it.
If you have a few Polycoms you might want to test it out. The evaluation is free to download but you can only put three systems in. This will tell you what you need to know though.

[Andrew_B]

I have all tandberg equipment (endpoint, mcus, TMS) but not the gatekeeper. I tried switching IPs and it didn't work.

[Andrew_B]

I installed TMS 9.6 on a different machine. I didn't have to change it to Basic authentication, it was already done. But when I went to Monitoring, java asked me for a password and it didn't work (proxy issue with NTLM). So I changed it so all the directories under TMS were set to basic auth and I got locked out....help.



Andrew

[trapehzoid]

don't change things manually.. you'll screw it up and not know how to go back :)

When you get prompted for a password at monitoring.. simply enter the same login stuff you logged into TMS with. Don't forget machine name if using local accounts

[Andrew_B]

The thing is, I need to change something to basic authentication. Our proxy won't allow for NTLM authentication. For 9.2 I got it to work. 9.6 got me locked out.

[trapehzoid]

just use IIS manager and look at the properties of the directories/files.