OK, gang been getting lots of questions on this here and via email Ive included a brief statement from the folks upstairs on this issue below. I know not what everyone was waiting to hear.<br><br>The short story is the support issues for having an Exchange 5.5 based system running in an Exchange 2000 environment proved too complex and error prone to be able to support it cleanly. Further, if a site is already running a native Exchange 2000 environment, we cant add Exchange 5.5 to that setup Since Ex2K no longer has the concept of Organizations/Sites/Servers, the schema is inconsistent with 5.5 and the two cant share information at all. The only way to pull this off is to actually install the Ex2K servers INTO the Exchange 5.5 site such that their schemas matched. Existing sites with Ex2K were not thrilled to hear this and thats understandable.<br><br>Even with the Exchange based limitations accepted, weve been testing a bunch of scenarios in our labs and at a few field test sites and the short story is, shoe-horning in an Exchange 5.5 system into an Exchange 2000 environment is very difficult, error prone and messy. The chances for potentially ugly results (i.e. directory corruption across the boards) is just too high for us to be able to recommend and/or support it in the field.<br><br>Short story: Until Unity 2.5 is released with NATIVE support for Exchange 2000, we wont support Unity installed and interacting with Exchange 2000 servers in any way. I dont have a release date for 2.5 yet. Of course Ill post it here when its known.<br><br>Support will be making no exceptions for this rule, so please don't ask them to do so.<br><br>I know this is going to upset some folks we wanted this to be workable as much as any of you, but its simply not a supportable configuration. <br><br>===============================================<br><br>Marketing Flash - 21 Nov 00 - Exchange 2000 update<br><br>On November 1, we distributed an Exchange 2000 Roadmap that indicated Unity Enterprise with Exchange 5.5 on the Unity server could be installed into an Exchange 2000 environment shortly after Unity Enterprise 2.45 is shipped. This involved a MAL patch that required testing by QA. <br><br>Unfortunately, our testing has revealed this to be very, very complex. Although we investigated limiting E2K support to a few, tightly defined scenarios, due to the technical complexity and extremely high level of support required to make Unity Enterprise 2.45 work in an Exchange 2000 environment, we will not be able to support Unity Enterprise in an Exchange 2000 environment until Unity Enterprise 2.5 releases this summer. <br><br>Unity Enterprise 2.5 will hit the ground running with full native support for Exchange 2000, including support for Exchange 2000 on the Unity server.<br><br><br>Jeff Lindborg<br>Unity Product Architect<br>Active Voice<br>firstname.lastname@example.org<br><A HREF="http://members.home.net/jlindborg" target="_new">http://members.home.net/jlindborg</A>
Thank you for a thorough and technically detailed answered. Even though, it is not what we all wanted to hear, no one can fault honesty and sound technical advice. This type of response is extemely useful in guiding our customers. Thanks Jeff, your efforts are appreciated!
I have implemented two solutions involving Blackberrys and haven't had any problems. There's nothing extra that you have to do for either installation. Blackberry adds its own plug in and doesn't affect Unity's Custom Attributes
Jeff, If we install Unity on an Exchange 5.5 server in an existing Ex 5.5 organisation and that customer is planning to upgrade their Exchange 5.5 system to Exchange 2000 in the future. How much of the upgrade to Ex 2000 can be completed before Unity 2.5 is released ? Chris Vain
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...