Outlook 2013 with Exchange 2013 keeps giving read receipts

Hello experts,
We have an Exchange 2013 server. All users are joint to the domain, except one user (Windows 8.1) which is in a Workgroup, and using Outlook 2013 with IMAP protocol. 
This particular user is having a problem. When he send's any email from Outlook and requests a read receipt, after that he keeps getting hundreds of read receipts in his inbox. I have tried disabling (for temporarily) the Windows server 2012 firewall,  but
still having the same issue. 
Is this a known bug in Outlook 2013 with Exchange 2013? Any help troubleshooting this?

Hi,
According to your description, I understand that IMPA account get hundreds of read receipts while he requests a read receipt.
If I misunderstand you concern, please do not hesitate to let me know.
Whether are all account or some special user experience this question? Please do a test in external with IMAP account to double confirm.
How about the “Request a Delivery Receipt”?
Also, please run message tracking log to get more details about message mail flow:
Get-MessageTrackingLog –Server “mailbox server” –Sender “[email protected]” –Recipient “[email protected]” –MessageSubject “Read: message subject” | Select Timestamp, ClientHostname,ServerHostname,Source,EventID,Recipients,RecipientStatus,Sender | ConvertTo-Html > “C:\Test\Test.xml”
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]
Allen Wang
TechNet Community Support

