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...
