same here. Additionally I´m interested in how the new Exchange extension will connect to Exchange, as we are not allowed to install anything on Exchange Server.
The next version the TMS Exchange integration software (TMSXE 3.0) is currently scheduled to be released sometime in January 2012. This is an approximation dependent on QA testing which is ongoing currently. When it is released it will be installed on a separate Windows 2008 server OS and can be configured to communicate to the Exchange server via Http or Https and will utilized the EWS technology in Exchange 2007 and 2010.
We are very limited in what information can be provided at this time as some additional features may be added or taken away depending on QA testing and the approaching deadline.
When the product is release it will be very important that you read all of the documentation as there will be some significant changes to deploying the new application.
Please feel free to contact me with any additional questions.
No it does not
Phone: (703) 707-1033
Cisco Systems, Inc.
1860 Michael Faraday Drive
Reston, VA. 20190
Cisco.com <> >
Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Cisco Systems, Inc.
Registration Address: 170 West Tasman Drive,
San Jose, CA 95134
Place of Registration: California, USA
For corporate legal information go to:
Those details will be in the install documenation when it's released, but it definitely won't be installed to the Exchange server as the former product was, aka TMSXE 2.3 and earler
Does anyone know whether this product will be backward compatible with other versions of Exchange (namely 2003/2007) or will it just support 2010 via EWS?. I need to make a decision on whether forge ahead with version 2.3.1 or wait for 3.0 now and no documentation is available - or PDI assistance from Cisco. I can ask the our local reps but if anyone knows the answer it would be appreciated.
TMSXE 3.0 will support (with no guarantees due to possible last minute changes):
Exchange 2010 SP1
Exchange 2007 SP3
2003 Is not supported, this was not supported in TMSXE 2.3.1 either.
Clients will be Outlook 2007 SP2, 2010
TMSXE needs to be installed on windows server 2k8 or 2k8 R2.
Hope this helps.
Thanks for the reply Magnus - most helpful. I have been told the FCS date is Feb 17th...is this still accurate?
In reference to E2K3 support under TMSXE 2.3 ...are you sure this is not supported? The Installation guide (dated June 2011) on page 5 mentions E2K3 support with SP2.
Sorry about that, of course you are right, I was messing up with the outlook client support. Regarding the date I´m not sure, but it´s coming soon.
Any update on TMSXE 3.0. When is it being launched. I am looking to integrate Exchange 2010 with TMS 13.1.2. Also another question is it must that the user has be present in TMS to book the meeting when booking thought OUTLOOK. What kind of permissioning is reqired at a user lever in exchange to enable user to book the meetings.
User account do not have to exist in TMS in order for them to be able to schedule meetings through Outlook. The first time that a user schedules a resource that is integrated with TMS and Exchange a user account will be created for the user in TMS and the user will be added to the default user groups that are configured in TMS.
As far as being able to schedule meetings in Exchange this depends on how the resource accounts are configured from a security perspective. This would be different in some environments depending on their security model. But in most cases all users have the ablility to schedule resources within Exchange.
Thank you for your reply Tim. This is great. Just another question.
you mentioned that a user account will be created in TMS. Is this the user account of the organizer. If that is the case, what if that already exists in TMS.
I have approx 15000 user world wide in different AD forests. They all have ability to schedule resources with in exchange. TMS is only pointed to the single AD and approx 2000 user are synced with AD using LDAP rest of them are in different AD forests with TRUST.
Please let me know.
The user account of the organizer. For example I login to my PC with my domain account timwalk. I then open my Outlook client and schedule a meeting. In TMS a user account cisco\timwalk will be created.
Cisco TMSXE 3.0 is right around he corner -- we hope to release next week.
Permissions on a user level in Exchange: As long as a user is allowed by the Exchange booking policies to book the resource representing the TelePresence system, TMSXE/TMS will accept he booking. Throwing TMSXE into the mix won't change anything permissions wise.
Thank you for your reply. Is it possible for one of you to call me. i have some more questions i want to clarrify. I assure you it will be no more then 5 min call.
Thanks for the links to the forms. I found in the release notes the following statement "Previous versions of Cisco TMSXE were installed on the Exchange server itself. Cisco TMSXE 3.0 must be installed on a separate server".
When it says "separate server", does it mean its own server? Bluntly put, do you know if I can use the TMS server to install TMSXE 3.0? I found nothing in the docs (so far) that says it can or cannot be installed on the TMS server.
When we say "separate server", we basically mean "not the Exchange server".
We generally recommend installing TMSXE 3 on its own, separate Windows server, but sure, you can install it on TMS's Windows server if you want to.
Thanks a million! For us a separate server is not available and wouldn't be for some weeks to come. The deployment is all but ready and the delay for the separate server would not be a good thing!! So thanks again for the info ('recommend its own server but can be put on the TMS server')
Just to be clear. Cisco's Best Practice recommendation is what for the TMSXE?
1. TMSXE and TMS 13.1.2 on the same server
2. TMSXE on a separate server and TMS on a separate server
What I am hearing from Timothy is that as some point they may have a separate server and if so, then they will want to move the TMSXE to another server.
I think that our best practice configuration for the TMSXE is for it to be installed on a separate server from the TMS server.
We recommend scenario 2: separate servers for TMSXE and TMS.
If one ever needs to move TMSXE from one Windows server to another, just uninstall it on the first, and then do a fresh install using the same connection settings.
Sent from Cisco Technical Support iPad App
I have a question about High Availability options. We were going to install twi TMS servers behind a load balancer and external SQL databse on our existing SQL cluster. How can we make TMSXE work with this solution? Is there any better HA solution?