Does anyone have any experience of CTM 1.7.0 & Exchange 2007 SP1 CCR.
We are currently running our TP mailboxes on Exchange 2003. There is a requirement to migrate from 2003 to 2007. For added confusion we hit some issues upgrading to 2007 last year when we were running CTM 1.5. The issues I believe were due to Clustering of Exchange 2007. We are now running CTM 1.7.0 & CUCM 8.0
Does anyone know if I will be OK to run CTM 1.7.0 & CUCM 8.0 with Exchange 2007 SP1 CCR?
Cisco AS have a Pre-Qualification Tool, I am also investigating how to test prior to any Exchange migration.
You will need Exchange 2007 SP2 (supported versions are listed in the document above).
If you migrate the mailboxes to Exchange 2007, you have the option to connect using WebDAV or EWS; if you decide to go with EWS, I would consider upgrading CTS-Manager first as NTLM v2 support is only available from 1.7.2 on and 1.7.4 has some important bug fixes when using EWS.
Also keep in mind that when you would change CTS-Man to EWS, you cannot revert back to WebDAV without re-installing the server and that if you plan to migrate to Exchange 2010 in the future that WebDAV is not available anymore on Exchange 2010.
The prequalification tool can definitely help with making sure CTM can connect to Exchange and LDAP, sync and subscribe rooms, etc. I would strongly advise making use of it; it is readily available for download on CCO under the specific CTM version you a) plan on upgrading to and/or b) that is currently installed, if using the prequalification tool for troubleshooting purposes.
Just to clarify: NTLM v2 support can be found in CTM 1.6.3 and higher; we only started supporting NTLM v2 with session security extensions/options as found in Windows 2008 Local/Domain Security policies in CTM 1.7.2 and higher.
Additionally, Exchange 2007 SP1 has a known issue with not "stamping" the correct properties onto recurring meeting exceptions (a very simple explanation), leading to potential issues with CTS-Manager meeting booking behavior. This issue is corrected in Exchange 2007 SP2, hence why it is required.
If you do decide to move to EWS, you need to be at CTM 1.7.4 or higher specifically to avoid known bugs in CTM meeting booking behavior relating to recurring meetings/recurring meeting exceptions. Also, CTM 1.7.0/1 using EWS has issues with duplicate meetings being created for certain modified recurring instances, so it would be wise to move to CTM 1.7.4 with Exchange 2007 SP2 to avoid these potential issues. If you stay with WebDAV, you shouldn't see these issues - they only occur with an EWS integration on CTS-Manager.
Thanks and HTH. It can definitely be tricky to navigate, as you stated.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...