Unity & Exchange 2007

I need to know what versions of Unity will support Exchange 2007? Currently we are running Unity 4.04SR1 in conjuction with Call Manager 4.0(2A)SR2B...

Currently Unity is not supported with Exchange 2007. As Exchange 2007 isnt even out in full, there isnt an exact release date on the Unity integration. Probably next year some time.

Similar Messages

Unity 5 with MS Exchange 2007 and Windows Server 2003 Ent w/ SP2

Hello,
We have Unity 5 with Exchange 2007 SP1 on Windows 2003 SP1 Enterprise server. We want to upgrade Exchange to SP2 or SP3 but I could not find enough information, may not have looked in right places.
Does anyone have Unity with Exchange 2007 with SP2 or SP3? has anyone experienced issues with such upgrade?
Thanks,
Paresh.

Paresh,
Here's what you need:
Recommended Service Packs—Message Store
Revised October 25, 2010
•Exchange 2010 Service Pack 1
•Exchange 2007 Service Pack 3
For support information, refer to the "Support Policy for Microsoft Service Packs and Updates" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
I pulled this straight from a Cisco document so you could be sure that you are moving to the latest recommended SP for Exchange which is SP3. I have clients running this SP without issue.
Hailey
Please rate helpful posts!

Unity Connection 8.5.1ES16.11900-16 upgrade for Single Inbox with Exchange 2007 ?

Hello friends,
I'm currentely running Unity Connection 8.5.1ES16.11900-16.
I would like to use the single inbox feature with Exchange 2007.
It is in the documentation that we need at least Unity Connection 8.5(1) Service Update 1 (UCSInstall_UCOS_8.5.1.11900-21.sgn.iso).
I downloaded, checked MD5 but when searching on the FTP directory it won't accept it (No valid upgrade options were found). Is this a supported upgrade?
Same happens with the localization file in Portuguese that i need to install: uc-locale-pt_PT-8.5.1.1-16.cop.sng ...
Please can you give me some hints about what I may be doing wrong?
Thank you very much and warm regards,
met

Hi Met,
Hope all is well
I think you are hitting this caveat. Although the numbers don't match exactly I'm
pretty sure you will need to wait for an 8.5.1.12xxx.x ES
If the Connection server is running an engineering special with a full Cisco Unified Communications
Operating System version number between 8.5.1.11001-x and 8.5.1.11899-x, do not upgrade the server
to Connection 8.5(1) SU 1 because the upgrade will fail. Instead, upgrade the server with an ES released
after 8.5(1) SU 1 that has a full Unified Communications OS version number of 8.5.1.12xxx.x or later
to get the SU 1 functionality.
http://www.cisco.com/web/software/282074295/44508/851su1cucrm.pdf
Cheers!
Rob

Unity Connection 8.5 and Exchange 2007 UM

Hi everyone--has anyone configured Unity Connection 8.5 with Exchange 2007 for Unified Messaging yet? I'm having some odd issues...now every message gets a delayed delivery receipt (regular email messages). When i followed the guide from Cisco, it didn't work...reported a 503 error when i ran the test from a user's account...
Can anyone provide guidance? I've only done it under Exchange 2010 (with little to no issues...).
SJ

I did. Initially it was only Exchange 2010, however in SU2, Exchange 2007/2003 support was activated. It is currently working flawlessly. Just make sure to apply SU2 or upgrade to 8.6 (a little extreme, but to each, their own…). SU2 works well though.
SJ

Intergrating Unity 7.0 with Exchange 2007

I have a customer that is currently on Unity 7.0 and Exchange 2003. They are building a new 2007 Server and want to intergrate it with Unity 7.0. Does anyone have any documentation or videos on how to do the migration?

