Clarification with Unity 3.x and Exchange 5.5

[bbickerstaff]

I have been told by conversations with TAC that Unity 3.x is supported within an Exchange 5.5 Environment, however, it is not recommended. I was told that Unity 3.x does not "Play Well" with a Unity 3.x, Exchange 5.5 and SQL 2000 integration. <br><br>Could I get some clarification on this. I have several customers that are using 2.4.6 and would like to install 3.x to utilize the features within the product. I just would like a little clarification before making recommendations. <br><br>All of our customers who are running 2.4.6 were installed with W2K and not NT4.<br><br>

[#2]

Not sure where you're hearing this but it's not correct. Unity 3.0 works fine with Exchange 5.5.

There may be some confusion about folks wanting to MIX Unity 2.4.x and Unity 3.x and use networking features across them (this wont work) or having some users on Exchange 2000 and some users on Exchange 5.5 with Unity in the mix (it's really a good idea to get Unity on Ex2K in this situation). But if a customer is running Exchange 5.5 and they wan to use Unity 3.0, there should be no problem at all with that.

Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

[bbickerstaff]

Is their any issues with running the version of SQL 2000 with Unity 3.x and Exchange 5.5. Just wondering.

Thanks

[Anil Verma]

No, there are no issues there.
Infact all Unity systems that are over 16 ports are running with SQL 2K, whether they are Exchange 5.5 or Exchange 2K.

Anil Verma
Cisco Systems
anilve@cisco.com

[bbickerstaff]

Thanks