Outlook 2013 not automatically configuring Exchange (2007) account when running the Auto Account Setup

In previous versions, once I launched Outlook, it would automatically detect/passthrough my username and email address into the fields so that I could just click next and be done. In Outllok 2013 on Windows 2008 R2 this doesn't appear to be working even
thought I am able to successfully resolve my autodiscover domain.

Hi,
Is there any error when you can’t connect your Outlook 2013 to Exchange 2007?
If the autodiscover service is configured correctly, please change a computer to have a try. In this local windows 2008 R2, please check the following settings in Internet Explorer:
Click Settings > Internet Options > Connections > LAN settings, please make sure there is no proxy server set there. Only “Automatically detect settings” option is checked.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

  • Outlook 2013 not connect with Exchange server 2013 in internal network

    Hello All,
    I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
    but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
    I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network. 
    Can you please suggest as soon as possible.
    Thanks,
    Parvez

    Hi,
    Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
    Thus, let’s try the following resolutions:
    1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
    2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
    3. Check if the above host name is in your certificate.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Exchange 2007 / Outlook 2013 "Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable"

    One of our users is having problems setting replies from Outlook on his local PC.  This is an SBS 2008 Server with Exchange 2007.  The client PC is running Windows 8 with Outlook 2013.  This issue doesn't seem to affect other users but this
    is the only client with Outlook 2013.
    When trying to set an automatic reply from within Outlook 2013 we get the "Your automatic reply settings cannot be displayed because the server is unavailable".  Outlook seems to be connecting and working fine so connection to the server does
    exist.
    Trying this same operation from owa works without issue.  Please let me know what we need to do to find a solution.
    Thanks so much!

    Problem: 
    IMAP downloads inbox don't work after November patches.
    If you install a fresh OS and O2K13 unpatched ,the IMAP works fine.
    Fully patched O2K10 works fine too.
    It worked for my customer until November patch Tuesday broke the IMAP sync.
    Consultant opened case. 
    Response from Microsoft:
            This is with regards to the issue faced by you due to regression         caused by November security update. This is further to inform         you
    that fix is out and below is the download links for 32 bit         and 64 bit of the office suites. You need to apply all 3 hotfix.         The crash issue and IMAP issue would get resolved
    immediately         while the issue related to Free / Busy and OOF not getting set         would take 24-36 hours to start working once the patch is        
    applied.
    Below
            are the KB articles:
    Description
            of the Outlook 2013 hotfix package (Outlook-x-none.msp):         December 10, 2013:
    http://support.microsoft.com/kb/2825652        
    Description
            of the Word 2013 hotfix package (Word-x-none.msp): December 10,         2013:
    http://support.microsoft.com/kb/2837674        
    Description
            of the Office 2013 hotfix package (       2013:
    http://support.microsoft.com/kb/2849994        
        Description of the Office 2013 hotfix package (   December 10, 2013:
        http://support.microsoft.com/kb/2849994
    Issues that this hotfix package fixes
    Consider the following scenario:        
    You have a SharePoint Server environment that has complex             workflows.         
    You implement the ReceiveTimeOut registry entry to             increase the global timeout to 90 seconds.         
    You click Open this task             button to open a workflow task in Outlook 2013.       
            In this scenario, when you click any approval option from the         popup dialog box, you receive the following error message:        
    This task could not be updated at this               time.
    When you reply or forward an email message by using inline         replies, you cannot use the Close and Delete method of Outlook         Visual Basic for Application. Additionally, you
    receive the         following error message:        
    Run-time error '-2147467259               (80004005)': This method can't be used with an inline               response mail
    item.
    Consider the following scenario:        
    Assume that User A is located on an on-premises Exchange             Server, and User B is located on Cloud.         
    Both the on-premises Exchange Server and the Cloud enables             the Federation Trust.         
    User A share his own calendar to User B with Full Details             permission, and send the sharing invitation to User B.         
    User B opens the sharing invitation from User A, click             Open this Calendar, Outlook browses to the Calendar module             and opens
    the shared calendar.       
            In this scenario, the shared calendar does not show any content.     
    Consider the following scenario:        
    You install Outlook 2013 on Windows Server 2008 R2 or             Windows Server 2012 with Terminal Server Role installed.         
    You implement the Use Cached Exchange Mode for new and             Existing Outlook Profiles Group Policy settings and enable             it.       
            In this scenario, when you open the           Outlook Account Settings window, and double-click the         Exchange
    account, the Use Cached           Exchange Mode check box is not checked in the popup         dialog box.     
    Consider the following scenario:        
    You have an Exchange Server that has Public Folders.         
    You create the Outlook Security               Settings folder under
    All               Public Folders.         
    You publish the AdminSecurityMode registry entry and set             to a value of 1.          
    You configure Outlook 2013 to use cached mode.       
            In this scenario, when Outlook 2013 connects to Exchange Server,         Outlook crashes.   
        Description of the Word 2013 hotfix package (Word-x-none.msp):     December 10, 2013:
        http://support.microsoft.com/kb/2837674
        Assume that you open a meeting request in a separate window in     Outlook 2013. When you click
    Accept and     then click
    Send Reply Now,     Outlook crashes.
        Description of the Outlook 2013 hotfix package (Outlook-x-none.msp):     December 10, 2013:
        http://support.microsoft.com/kb/2825652
    Issues that this hotfix package fixes
    Assume that you have a recurring appointment that does not         have a subject. You make some changes to one instance of the         appointment and then save the instance. When you
    try to open or         delete the instance, Outlook may crash. Additionally, when you         drag-and-drop one instance of the appointment to a different        
    time in the calendar, Outlook may crash.     
    When you reply or forward an email message by using inline         replies, you cannot use the Close and Delete method of Outlook         Visual Basic for Application. Additionally, you
    receive the         following error message:        
    Run-time error '-2147467259               (80004005)': This method can't be used with an inline               response mail
    item.
    Consider the following scenario:        
    Assume that User A has a mailbox that is located on an             on-premises Exchange Server, and User B has a mailbox that             is located
    on Cloud.         
    Both the on-premises Exchange Server and the Cloud enable             the federation trust.         
    User A share his own calendar to User B with Full Details             permission, and send the sharing invitation to User B.         
    User B opens the sharing invitation from User A, click             Open this Calendar, Outlook browses to the Calendar module             and opens
    the shared calendar.       
            In this scenario, the shared calendar does not show any content.     
    Consider the following scenario:        
    You install Outlook 2013 on Windows Server 2008 R2 or             Windows Server 2012 with Terminal Server Role installed.         
    You implement the Use Cached               Exchange Mode for new and Existing Outlook Profiles             Group Policy
    settings and enable it.       
            In this scenario, when you open the           Outlook Account Settings window, and double-click the         Exchange
    account, the Use Cached           Exchange Mode check box is not checked in the popup         dialog box.     
    Consider the following scenario:        
    You have an Exchange Server that has Public Folders.         
    You create the Outlook Security               Settings folder under
    All               Public Folders.         
    You publish the AdminSecurityMode            
    registry entry and set to a value of 1.          
    You configure Outlook 2013 to use cached mode.       
            In this scenario, when Outlook 2013 connects to Exchange Server,         Outlook crashes.     
    Consider the following scenario:        
    You have two Active Directory forests (Forest A and Forest             B).         
    User A and User B have their mailboxes that are located on             Forest A.         
    User A share his own calendar with User B with Full             Details permission.         
    User B add the shared calendar and let it sync.         
    You move User B’s mailbox to Forest B.       
            In this scenario, the shared data in the shared calendar is         removed every second time that User A restarts Outlook. And it         is re-synced
    when User A browses to the Calendar module.
    Unfortunately TechNet isn't coming back, sorry folks :-(
    The 3 patches above immediately fixed the issue for me!
    Thanks so much!

  • Outlook 2013 not compatible with Exchange 2003

    Hello
    Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
    clients to 2013 version.
    Microsoft, is this correct?!

    If this post is hard to read, it's because of Dragonsoft!!  (sometimes it is like auto-correct on the phone - "I said WHAT!??")
    Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
    As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
    When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
    So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
    The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
    The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
    Windows for which they are named.  So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
    made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
    package which could handle the intricacies of the licensing limitations on the SBS system.
    SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
    and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
    My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version.  You must purchase a new server, install the new SBS version, and migrate your
    entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!)  The whole process is rather daunting as not
    all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
    So off we went with our new installation of SBS 2003 R2.  Then along came SBS 2008!  I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
    When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I  fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
    nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware.  (I was not going to get stuck in a hardware box that I could not replace
    if I ever needed to restore the operating system due to a massive failure.)  So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
    Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
    on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
    that they modified, and even performed a little cleanup, after they performed their cleanup!  I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
    Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
    Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false!  I live in Texas, and the state of Texas DIR program has adopted standards which state that
    you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional!  Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
    from, anyway?)
    One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
    Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
    any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
    The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs. 
    I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
    A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
    having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
    If you allow a client to be painted in a corner, then it's not their fault, it's your fault!  Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
    expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
    If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
    they are unwilling to spend money.  You don't work for free.
    One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well.  I put it like this, "You pay me to make certain that your business operates in good times and in
    bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully.  The equipment that we have operating here is no longer
    available on the market.  If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
    I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
    can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
    where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
    It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years.  We don't want to patch this together
    and always have problems."
    And just as a note, your customer can write off $10,000+ per year for new equipment purchases.  I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
    a month later, in the next year!

  • Outlook 2013: Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable

    When I configure the Outlook profile manually then receive warning "Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable" when clicking "Automatic Replies (Out of Office)".
    However if I use Autodiscover to configure the Outlook profile the above does not occur and "Automatic Replies (Out of Office)" works fine.
    Client: Outlook 2013 Click-to-Run version 15.0.4551.1011 on Windows 7 Pro SP1.
    Server: Exchange 2007 SP3 on Windows SBS 2008 SP2.

    Hi,
    First of all, please make sure you have installed this Outlook 2013 hotfix package (December 10, 2013):
    http://support.microsoft.com/kb/2825652/en-us
    It may fix the issue.
    If the hotfix doesn't help, please note, this problem can occur after your primary SMTP address changes. The problem occurs because your previous primary SMTP address is cached in the Windows registry under your Outlook profile and this information does
    not get refreshed for 24-48 hours after the SMTP address change.
    So please make sure you have configured smtp address correctly, or, we can find some workarounds from the link below:
    http://support.microsoft.com/kb/2693800/en-us
    Regards,
    Melon Chen
    TechNet Community Support

  • Outlook 2013 OOF "Forward" rules not working against Exchange 2007

    We have found that on Outlook 2013 clients (connecting to Exchange 2007) we cannot set forwarding rules in OOF (Out of Office / Facilities) if we select a recipient from the GAL. The error we get when trying to set the rule is:
    "Changes to the rule cannot be saved"
    However, if we manually type the SMTP address (without resolving it to the GAL) and click OK the rule is accepted.
    We have tested the rule using other versions of Outlook and it appears that Outlook 2013 is the only client that has this problem.
    Any suggestions would be welcome.
    Mark

    The issue is know under OffBug 57619. A support case for this had been started in April but no customer pursued a fix yet.
    Currently its status is low and no fix is intended. If this is a critical issue for you and to get it reconsidered, you'll need to open a support incident of your own, refer to OffBug 57619 and state your case as "high customer impact" (in case your not
    a Premier customer) and request a Hotfix.
    Robert Sparnaaij
    [MVP-Outlook]
    Outlook guides and more: HowTo-Outlook.com
    Outlook Quick Tips: MSOutlook.info

  • 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

  • Behaviour of Microsoft Transporter Suite (Notes migration to Exchange 2007)

    Dear Sir, 
         I have a question about configuraiton of Microsoft transporter, not sure whether it is a behaviour or it can be fixed.
    Question 1:
    Lotus Notes 7.04 --> Exchange 2007
    Microsft Transport: Scheduler set to every 15 min.
    Q1. Does it mean that Notes sync to AD User account setting only in every 15 min only ?
    Q2. It seems that it will not sync Notes email mailbox message with Exchange mailbox until manual press
        'Migrate selected mailbox', may I confirm that is it a design behaviour.
    Q3. After created free/busy connector (Every 60 minutes of sync), it seems that it will not sync
          user calendar until manual pressed 'Synchronize Now'.
    Q4. Can Mirocosft transport suit support workstation NSF file to PST file ?
    Q5. In notes environment, ACL will be used to configure boss/secretary condition which allow send as permission.
        Does it mean that all permission will be reconfigured manually? Or any Microsoft tools to work on it.
    Regards,
    Joe

    Hello Joe,
    I checked with a specialist regarding your questions and here are the responses.
    I hope this helps!
    Q1. Does it mean that Notes sync to AD User account setting only in every 15 min only ?
    If this is referring to Direcctory Synchoronization, then yes, it will synch any updates every 15 minutes. However, there is no reason to do a dirsync that often.
    Q2. It seems that it will not sync Notes email mailbox message with Exchange mailbox until manual press
        'Migrate selected mailbox', may I confirm that is it a design behaviour.
    This one seems to refer to migration. If you are wanting to migrate the mailboxes and email, you would have to manually migrate each user. In other words, this is not an automated process. So yes, this is by design
    Q3. After created free/busy connector (Every 60 minutes of sync), it seems that it will not sync
     user calendar until manual pressed 'Synchronize Now'.
    A dirsync will have to be run after the Free/Busy Connector is created. However, it should only have to be run once. After that, when a user requests new calendar information, it will pull information for that user
    Q4. Can Mirocosft transport suite support workstation NSF file to PST file ?
    Yes, you will have to use the EMS to do this. It's not possible via the GUI.
    Q5. In notes environment, ACL will be used to configure boss/secretary condition which allow send as permission.
        Does it mean that all permission will be reconfigured manually? Or any Microsoft tools to work on it.
    There is not an automated way of doing this.
    Kevin Ca - MSFT

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

  • Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

    I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

    All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
    A. For local clients
    You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
    Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml" 
    Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
    B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
    If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
    If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
    Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

  • Outlook 2013 not warning of oversized email

    We have a 10MB limit for emails on our server. We host but not on an Exchange server. I have a few Users who are NOT getting the warning that their email message is over the limit from Outlook. Outlook sends the email instead of placing the email in the
    Outbox and the User assumes the message is gone. The server actually deletes the email but the User still doesn't know that. Any ideas why Outlook is not warning with the prompt?

    Hi jpwesty55,
    Might be these given links can help you more:
    http://arstechnica.com/civis/viewtopic.php?f=17&t=1115668
    http://social.technet.microsoft.com/Forums/en-US/a2f1e34c-8a3e-4ae3-9903-c3c68fbddb3a/outlook-2013-not-warning-of-oversized-email?forum=outlook
    Note: Improve community discussions by marking the answers helpful.
    Thanks
    Clark Kent

  • Contacts created with Lotus notes are not seen in Exchange 2007 SP3 Rollup 7.

    Contacts created with Lotus notes are not seen in Microsoft  Exchange 2007 SP3 Rollup 7. the same is seen in Microsoft Exchange 2010 without issues.
    when we create a new contact on Microsoft Exchange 2007, the contacts gets created but it is not seen unless we filter the EMC to list the contacts. Microsoft Exchange 2010 does not have any issues. 
    any help or inputs will be appreciated.
    Thanks,
    Sid

    You shouldn't be using the 2007 EMC or cmdlets to create new objects if you have a more recent release installed in your organization. Use the 2010 software.
    If you create the mail-enabled contact with the 2010 EMC or cmdlets do you see it in the 2007 EMC?
    When you say the contact "is not seen unless we filter the EMC to list the contacts", does that mean you don't see the contact when you're looking at the "Recipient configuration" container? Is there a default filter on that container? Do you have a limit
    on the number of objects shown?
    As for the objects created by 3rd-party software (Lotus), are they creating the contacts correctly?
    --- Rich Matheisen MCSE&I, Exchange MVP

  • Using Outlook 2007 I want to receive emails on my iPhone 4 only when Outlook is NOT open on my computer, as when away from home or want to quickly check email when computer is not turned on. Either ALL emails come to my iPhone or none at all.

    Using Outlook 2007 I want to receive emails on my iPhone 4 only when Outlook is NOT open on my computer, as when away from home or want to quickly check email when computer is not turned on. Either ALL emails come to my iPhone or none at all. Is the setting I need to change in Outlook or on the iPhone or is it somewhere else?  I used to have this setting but transferring Outlook to a new laptop somehow turned it off.

    No. You really can't do that. Not easily at any rate. You would have to set them both up to use POP3, but even then there is no way to guarantee that the phone won't poll the server prior to your computer doing so, pulling down the message from the server.

  • Help - iCal All Day Events Not Syncing on Exchange 2007

    When I enter an all day event in iCal it does not sync to my Touch Pro 2 through Exchange 2007. I see the event in OWA and also in Entourage through Sync Services but it simply does not come onto the TP2. All day events entered in Entourage or OWA DO show up in the TP2. Strange but very frustrating because I like to enter my events using Launchbar which works with iCal only.
    I don't think I had this problem with 10.5
    Greatly Appreciate Help.

    I've noticed a similar problem. Previously, "all day" events listed correctly in both iCal (on my Mac) and in the calendar on my iPhone. Now, all day events on the iPhone cover the entire day, set to a time of 12 am to 12 pm.
    I'm not sure if this is related to 10.6.4 or my recent update to iOS4 on the phone.

  • CRM2011 and Exchange 2007 (why to upgrade the Exchange server??)

    Hi,
    Does anyone have any thoughts benefits for CRM 2011 or 13/15 and upgrading the Exchange server from 2007? What would be benefits to CRM if we upgraded from Exchange 2007?
    I see that CRM 2015 is not supported on Exchange 2007. Was wondering what other benefits would be there

    There are lot of benefits to migrating from Exchange 2007 to Exchange 2013.  The best place to start would be to take a look at the new features in Exchange 2013. the introduction of DAGs in Exchange 2010 and continuation of the DAG in Exchange 2013
    and the changes to CAS and Mailbox roles are just a few of the benefits. 
    https://technet.microsoft.com/en-us/library/jj150540%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    As benefits of updating CRM, I suggest you post that in the forum below.
    https://social.microsoft.com/Forums/en-US/home?category=dynamics
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Maybe you are looking for