Hello Dushaune,
Basically integrating means that you are going to change Message Store also known as the partner server (Exchange 2k3) to the new partner with Exchange 2k7. For this there are several steps:
-OAB and Extending AD schema
- PW (Permission Wizard)
- MSCW (Message Store Configuration Wizard)
You need to follow this mandatory steps on the guide:
Configuring Exchange 2007 for Cisco Unity & Extending the Active Directory Schema for Cisco Unity
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/installation/guide/umexnofo/5xcuigumenofo060.html#wp1942680
***Even though on the title you see unity 5.x this is still applicable for Unity 7.x, on the documentation guide you will read:
Note
The following link goes to a Release 5.x version of the guide; all 5.x content applies to version 7.x as well.
On the Exchange side make sure you meet the following system requirements:
Minimum Service Packs Required—Message Store
•Exchange 2007 Service Pack 1 Update Rollup 4:
–On Exchange 2007 servers that are running Windows Server 2008. Without the update rollup, message waiting indicators will not function properly. See Microsoft KB article 952580.
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/7xcusysreq.html#wp472166
As a side note but still related, i'm not sure what outlook version you have so make sure it is on the compatibility matrix:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.html#wp364674
As for the PW (Permission Wizard) it grants permissions for the Unity Service Accounts (Unity Install, Unity Directory Services and Unity Message Store) and to run it you need to be a domain admin. This tool is found on Tools Depot> Administration Tools> Permission Wizard. Make sure it is the latest and greatest version (3.0.0.7) For a more detailed understanding with screenshots go to:
Granting Permissions with Cisco Unity 5.0(1)+ Permissions Wizard
http://www.ciscounitytools.com/Applications/Unity/PermissionsWizard/Unity50/Help/PWHelp_ENU.htm
After you run the PW (Permission Wizard) you will get a pop-up window advising what permissions to apply depending on the Exchange version you choose, in this case:
Version of Exchange in Which Mailboxes Are Homed: Exchange 2007 only
Active Directory Account: Cisco Unity installation and Cisco Unity directory services
Permissions to Grant to previous AD (Active Directory) accounts:
Delegate Exchange Organization Administrator administrative control
Delegate Exchange Organization Administrator admininistrative control
The MSCW (Message Store Configuration Wizard) will define the actual partner. Here is a link with a short description:
https://supportforums.cisco.com/docs/DOC-23513
This tool is found on Control Panel> Add Remove Programs> Cisco Unity Message Store Configuration Wizard> Click on Change/Remove to execute it, below are the screenshots guiding through the tool. **The only screenshot missing is where you see a pencil writting a book, this means it's synchronizing, just let it finish.**
In this case my installation account was unityinstall, however sometimes people name then just Unity, or company_unityinstall and so on so chooose the applicable. For the admin account you could use unityadmi, i decided to use unityinstall:
In the screenshot i only have a 2010 Exchange, however this will reflect all Exchange versions in your deployment (2k3 and 2k7) chooose the applicable, also this will require to stop Unity, so no auto attendant and no voicemail during this time:
On this last part pay attention where it says Directory Service account:
Best Regards,
+|>@|/1D+

Installing Unity 7 with Exchange 2007

I need to install Unity 7 with Exchange 2007
The DVDs that I have received from Cisco contains Unity 2003 Message store.
How I can Install Unity 7 with Exchange 2007 and I have 2003 on Unity server.
Any body can advise me?
and is there any documnet contains the requirements for installation( what I should do on Exchange server)

Here are the questions I need you to answer:
1) If you plan on integrating with Exchange 2007, my assumption is that you are planning on a Unified Messaging deployment and you will be integrating with your CORPORATE (i.e., existing) Active Directory and Exchange 2007 environment. Is that correct? If not, and you are installing a standalone Unity messaging environment then my advice is to use Exchange 2003 as this will provide better ease of use in a standalone environment for you (I'll get to this point in more detail as I answer your questions).
2) Do you need to configure OAB for Outlook 2003 and Earlier Clients even if all of your users have Outlook 2007? Yes. I believe the actual setting in E2K7 may not read exactly as it is written here but the premise is the same which is why the statement "regardless of which versions of Outlook you are using" is included in the installation notes.
3) What is the difference between Unity with Exchange 2003 vs. Exchange 2007?
- With Exchange 2007, Unity cannot create mailboxes directly in Exchange due to permission restrictions. All users and mailboxes must exist before you create a Unity subscriber. Going back to #1, if you are doing a standalone environment then Exchange 2003 integration is easier from an adminstration perspective. Unity can create AD users and mailboxes for you with Exchange 2003 but not with Exchange 2007.
- Expanding on your second question, even with Exchange 2007 the Exchange 2003 System Manager is installed on the Cisco Unity server because it includes the Microsoft messaging API (MAPI) that Unity uses to communicate with Exchange for addressing, sending, and retrieving messages. When using Exchange 2007 as the partner Exchange server for Cisco Unity, offline address books for “Outlook 2003 and earlier clients” should be configured regardless of which version of Outlook is being used or Cisco Unity will not function properly.
- If you are running a mixed environment of 2003 and 2007 Exchange servers, the Unity partner server must be an Exchange 2007 server.
- When you install Unity with Exchange 2007, you must run a script on the Exchange 2007 server during the installation. This is a Power Shell script that creates the primary system accounts (3 of them) that Unity needs to operate because again, it cannot create mailboxes in an integration with Exchange 2007.
That's all the primary points.
Hailey
Please rate helpful posts!

Exchange 2007 and 2010 with Unity Connection 8.6

Hi all,
We have unity connection 8.6 and exchange 2007 currently in place and runnign fine. I am ready to start migrating mailboxes over to our new exchange 2010 farm and as such we will be in co-exsistance with exchange 2007 and 2010 for awhile. What are the steps or procdures to also include exchange 2010 with the 2007 in unity connections? Currently under Smart Host is the IP address of our exchange 2007 server.
Thank you.

