topic Re: Cisco Unity 5.0(1) & exchange 2007 in Unified Communications Infrastructure

Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Tue, 19 Mar 2019 03:48:12 GMT

Folks

Do you have documentation and/or any recommendation on how to migrate cisco unity from exchange 2003 to exchange 2007?

Re: Cisco Unity 5.0(1) & exchange 2007

Tommer Catlin — Thu, 17 Apr 2008 17:17:32 GMT

VM only or Unified?

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Thu, 17 Apr 2008 17:20:23 GMT

Both

Re: Cisco Unity 5.0(1) & exchange 2007

Tommer Catlin — Thu, 17 Apr 2008 17:24:38 GMT

Does not make sense. You can only have VM only setup or UM setup.

For UM setup, you will need to upgrade Unity 4.x to 5.x FIRST. Then Migrate the AD users to Exchange 2007. Then re-run permissions and mailbox wizards for 2007.

Same for VM only, but for VM only, you will need a separate server. Exchange 2007 can not be install on a Unity server. Must be on a separate server.

For VM only

Install new Unity 5.x server and Exchange 2007

On old Unity server, upgrade to Unity 5.x

DIRT export

DIRT import to the new setup.

Reconnect your CUCMs, etc.

Make sense?

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Thu, 17 Apr 2008 17:29:48 GMT

That makes totally sense, we have Unity 5.0(1) already, and we are running exchange off box. we only need to migrate from exchange 2003 to 2007 and basically what i need to do i migrate the AD users to Exchange 2007 and then re-run permission wizard and the message store configuration wizard with the options for Exxchange 2007.

for VM only we just need to create a new integration on the UTIM, riht ?

Re: Cisco Unity 5.0(1) & exchange 2007

Tommer Catlin — Thu, 17 Apr 2008 17:33:48 GMT

I guess Im a little fuzzy on your setup.

VM-Only setup with Unity is in it's own domain. So let's say you have Windows 2003 and Unity 4.2 running with Exchange on box. (single box setup) You want to upgrade to Exchange 2007 for the VM Only domain. You will need to do the following:

- Install new Exchange 2007 server in VM-only domain

- Upgrade Unity to 5.x

- Migrate users from Exchange 2003 to Exchange 2007

- Re-run Unity permissions and mailbox wizards.

Re: Cisco Unity 5.0(1) & exchange 2007

bpalmquist — Wed, 25 Jun 2008 18:35:21 GMT

So..for 5.x UM when going from Exch2003 to 2007, all you need to do is run permissions wizard and MsgStore config wizard to point to the new 2007 server? (And move the users, of course).

Any considerations for failover?

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 18:36:15 GMT

what I did for failover, I removed the failover configuration upgraded and then re-integrated again

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 18:38:01 GMT

ah and also, I had to recreate the MAPI

otherwise when you try to retrieve VM you will get a recording stating that the VM server is down

Re: Cisco Unity 5.0(1) & exchange 2007

bpalmquist — Wed, 25 Jun 2008 18:38:12 GMT

The UM is already 5.x, so no upgrade will be needed...and I'm OK with that.

🙂

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 18:39:06 GMT

so whenever you change the partner exchange to 2007, just run the permission wizard and the message store configuration wizard and recreate the MAPI

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 18:44:11 GMT

this link could be useful

http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcuruge050.html#wp1157854

Re: Cisco Unity 5.0(1) & exchange 2007

bpalmquist — Wed, 25 Jun 2008 19:27:09 GMT

Thanks Cris for all your fast replies!

...I will be working from that document, but was wondering if there are any "real world" gotchas out there.

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 19:29:39 GMT

not really.

the only issue that I faced was to recreate the MAPI that is not mentioned on the document.

when you recreate the MAPI you need to logint with the MessageStoreSvc account and you need have a VNC connedtion not an RDP to the unity box

Re: Cisco Unity 5.0(1) & exchange 2007

ranpierce — Wed, 25 Jun 2008 19:31:20 GMT

Of course there are and that is why we should test it in the lab first.

🙂 everyones experience is going to be different cause the site and configs are different too.

rlp

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 19:33:11 GMT

good luck, fortunately you have a lab environment

I don't have one, so I did it on production servers and troubleshoot to solve the issues.

Re: Cisco Unity 5.0(1) & exchange 2007

ranpierce — Wed, 25 Jun 2008 19:38:18 GMT

Chris can I ask what do you mean by recreate the MAPI? What steps? I never had to do this. Running MSCW creates the MAPI.

If Unity is already installed and you are rerunning MSCW for whatever reason. (partering) it should be run from control panel > add remove programs. It will run again not remove.

rlp

Re: Cisco Unity 5.0(1) & exchange 2007

bpalmquist — Wed, 25 Jun 2008 19:41:14 GMT

Yeah..I've the MSCW thing before..it is truly bizarre how they wrote that. But it does stop you from running it by accident!

I was going to ask the same thing about MAPI. Never had to do that.

Re: Cisco Unity 5.0(1) & exchange 2007

ranpierce — Wed, 25 Jun 2008 19:42:33 GMT

Ben there and done that too. I used to work for TAC too so I was helping on the troubleshooting. 🙂

Don't take it the wrong way please.

Randy

Re: Cisco Unity 5.0(1) & exchange 2007

cris_jimenez — Wed, 25 Jun 2008 19:44:26 GMT

Log on to the Cisco Unity server with the help of an account which has Local Administrator privileges. This is required to allow changes to the registry.

Go to the Start menu and choose Settings > Control Panel > Administrative Tools > Services. Look for the AvCsMgr service and note what the "Log On As" value is set to for this service. Specifically, note if it is the Local system or a domain account.

Check which domain account AvCsMgr is active as, and then log off from the current windows session and log back on as the same account in which the AvCsMgr isactive, and continue with Step 4 here. If AvCsMgr is active as the local system account, go back to the start of this document to make sure that have assigned the correct Cisco Unity service accounts to the Cisco Unity services.

Go to the Start menu and choose Run.

Type regedit.exe and click OK.

If AvCsMgr was running as a domain account, go to:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

If AvCsMgr was running as the local system account, go to:

HKEY_USERS\Default \Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

Note: Both places should be checked, as this account may be changed in the history of your system from Local to Domain.

Right-click the Unity System Profile entry and choose Delete.

Restart the Cisco Unity server.