We're planning a UCM deployment using CUWL licensing. It's my understanding that we could deploy Unity or Unity Connections.
We have 650 users, so I think either would work. Also, we don't need exchange integration -- we'll use IMAP to access our voicemail through Outlook.
So are there any other factors to help guide our selection of Unity vs Unity Connections?
As Steve nicely suggested (+5 Steve :) it sounds like UC would be an excellent fit here. The feature sets are getting closer and closer with Unity and UC. This doc nicely encapsulates some of the differences. UC is not integrated with Exchange but can currently support up to 7,500 users (and this number is increasing - see below) Also, UC 7.0 supports Active-Active redundancy which was a stumbling block for many enterprise type deployments that require full redundancy. Another rather large difference is that Unity is a Windows based model and UC is a Linux based appliance like the newer 5.x, 6.x and 7.x Communication manager versions.
Unified Communications Applications: Unity Connection 7.0 EFT Opportunity
The differences are nicley encapsulated in these docs;
Cisco Unity Connection - with Video
Cisco Messaging Products: Feature Comparison
There is also a doc (attached) called "Selling Cisco Unified Communications Express". It gives a feature comparison between CUE, Unity and Unity Connection.
Hope this helps!
PS: We just placed our order for UC 7.0 after testing in the lab for a fair bit :)
If you're just going to use IMAP, Unity Connection would most likely be the way to go. Typically Unity is used in situations where the customer requires full unified messaging, or a legacy integration that needs the Dialogic card support that Unity provides. I do have some customers that have a Unity system in place currently, and are planning on moving over to Unity Connection. Hope this helps,