Hi,
This depends on how you plan on performing the migration. I would suggest the following:
-Creating a new unified messaging service for Exch 2010. You can re-use the same service account name as long as you completed the configuration steps for that integration.
-As you move over user's mailboxes from 2007 to 2010, you can delete the 2007 UM service and add the new 2010 UM service. If you want to change many users at a time you'll need to use bulk administration to change them. If you use BAT to change accounts, see the link below where I have listed them out for another CSC user.
-You can change the Smart Host setting once you have configured the Exch 2010 enviornment to handle your main corporate mail (changing the MX records to point to a 2010 Edge Transport).
Changing the UM service with BAT:
https://supportforums.cisco.com/message/3572200#3572200
Good luck.

Getting UConn 8.5 to work with both Exchange 2007 and 2010

According to the document below, I should be able to set up one Unified Messaging service to access mailboxes on both Exchange 2010 and Exchange 2007 servers. I setup my service to point to 2010 CAS servers and I can access 2010 mailboxes, but testing 2007 mailboxes comes up with an http 200 error. If I setup the CAS server as 2007, I can access 2007 mailboxes, but get an error on 2010 mailboxes. This will be a real pain if I can't do this with one service. I don't want to have to keep Unity Connection updated as users get moved from 2007 to 2010! Anyoe know how to do this?
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html#wp1198171

I got this to work! My Unified Messaging Service was originally setup to Specify an Exchange Server. That is where I had put the DNS name of the CAS server (and that DNS entry pointed to several CAS servers). I changed the Service to Search for Exchange Servers instead and used that same DNS name in the Active Directory DNS Domain Name. When I do the test of this service, it tells me it Failed to locate a Domain Controller via DNS, but that is just informational. It also says it successfully connected to the Exchange CAS server with the autodiscover.xml. Now my mailboxes on both Exchange 2007 and 2010 are able to receive voicemail messages with this one Service configured.

Exchange 2007 Compatibility?

We are running Unity 4.1 and are looking to run Exchange 2007. Everything I can find says that Unity 5.0 is the only supported configuration? Is this true? When will Unity 5.0 be available? Is there a temporary fix to help transition over in the mean time.

Yes Exchange 2007 is ONLY supported with unity 5.0.
Check Link
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheet0900aecd805e6e12.html
I would not recommend running exchange 2007 on a production unity (4.x).It might work but again you taking the risk for running unsupported software(plus exchange 2007 is quite new which might be buggy also)
I guess you can contact Cisco Representative for unity 5.0 availability or contact your cisco presales.
As far as I know there is no temporary fix ...I hope it doesn't ruin your day

Moving mailboxes in Exchange 2007

Does anyone know what is the effects of moveing VoIP-enabled mailboxes to another Exchange 2007 servers?

The key text from the link I cited in my initial response:
Moving Subscriber Mailboxes for Cisco Unity 8.x
From time to time you may need to move subscriber mailboxes to another server that is faster or has more disk space available, or you may want to move mailboxes when you add new servers to your network. It is possible to move subscribers between servers without having to shut down Cisco Unity.
Caution If you are moving a group of subscriber mailboxes at once, confirm that you do not inadvertently select the Unity Messaging System, UAmis, UVPIM, UOmni, or USbms Exchange mailboxes. To move these special mailboxes, see the "Moving the Unity Messaging System, UAmis, UVPIM, UOmni, and USbms Exchange Mailboxes for Cisco Unity 8.x" section.
To move Exchange mailboxes from one server to another, follow the instructions in the Microsoft Exchange documentation. "

Migrating to Unified communications exchange 2007

we are currently using unity 5.0 and it is in its own active directory domain and forest as well as the exchange 2003..we want to move to exchange 2007 unified communications and this is in a different domain/forest as well...what would be the proper steps to migrate over in a situation like this from untiy 5.0 in one seperate forest than exchange 2007 thats in another forest?

Hi,
This is really more of an MS question.
But I take it you are using Unity VM only for exchange? If it is a separate AD then the only info in that AD is used for Unity so you dont really need to keep any of it.
If it's in a separate AD then why not just configure your exchange 2007 for UM in parallel.
In CallManager you can configure a separate voicemail profile for Exch UM and assign it to certain users.
Have you piloted this yet? There are some limitations with UM for Exch 2007.
You can export subscriber information from SQL database on unity, and use it with powershell script for exch 2007 to actually get the users across.
I'd say when people move, they are going to have to re-record greetings, and lose their old voicemail etc.
Cheers,
Tim

Cannot send email from Exchange 2007 to Exchange 2013

