TMS/TMSXE messing up Exchange synchronization - especially for recurrent meetings
TMS version: 14.4
TMSXE Version: 4.0
Exchange 2010 SP2
Note that we had the same issues in previous versions.
Since we put the TMS-Exchange synchronization in place we the TMSXE. We keep on facing multiple issues.
One of them is that TMS/TMSXE often completely messes-up the scheduling. Especially for meetings scheduled as recurrent meetings in Exchange.
Frequently the TMS will cancel some occurrence of the meeting in Exchange for apparently no reason (without the user making change to his/her booking) while keeping the meeting in the TMS schedule.
The last one we experienced was a user who canceled the 4 next meetings of his recurrent meetings and change the time of all the others. Exchange validated all the changes. First the TMS kept in its schedule 2 of the 4 meetings cancelled and then it cancelled in Exchange the meetings which schedule was changed. For those booking, the users received a meeting cancellation email saying "ERROR: The videoconference resource could not be booked in Cisco TMS. The system is not available for booking at the requested time". While the rooms are available in Exchange and the ressources on the multipoint bridge are not used. On top of that the meetings that the TMS cancelled in Exchange are still inside the TMS schedule...
I have the same issue but not sure if it is the synchronization that is causing it. I know that you cant change a meeting in the past to the future, you have to create a new meeting. But we have cases where users will just get a random decline with the error "cant book meeting that is in the past" The user did not do any new meeting or changed any meeting.
it is as if the meeting is getting sent to the TMS again without user interaction. Meetings getting re-submitted automatically but have already past.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...