Unity 7.x Unified Exchange 2007

customer deleted mailbox from exchange
then recreated mailbox.  Is there a way to resync Unity so that recordings and personal settings for the user are not lost. Again  thx

Hi,
All of the personal recordings/greetings/user configurations are stored in Unity.  If only the Exchange mailbox is deleted, Unity data should not be lost.  If the user account in AD is deleted completely, Unity can purge them out of the database automatically.  If you just recreated the mailbox in Exchange, Unity specific data remains.  The periodic Global Catalog sync and Domain Controller syncs should realign Unity with the new mailbox location/properties.  If that doesn't help, you can always re-run the Message Store Configuration Wizard which should sync all users/mailboxes up.
Hope that helps,
Brad

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!

  • 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+

  • Unity 5.x and Exchange 2007

    When trying to switch from a 2003 Exchange partner server to a 2007 Exchange server the reconfiguration guide states to "Configure Offline Address Book (OAB) Distribution for Outlook 2003 and Earlier Clients".
    Does anyone know why this should be done? Is Unity using an OAB when operating normally or is it only for when the Exchange server might go offline?
    In addition, is changing the partner server from a 2007 Exchange server back to a 2003 Exchange server not supported?
    The configuration guide only states how to change from 2003 to 2007, and not the other way around.
    Thanks in advance for any input.
    The configuration guide I keep mentioning is this one: http://www.cisco.com/en/US/partner/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcuruge050.html

    Great thanks, it was really the first time we were doing this and it was a fast request from the customer so we were a little less than prepared.
    that being said, we did the upgrade last night and everything went fine. Instructions from running permissions wizard to the message store wizard were on spot. (The only thing that caused us an extra five mins is calling our Microsoft Engineer to find out how to actually run the script :) ). The Users were migrated a couple of days ago so the time on the messages were incorrect. we are monitoring today so we will see.

  • 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

  • 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!

  • 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

  • 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.

  • Migration of Unity users from MS Exchange server 2007 to 2010

    Hi,
    I am having Unity 7.0 with MS Exchange server 2007,now want to transfer the users and Unity mailboxes to MS Exchange server 2010. Want to know the procedure. Can anyone help me out?

    The way you're doing it has two very high hurdles.
    First, you have to get the data out of an offline server and into Office 365.  That's hardly a trivial task.  If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
    Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Unity 5 with Exchange 2007 - adding Exchange 2010

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin-top:0in;
    mso-para-margin-right:0in;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    We will be adding and Exchange 2010 server to the existing Exchange environment and then migratomg user mailboxes to the new 2010 server. My question is, does the mere presence of the Exchange 2010 server require me to update Unity with ES patches, or can I wait until I am ready to start migration mailboxes?
    I would like to do this in steps:
    1. Add Exchange 2010 to the existing Exchange group, without moving mailboxes.
    2. Updated Unity to support 2010
    3. Migrate a few mailboxes and test
    4. After testing move all mailboxes.
    5. Change the Partner server to Exchange 2010.
    From all the reading I've done, it seems like this should not be a problem, but I am not 100% sure.
    Thanks!

    Hi -
    I have previous experience doing the exact same procedure you described, in test and in production.  Only when you move a Unity subscriber mailbox to Exchange 2010 do you have to have Unity running the ES for 2010.  I recommend testing just basic email routing between two test mailboxes, one on Exchange 2010 and the other on 2007 before moving forward with Unity.  Applying the ES to Unity is straight forward.  Changing the partner server to Exchange 2010 is the more complex part, in that you have to replace ESM on Unity with exchangemapicdo.  Follow Cisco's document to the letter and also make sure the exchangemapicdo version is the same on Unity as on Exchange.  There are a few forum trains here that will help (relates to issues with MWI).
    Sincerely, Ginger

  • 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.

  • 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.

  • Unity Connection 8.5 Exchange 2010

    Does the exchange server need to be in the same location as the Unity Connection 8.5 server for single inbox to work?

    In the single inbox design guide here....
    http://www.cisco.com/en/US/partner/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg032.html
    Calculating the Number of Connections for a Connection Cluster
    If both Connection servers in a cluster are in the same location, so they have the same latency when synchronizing with Exchange, you can calculate the number of connections the same way you do for one Connection server.
    If one server in a cluster is collocated with the Exchange servers and the other is in a remote location:
    •Install the publisher server in the location with the Exchange servers. The publisher server should always be the primary server unless the server is offline for maintenance or is unavailable for some other reason.
    Also here in this guide....
    http://www.cisco.com/en/US/partner/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928
    Unified Messaging Requirements: Synchronizing Connection and Exchange Mailboxes (Single Inbox) (Connection 8.5 and Later Only)
    Revised February 22, 2011
    •Cisco Unity Connection integrated with a supported version of Microsoft Exchange Server:
    –Exchange Server 2010 with Update Rollup 3 or later (All editions are supported.)
    –Exchange Server 2010 with Service Pack 1 (All editions are supported.)
    –Exchange Server 2007 with Service Pack 2 or later (All editions are supported.)
    To synchronize Connection and Exchange 2007 mailboxes, you must install Connection 8.5(1) Service Update 1 (SU1), which is available on the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.
    In the tree control on the Downloads page, expand Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity Connection > Cisco Unity Connection Version 8.5. On the Select a Release page, select SU1, and the download buttons appear on the right side of the page.
    –Exchange Server 2003 with Service Pack 2 (All editions are supported.)
    To synchronize Connection and Exchange 2003 mailboxes, you must install Connection 8.5(1) Service Update 1 (SU1). For download instructions, see the previous bullet.
    Microsoft Business Productivity Online Suite is not supported.
    •Exchange servers and Active Directory domain controllers/global catalog servers (DC/GCs) can be installed in any hardware virtualization environment supported by Microsoft. (Cisco does not provide technical support for message-store servers or for DC/GCs.)
    •The Microsoft Exchange message store can be stored in any storage area network configuration supported by Microsoft. (Cisco does not provide technical support for message-store servers.)
    •Exchange clusters are supported.
    •To access Exchange servers in more than one forest, you must create at least one unified messaging service for each forest. Connection supports a maximum of 20 unified messaging services per Connection server.
    •Depending on the number of voice messaging ports on each Connection server, the path of connectivity must have the following guaranteed bandwidth with no steady-state congestion:
    –For 50 voice messaging ports on each server—7 Mbps
    –For 100 voice messaging ports on each server—14 Mbps
    –For 150 voice messaging ports on each server—21 Mbps
    –For 200 voice messaging ports on each server—28 Mbps
    –For 250 voice messaging ports on each server—35 Mbps
    The bandwidth numbers above are intended as guidelines to ensure proper operation of mailbox synchronization. For information on bandwidth requirements for Connection clusters, see the "Requirements for a Cisco Unity Connection 8.x Cluster" section. Additional conditions such as network congestion, CPU utilization, and message size may contribute to lower throughput than expected. Call-control and call-quality requirements are in addition to the guidelines above and should be calculated by using the bandwidth recommendations in the applicable Cisco Unified Communications SRND at http://www.cisco.com/en/US/partner/solutions/ns340/ns414/ns742/ns818/landing_uc_mgr.html.
    •The default Connection configuration is sufficient for a maximum of 2000 users and 80 milliseconds of round-trip latency between Connection and Exchange servers. For more than 2000 users and/or more than 80 milliseconds of latency, you can change the default configuration. For more information, see the " Latency" section in the "Single Inbox in Cisco Unity Connection 8.5 and Later" chapter of the Design Guide for Cisco Unity Connection Release 8.x. at http://www.cisco.com/en/US/partner/docs/voice_ip_comm/connection/8x/design/guide/8xcucdgx.html.
    •Users must be assigned to a class of service that is enabled for using single inbox.
    •For each user configured for single inbox, an email client that is configured to access the user's Exchange mailbox. For full single-inbox functionality, we recommend that you use Microsoft Outlook and install Cisco ViewMail for Microsoft Outlook. ViewMail for Outlook is required to:
    –Review secure Connection voice messages by using Outlook.
    –Compose, reply to, or forward synchronized voice messages by using Outlook.
    Other email clients can be used to access Connection voice messages in Exchange, but users will not have the functionality provided by ViewMail for Outlook.
    For information on Connection support for Outlook, see the "Requirements for Accessing Voice Messages by Using Cisco ViewMail for Microsoft Outlook 8.5 and Later" section.
    •For users who are configured for single inbox and SpeechView transcriptions, the message in Exchange is not updated with the transcribed text. You can configure Connection to send a notification message that contains the transcription.
    •When message expiration and single inbox are configured, the .wav file is not deleted from the message in Exchange. Voice messages in Connection are still removed from user mailboxes and are replaced with a recording that tells the user "This message is expired."
    Specifically teh bandwidth requirements. Typically it's always best to have Exchange as close as possible to the CUC servers for performance to be ideal but this should give you some guidelines.
    Tray

  • How to set up fax solution using Windows 2008 R2 Fax server role and Exchange 2007

    Hello, 
    I don't know if this is the right forum to post this but since it is related to Exchange I thought it might be. If this is not the right place, please direct me to the forum where my post would be more appropriate.  
    I'm looking to set up a Fax solution for the company that I work for as we are moving away from analog phone lines to VoIP using SIP. My original thought was to set up a Windows 2008 R2 server with Fax server role installed and have it route the fax message
    to Exchange 2007 SP3 so the fax message can be delivered to each user's inbox. I was reading a little bit on the Windows Fax server role and from what I saw it looks like it can only route fax messages to one email address. This not ideal for my company. Is
    there a way to have the fax server role route the email to each user's inbox? If so, how can I achieve this?
    How can implement this for this sending outgoing faxes as well?
    I don't know if this releveant or not but I will be using Asterisk as a media gateway between our SIP trunks and the Windows Fax server. 
    Any help is appreciated. Thanks!

    Please find the below url for the complete Fax configuration in Exchange 2007 Unified Messaging
    http://blogs.technet.com/b/exchange/archive/2007/04/18/3401950.aspx
    The article is so easy to understand with detail procedure and guideliness
    Exchange Queries

Maybe you are looking for