Hello Anyone,
Anyone can help? I've prepare MS Exchange 2013 already, for Migration MS Exchange 2007 and I got the issue.
My issue is I can't send email from Exchange 2007 to Exchagen 2013, but for Exchange 2013 can send email to Exchange 2007,
is my issue only internal email for external email both Exchange server is working fine.
Regards,
Eakkasak

Thanks for your reply, when I send email from Exchange 2007 to Exchange 2013 I'm get the error message below.
Delivery is delayed to these recipients or distribution lists:
Eakkasak Buajan
Subject:
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 8/29/2014 8:30:29 PM (GMT+07:00) Bangkok, Hanoi, Jakarta. Microsoft Exchange will notify you if the message can't be delivered by that time."
I'm already tick "Exchange server Authentication" in the Default Receive connector properties of Exchange 2013"
I'm restart services and restart all Exchange Server but doesn't work.
Thanks,
Eakkasak
Sent by Microsoft Exchange Server 2007

Cannot send email from Exchange 2007 to Exchange 2013 - Coexistence

Existing Exchange 2007 SP3 1 MBX, 2 CAS/HT, 2 ET servers.
I have added an Exchange 2013 server with MBX/CAS role.
Email will flow from Ex2013 server no problem. Mail from Ex2007 systems cannot deliver to Ex2013 boxes, it dies in queue with a 4.4.7 expired message after issuing a delay message.
I can telnet to ports 25, 587,717,465,475, and 2525 from Ex2007 HT role to new Exchange 2013 server. I can send email from Ex2007 HT role server to new Exchange 2013 server using telnet to port 25.
A ‘get-mailbox’ from the Ex2007 HT role server returns the server and database properly on the test users on Exchange 2013 server.
The only strange thing I am seeing is from the Ex2007 systems, a ‘get-exchange server’ command shows the new Ex2013 server as role ‘16439’ which looks to perhaps be normal.
Why is email not flowing to the new users on Exchange 2013?

You should have exchange server authentication ticked in Default Receive connector in Exchange2007.
Exchange 2007 and Exchange 2013 in the same subnet/network. if not please check any spam agent running between the networks. Are you running antispam on Exchange2013 ?
MAS

Uppgrading Exchange 2007 from sp1 to sp3 on small business server 2008 sp1

Hello everyone
I know this topic has been discused many time in this froum. but i have to ask it again in my exact situation.
I have a realy unstable and unsafe server which i am planing to migrate all the apps and services to some virtual servers soon.
first migrating is Exchange. i have Exchange 2007 sp1 on my server sbs 2008. i have my DC,AD, dns, DHCP, File, etc on the same server as well . So that is way it is scary for me (as i am not really experienced) to even upgrade one service pack.
Now, i want to know if anyone did it before. What should i expect during upgrading or after that? so i can be ready for that?
which kind of backup can save me if somethings happens to my Exchange? is there any way to install the new Exchange 2007 and sp3 rollup 10 and then migrate all databases and mailboxes to that new server? if yes, how to do that?
Thanks
Nima

Hi Nima,
Ok, I know your concern. Please make sure you have read the above KB I provided before installing SP3 for Exchange 2007. What's more, you need to make sure you right mouse click and run as admin to install it.
Moreover, here is a thread about migrating Exchange 2007 SP3 to Exchange 2013 for your reference.
Migrate SBS 2008 R2 running Exchange 2007 to Windows Server 2012 Exchange 2013
http://social.technet.microsoft.com/Forums/en-US/4c9b96c2-fd5e-4fbe-8b3a-fb5b3ab29da8/migrate-sbs-2008-r2-running-exchange-2007-to-windows-server-2012-exchange-2013?forum=smallbusinessserver
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Move mailboxes and public folders from exchange 2007 to Exchange 2013

1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
2. I want to move public folders from Exchange 2007 to Exchange 2013.
I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
Get-publicfolder
Name Parent Path
IPM_SUBTREE
Get-publicfolder | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
exchangeV1 schema-root\microsoft\exchangeV1
Internet Newsgroups Internet Newsgroups
Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
Name : IPM_SUBTREE
Replicas : {}
Name : Internet Newsgroups
Replicas : {MAIL\Public Folder Storage\Public Folder Database}

I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
PS] C:\Windows\system32>Get-MailboxDatabase -server mail
Name                           Server          Recovery
ReplicationType
Mailbox Database               MAIL            False           None
[PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
Name                           Server          Recovery
ReplicationType
Mailbox Database 1460777952    MAIL1           False           None
[PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
DisplayName               StatusDetail              TotalMailboxSize
TotalArchiveSize         PercentComplete
[email protected]          Queued                    363.6 MB (381,217,115 ...
0

Unity & Exchange 2007

Similar Messages

Maybe you are looking for