[cisco-voip] Exchange 2003 & 2007 co existing in Unified Messaging

Maybelyn Plecic maybelynplecic at gmail.com
Sat Oct 16 18:48:53 EDT 2010


Similar situation, except we are not able to partner with 2007 with the
primary Unity server.   We have a failover Unity 5.0.1 cluster.   Even after
the permissions wizard was ran and MSCW was completed and the mailboxes were
created in the Ex 2007 server, we also were not able to receive the messages
via e-mail nor access to the TUI.

Can somebody confirm that the only way to co-exist is to point to the Ex2003
first and then Ex2003 relays to Ex2007 the voice mail messages with
mailboxes in Ex 2003 only? or can we do the following partner to Ex 2007 and
relay back to Ex 2003 with mailboxes in Ex 2003 and not Ex 2007?

Any assistance is appreciated.  Thank you.

Best Regards,
Maybelyn

On Fri, Jul 30, 2010 at 10:14 AM, Nick <csvoip at googlemail.com> wrote:

> Thanks Guys
>
> We had to run the permissions wizard, which got the messages into the
> Inboxes but could we could not pick them up from the phones and had to force
> Unity to sync using the Message Store Configuration wizard. All the migrated
> users are now working fine and we will re run the Message Store
> Configuration wizard once all users have been migrated to change the partner
> server to Ex 2007.
>
>
>
> On 30 July 2010 12:54, Ed Leatherman <ealeatherman at gmail.com> wrote:
>
>> We are performing this same thing and it's working exactly as James
>> stated below. Once we get all the mailboxes migrated over, we plan on
>> running the MSCW and setting up Unity to partner with one of the 2007
>> servers.
>>
>> Unity 7
>>
>>
>> Ed
>>
>> On Fri, Jul 30, 2010 at 7:36 AM, James Buchanan <jbuchanan at ctiusa.com>
>> wrote:
>> > I believe when running mixed like that you must have the 2003 server as
>> the
>> > partner server. On the back end, the two servers will communicate with
>> each
>> > other and messages will continue to be delivered without issue.
>> >
>> >
>> >
>> > When you’re ready to retire the 2003 server, you’ll need to run the
>> MSCW.
>> >
>> >
>> >
>> > James Buchanan | Senior Network Engineer | South Region | Presidio
>> Networked
>> > Solutions
>> > 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com
>> > D: 615-866-5729 | F: 615-866-5781 | www.presidio.com
>> > <http://www.presidio.com>
>> >
>> > CCIE #25863, Voice
>> >
>> >
>> >
>> > From: cisco-voip-bounces at puck.nether.net
>> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nick
>> > Sent: Friday, July 30, 2010 5:08 AM
>> > To: cisco-voip at puck.nether.net
>> > Subject: [cisco-voip] Exchange 2003 & 2007 co existing in Unified
>> Messaging
>> >
>> >
>> >
>> > Hi All
>> >
>> >
>> >
>> > I have a customer who is running Unity 5 with Exchange 2003 Unified
>> > messaging, they have built a new separate exchange 2007 cluster and
>> > co-existed it within the same organisation as the Ex 2003 and they are
>> > hoping to migrate users in a staged fashion.
>> >
>> >
>> >
>> > Is it going to be possible to add another message store to Unity and
>> have
>> > users on both clusters or will they have to migrate all of the users in
>> one
>> > go and then re run the Message Store Wizard to change the Partner server
>> to
>> > 2007.
>> >
>> >
>> >
>> > Just wondering what the best options are to tell this customer as they
>> have
>> > already migrated some users without thinking about the Unity
>> implications.
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > cisco-voip mailing list
>> > cisco-voip at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/cisco-voip
>> >
>> >
>>
>>
>>
>> --
>> Ed Leatherman
>>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101016/d8fac458/attachment.html>


More information about the cisco-voip mailing list