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!

Similar Messages

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

  • Help with Exchange 2007, Active Sync and iPhone 3g - software 2.0.2

    Hello good evening and *******
    Now that's said, is anyone else having 'issues' with this?
    I'm on install number ten of Exchange 2007 and god knows how many different variations of trying to connect to it on the phone. I can get OWA working on the phone and via the web both on the phone and via my home pc, i've had Outlook at home working and i've had Outlook at work working. Honestly when it works, it's seamless and very very quick however i'd like it to work for longer than a day and have some faith that it will do so.
    What I keep finding is that for some reason, despite nothing changing on the server or the phone is that Active Sync eventually fails and for no apparent reason. The longest i've had it working is just over a day ( yesterday) and last night it packed up again.
    I think it's something to do with certificates / dns but that's purely guesswork as I thought i'd fixed it last time by setting up the FQDN to point at both internal and external network cards on our internal network.
    I would also like to point out that Exchange2007 has been working perfectly throughout all of this, it's just the iPhone / ActiveSync part that dies - unsurprisingly this is the most important bit for me as that's the bit our sales force will be relying on when we transfer to exchange.
    I'm no Mac 'fan' and i'm not that much in love with Windows but there seems to be something amiss between Apple and Microsoft and due to the iPhones complete lack of diagnostic logging further compounded by silent error messages i'm at a loss to find out where / why / when it's breaking.
    Is there a 2.0.3 update due which will address this problem?
    In the meantime i'm off to install Exchange ..... again, set up security certificates ... again ..... and see if it will fix what's broken .... again

    And now it's working!!!
    I changed the following in IIS.
    Default website - Microsoft Server ActiveSync Properties
    virtual directory - read access enabled
    directory security - integrated windows authentication, digest authentication, basic authentication enabled
    realm - set to mydomain.com
    Changed the same things for OWA
    That appears to have done the trick but i've been here before so i'll see if it stays working over the weekend.
    As a phone ... i'm impressed, as a web enabled device, i'm impressed but as a Corporate Tool ..... i've yet to be impressed, largely due to the complexity of integration into exchange.

  • Exchange 2010 co-existence with Exchange 2007 issue NDR size Four Times then we send

    Hi All,
    I am facing some strange issues of NDR size four times then we send like if I send 1 MB message to internal OR external recipient then we receive 4 MB NDR.
    Even we send one black mail with subject Test mail of 4 kb then we receive 16 kb NDR is it due to architecture change or something else.
    Everything was fine with Exchange 2007 but facing this issues after we change the mail flow to Ex2010.
    Any help really appreciated
    Regards
    Anand S
    Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

    Hi Anand,
    From your description, the NDR size is four times than original message size. I would like to verify the following thing for troubleshooting:
    How many people has this issue, only one or all the people?
    If only one user has this issue, I recommend you move the user's mailbox to another mailbox database and check the result.
    If all the people have this issue, please enable Pipeline tracing and see if there is any hint. If the issue persists, please install the latest Service Pack and Rollup and check the result.
    Here is an article for your reference.
    Enable Pipeline Tracing
    http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Outlook 14.4.8 not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox"

    Outlook 14.4.8 on iMAC Retina and Yosemite 10.10.2 is not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox".
    Accessing Mails with Webbrowser and from Windows Outlook is working correctly.
    All Macs (also the ones with OS 10.6.8) do not anymore show any new messages in inbox.
    Restarted Server, tried to disable autodiscover on macs and deleting/adding account and repairing database does not fix the problem. Also restarted server several times.
    We have the same problem on 2 imacs retina with yosemite and on 2 mac pro with 10.6.8 and different office 2011 versions.
    i tried to configure the exchange account in apple mail on yosemite and it also states "connected" and does list some folders but no new mails are getting in.
    Windows clients and outlook on them works and syncs fine, and also when connecting via webbrowser at owa it must be a mac-specific/webdav issue.
    exchange 2007 Sp3 Version 8.3 (bild 83.6) and Update Rollup 15 for sp3 (automatic updates "HIGH" for server and clients)
    there is one update popping up again and again even after everytime successull installation: Windows Mlicious Software Removal Tool x64 - October 2010.
    i tried to configure a new user with empty mailbox and configured it with microsoft mail (mac - yosemite)  as exchange and was able to send a mail from there (even if quite delayed).
    but there are not coming in any mails.
    same exchange accounts triggered by imap do work and also via owa.
    Exchange Accounts in Outlook for MAC and also in Mail (Yosemite) do show the folder structures but there is no mails showing up. I can send mails from the exchange accounts created but they seem to be processed with a delay of like 15minutes and outlook
    is giving error "end of file reached" but messages are send after some time.
    Does seem like EWS is extremely slow, to slow perhaps to sync and therefore ending in timeout.
    Also i cannot reach the server from externally over ssl https 443. if testing port 443 of exchange from outside the port seems closed even firewall settings of sbs 2008 and sonicwall ports are correctly open.
    could it be there is something in regarding webdav which is very slow and leading to timeouts ?
    in application log i do have the following two information events every few minute:
    The Exchange Web Services started successfully. Event ID 1
    and
    Process STORE.EXE (PID=3688). Exchange Active Directory Provider has discovered the following servers with the following characteristics: 
     (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) 
    In-site:
    SERVER.org.local CDG 1 7 7 1 0 1 1 7 1
     Out-of-site:
    Errors in Application log:
    The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section 
    The entry <C:\WSUS\WSUSCONTENT\CONTENTFOLDERACLSCHECK.TXT> in the hash map cannot be updated.
    An exception Microsoft.Exchange.Data.Storage.ConversionFailedException occurred while converting message Imap4Message 69447
    Also outlook 2011 clients are asked by time to time to reenter pwds and errors like "connection is closed. 13" 
    Faulting application taskeng.exe, version 6.0.6002.18342, time stamp 0x4cd34898, faulting module ntdll.dll, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc000071b, fault offset 0x0000000000082445, process id 0x3288
    Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.
    Backup Exec:
    FULL_BACKUP -- The job failed with the following error: A failure occurred querying the Writer status.
    Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered.  This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider.  The
    error returned from CoCreateInstance 
    Exchange VSS Writer (instance 2d932ef8-6319-4ab8-a45f-1242480b44ad:15) failed with error code 1295 when processing the backup completion event. 

    Hi,
    Since Outlook running on Windows works well, it seems an issue on the Mac side. I suggest ask Mac for help so that you can get more professional suggestions.
    More information for your reference:
    Please try to verify whether there is any expired certificate from the computer personal store.
    If it is the case, please remove them.
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Mavis Huang
    TechNet Community Support

  • Migrate SBS Server 2008 with Exchange 2007 to Exchange 2013

    I have looked at the documentation to co exist 2007 and 2013.  However I am concerned as it talks about changing the dns name to something like legacy, as the dns name that is used for outlook to connect is the name of the server.  So here
    is my question.  Would I have to change the name of the actual server itself?  and if I choose not to, and use a new name for the 2013 server, such as mail, would the users that get migrated, would they automatically update the
    name change?  Also note the SBS server with exchange 2007 is also their file server at present but will be changing.    

    Hi ,
    Thank you for posting your question in the forum.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards,
    Andy Qi
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback
    on our support quality, please send your feedback here.
    Andy Qi
    TechNet Community Support

  • Does anyone know how to get apple mail in Lion to connect with Exchange 2007?

    Does anyone know how to get apple mail in Lion 10.7.2 to connect with Exchange 2007?  It worked perfectly with Snow Leopard... upgraded to lion and it won't work.  We use Exchange 2007 with SP 3 and Rollup 4.  Won't connect... and I can't get Apple to give me any direction. 

    We finally got it to work today.  We had to call and pay for the microsoft support service, but the issue was on the server end.  We had to go into the iis manager... went to sites... when to default website...and changed the SSL settings for Auto Discover, EWS Exadmin, echange, exchweb, owa... and the rest..
    Change the settings to ignore client certificates.
    Problem solved. Can finally send and receive.

  • Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

    HI, i need help here
    I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
    flow went back to normal. We then remove the program from the control panel.
    Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
    Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
    Much Appreciated

    Symantec's support group should be able to tell you what happened.
    --- Rich Matheisen MCSE&I, Exchange MVP

  • ICal still does not sync with exchange 2007 in Lion

    Dear,
    In Snow Leopard, iCal was not syncing with Exchange 2007. I read a lot of things on this and it all led to recurring events. Indeed, after deleting them, things started to work. But I cannot delete recurring events! I need them!
    Seeing that there was soo much talk on this all over on apple, I assumed that Apple would fix it. Instead, all we're seeing is some enhanced UI.
    Can somebody at Apple please make sure that this thing finally gets fixed? Really, how hard can it be, knowing that the hardware based i devices can sync without any trouble?
    Just for extra information, so you know what direction to look for:
    I have Windows SBS 2008 in Dutch language. Timezone is Brussels. Exchange 2007 and all updates.
    The system is running a self signed certificate
    Outlook works fine on the Mac. I don't want to use Outlook on the Mac but am forced to at the moment.
    Mail/Addressbook sync fine. Only Outlook doesn't!
    I did try deleting recurrent events and this worked for a day. Basically stopped working I think when I added again those recurring events.
    There are some errors in the console:
    21/07/11 11:42:36,563 iCal: Couldn't find an NSTimeZone to match the SerializableTimeZone
    21/07/11 11:42:36,563 iCal: WARNING: Failed to find TimeZone Identifier for Windows MeetingTimeZone: (GMT+01:00) Amsterdam, Berlijn, Bern, Rome, Stockholm, Wenen
    21/07/11 11:42:36,580 iCal:  error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken." UserInfo=0x7fbe94adb8b0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7fbe94102d40>, NSLocalizedDescription=iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken., NSLocalizedFailureReason=De account 'Exchange' kan momenteel niet worden bijgewerkt.}
    Please fix this,
    Guido
    Message was edited by: guido4096. Added error message

    Hi all,
    I do have exactly the same problem.
    But I am adding a new flavor, but I can not understand it.
    I've setup two Exchange calender connections. Both servers are inhouse. The setup of the Exchange servers are most likely the same.
    But one works and one not! How could this be explained?
    I like to express my deep disappointment about iCal and partly Apple Mail. It is unbelievable for me, that years after Apple's cooperation with Microsoft there are still such problems.
    I like my Macbooks and I certainly have the absolutely full bandwidth of all Apple products in my household and companies. But I think I have to go back to Microsoft and Sony Laptops in the near future.
    Although this kind of bugs are small one's, but the hurt constantly. Apple - please fix that.
    Here just for the interested reader is my console error message:
    3/15/12 11:51:29.819 AM iCal:  error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal can’t refresh events in the calendar “Kalender”." UserInfo=0x7f856d4bddb0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7f856c5ca060>, NSLocalizedDescription=iCal can’t refresh events in the calendar “Kalender”., NSLocalizedFailureReason=The account "DR InfoDyn" currently can’t be refreshed.}

  • Has anyone managed to create an email account on the OS X mail client with Exchange 2007?

    Hi guys,
    the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
    Thanks
    Juergen

    jthurner wrote:
    Hi guys,
    the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
    Thanks
    Juergen
    No workaround needed, open Mail, Contacts and Calendars (in System Preferences) select Exchange, enter your email address and password, opt to setup Contacts and Calendars as well as mail and hit enter. That should set it up (assuming your apparently witless IT dept has setup the autodiscover record correctly at their end)

  • Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

    I have exchange 2013 and 2007 set up in a coexist environment.  At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007.  I found an article
    that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.)  I would like someone to confirm
    if the change I am about to make from doing research will help me in my situation.
    Current Setup:
    Exchange 2007 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: NTLM
    IISAuthenticationMethods : {Basic, Ntlm}
    Exchange 2013 OA CAS Settings
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod: Negotiate
    IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
    New Settings I am considering based on research:
    Exchange 2007 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: Basic
    IISAuthenticationMethods : {NTLM}
    Exchange 2013 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: Basic
    IISAuthenticationMethods : {Basic}
    Will this work and eliminate my popups?

    Hi,
    The following TechNet article indicates that:
    “In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
    Exchange Deployment Assistant. Specifically,
    you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
    Client Connectivity in an Exchange 2013 Coexistence Environment
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

    Team,
    I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp.  However, we have a coexistence environment with exchange 2007.  When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
    mailbox is still within exchange 2007, you get a blank login page.  If you mailbox is in exchange 2013 then you successfully get the owa page for 2013.  The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
    that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed.  Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
    the much needed mailbox lookup for a coexistance environment?  A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.  

    Hi,
    Try using AD FS claims-based authentication with Outlook Web App and EAC
    http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    Hi,
    From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
    Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
    http://support2.microsoft.com/kb/2997209
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Outlook 2013 with Exchange 2007 - out of office problem

    We are using outlook 2013 with Exchange 2007. When users select their out of office it will work fine for the first day, however there after the Out of Office replies stop working. Out of Office is set correctly within Outlook, but what we have found
    is that if the user opens Outlook the Out of Office starts to work again. Also when the user opens Outlook it takes around two minutes before it registers that Out of Office is on.
    Any Ideas?

    Hi,
    How do you configure your OOF? From standard OOF wizard or define an automatic reply template from Rule wizard?
    If you are using a template, Outlook must be running for the Rules Wizard to automatically reply. Please refer to the Note in the following KB:
    http://support.microsoft.com/kb/311107
    If it is configured by using standard Out of Office assistance in File > Automatic Replies, please remove OOF settings in Outlook and set it from OWA 2007, then check whether the issue can be reproduced.
    Regards,
    Winnie Liang
    TechNet Community Support

Maybe you are looking for