Similar Messages

  • Outlook 2013 with Exchange 2013: Mails stuck in Outbox

    Hi everybody,
    I am using Outlook 2013 connecting an Exchange 2013 server. After sending a mail, all outgoing mails remain in the outbox. After removing the cache files it works for a while until the problem occurs for the next time (approx. once every two days). 
    I already re-installed Windows 8 to test it on a completely clean environment...OWA works fine, the problem only exists with Outlook. 
    Additional note: It might be interesting that after sending a mail, the "Send/Receive progress" window states "sending [email protected] - complete" but the Mail is still in the outbox and was not delivered to the recipient. Safe mode doesn't work
    for me. Other users connecting with Outlook 2010 don't have a problem with this exchange server.
    Do you have any ideas? If I can provide you with further information, please let me know.
    Greets,
    Basti

    Thanks for your answer. Here are the requested information:
    >What addins are you using?
    No 3rd party addins, at the moment "Microsoft Exchange Add-In", "Microsoft VBA for Outlook Addin",
    "OneNote Notes about Outlook Items" and "Outlook Social Connector 2013" are activated. But the problem also occurs if no addin is active (or even in Safemode).
    >Antivirus
    scanners can prevent Outlook from moving messages to the sent folder.
    I will try to deactivate the virus scanner the next time. (Avira is used)
    >Can
    any address trigger this behavior or does it happen with certain addresses?
    No, it does happen with any address by random. Once the problem occurs, I can try to send as much mails as I want to
    any address - nothing leaves the outlook client.
    >Is
    this your mailbox or a shared/secondary mailbox?
    It is a user's mailbox, nothing shared.

  • Can't add multi exchange account on outlook 2010 with exchange 2013 Sp1

    I did install exchange 2013 with DAG group successful, the exchange work fine now
    Outlook can connect to exchange automatically and working fine
    The problem appear when i need create the second exchange account by go to control panel/Mail add new profile and add new exchange profile
    How can i solve the problem ?

    This Problem in exchange generally appear when users mistakenly create the wrong account type or Outlook upgrades an older account profile.In these situations you need to remove that wrong account and  create a New account .
    When you have the wrong type of account configured in Outlook you can easily remove the account and create the correct type of account. 
    1 Go to Control Panel, search for the Mail. If you are using 64-bit Windows and 32-bit Outlook, it will be named as “Mail (32-bit)”
    2 Double click on Mail (or Mail (32-bit)).
    3 Click Email account button
    4. Select the wrong account and click Remove. (If you only have one account listed in your profile,But you may need to create a New account first, set it as default then remove the wrong account.)
    5. Click New, select Email Account for POP3 or IMAP accounts, or select other then the correct account type.
    6. Fill in your preferred display name, email address and password on the Add New Account dialog.
    Outlook will look for published account configuration for the domain and setup the account automatically.
    In this event if your email provider does not publish autodiscover information, you’ll need to set up the account yourself. Check your mail providers support site for the proper configuration and then check the box to Manually configure the account at the bottom
    of the Add New Account dialog. 

  • Delete Button Disabled in Outlook 2010 with Exchange 2013

    I recently switched from a 3rd party mail software to Microsoft Exchange.  I have had some users ask me why the Delete button is disabled.  I didn't enable any special policy to cause this, and the Delete key on the keyboard will delete messages. 
    The disabled Delete button I am referring to is in the Home ribbon and the right-click menu for selected e-mail(s).  Is this standard behavior for Exchange, and can it be changed?

    It so happens that I have an XP VM with Outlook 2007.  That having been said, as previously mentioned, before testing, I (thought I) could confirm the same consistent behavior in the following configurations:
    WinXP + Outlook 2003
    Win7 + Outlook 2010
    Each of these systems was using a different user account, and I have tried folderview repairs in EMC to no avail.
    Strangely, WinXP + Outlook 2007 does not appear to exhibit the behavior.  In this test case, the profile and OST were just created, but switching to folderview or moving the reading pane to the bottom did not affect the behavior.
    Given that information, I proceeded to re-verify, and I hadn't checked winXP + Outlook 2003 because the computer in question had been upgraded to Outlook 2010.  However, I verified the issue does still exist there.  Next, I proceeded to check another
    computer that I thought would be WinXP + Outlook 2003, but it had also been upgraded to Outlook 2010.  This computer did not have the issue, and this leads me to a new theory about the cause (but no closer to resolution).  For the record, of the
    three computers (two exhibiting the issue, one not), only one has the Adobe plugin mentioned in my last post in response to Diane Poremsky, so the issue doesn't appear to be related to that.
    That said, my theory follows:  This is somehow related to IMAP in Outlook 2010.  The computers that exhibit the issue were all previously running IMAP in Outlook 2010, and the IMAP PST filse were imported using the MailboxImportRequest feature. 
    I suspect this is related because of other issues that happen for these accounts.  For instance, all new e-mail was only visible in OWA and not Outlook on all folders on these accounts, and I have had to have the users reset filters in the view settings
    for each folder individually.  I don't remember exactly which filter was somehow imported, but it definitely had to do with IMAP.  This may be another red herring, but the behavior is consistent with it.  I should also note that this behavior
    did NOT exist when they were connected via IMAP to the old (non MS) server.  I should also note that the filter behavior is somehow stored on the server (and therefore I imagine the delete button behavior could be as well), because creating a new Windows
    Profile  (and as such, a new Outlook profile and OST file) on a new computer did not make the IMAP filters go away.

  • Lync Server Integration with Exchange 2013

    Hello,
    I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
    in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled. 
    So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
    Thanks and Regards,
    Nash Burns

    Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
    Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
    Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
    to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
    www.lynced.com.au | Twitter
    @imlynced

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Outlook 2013 can't communicate with Exchange 2013

    we're just finishing migration to Exchange 2013 and found some Outlook 2013 clients (migrated from Exchange 2010) can't communicate with Exchange 2013. even if i recreate the Outlook profile.
    what worked is to reinstall Office 2013.  just want to get ideas why a reinstall fixed the problem.
    same outlook proxy is there in the account settings.

    Hi,
    What was the symptom that Outlook couldn't communicate with Exchange 2013? Could you please detail this a bit?
    If the Account Settings are completely same before and after the reinstallation, we can say the cause is not on the Exchange side. While I can't guarantee the root cause based
    on the provided information. A reinstallation fixes the corrupted or missing components/files in Office, but it's hard to say what has been fixed during the reinstallation.
    If you still have some Office 2013 clients that have not been reinstalled, try to run Microsoft Office Configuration Analyzer Tool to quickly identify problematic configurations in Outlook:
    https://www.microsoft.com/en-us/download/details.aspx?id=36852
    Regards,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here.

  • Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

    Hi,
    the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
    purchase a third party certificate or get one from a internal CA.
    Anyone can answer this question with no doubt?
    Thanks in advance!
    jspt

    Hi Abhi,
    I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
    Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
    problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
    Anyway thanks for your answer.
    jspt

  • 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

  • Outlook 2013 connection issue with exchange 2013

    my exchange 2013 was upgrade from exchange 2010. after the upgrade (migration), i using outlook 2013 connect to exchange 2013. some very
    weird issues happened.
    when i using auto discovery to create profile and connect to exchange will success. but when i manually create the profilewill failed. the following pic for your reference. (same account, same PC)
    please help, thanks lots!!!!

    This is what changed in Exchange 2013. It uses RPC or HTTPs (Outlook Anywhere) and uses Server GUID to connect...
    "As a result of these architectural changes, there have been some changes to client connectivity. First, RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as
    Outlook Anywhere). At first glance, this may seem like a limitation, but it actually has some added benefits. The most obvious benefit is that there is no need to have the RPC client access service on the Client Access server. This results in the reduction
    of two namespaces that would normally be required for a site-resilient solution. In addition, there is no longer any requirement to provide affinity for the RPC client access service.
    Second, Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary
    SMTP address. This simple change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013."
    From : What's New in Exchange 2013-
    http://technet.microsoft.com/library/jj150540%28EXCHG.150%29.aspx#BKMK_arch
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Outlook advanced search & Exchange 2013 - "Sent to...." field doesn't work correctly in online mode?

    Hello,<o:p></o:p>
    We've come across what seems to be a problem with advanced find in Outlook in online mode, when used with Exchange 2013. 
    Using the "Messages" tab of "Advanced Find", anything typed into the "Sent to...." field produces no search results.  If the field is populated by clicking
    "Sent to..." and selecting a name from a contact list or GAL, results are returned. 
    eg. 
    Sent items contains messages to "Charlie" who has the email address
    [email protected] and sender is
    "Dave" who has the email address
    [email protected] 
    Entering "charlie" or
    [email protected], (or any previously acceptable partial term such as "charl" or "@contoso.com") into the "Sent to"" field produces no results.  If the user exists in a contact
    list and is selected from it, the search works fine.  The same is true searching the inbox, using the local user's id of "Dave" or
    [email protected]
    We've confirmed this issue occurs at four client's sites, plus our own internal Exchange 2013 CU3 system.  Four of the sites have been transitioned from Exchange 2010, the fifth was a completely new installation.  The problem occurs with Outlook
    2007, 2010 and 2013. 
    This works fine in cached mode (not a solution as our clients are predominantly Citrix/RDS).  Exchange search doesn't report any issues and the index states are all "healthy",
    we've also tried rebuilding the indexes with no improvement.
    Any ideas would be appreciated, or even if someone else can confirm they see the same thing.
    Thanks.

    Hi Winnie,
    Thanks for your reply, and I'm sorry I've not responded earlier.  While this problem is one that's annoying several of our clients, and while I have been doing further testing and investigation, it's had to take a back seat to other more pressing issues
    until now.
    OWA search works fine, as does using "From:" in instant search, and the "From" query on the Advanced tab in Advanced Find.  The search services have been restarted, indexing state and copy status etc are all healthy, the indexes
    have been rebuilt/reseeded, and I've gone through the diagnostics again.  Nothing is logged in event viewer, and the only error that comes up when checking failed index docs for a user are for unsupported format handlers (.png etc).
    The issue seems purely to be with the "Sent to..." field on the Messages tab, it's as if it gets completely ignored.  The search returns instantly with "There are no items to show in this view".  Just to make sure I wasn't losing
    my marbles, I've compared searches on Exchange 2007 and 2010, and on those I can enter as little as a single letter or email domain and receive the expected results.  On 2013 I get nothing whatsoever whatever I enter, unless I pick an address from a contact
    list.
    At this point, I thought that since Office 365 is Exchange 2013 based it'd be worth testing that, and sure enough I got exactly the same issue.  I setup an Office 365/Outlook 2010 profile on a machine that is currently in an existing Exchange 2010
    environment where search works correctly, searching Office 365 doesn't work on that either.
    EDIT - Ignore this bit, a fresh install of Windows 7 and Office 2010 doesn't work with Office 365 either.  I am exploring another avenue.  I setup a fresh Windows 7 VM, installed Office 2010 and connected that to Office 365, search worked fine,
    so I'm now looking into what the difference with that VM and the servers and workstations out "in the wild" could be.  For example, the test VM isn't on a domain, it's not fully patched, it has no additional software installed etc.  Outside
    of Microsoft applications and operating systems and having similar configurations, I haven't isolated a common link across all of our client sites that are affected, there's no single 3rd party application or anti-virus solution in place at all of them for
    example. 
    I'll update with any findings, but if you or anyone else has any idea in the meantime I'd be grateful for your input.
    Regards.

  • Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

    I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
    Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
    Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
    Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
    Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
    Note
    If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
    Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
    Based on you installation scenario, follow one of these steps to configure ARR:
    If you are performing a clean setup, run the following command:
    ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
    I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
    that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
    working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
    I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
    in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
    Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
    names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
    config –cert path to the certificate file –hostnames host names for Exchange Server",
    when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
    I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
    domain I figured it would be ok to run the risk.. ;)

    Hi
    found this on
    https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
    "Ok just an update for anyone else how has this issue.
    The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
    I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
    of a better word. I should have retyped the whole command from scratch and it would have been right!
    Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
    From Microsoft:
    We have tested on your environment and here is the investigation result from our senior engineer:
    ================================================================
    Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
    can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
    The one we check (compare) is ‘-‘ which has the code 0x45.
    So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
    The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
    Best Regards,
    Johnny Chen
    Microsoft Partner Support Community Technical Support Engineer
    Microsoft Global Partner Services"

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    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.

  • Outlook 2003 and Exchange 2013

    We have just installed Exchange 2013 servers in our organization alongside existing Exchange 2007 servers. No mailboxes have been migrated yet and we are about ready to point our client access namespace to the Exchange 2013 servers and go into the co-existence
    stage.
    We still have some Outlook 2003 clients and I know these need to be updated to 2007 SP3 or 2010 Sp1 or 2013 before those mailboxes are migrated to Exchange 2013.
    However, I am curious as to whether we would hit any problems at all if we pointed our namespace to E2K13 before upgrading the Outlook 2003 clients, as long as none of the Outlook 2003 clients use Outlook Anywhere and the mailboxes those clients
    connect to remained on Exchange 2007 for the time being ?
    Clearly, Outlook 2003 is not 'supported' but the wording in the following link...
    http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
    says " Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013"
    Would the situation I'm thinking of be one of those 'compatible but unsupported' scenarios. i.e I can't think of any reason why the Outlook 2003 clients would have a need to connect to an E2K13 CAS server ...
    I'd be interested to hear other people experiences/opinions on this. Thanks!

    Hi,
    Based on my knowledge, for internal users whose mailboxes exist on Exchange 2007, it is ok to still use Outlook 2003 as clients. Because
    they will still connect to the Exchange 2007 Mailbox server instance hosting the mailbox. If the user is moved to Exchange 2013, please upgrade the Outlook client to higher version. Because Exchange 2013 doesn’t support Outlook 2003 client.
    For Outlook 2003 clients connected to Exchange 2007, they doesn’t support autodiscover service to get some Exchange services such as free/busy information, OAB. Outlook 2003 would connect to Public Folder in Exchange 2007 to retrieve these
    services. For OWA and ActiveSync service, it is not related to Outlook 2003 client, the CAS2013 would redirect the service request or send to CAS2007 for necessary data.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2007 SP3 RU compatibility with Exchange 2013 lattest CU

    Hi Team,
    I have question, I want to migrate my exchange 2007 to 2013.
    right now exchange 2013 already provide CU7. 
    My question is, is exchange 2013 CU7 compatible with Exchange 2007 SP3 lattest RU (SP3 RU15) ?
    is there any limitation of version if i want to upgrade Exchange 2007 to 2013
    Thanks Before

    Hello,
    The first thing I would say, is that the MINIMUM supported update for Exchange 2007 is SP3 RU 10, so you should be ok with RU15 installed with Exchange 2013 Cu7.
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    The second thing I would say, and I am not sure how you're current environment is configured and how you plan on configuring your future environment, but if you are using Public Folders, Exchange 2013 CU7 changes the way public folders are handled during
    coexistence.  I would recommend taking a look at this blog post from The Exchange Team
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx 
    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